About Conversion Modes

Conversion As Result is the default mode which enables the conversion of parts and shapes to a lower version using start-up parts.

When you run DownwardCompatibility batch you can use a startup CATPart. Then the CATPart created by the DownwardCompatibility batch is initialized with the content of startup CATPart.

By default, the value displayed in this box is the last value used because the value you enter is stored in preferences files. If this box is left empty, then no part will be used as a start-up.

If the selected CATPart is not valid (whatever its origin: text, variable, preferences, etc.), then the selection is ignored and a pop-up message is displayed to give the reason of the conversion failure:

• The document does not exist.
• The document is not a CATPart.
• The document is a CATPart but has no Read access.
• The document is a CATPart but its version is higher than the targeted version. For instance, you cannot use a CATIAV5R20 CATPart document as a start-up part when converting data down to CATIAV5R19.
• The document is a CATPart but it results from a previous DownwardCompatibility conversion and therefore, it cannot be used as a start-up part.

An additional tag is inserted in the XML file generated when the batch is run:

<CATDWC_3DRep_StartUp> </CATDWC_3DRep_StartUp>

This tag supports the ${VARIABLE} and ${VALUE} mechanism, which means that when editing the XML file, the value can be replaced by a ${MYREP_PATH} variable (where "MYREP_PATH" is the environment variable exported before running the application). However, if the selected CATPart is not valid, no tag is inserted in the XML file. Regarding ${VARIABLE}, note that:

• The following characters are forbidden in a string (or the value of a ${VARIABLE}): * : ? < > | , \\ / ". These characters are ignored when defined in a string.
• A list of "." characters is automatically replaced by a simple ".". A name cannot contain the string "..".

When the conversion starts, 3DEXPERIENCE attributes are always transferred to the V5 CATPart, whether a start-up part has been defined or not:

• When the XML file contains the <CATDWC_3DRep_StartUp> </CATDWC_3DRep_StartUp> tag valuated to a valid CATPart document, original UUIDs (Universal Unique IDentifiers) of the start-up CATPart are kept. This means that 3DEXPERIENCE Representation UUIDs are not transferred to the global report and to the reports generated for each object.
• When the XML file does not contain the <CATDWC_3DRep_StartUp> </CATDWC_3DRep_StartUp> tag, or contains a non-valuated tag, no start-up mechanism is applied. CATPart documents are created as new and 3DEXPERIENCE Representation UUIDs are transferred when possible to the newly created CATPart. The UUID report can be tracked by exporting the CATDWC_TraceConversion environment variable.

When converting parts as result, you can also select the Convert Publications on Intermediate Geometry box if you need to convert publications linked to an intermediate geometry.

Convert Part as Specifications mode converts all 3D Shapes with their specifications whenever possible.

This mode lets you edit the part in 3DEXPERIENCE but also modify the converted part in V5.

Important: This option is available either when converting to a file or to a database. V5 data are supported starting from V5-6R2012, not from previous levels. Each 3DEXPERIENCE release is mapped with only one V5 targeted release. For more information, see Release Compatibility. This option is available only for: Generative Shape Design, Sketcher, Part Design, Functional Shape Design and partially Knowledgeware.

When the batch is run, all selected options are checked to ensure consistency. If incompatible actions are detected, the batch ends. The following message is displayed in the report Object xyz contains feature which cannot be converted AsSpec.

A check is also performed to make sure that the 3D Shape can be converted "As Specifications". If at least one feature is not supported, then the 3D Shape is not converted. The batch ends and the following error message is displayed in the report Object xyz contains feature which cannot be converted AsSpec.

For each converted 3D Shape, an information will be displayed in the report to clearly identify which conversion option has been applied.

For Generative Shape Design and Part applications, all applicative features will be copied to the resulting V5 document without any modification. This means that all generated CATParts and CATShapes will contain a copy of the original 3DEXPERIENCE specifications instead of "import features". Moreover, there is no impact on:

• 3DPart support
• Generated CATProducts, CATDrawings, V4 models and cgr. Their contents is exactly the same.
• V5 generated structure: the list of V5 files is exactly the same and the assembly structure is kept as is.
• Multirepresentation management, attributes conversion or Part Number definition
• File names.

If you leave the Use Mapping Tables option selected (default) and export a 3D Shape or a 3DPart without its representation they will not be exported to V5. The following warning is generated in the report:

Selected 3DShape cannot be exported standalone.

If you clear the Use Mapping Tables option, no information is kept regarding the conversion option which means that no check can be performed between two exports of the same 3DEXPERIENCE objects. Therefore, the 3D Shape is always exported and the V5 file is overwritten, if available.

An additional tag is inserted in the XML file generated when the batch is run:

<CATDWC_3DRep_AsSpec> </CATDWC_3DRep_AsSpec>

Possible values for the tag are: Yes, Y, No, N. A null or invalid value means that objects will be processed using the default value (i.e. no specification conversion).

This tag supports the ${VARIABLE} mechanism, which means that when editing the XML file, the value can be replaced by a ${MYOPTION_VALUE} variable (where "MYOPTION_VALUE" is the environment variable exported before running the application).