Showing results for 
Search instead for 
Do you mean 

PLMXML Export Import BOMViewRevision status

[ Edited ]

We are about to move/migrate some of our data from TC10 to TC11 (new installation). The plan is to use PLMXML for this and we have created custom TransferMode with custom closure rules, this seems to work fine except that upon import (after) the bvr does not get release status.


In the closure rule we have defined the following clause:



Everything else which has a status in the old system get the same status after imported but not the bvr.

I guess this has something to with that the bvr aren't "migrated", it is created when importing structures.


Am I doing something wrong here or do I thinking in the wrong direction?

Is there another way to get status on the bvr after import, like a post action which "releases" the bvr?


Thanks in advance



Re: PLMXML Export Import BOMViewRevision status

For small amounts of data, PLMXML will work. For large amounts of data PLMXML is too slow and you should investigate low-level TCXML. There are some shortcomings in both tools. You can release the BVR's by pasting them into a folder (infodba Home\ReleaseMe) and running release_man against the folder.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: PLMXML Export Import BOMViewRevision status

Hello , 


I think the problem is because you are looking for a propriety in a class . 

Try this 2 methods : 1 .change from propriety to attribute and keep the class for primary and secondary. 

2.change the secondary object from class to type and keep the propriety.


Thank you .