Cascading - Multiselect dropdown values not removing after save for later constellation
How to replicate issue:
- Create a case with a multiselect dropdown - data coming from a DataPage accepting a filter value from another field (cascading Multiselect).
- The user selects any value in the Multiselect. It can be one or more items from the list.
- Click Save for later.
- The user again opens the assignment and updates the value of another dropdown that will update the source of the Multiselect.
- User selects any value in the Multiselect.
Issue: The old values of the Multiselect will come back and gets appended in the Multiselect.
As per analyzing the tracer once the data has been persisted, the persisted data keeps on displaying on the UI. Though we remove it whenever a value changes (e.g another dropdown triggers a refresh of the Form), the persisted data from the server once again is shown in the UI.
HCA Healthcare
US
@JillMC This happens because Save for later stores the old selected values on the case, and when you reopen and change the parent filter, the UI reloads options but still binds to the saved list, so the old items come back. Fix it like this: on change of the parent field, first run a data transform that clears the multiselect property (Property-Remove or set it to empty), then Post value and Refresh the view so the data page reloads with the new filter. Make sure the source data page is parameterized and set to reload per interaction (or reload if older than 0) so you don’t reuse a cached list. Add a server-side guard: after submit (or in post-processing), intersect the selected values with the current data page results and drop anything that no longer exists. On open of the assignment, run a pre-load data transform that clears the multiselect if the parent value changed since last save. Avoid client “remember last selection” behaviors; always replace the value rather than append. If it still reappears after these steps, capture tracer and raise a support ticket, as it may be a control-state bug in your patch level.
Cognizant
PH
Thank you for your response. We have followed the same steps provided, pre and post data transform, change events and submit we are refreshing the multiselect selection. But every time the view triggers a refresh the same value that was saved/posted is returning to the multiselect, unless and until a user manually click the [x] or [remove] from the selection from multiselect that selection is removing.
I thought of Post value also, but unlike theme cosmos, in constellation we don't have a way to add a post value event in the control it-self.
Can you elaborate on how would the post value can be achieved in constellation without submit and save for later?
Regards, Jill Cariaga
HCA Healthcare
US
@JillMC In Constellation there is no Post value on the control, so I trigger a server trip to get the same effect. On change of the parent dropdown I first run a data transform that clears the multiselect property using Property-Remove or by setting it to empty. Right after that I call Refresh view so the child data page reloads with the new filter. That sequence forces the client state to post to the server before the refresh, which is effectively Post value. I set the child data page to reload per interaction or reload if older than 0 to avoid cached items. I add a small pre-load data transform that compares the current parent value to a stored last parent value and clears the multiselect if they differ. On submit I also intersect the selected values with the current options from the data page and drop anything stale. With these in place the old selections stop reappearing without needing the user to click remove. Thanks
Updated: 2 Dec 2025 8:16 EST
Cognizant
PH
I've followed the steps provided. There are 2 scenarios with this approach that will still display the previous value. This all happens when Save for later is triggered and selected values for the child Multiselect is persisted to the database.
1. For this step you provided:
"I add a small pre-load data transform that compares the current parent value to a stored last parent value and clears the multiselect if they differ. "
Scenario: Whenever the parent dropdown is updated back to the previous value (then the parent dropdown old value and new value is the same), then the old selected values of the child multiselect dropdown will display again.
2. When a user removes all the selected values from the multiselect then the old values of the multiselect are added back to the control. There is no way to clear the multiselect control back to empty.
As per the tracer step 3 of pzApplyPageInstructions activity is skipped hence UpdatedFieldsData will not contain the page instruction for the multiselect property. Without the instruction from the UpdatedFieldsData the deleted value is added back to the multiselect control.
An SR has been raised for this: INC-C52593
Thank you.