Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Admin |
A calculated attribute is a category you define: grouping values into something your business actually uses.
Create one
- Open your cloned dataset.
- Add a calculated attribute and name it.
- Write the rule that assigns each ticket to a category.
- Include a catch-all for everything else.
- Save and check the distribution.
A worked example
Twenty products in a drop-down, and the business talks about four families. A calculated attribute maps each product to its family, and every report can then group by family.
Without it, every report repeats the same twenty-way grouping and somebody adds up the columns by hand.
Always include an else
Whatever the rule does not cover has to land somewhere named, such as "Other". Without it those tickets get an empty value and quietly disappear from grouped reports.
Then watch the size of Other
If it grows, something new is not covered, usually a product added after you wrote the rule. That is the maintenance signal for this kind of calculation.
Name the categories as the business says them
The point is that reports speak the language of the people reading them. If the categories need translating in the meeting, they are the wrong categories.
Values matter, not labels
Write the rule against the stored values of a field rather than its display labels where they differ, because labels can be edited without anybody thinking about reporting.
Test on known tickets
Take five tickets whose category you know and check where they land. A rule with an ordering mistake assigns plausibly and wrongly.
Comments
0 comments
Article is closed for comments.