what wrong with the assy

[uwam2ie]

I have attached an assy, where I haven't found the NX5 part settings, how to reset to following behaviour:
When I'm opening the assy (bg2) I select the model4 part in the assy-navigator, hit the crtl+J for object display and change the color or the layer, ok an leave the dialog. Now the bg2 or the model4 part doesn't get the modified in the navigator but the display updates. What setting controls this behaviour?
thx in ad

 

[JohnRBaker]

There was NO attachment.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[uwam2ie]

whats wrong with the assy
mess,
here it is

 

[uwam2ie]

...

 

[JohnRBaker]

OK, I can explain at least half of the behavior that you're seeing.

First, the reason that it does NOT indicate in the Assembly Navigator that the Part file 'model4' has been modified is because the Part file 'model4' has NOT been modified. When you edit the color/layer of the COMPONENT in an Assembly you are ONLY modifying the object inside the Assembly which represents the COMPONENT, which is NOT the same as editing he original master part file. The color assigned will only apply to that local object, it will have NO effect on the master part file.

Now as for why the Assembly itself does not become modified, or at least there is no indication that it has been modified, I don't really know although it would seem logical that it SHOULD have been flagged as modified. I suspect that what you've stumbled onto is a 'gap' in the behavior of NX, which is probably because the software failed to detect what is known as a 'lightweight' edit. These lightweight edits are ones which do not require the system to fully load the component being modified and while it's still results in a change to the Assembly and should have been detected and reported in both the Assembly Navigator and the 'Title' line at the top of the NX window. I'll open a PR and see what sort of feedback I get back.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[uwam2ie]

thank you John,
I knew that the component would no get modified, but the assy should, thought it is an for me unknown part setting.
The trouble is that this files created from template parts is/was used starting with nx5 two years ago. (shit happens)
thx

 

[JohnRBaker]

Upon further investigation, it appears that this behavior is unique to that particular part file. I tested this in NX 5.0 (as well as NX 6.0, NX 7.0 and NX 7.5) by creating totally new part files, using both a template file as well as from scratch, and in both cases, when I edit the color of the Component, the Assembly file is flagged as modified.

If you are seeing this behavior only when using your existing templates, you may need to recreate them from scratch to overcome this.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[uwam2ie]

The template was the seed part of the old nx2 environment.
As we switched from nx2 to nx5 we have refiled the part(s). We where happy to use it in combination with the drafting setting: use setting from template file. All under TCE managed mode conditions with heavy workflow in reuse with cloning. Outside this environment everything works fine. ->
a data disaster.
thx