Using .VPMNav Files with CoexistenceBatch

This task explains how to use the CoexistenceBatch batch

.VPMNav files must contain the following information for each object to be transferred:

  • Object DOMAIN
  • Object NAME
  • Object V_ID/V_instance_ID or Object OID
  • Object V_Version (for Part Version object)

They must also contain the expand level information. If the expand level is not mentioned or if the value provided is wrong, it will be 0 by default. This expand level will be applied to all objects from the file.

Here are two samples of a .VPMNav input file with a suitable format:





You should consider the following particular cases:

  • If the input file contains II or AR objects with only information on the V_instance_ID, as there is no notion of a version with these objects, we might retrieve all AR and II objects with the same V_instance_ID and send them to the 3DEXPERIENCE side. So if you have any doubts about the number of objects with the same V_instance_ID, it is better to use the object's OID in the input file.

  • If the input file contains only II or AR objects without any parent or child reference, as the complete graph process will be called up, the related parent and child reference will also be created on the 3DEXPERIENCE side.

  • If the input file contains attributes on the document file object, it will not be taken into account. The document file object will be retrieved only using the object’s OID.

Important: It is your responsibility to provide the CoexistenceBatch batch with a .VPMNav file that is correctly formatted.