Cancel
Showing results for 
Search instead for 
Did you mean: 

PLMXML Export/Import for custom relation between DesignRevision and Document Item

Solution Partner Experimenter Solution Partner Experimenter
Solution Partner Experimenter

Hello all,

Consider the following relationship between DesignRevision and Document, where a custom relation  BCT4_relation_04 links them.


BCT4_E_Design
|--BCT4_E_DesignRevision <--------BCT4_relation_04--------> BCT4_D_Document
                                                                                                        |--BCT4_D_DocumentRevision
                                                                                                            |--Datasets

We need to export this data from one site and import this at another site. For this, we plan to use PLMXML export/import in combination with respective CAD export/import tools, e.g. Pack and Go. Hence, CAD data (represented by BCT4_E_Design) could be handled using respective CAD export/import tools. The associated non-CAD Document data (represented by BCT4_D_Document) could be exported/imported using PLMXML.

For handling non-CAD Document data related to Design data, we need to Traverse and Process:
1. DesignRevisions (this could be a NX/Solidedge BOM)
2. All Document Items related to the Design Revisions
3. DocumentRevision(s) related to the Document
4. Dataset(s) related to the DocumentRevision

We are able to export the required non-CAD data and files. We can see this information in the exported PLMXML file. However, we are facing issues when importing this back to Teamcenter. The PLMXML does not get traversed past the Document Item during import. It traverses the Design Revisions, traverses and creates the custom relationship, creates the Document Item (with default revision) and stops there. As a result, the Document Revisions (except for a default revision) do not get created during import. As the DocumentRevisions are not traversed, the datasets related to the DocumentRevision(s) also not traversed and hence not created.

How can I make the PLMXML engine to traverse past the Document Item to the Document Revision?

 

Snapshot of current PLMXML import closure rule is attached for reference.

3 REPLIES 3

Re: PLMXML Export/Import for custom relation between DesignRevision and Document Item

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

The OOTB "unconfiguredDataFileExport" closure rule shows you how:unconfiguredDataFileExport.png

 

 

 

Arden Bedell | Teamcenter Wonk | Applied CAx, LLC

Re: PLMXML Export/Import for custom relation between DesignRevision and Document Item

Solution Partner Experimenter Solution Partner Experimenter
Solution Partner Experimenter

Thanks for the reply. However, I reckon there are no issues with data export. I am able to see the required information exported.

 

During import, I need some way to make the PLMXML engine traverse past the Document to the DocumentRevision level. Is there some limitation wherein traversal from Item to Revision level is not possible?

Re: PLMXML Export/Import for custom relation between DesignRevision and Document Item

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
TCXML is a better choice for sharing data between Teamcenter systems as long as the software is at the same version and the data models match. What is your process for importing (Transfer Mode, Filter Rule, Action Rule, Property Set and Transfer Option Set)? Using canned or custom?

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4