Limit to the Number of Incident Attributes

Starting with quarterly update 25A, you won’t be able to add more than 25 result attributes to a transaction model. We’re making this change to permit better performance and scalability.

This limit doesn’t include derived attributes, which are values calculated by a model and included automatically among its results. An example would be averages of a value from grouped records, calculated by a model that uses the Average function in a filter. So a model can include up to 25 attributes you select plus any number of derived attributes.

Your current models and controls won’t be affected; they’ll still generate new result records, and those records will have all the result attributes you’ve specified previously even if there are more than 25. And you’ll still be able to export all model and control definitions, even if they have more than 25 result attributes.

So there’s nothing you need to do to prepare for this change. But after your environments are updated to 25A:

• If you import, edit, or copy a model that has more than 25 result attributes, you’ll have to reduce the number to 25 or fewer.
• You won’t be able to deploy a model as a control until it has 25 or fewer result attributes.
• You won’t be able to edit a control that has more than 25 result attributes. Instead, inactivate it and deploy another that has 25 or fewer.
• If you want to import a control that has more than 25 result attributes, import it as a model, reduce the number to 25 or fewer, then deploy that revised model as a control.

Business Benefit

This feature will not only improve performance but will also will help you ensure your models are designed with an optimal output in mind. 

Steps to Enable

You don't need to do anything to enable this feature.