cascading attribute can be used as replacement for attribute having multiple conditional constraint, currently neither is supported by export / import from spreadsheet, which causes huge impact on customer daily work.
This is our TS case Import from Spreadsheet throws error "The value for attribute xxx must be one of the following "
The same situation happens to attribute using multiple conditional constraints with enumeration list. We would ask to enable export / import from spreadsheet also for this kind of attribute.
Wanted to share CS334077 where this issue is incapsulated. There is a "sort of" workaround detected that you may be interested in, if you're trying to accomplish this for one time activities, rather than for an ongoing usage.
PTC Windchill version 11.2 M020 CPS 03 has a bug when using OOTB spreadsheet tool for loading parts. PTC has provided a slight workaround in an article, the workaround is not helpful and cannot be implemented for us, we need this prioritized and a hotfix as part of the current version of PTC Windchill.
The Business is unable to perform data loads and relying on IT to perform the data load by using the Windchill Bulk Migrator that is leading to delays and additional costs and efforts in the Project Implementation.
I understand this idea to be able do import and export cascading rules independently from the import from spread sheet functions for WTParts.
Please correct if I am wrong. We currently have to define a large number ob cascading attribute rules as part of a 3rd party data base to Windchill migration.
And according to PTC Article CS305741 there is no way to do the initial load of the rules via a load file! Not even via API.
Creating a large rule set of cascading attributes via the UI is very error-prone.
We are currently working on supporting Cascading attributes on Import from Spreadsheet.
Hello @JeffZemsky ,
thank you so much for considering this improvement for Implementation in a future release.
Currently we have the situation that we are no longer able to use the very powerful and helpful "Import from Spreadsheet" functionality because we are required to use "Cascading Attributes".
Users do see this current behavior as a big blocking point and we are asked regularly to deliver any kind of improvement as soon as possible.
Do you have any information for us when the planned solution can be implemented in Windchill?
Thank you and best regards
Yes, thanks! I have created few weeks ago for 8 WTPart subtypes multiple cascading attributes with longer selection lists. I created the rule, exported the type, find/replaced the text (not that easy to find...) and imported the type again. Any help is definitely welcome!
Windchill 12.1 provided fixes for import from Spreadsheet to support Cascading attributes. This work was backported to the following Winchill releases:
Hello Jeff, great news. Under which point is this documented in the help?
Thanks for the great news Jeff!
@mschulze -as this was considered a bug there is no change to the documentation - it is expected that part attributes are imported based upon the values provided whether tied to Cascading attributes or other attribute constraints.
Ok, so CS305741 is still valid. And there is no method for an initial load. 😐
@mschulze this is different idea for loading Cascading lists. This idea is using Import from Spreadsheet where the Part as attribute values that have Cascading constraints. I would recommend creating a separate idea for loading / maintenance of Cascading attributes please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.