Optimizing Calculations Using STEPXML

When exporting calculated values in STEPXML files using cross-context mode, STEP will attempt to perform some optimization to avoid repetitive calculations per context. In this scenario, the following limitations exist:

  1. None of the attributes used in the calculation can be dimension dependent.
  2. There must be no iterations in the calculation that involve any kind of references or child products. Only attribute values that are directly on the selected object (or, if a product, an inherited value from a higher level) are allowed.
  3. The calculated attribute cannot rely on the value from another calculated attribute, since the value does not actually exist in the database.

If these criteria are met, then the system will calculate the value once and will export that value for each of the selected contexts. This can result in a reduction of the time to create the exported STEPXML file.

If these criteria are not met, then the calculation will be performed per context, which can increase the time to create the exported STEPXML file.

For more information on the STEPXML format, refer to the STEPXML Format topic in the Data Exchange documentation here.