Inactive list values allowed on affected items on change orders
Hi,
It seems that if you have a part that had an attribute with list values, and then you inactivate a list value that was already used, the system still allows it even on release of a new change order.
I’ve looked thru smart rules and preferences and don’t see anything to get the system to flag you if there is an inactive list value on the affected item you’re releasing. Am I missing something?
Is there any way to do it besides a PX checking list values of every attribute to make sure no inactive list values are there?
I’ve suggested exporting the parts and re-importing with correct list value. Any other options? Is there a way to Import a ‘blank’ value for prelim parts so that the attribute must be filled in?
Thank you,
Laura
Disabling the list value just means it cannot be chosen from the list. All existing data is left intact. If you delete the value in the list that will clear out that value where ever it is used.
In every agile user profile’s preferences tab, there is an option under display preferences header, whether you want to show Inactive list values for a particular user. You can try once by setting it to No and then try to release the items with inactive list values to see how the system behaves, it should show the attribute’s value as blank.
Hi Steve,
Yes, but to delete the values you have to change them to something else anyhow since the system won’t let you delete values that are being used. So we may as well just change them to the proper value. I also don’t want to delete them since it will also remove history. I think for us the best answer is to do an import to correct the values all at once, which is what I’ve told them to do.
Thanks,
Laura
Hi Swagoto,
Thank you for letting me know about the preference. I never noticed it before.
It seems like all it controls is when you search, if it is flipped to No then you don’t see Inactive list values in the search.
I processed a part through with an inactive product line and the system didn’t stop me even with this preference set to No.
Too bad, that would have been great if it could fix this issue.
Thank you,
Laura