attributes not updating right away with nx5

[aluminum2]

I have nx5. It seems like most of the time the attributes do not update right away. I usually have to close the file and reopen or add the attribute again. I was wondering if there was a setting in UG to prevent this or if this is how ug works or if they fixed it at a later version.

 

[jerry1423]

Do you mean that they are not updating in the parts list ?

 

[aluminum2]

they are not updating in the note. I make a change to an attribute and in order for it to update in a regular note, I either have to change text in the note or reopen the file.

 

[JohnRBaker]

Yes, that is a known issue which was addressed in NX 8.0 with the work that was done on enhancing attributes. The best way to 'force' updates based on changes made to attributes prior to NX 8.0 is that while in Modeling, go to...

Tools -> Update -> Update for External Change

...and this will force a complete update of any pending chnages.



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

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

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

 

[aluminum2]

So when you say addressed in nx8, do you mean fixed?

 

[JohnRBaker]

What I mean is that the issue with changes to the value of an Attribute not being recognized by downstream applications, like Drafting, has been fixed so that a change like this is treated like any other 'parametric' edit. That is, when you edit an Expression, it's flagged as having been changed and all other items which reference that Expression are 'notified' and it's then up to the Application code to respond by doing it's thing. Up until NX 8.0, when changing the value of an Attribute, NO notice was 'sent out'. Instead, the code depended on the applications 'asking' the system IF an attribute had changed. If the application didn't ask, nothing was done. When you perform that 'Updare for External Changes' operation, what you're doing it manually telling the system to go and check virtually everything that might be out-of-date. Granted, it's a bit of overkill in this case, but it does work every time.

The reason that saving your file and reopening it again caused the update to take place is because we always check stuff like this as we're saving the file to make sure that nothing is left 'pending'. The problem is that the updated data went to disk but the current session was left unaware of what had happened, but of course when you open the file the next time the fully updated data is now loaded.

To make a long story short, starting in NX 8.0 we treat a change in the value of an Attribute exactly the same as a change in the value of an Expression.

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

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

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