Skip to main content
P
pdiletti-21-Visitor
1-Visitor
February 1, 2019
Question

Session ID for Assembly Components

  • February 1, 2019
  • 2 replies
  • 3873 views

Hi everybody.

I have a question about the session ID of assembly components. I'm using CREO4.

Let me explain with an example.

I have an assembly with two components which have the session IDs #2 and #4.

I Save a Copy of assembly and two components as well.

In the new assembly the session IDs of new components are different (e.g. #0 and #2)

 

Do you know if it's possible to manage this IDs or is it possible to keep the same ID of the original file ?

 

Many thanks 

Pierluigi

 

 

2 replies

B
BenLoosli23-Emerald III
23-Emerald III
February 1, 2019

Each assembly as it is built will have unique SIDs for its components. They should remain static within the assembly, but as you notes a SaveAs will create new SIDs in the renamed assembly.

 

I do not believe there is a way to manually manipulate these, they are internally generated.

 

T
TomU23-Emerald IV
23-Emerald IV
February 1, 2019

Session IDs are just that, an ID for that specific component for that session.  These are assigned sequentially as objects are loading into memory and released as objects are removed from memory.  Creo is smart enough to automatically keep the values (relationships) correct as objects are loading into session.  You can get into trouble if you try to build mapkeys that refer to session IDs or you try to do a 'Save As' with models suppressed that contain relations that use session IDs.

P
pdiletti-21-VisitorAuthor
1-Visitor
February 1, 2019

Yes, exactly.

I'm trying to automate some operations and I found this limit. 

I hoped that using "Save As" had possibility to keep the ID ... But unfortunately it doesn't.

Thanks anyway .

 

Pierluigi 

T
TomU23-Emerald IV
23-Emerald IV
February 1, 2019

Just realize that they don't *need* to stay the same, they simply have to maintain the same relative relationships.  As long as the 'Save As' happens with everything related in session, you should have no problems.

Terms & ConditionsAccessibility statement