The decision to use a calculated attribute, and then the steps to create it to perform as expected, should include a consideration of the following topics:
- Deciding to Use a Calculated Attribute here
- Setting up a Calculated Attribute here
- Using Variables in a Calculated Attribute here
- Optimizing Calculations using STEPXML here
- Limit Performance Penalties for Calculations here
Limitations
The following limitations exist because calculated attribute values are generated on-the-fly:
- Searching for the value of a calculated attribute is not possible since generating all possible calculations would cause substantial performance issues.
- Depending on the calculation formula, the revision history of an object does not necessarily display the calculated attribute value that was in effect at the time of the revision.