Calculated Attributes in Salesforce Maps Territory Planning

Understanding Calculated Attributes

• Calculated attributes can be used at different levels, which is important to understand because the same attribute can produce different results depending on where you calculated it.
  • Area: Unit/Container attributes are rolled up first, then operators are applied.
  • Container: Unit attributes are rolled up first, then operators are applied
  • Unit: Operators are applied at the unit level
• Calculated attributes are stored on the alignment config only.
• Calculated attributes must return numeric values to be referenced in the area legend.
• Text comparison using the IF function is case-sensitive.
• If a formula references an invalid attribute, denoted by the brackets “[]”, then it will be returned as 0.
• Calculated attributes can reference attribute data imported from CSV.
• Calculated attributes are not shared across data sets
• You cannot optimize on container or area calculated attributes
• A cross-unit formula can only be aggregated using addition, which is represented in the completed formula.

Creating Calculated Attributes

1. With an alignment open, click Settings in the top right corner.
2. Select Attributes | Calculated Attributes.
3. Click New next to a level to start building a new calculated attribute
4. Define a Name for the calculated attribute.
5. Use the Attributes and Functions tab to start building your formula—remember that it must return numeric values.
   1. Note: If you are using multiple unit types, you will see a tab for each unit type. Selecting each will update the Attributes tab with the appropriate values.
   2. Note: Cross-unit formulas can only be aggregated using addition, which is represented in the completed formula. 
6. When you are finished editing your formula, click Add to Attribute Formula.
7. Click Save to finalize your calculated attribute. You can edit it later by returning to the same screen.
8. Your calculated attribute can now be used like any other numeric attribute in the application depending on its level
   1. Area/Container attributes cannot be used for optimization
   2. Unit attributes can be used for optimization

See Also: