You can't avoid it, but there are a few utilities floating around to help rename such expressions. I believe John has posted a grip file somewhere in this forum...
Thanks for Your response, I need it for my journal from the other topic
My CAM setup has some feature data, what I want to update at import..
So GRIP is not for me..
The so-called 'hashing' of expressions names is done so as to avoid any conflicts which would occur if expressions names were left unchanged during a part merge or a 'Cut & Paste' operation between part files.
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA Siemens PLM: UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
The mechanism used is NOT adaptive, that is it does NOT attempt to determine IF there is an actual need to do the 'hashing' but rather it simply performs the task based on the fact that there COULD be a problem. To do otherwise would involve significant logic constructs and would also be potentially compute intensive if a large and complicated model was being imported into another large and complicated model. Granted, for the simply case of anything being imported into an empty file the time would be minimal, but the code would HAVE to be written to account for the worst case scenario. So to avoid all of that extra coding and execution time and the idea that the more complex the models involved the more likely that problems would occur, it was decided a long time ago to simply go with an approach which by its very simplicity would ALWAYS work in EVERY possible situation with the FASTEST execution time.
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA Siemens PLM: UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
