We would appreciate guidance on the recommended pattern to stop changes to a delegated data type from breaking previously created cases.
When a delegated persona updates, deletes, or deactivates a value, existing cases that already captured that value no longer resolve it (the picklist reads from the data page). We’ve tried simply deactivating the value instead of deleting it, but that didn’t resolve it for existing cases either. (Pega 25.1.3 version)
@Chaitanya_G have you tried playing with the difference between the data model definition and view definition?
View
Data model
My first though would be it still need to be a valid record, you just need to stop people from selecting these “inactive” values in future?
Thanks, Marc, for quick response. We have validated with view approach too but search-and-select won’t work in our use case, it has to be a dropdown. To clarify: this is reference data (e.g. Root Cause, Product Type around 5-6 fields) that changes monthly - values get retired over time. On the case it’s a picklist (dropdown) sourced from the data object
Since the picklist reads live from the data object, deleting or deactivating a value is breaking previously created cases (case which are open and trying to update the same property by other persona in case workflow)
The example was more to show a data reference in action, not specifically the search and select. Personally, I am not a fan of Picklists (as the Field Type), nothing is ever a picklist, it eventually always turns into a Data Reference as its selecting more than just a name. In your example, you are selecting reference data, that likely has active, display value, ID, and other meta data - so now its Data Reference.
Data references support drop downs too AND they can source from different lists
I just tested, my alternative list is only 3 options (left above) and my main list is 5 options.
I am getting no errors when my partial view sources the full list and my form sources the 3 options.
Video with run time and design time example
Even better yet, if i go back to the form, when only 3 options should be, but in the past i selected one of the now invalid 5, it appears in the list and no errors on submit.
I believe this is your desired outcome?
