Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations IDS on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Part is not a version of the component part

Status
Not open for further replies.

27607

Aerospace
Jan 5, 2010
2
i have been getting this error message whenever i tried to load the assembly, even after turning on the "Allow replacement", when i did the root cause for the error part number, i found 1st revision of the component doesn't have the NX dataset. NX datasets are added after the 1st revision or later version of the revision for the component. But not only for this case, i saw the error message even for the component which has NX datasets from the 1st revision. Can you guys let me know what is the root cause for this error? I still have lot of error messages while loading
 
Replies continue below

Recommended for you

I am guessing that you are using Teamcenter.
Are these components created by you (or someone using your TC) or imported from another system?

Normally you get this message when someone has copied a file and then you try to open it from an existing assembly. The copy may have the same name, so versioning rules would look for the file, but the internal file ID is off because of the copy.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
 
It seems to me we get this same error in Native, when trying to load assemblies with different revision levels of components.

When this happens, we can usually close all parts, then open the new revision of the component first, and then open the assembly. Usually the assembly will automatically load that component in it then.
 
Loading the assembly and having it find the components requires that the components be created from a save-as operation so the internal ID marking of the file matches. If you create a new component from scratch (or rename or save-as from another) then the internal ID will be different even if the external name and revision might be right for versioning rules.
Loading a mismatched internal ID component first, then the assembly will work as the system will overlook the internal IDs since the component name is correct in memory.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
 
Teamcenter will store the last (by default)3 saves of your NX part. Each time that you save, the oldest will be removed. These datasets are the versions (not to be confused with revisions) of your NX part. In your case, you have loaded a newer version dataset than the one which was originally created in your assembly.

This happens, for instance, when you change a part out of context of your assembly and then save it (it gets a higher version). When you leave this newer part loaded, and then load your assembly, NX sees that the assembly should look at an older (previous save) version of your dataset.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX12 / TC11
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor