8.5.2. Problem importing supports between different SuCri versions

In this article you will learn why errors can occur when importing supports between different SuCri versions and how to resolve them. The consistency of the software versions is decisive for a smooth data exchange within your projects.

Prerequisites

• Access to the source and target installations of SuCri.
• The support data to be imported is available in JSON format.

Step-by-step instructions

1. Check versions: Determine which SuCri version was used for the export. An error occurs, for example, when supports were exported with version 24.1.7.5 and are now to be imported in version 25.1.0.2.
2. Re-export: Open the source data with the current SuCri version (e.g. 25.1.0.2).
3. Export supports: Perform the export of the supports again to generate a compatible JSON output format.
4. Perform import: Import the newly created files into your target environment.

Expected result: The import process is completed without an error message and the supports are correctly available.

Important notes

• Format changes: Between versions 24.1.7.5 and 25.1.0.2 there were changes to the JSON output format that prevent backward compatibility.
• Best practice: For export and import within a project, ideally always use the same SuCri version.
• Project coordination: Before a version change, clarify within the team whether existing export data must be migrated or recreated.
• Plant 3D: Standard supports from Plant 3D are generally not affected by this issue.

Troubleshooting

• Error persists despite re-export: Check whether these are standard supports from Plant 3D.
• Technical support: If problems continue to occur, please contact support and provide the affected export data for analysis.