adra
Computer
- May 20, 2010
- 3
HI!
Brief description of our needs:
We export models from .prt to .jt. Later, we use .jt in our application. In order to connect single elements of a model with out data base, we use attribute: DNV_UID. Attributes are set in Root assembly in NX, and are unique for all elements (including instances). E.g. Instance 'A' of assembly 'B' will have its unique id, and all its children will have its unique ids.
Problem:
After exporting to JT, our attributes are no longer unique. You can see, that Instance A and Assembly B will have an unique DNV_UID, however all children of A, will have exactly the same DNV_UID as children of B!
Answers I am looking for:
How can I fix the problem?
What are my options here? Please note that there is also a requirement on the model, to be able to alter the model, with preservation of all DNV_UID's that where defined earlier.
Additional info:
We are not using TeamCenter. Just plane NX modeling license.
Thx for any help!
Brief description of our needs:
We export models from .prt to .jt. Later, we use .jt in our application. In order to connect single elements of a model with out data base, we use attribute: DNV_UID. Attributes are set in Root assembly in NX, and are unique for all elements (including instances). E.g. Instance 'A' of assembly 'B' will have its unique id, and all its children will have its unique ids.
Problem:
After exporting to JT, our attributes are no longer unique. You can see, that Instance A and Assembly B will have an unique DNV_UID, however all children of A, will have exactly the same DNV_UID as children of B!
Answers I am looking for:
How can I fix the problem?
What are my options here? Please note that there is also a requirement on the model, to be able to alter the model, with preservation of all DNV_UID's that where defined earlier.
Additional info:
We are not using TeamCenter. Just plane NX modeling license.
Thx for any help!