8.3.3. Dynamic properties are reset

Learn how you can minimize data loss for dynamic component properties in Plant 3D. This documentation provides you with important tips for avoiding configuration problems caused by a SpecUpdate.

Prerequisites

• Use of AutoCAD Plant 3D within a project.
• Use of dynamic component properties (e.g. generated by SuCri).

Step-by-step guide

To prevent or reverse the loss of data, please follow these instructions:

1. Check before the SpecUpdate: Before you carry out a SpecUpdate, check whether individual dynamic properties that are not defined in the pipe class are used in the current project.
   Result: You avoid an unintentional overwriting of data.
2. Store properties in the pipe class: Transfer recurring dynamic properties into the corresponding pipe class. To do this, open the pipe class editor and add the fields.
   Result: The values remain consistent even after an update.
3. Update again via SuCri: If an update has already been carried out and properties have been lost, run the SuCri tools again to restore the values automatically.
   Result: The dynamic fields are recalculated based on the current project rules.

Important notes

• Awareness: Inform your project team that a SpecUpdate compares the components with the standard definitions of the pipe class and overwrites manual changes.
• Process control: Establish clear project standards for who may carry out a SpecUpdate and when.
• Data integrity: Dynamically generated values are always lost when Plant 3D detects a discrepancy between the component in the model and the source pipe class.

Troubleshooting

Problem: After an update, components suddenly show standard values again instead of the adjusted properties.

• Solution 1: Run the function Data update via your additional tools (e.g. SuCri) again.
• Solution 2: Check whether the SpecUpdate was strictly necessary for the affected components, and undo the change via a backup copy if needed.