Migrating Design View Data

This section shows you how to migrate Inventor data from versions 10.6 or 10.6.SP1 to 3DEXPERIENCE R2022x. The design view objects are handled differently in Connector for Inventor 3DEXPERIENCE R2022x from the pre-10.7 releases. Since the 10.7 release, the design view files are added in corresponding assembly objects. Migration must be done from MatrixOne Inventor Integration release 10.6 or 10.6.SP1 to Connector for Inventor 3DEXPERIENCE R2022x integration to maintain data consistency and the interaction with 3DEXPERIENCE R2022x client.

The basic steps in migration are:

  • Finding all objects that are connected to Assembly objects using CAD SubComponent relationship. These objects are design view [major and minor] objects and their derived types.
  • Checking out files from Design View objects using default format and checking files back to the assembly objects in the default format of assembly.
  • Disconnecting the design view objects from their assembly objects.

  1. Open MQL from 3DSpace Server and login as the administrator user [creator].
  2. Run Migration TCL script

    Run the InvIntegMigration-V6R2010.tcl tcl script in the MQL utility using the following command,

    run <Live Collaboration Server Install Location>/ConnectorforInventor/3DEXPERIENCE R2022x/Modules/ENOConnectorforInventor/AppInstall/Programs/InvIntegMigration-V6R2010.tcl;

  3. Specify the following once the script file is run.
    • working folder - Specify the working folder for the integration.
    • MigrationData file details.

    This file contains all the information about the objects that are required for migration.

    This file is generated using following query:

    "mql temp query bus "INV Design View" * * select id 
relationship[CAD SubComponent].from.id dump |;" 
"mql temp query bus "INV Versioned Design View" * * select id 
relationship[CAD SubComponent].from.id dump |;"
::
::
::

    and similarly for all derived types of "INV Design View" and "INV Versioned Design View" that are also taken as user input. The result of the queries is dumped in the MigrationData file.

    The format in which the data is present in the file is,

    <<INV Versioned Design View Type>>|<<INV Versioned Design View

    Name>>|<<INV Versioned Design View Revision>>|<<INV Versioned

    Design View bus id>>|<<Pipe seperated list of bus ids of connected

    assembly objects [INV Assembly/INV Versioned Assembly >>

    <<INV Design View Type>>|<<INV Design View Name>>|<<INV Design View

    Revision>>|<<INV Design View bus id>>|<<Pipe seperated list of bus

    ids of connected assembly objects (INV Assembly or INV Versioned

    Assembly)>>

    The following example shows the content of a MigrationData file,

    INV Design View|JP_PS7_Part1|C|18362.27301.1120.33399

    INV Design View|JP_PS7_Part1|A|18362.27301.8795.60572

    INV Design View|JP_PM_Set2Part|A|18362.27301.10796.516

    INV Design View|JP_PS7_Part1|B|18362.27301.28982.4505

    INV Design View|JP_PM_Part3|A|18362.27301.32502.53861

    INV Versioned Design View|JP_PM_Part3|A.3|18362.27301.37089.2437

    INV Versioned Design

    View|JP_PM_Set2Part|A.0|18362.27301.53543.9744|18362.27301.6152.30027

    INV Versioned Design

    View|JP_PM_Part3|A.5|18362.27301.54289.52911|18362.27301.61947.41412|1

    8362.27301.38234.26626|18362.27301.20693.44412

    INV Versioned Design

    View|JP_PM_Part3|A.1|18362.27301.55642.3794|18362.27301.11132.5072

    INV Versioned Design

    View|JP_PM_Set2Part|A.1|18362.27301.56859.52240|18362.27301.62295.2642

    0

    INV Versioned Design

    View|JP_PM_Part3|A.4|18362.27301.58634.27853|18362.27301.2885.23026

    INV Versioned Design View|JP_PM_Part3|A.2|18362.27301.58806.29949

    INV Versioned Design View|JP_PS7_Part1|A.2|18362.27301.357.53681

    INV Versioned Design View|JP_PS7_Part1|B.0|18362.27301.1003.7983

    INV Versioned Design

    View|JP_PM_Part3|A.0|18362.27301.5608.43589|18362.27301.18721.35835

    INV Versioned Design View|JP_PS7_Part1|A.0|18362.27301.16829.20840

    INV Versioned Design View|JP_PS7_Part1|C.0|18362.27301.22683.44909

    INV Versioned Design View|JP_PS7_Part1|A.1|18362.27301.25149.54832

    INV Versioned Design

    View|JP_PM_Part3|A.6|18362.27301.29389.15077|18362.27301.54715.6223

    Note:

    To generate a new MigrationData file, the user must specify a blank value. Otherwise, an existing migration data file will be used for migration. The user can also specify the MigrationErrors file [ generated in some previous migration iterations] as MigrationData file. For more details on MigrationError file, refer MigrationErrors section for more information

    MigrationError fileThis file is generated by the migration script and has same format as MigrationData file. This contains business ids of files that generated errors in migration. The user reviews the MigrationError file and correct the data in the database for which errors were generated. During next iteration, the user can use this file as the input for MigrationData file. In doing so no extra migration data file will be generated.
    Design view object types and all their derived design view objects typesThis file contains all the designview types corresponding to Matrix. The default types are "INV Design View" and "INV Versioned Design View". If the user uses any derived custom types then they must be added.
    GCO TypeThe migration is done in the context of a GCO. Using the GCO Type, the script aqquires information of the corresponding policy , finalization states of objects, and so on. For example, MCADInteg-GlobalConfig. The GCO Type must be specified.
    GCO NameThe migration is done in the context of a GCO. Using that GCO Name, the script aqquires information of the corresponding policy , finalization states of objects, and so on. For example, INVNewArch. The GCO Name must be specified.
    GCO RevisionThe migration is done in the context of a GCO. Using the GCO revision, the script aqquires information of the corresponding policy , finalization states of objects, and so on. The GCO Revision must be specified.

    Note: Relationship attributes between the assembly and designview objects are lost.