cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

DATA SHARING & INHERITANCE NO DEPENDENCY OPTION IS DANGEROUS

DATA SHARING & INHERITANCE NO DEPENDENCY OPTION IS DANGEROUS

It is possible to break DEFINITIVELY the link of a data sharing feature with the source model (copy geom, inheritance...).

In CREO3 this possibility has been added in the feature option #NO Dependency


The users in CREO2 now often switch off the button #Dependent to create a non dependent feature, in CREO3 corresponding to #Manual update: in Creo3 they will naturaly choose #NO Dependency instead of #Manual update...and they will say OK at the warning window !

If the option #NO Dependency is selected the user can't change it after the fearture creation: there is no #Edit Definition now !

Please change this option name to avoid user mistakes: "ULTIMATE BREAK DOWN" for example (« RUPTURE DEFINITIVE » in french)

and if possible, change the icon in the model tree for this "dead" data sharing feature...

HERITAGE_INDEPENDANT_CREO3.jpg

4 Comments
Visitor

This issue is more UI problem. If you have broken the dependencies in CREO 2 completely inside the Global Reference Viewer, CREO 3 interpretes this  as "No Dependency". And you can't go back to dependent which was possible in CREO2. This behavior of CREO 3, do not allow an update from Creo 2 to Creo 3, if you have maintained the models like this in Creo2. Braking dependencies is a common methode to avoid regeneration problems with legacy data in Creo 2!

Visitor

Hi Fabrice,

there are a new hidden config to go back from No Dependency to Manual Upate with Creo3 M080.

You will get the Creo2 behaviour with disallow_restoring_broken_deps no

There are an article available. https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS187098&source=Case%20Viewer

Amethyst

Hi Bernd,

Thanks a lot for your comment !

You're perfectly righ, my last information about this parameter (17.07.2015) was that this option was (?)  not supported by PTC.

PTC hotline answer:

"The reason we decided to remove unbreak option is that while dependency was broken user could manipulate models in such way, that un-breaking dependency will corrupt models"

I will open a new call to be sure this option is now supported !

Best regards.

Community Manager
Status changed to: Acknowledged