I just reviewed a model with 2 nearly identical merge/inheritance features. I discovered that one of these models was not updated to the new model which would have been a terrible costly mistake had I not noticed the small difference prior to my model release.
My problem is this: When inserting the merge/inheritance feature it assigns a completely random number to what it inserts. I can not identify a problem in my model tree, but I really should be able too.
This is how the models come in.
My question is whether there is a setting that would retain the model name of that which is inserted? Below is the number I would like in the tree.
I can always rename this after import, but even here a mistake could be made.
Please let me know if I can retain the model name on import. If not I will submit this request as an idea. There is no reason this shouldn't be possible. In our former CAD system this was no problem. I was a few clicks away from costing our company dearly. This can be avoided.
I don't think there is a setting to get the filename.
I would vote for a product idea to add that.
Steven: I will wait a little just to make sure that there isn't a magic config setting, but I will update this thread when I do submit this idea.
After making the shocking discovery my boss asked me the question "what could you do to make sure this type of mistake doesn't happen?" Retention of the imported name would go a great way towards resolving this issue.
Using the reference viewer you can access the name of the parent object driving the inheritance feature. In theory you should be able to use Toolkit or J-link to write a program which can read the parent object name and assign that name to the inheritance feature. Investigating model check functionality to see if that could support reading and assigning the names may prove fruitful.
Yes, by digging into the import itself you can see what you are bringing in. That in itself isn't a timely double check but it does reveal the inserted model.
In lieu of waiting for PTC to allow inserted models to retain their name perhaps if there is a way to program in this function it would be worth looking into.
If you are using windchill, you can make use of annotation to display the version of the reference part used in the last regeneration. With a glance, you can tell if your part is outdated. Does this work for you?
BHOoi: Sorry, I thought I replied but I did not.
Our company doesn't use Windchill so unfortunately that won't work for us.
you can use relation/feature
on merged part:
(merge_base_part is a local parameter)
note: create parameter "merge" before writing the relation.
it will take the file name.