Cache issue in cascading dropdowns sourced from datapages

General
1

Scenario:
I have a set of cascading dropdowns where multiple dependent dropdown fields are sourced based on the value selected in the first (parent) dropdown.

Issue:
When I change the value in the first dropdown, the dependent dropdowns are expected to refresh and show only the relevant values. However, I am noticing that the dependent dropdowns still contain some stale/extra options that were populated based on the previous selection of the first dropdown.

Observed Behavior:

  • Initial selection works correctly.

  • After changing the parent dropdown value:

    • Some old values (from previous selection) are still visible.

  • It seems like caching or data page reuse is causing stale data to persist.

Expected Behavior:
Dependent dropdowns should display only the values relevant to the current parent selection, with no leftover options from previous selections.

2

Just to confirm is it Traditional UI or Constellation?

3

It is in Constellation.

4

Could you share your configuration? and Version?

Looking to see if

  1. you have followed this approach and put that in the data model ( Quickly building dynamic form field behavior with Constellation and App Studio: Cascading dropdowns | Pega ) OR
  2. you override the parameters and put in the View definition OR
  3. you’ve put this in the data page load, either populating via a Data Transform or using Response data transform (would like to know if the data page is queryable)
5

@AshwinBharatha I was curious, as I hadn’t done this since Infinity '24, so implemented it just now in '25.1.2 (community edition). Some details showing this working and the configuration - if you can share your approach, maybe we can guide you to what might be missing.

Working Run Time

Design Time Configuration

6

The issue has been resolved.

Root Cause:

I was using a field as the identifier which contained duplicate values across records. This was causing inconsistent behavior in the cascading dropdowns.

Fix:

I updated the configuration to use a unique field as the identifier for all records.

Result:

After making this change, the dropdown values are now refreshing correctly without any stale or duplicate entries.

Appreciate your effort and support in resolving this issue!

7

Thanks for sharing root cause analysis.