export .step file / create copy - automatic rename shares/groups

[Diddo]

Good morning.

I am new to this community but I would need someone more experienced than me about this topic because I have worked with creo element direct/modelling for less than a year.
I realized that the result of an export in step format of the model 3d of our machines is different from the original model for the codes contained within, not of all but only of those created in turn by a copy of an existing model. this operation with identical result is obtained by creating a multi-level copy.
in practice the program automatically renames the component with the name of origin with which it was created.
I noticed that it renames it with the code found in the column "path name" as if it was related to the machine structure.
This is in my opinion chilling and now that we start working with external suppliers with which to share files and bom creates a lot of problems.
from the assistance of those who give us the software tell me to be a proper behavior of the software and can not give me alternative solutions if not paid. I hope they're wrong because I find it hallucinating.
Can anyone help me? Where are we wrong?
Thank you.
d

 

[reb_bl]

This software, do whatever you want, believe me! Then they want to monetize everything is another story.
via lisp and development kit you can do everything.
Unfortunately now I have nothing to help you, if you have a lisp that launches this command, maybe post it we see.

 

[cacciatorino]

Good morning.

I am new to this community but I would need someone more experienced than me about this topic because I have worked with creo element direct/modelling for less than a year.
I realized that the result of an export in step format of the model 3d of our machines is different from the original model for the codes contained within, not of all but only of those created in turn by a copy of an existing model. this operation with identical result is obtained by creating a multi-level copy.
in practice the program automatically renames the component with the name of origin with which it was created.
I noticed that it renames it with the code found in the column "path name" as if it was related to the machine structure.
This is in my opinion chilling and now that we start working with external suppliers with which to share files and bom creates a lot of problems.
from the assistance of those who give us the software tell me to be a proper behavior of the software and can not give me alternative solutions if not paid. I hope they're wrong because I find it hallucinating.
Can anyone help me? Where are we wrong?
Thank you.
d

try to assign a model name to each part. that unlike the name instance is unique to all shared parts, and perhaps exporting to step in this way recognizes the sharing.

 

[Kaji]

I am sorry, but you have not understood the procedure or the problem; if I have a group that within it has subgroups with in turn shared details and I take it by creating a step, when the amount again in modeling, the structure is recognized with the shares etc.

what unfortunately does not do is assign the same id to a same step imported in two separate moments; every time you import it you are assigned an id which is therefore different from the previous import.

as to the model name it is possible to assign the same model name to two parts or unshared assemblies, even within the same group and if you save as 3d data the software assigns to a particular 3d its model name, to other details assigns model_1 name

 

[Diddo]

I am sorry, but you have not understood the procedure or the problem; if I have a group that within it has subgroups with in turn shared details and I take it by creating a step, when the amount again in modeling, the structure is recognized with the shares etc.

what unfortunately does not do is assign the same id to a same step imported in two separate moments; every time you import it you are assigned an id which is therefore different from the previous import.

as to the model name it is possible to assign the same model name to two parts or unshared assemblies, even within the same group and if you save as 3d data the software assigns to a particular 3d its model name, to other details assigns model_1 name

the problem is that it does not recognize the structure or the shares if I carry it out and remount.
my problem is that if I create a file step the program renames details with a code that does not match the model tree from which I left. does not do so of tt the groups indistinctly but only of those that have been copied from an already existing group and randomly assigns him just the first code with which he was created.
However, doing a test and loading only the incriminated groups and exporting them into step, this does not happen.
seems something related to the model tree and more precisely to the column "path name".
in the attached image, find the original structure below within our pdm, above the generated step file, the first group is fine, the second has been renamed.
the result is that if I send the step to a supplier for any reason it does not find correspondence between the bom and the machine structure.
d

 

[cacciatorino]

try to assign a model name to each part. that unlike the name instance is unique to all shared parts, and perhaps exporting to step in this way recognizes the sharing.

I tried with this method but it doesn't work, what is exported is always the name instance and not the model name.

 

[reb_bl]

the problem is that it does not recognize the structure or the shares if I carry it out and remount.
my problem is that if I create a file step the program renames details with a code that does not match the model tree from which I left. does not do so of tt the groups indistinctly but only of those that have been copied from an already existing group and randomly assigns him just the first code with which he was created.
However, doing a test and loading only the incriminated groups and exporting them into step, this does not happen.
seems something related to the model tree and more precisely to the column "path name".
in the attached image, find the original structure below within our pdm, above the generated step file, the first group is fine, the second has been renamed.
the result is that if I send the step to a supplier for any reason it does not find correspondence between the bom and the machine structure.
d

the problem is complex: exporting in step, you lose the info, except the shares, or recognize if a part is shared within the step.
as he said @cacciatorino name instance and name part is a different thing, you can export the parts with the model name, so they are unique, then, when you carry them back, peace of the senses and everything shoots flasha as on mib.
you can't even have the same name on the same level, so if you cover it or share it, it adds a [ .1 ] to do it different, if same name starts is inserted in different groups, here is that it keeps it because it sees it "univoc".

exporting the father (or even children) by model name is the only solution I see feasible

 

[cacciatorino]

exporting the father (or even children) by model name is the only solution I see feasible

I tried to assign to the part a model name but when re amount in solid edge I find the name instance. how do you export the step so that the model name is transmitted?

 

[reb_bl]

I tried to assign to the part a model name but when re amount in solid edge I find the name instance. how do you export the step so that the model name is transmitted?

when you ask for the file name to be saved, you compose it with the model name.
You do. It matters. However as the name starts, but at least you have a connection with the original.