Importing 3D XML Files

You can import 3D XML files using an interactive command, or by drag operation.

Notes:
  • While executing concurrent operations, either import or export of 3D XML files containing the same content, one operation can fail. In that case, an error message relative to a conflict of naming, identifier, or revision appears. In such cases, launch the operation again.
  • 3D XML exchange of a PartSupply data is not supported.
  • On the cloud only: Starting from R2021x FD04, importing 3D XML files containing more than 47 000 objects fails on the cloud. To import your content, you can split the 3D XML file into several smaller ones. For example, you can export subtrees of a structure, and then root nodes in separate 3D XML files.
Required access roles: Author, Leader.

This task shows you how to:

Before you begin: Export an object to a 3D XML file with the with authoring format. You can specify the identification string from Me > Preferences > Content Access > Identification.

Import 3D XML Files Using The Interactive Command

  1. From the Top Bar, click Add and select Import.
  2. From the Format list, select 3DXML with authoring (*.3dxml).

    Note: This command is touch compliant in Windows 8 environment.

  3. From the Source list, select one of the following options:
    • File on disk: Allows you to import a 3D XML file from the selected drive.

      This is the default option.

    • Exchange Space: Allows you to retrieve and import a 3D XML file from the exchange space available in Program Central.
    • Collaborative Space: Allows you to retrieve and import a 3D XML file from the project space available in Team Central.
  4. In the Location field, enter the path of the file from where you want to import the 3D XML file. You can also click , browse, and select the required file.

    If you browse and select the file, the required path is automatically generated and appears in the Location field.

    Note: If the Doc Locator Name is activated, the Browse section appears when you click . You can select the required file.

  5. Select the Import all files from the selected location option to import all 3D XML files.

    This option is only available for the import batch utility.

  6. In the Options area, select one of the following options in the General tab:

    Import Option Description
    As Reference

    Allows you to import an object into your database with the same name and internal identifiers as the originating site.

    If the 3D XML file was exported without delegation, the object is not locally editable, as the site ownership remains with the originating site. However, it is possible to insert an instance of another reference under this object, as it does not modify the object itself but creates a parent-child connection between the two objects. For more information, see Reference Library: PLM Components: Basic PLM Objects.

    If the 3D XML file was exported with delegation, the object is locally editable.

    You can receive automatic updates to keep the object up-to-date. In the updates, you can import only the changes since the last updates. Therefore, importing a 3D XML file with the option selected against the originating database has no effect.

    As Reference defines the final customized type of an object with the first minor revision encountered as 3D XML with authoring (*.3dxml) format.

    Only the Leader role allows you to import an object as reference. You cannot import an object as reference using the Author role.

    Notes:
    • When you import objects for the first time:
      • The information associated with the ownership (Project, Owner, and Organization) and the lifecycle is reset according to the local installation of the current user, in the connected environment.
      • The lifecycle stated is set to first level.
      • 3DEXPERIENCE content with CAD master remains unsynchronized after import.
      You can use a business logic to adapt this behavior.
    • When you import a library and its content, you need to import it in two steps. For more information, see Export of Libraries, Classes, and Classified Items to 3D XML.

    Reidentification:

    A PLM Briefcase contains all the PLM data of a 3DXML with Authoring file.

    If two different sites are using the same rules to identify an object, the different objects created on these sites have the same identification logic. If you exchange content using the PLM Briefcase, there could be a conflict on some objects if an identifier is already used on the target site.

    The reidentification option allows you to reidentify objects during Import As Reference to identify the objects to be imported with the local site identification rules. In this way, you can follow local counters and local naming logic.

    The name association between the emitter repository and the receiver repository is performed to ease the communication. The information is stored in a dedicated extension and is accessible in the Properties dialog box of the reidentified object.

    As New

    Allows you to create a new object as a copy of the original object. The receiving site becomes the owner of the object, applying new internal identifiers, business rules, and lifecycles from the receiving site. You do not receive automatic updates to the new object. By default, As New is selected.

    You can use customized settings to name the new objects. If you want to manually name each object, you can set the option at Me > Preferences > Content Access > Identification > Creation Preferences. For more information, see Installation and Administration: Native Apps: User Preferences: Content Access: Identification.

    Notes:
    • For all Revisions and Minor Revisions of an object, Import As New creates a new object.
    • You cannot import 3D XML files containing configuration information, libraries and classified content, or 3DEXPERIENCE content with CAD master using the As New option.
    • You can import the 3D XML for Review files as new.
    • You can use the Leader or the Author role.

    Duplication string:

    Duplication string is available only if the As New option is selected. This string is taken into account by the business logics while creating the PLM components. When you run the Import command, the field gets automatically filled in with:

    • The value set in the identification string settings at Me > Preferences > Content Access > Identification > Creation Preferences.
    • If the value is empty, the latest string that you entered in the Import dialog box is retrieved from the Import Preferences file.
    • If the file does not exist, or if you do not set the Preferences , the default value is - ImportedAsNew.

    You can manually modify the default value displayed in the Import dialog box. The value displayed in the Import dialog box is considered during the Import operation.

    If you voluntarily erase the value and leave the duplication string field blank, the message 'Import done without Duplication String' appears.

  7. Optional: To preview the geometry of the saved object, click 3D Viewer, if the 3D XML file has saved the geometry.  

    Note: You need the 3D Viewer to view the geometry.

  8. Optional: To view the manifest details and the list of attributes saved when the 3D XML file is exported, click Simulate.

    You can view, for example, the Title, Name, Date of Creation and Modification, Revision, Maturity, and Exchange Status)

    By default, the date and its value are displayed in the upper half of the Simulation dialog box. The receiver can view this ID card before importing the file.

    By default, the values of From, Title and Copyright attributes are generated from the customized CATNls file as filled in by the user. If there is a corrupted CATNls file or if the value of an attribute is empty, the value of that attribute is substituted with People and Organization values.

    Note: The Simulation dialog box is available only if with authoring format is used to export the objects to 3D XML.

  9. Optional: To return to the Import dialog box, click Close.
  10. Click OK.

    You can explore the content of the imported 3D XML file in the Product Finder app.

    Notes: While importing 3D XML files,
    • If you want to use Propagation to all children behavior, the product structure must be in the Expand All mode in the Explore window.
    • If multiple roots are the combination of simulation and product, or product and material, simulation and product are selected respectively as a Preferences. The remaining root is filtered out in this case.
    • When you import a 3D XML file under a folder, the imported content is attached in the expanded folder. You cannot explore them in a new work area.
    • You can save one or more root items in the database, and open in a Universal Finder window. This window supports opening and displaying multiple roots.
    • A warning message appears if the importing file is in the downward compatibility mode. While importing in the downward compatibility mode, you can accept or refuse the extracted content.
    • The content extracted is downward compatible. You can import it to the following levels:
      • 2013x FP1724
      • 2016x FD14(FP17817) and later
      • 2017x FD09(FP1819) and later
      • 2018x FD03(FP1822) and later
      • 2019x GA and later release levels

    • During the import, you can use the BriefcaseList.xml file generated during the export to generate the Preview dialog box. There are 2 cases:

      Case Description
      BriefcaseList.xml file generated with the new mode The preview panel needs to find the correct attribute name from the key and retrieves the corresponding NLS.
      BriefcaseList.xml file generated with the old mapping The preview panel needs to retrieve the corresponding attribute names without mapping to display the corresponding NLS.

    Important: When you execute the As New or As Reference options, you cannot receive notifications, even if Type Subscriptions is applied.

Import 3D XML Files Using Drag

  1. For Import As Reference, select and drag the 3D XML file from the Windows Explorer (from the local disk).
    The pointer changes to .
  2. Select the Product Finder work area, a search results list, or an empty work area, and drop the 3D XML file.

    If you drop the 3D XML with authoring file in any authoring work area, a message appears indicating that the file [path of the dropped file] is not valid for Import by drag operation.

    Notes:
    • There is no defined target for dropping the 3D XML with authoring file.
    • By default, Import As Reference is performed for importing the 3D XML file. Import As New is performed if you hold the Ctrl key for dropping the 3D XML file for import.
    • You can import multiple 3D XML files. If one of the 3D XML files fails to import, an error message appears, and the other files continue to be imported.
    • You cannot import 3D XML exported from an Academia configuration into another configuration.
    • You cannot preview and review the content contained in the 3D XML with authoring file before dropping and after importing it.