×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Preventing the Deletion of Child Features

Preventing the Deletion of Child Features

Preventing the Deletion of Child Features

(OP)
Hi,
reading some presentation I've found this option.
I think this it's very useful if unchecked.
Someone use this setting unchecked ?

During the lecture I read this :
"When this check box is cleared and a parent feature is deleted, the Edit during Update dialog will appear for each child and allow you to explicitly accept, delete, blank, or edit (reattach) it.", but this is not true or I wrong something ?

The tooltip doesn't explain about a dialog.

Anyway I would like to promote to my colleague.
If someone didn't like it, can this option be set at the user level ?

Thank you...

Using NX 7.0.1.7 MP3 and TC8.1

RE: Preventing the Deletion of Child Features

I suspect that the presentation is a bit out-of-date.  Did the author indicate which version of NX it was that he was referring to in his presentation?

You see we removed the 'Edit During Update' scheme a few releases back.  What happens now is if the child feature(s) cannot automatically update once its parent has been deleted, it will be placed in a state similar to being suppressed except being tagged as 'out-of-date'.  If you later create some other feature(s) which allows this existing feature to update it will automatically be made active once more and applied to the model.  Or you can edit it (by selecting it from the Part Navigator) and then you will have the opportunity to select new face/edge/curve/whatever reference so that it can once again be made active and usable.

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.
 

RE: Preventing the Deletion of Child Features

(OP)
Thank you John,
what about my last question ?
Setting at the user level in customer default ? Possible ?

Thank you...

Using NX 7.0.1.7 MP3 and TC8.1

RE: Preventing the Deletion of Child Features

- How come your User level settings are Read only ?

 The "normal" fashion is that "Site" settings are read only to everybody except the sysmanager and that he/she locks options away from the user level settings. Then all remaining user level settings are free to change.

So the response to your second question is yes, possible, if the read only is ...

RE: Preventing the Deletion of Child Features

NOT if you don't have READ access to YOUR .dpv files or if your system admin decides to lock Customer Default settings at his level.

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.
 

RE: Preventing the Deletion of Child Features

Sorry, I meant READ/WRITE access to YOUR .dpv file.

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.
 

RE: Preventing the Deletion of Child Features

(OP)
Sorry John,
what I need to say to CAD manager to create a user dpv for only this option ?

Thank you...

Using NX 7.0.1.7 MP3 and TC8.1

RE: Preventing the Deletion of Child Features

If it were me I would demand that your system manager NOT mess with USER options (we didn't call them 'User' for nothing) and to give you full access to you Customer Default file and to ONLY lock those items (if any) at the 'Site' level which are truly the options that should never be changed (if you think about it, this list will almost certainly be very short).  If you people just install the system as it's intended, it will work as you need it to.  It appears to be that it's the messing around by them that's making your life more complicated, not necessarily the software itself.

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.
 

RE: Preventing the Deletion of Child Features

(OP)
Hi John,
but I don't understand your English, it's clear that it's a my problem, but using Google Translate give me a bad translation.

What I can understand it's 'Avoid to manipulate Customer Default' ?

I think it's true, but this unchecked option it's very useful as mentioned in the presentation, but I would like to be an user setting.

Others CAD have this options on deleting (SolidWorks an Pro/E).
If I want delete a feature for different reason, why I need to lose time to avoid child deleting ?
Whit this option I delete and then I re-link what miss, as in assembly mating.

Thank you...

Using NX 7.0.1.7 MP3 and TC8.1

RE: Preventing the Deletion of Child Features

Now I don't know what it is that you're looking for.

Can you or can you not change this setting in Customer Defaults?  If you can, does it give you the behavior that I described or not?  If your complaint is about the fact that we no longer are using the 'Edit During Update' mechanism, then there's not much that we can do since this approach is no longer being used and it will not be resurrected.  The problem was that it halted update and forced the user to immediately try and fix the problem.  The current approach allows the model to update as best that it can but to the very end so that you at least have a valid model.  At that point you can decide what it is that you may wish to try to resolve the problem or perhaps to just ignore it or perhaps even delete the out-of-date features and try something else.

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.
 

RE: Preventing the Deletion of Child Features

(OP)
John,
I can change the customer default, but it's a CAD Manager job that usually ask to some experts users if it can be changed.
Some experts CAD users are users that use NX from V16 and model whit the same feature and method present in UG V16.
My passion is the CAD and I like to discover always the best approach, new feature a new solutions.
For example, all expert CAD user use block, cylinder, pad, pocket, etc...
I didn't like those and I use sketch.
This is only a little example of what is considered the guru in NX in our company.
So I'm not a real decisional, but if the option can be an user setting, then the CAD Manager can accept because I oblige all CAD user to use this setting.

For the rest I like the improvement made in NX on 'Edit During Update' mechanism, but this option permit me to delete bad feature made from bad users, create new and best feature and re-link blends, holes, etc..whit tranquility.

Thank you...

Using NX 7.0.1.7 MP3 and TC8.1

RE: Preventing the Deletion of Child Features

(OP)
Sorry...I wrote wrong...
"....then the CAD Manager can accept because I DIDN'T oblige all CAD user to use this setting."

Thank you...

Using NX 7.0.1.7 MP3 and TC8.1

RE: Preventing the Deletion of Child Features

Quote (JohnRBaker (11 May 11 3:52)):

we removed the 'Edit During Update' scheme a few releases back
In what version was it removed? I'm currently on NX6 and I'm still using it. I prefer to have at least a warning pop up if something goes wrong rather than having to scroll through the potentially long feature list looking for red X's. I have had to fix many files where others either didn't notice or didn't care about the red X's.

RE: Preventing the Deletion of Child Features

This was changed in NX 7.0 (there's an entry in the What's New document titled 'Error during update enhancements' which covers the changes implemented).

As for what your new options are, there is a Modeling Preference/Customer Default which will allow update to either run to completion with the failed feature(s) suppressed and flagged (this it the OOTB default) or to have the update halt and the failed feature set to be the 'Current Feature' thus allowing you to examine, edit, delete, suppress or whatever, similar to before, but not using an special dialogs, simply placing the system in a state where you can choose whatever action you would like to do next.

Also, irrespective of what the Modeling Preference/Customer Default is set to, the listing window will open with an explanation of what happened, but this will not halt the update, it's simply there to provide feedback and as a indication that something did fail to update as expected.

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.
 

RE: Preventing the Deletion of Child Features

Thanks for the info. I'm glad to hear there is still an option to stop the update and make the failed feature 'current'. It is also good that the listing window comes up, but personally, I'd like to see something a bit stronger. I've seen coworkers who have the information window off screen (usually unintentionally due to a laptop docking/dual monitor setup) or who just close it out without regard to why it opened. I think the listing window is generally regarded as a way to convey information you may or may not be interested in rather than warnings that must be read.

RE: Preventing the Deletion of Child Features

Well, since the whole idea was to provide an option where Update was NOT halted, the listing window was a convenient scheme to provide feedback which did not require the user to stop and acknowledge it.

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.
 

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources