Kenja824
Automotive
- Nov 5, 2014
- 949
This is more of a curiosity question to maybe help me avoid a problem in the future....
Recently I made changes to a Family part and all of its members. Moved it from rev 001 to rev 002. I had to do this in Team Center (in case this makes a difference) and then I exported the new family part to Native and crated the members for us to use in our designs. However, people are having a hard time replacing the old ones in their tools with the new one.
When they open their tools up, this component wont load because the old revision is no longer available in the library. When they try to replace component it says it wont load. The only way they can get it to work is they need to close all parts, open the new component member (not the parent family part), and once the member part they are replacing is open, if they then open their tool, it will open up with the new part already in it.
Is there something I did wrong in the updating the new revision that it cant just be replaced with the new revision? Most of the files I have done this to have not had this problem, so it makes me think I must have missed updating a setting or attribute or something. Anyone else run into this?
Recently I made changes to a Family part and all of its members. Moved it from rev 001 to rev 002. I had to do this in Team Center (in case this makes a difference) and then I exported the new family part to Native and crated the members for us to use in our designs. However, people are having a hard time replacing the old ones in their tools with the new one.
When they open their tools up, this component wont load because the old revision is no longer available in the library. When they try to replace component it says it wont load. The only way they can get it to work is they need to close all parts, open the new component member (not the parent family part), and once the member part they are replacing is open, if they then open their tool, it will open up with the new part already in it.
Is there something I did wrong in the updating the new revision that it cant just be replaced with the new revision? Most of the files I have done this to have not had this problem, so it makes me think I must have missed updating a setting or attribute or something. Anyone else run into this?