even If i configure Drop down values from Data page , in the UI drop down values will not be populated, can anyone explain why it’s and do I need any configuration.
Thank you,
Eranda,
Was this field originally created as a text property and then later changed to a pick list in Dev Studio?
The Constellation UI is tightly coupled to the underlying data model. If a property is changed directly in the rule form (for example, from text to pick list), and that property was already added to a view as a text input, the rule configuration can become out of sync with the view metadata. As a result, the UI may not render or populate the dropdown correctly—even if the data page itself is configured properly.
In this situation, I recommend going back to the view where the field is used, removing the field, and then re‑adding it. Make sure that when you add it back, it is recognized as a pick list in the App Studio View Designer.
I ran a quick test in my local lab following a similar sequence of steps and encountered the same behavior. The issue was resolved once the field was deleted from the view and re‑added after the data type change.
More generally, I would not recommend modifying a property’s type directly in the rule form. Wherever possible, it’s best to use the low‑code tools—in this case, the Data Model tab in the App Studio Case Designer—to ensure the data model and UI metadata remain aligned.
2 Likes
Thank you for your valuable answer and detailed explanation.
I really appreciate the guidance. I will review the property configuration in my environment, remove the field from the view, and re-add it to ensure it is correctly recognized as a pick list
Thanks again for your support!
As @Marc_Alderman mentioned, if a field was originally created as Text and later changed to a Picklist after being added to a view, the view metadata may no longer match the updated field definition. When this happens, Constellation cannot determine the correct model-driven control to render, so the dropdown appears empty. Removing (render the UI, without the field )and re-adding the field to the view (or recreating the view) forces Constellation to regenerate the correct metadata based on the data model rather than legacy section-driven settings.
If the issue persists, verify whether the Data Page is eligible for use in Constellation. Constellation limits picklists to Data Pages that meet at least one of the following conditions:
The Data Page has API status enabled.
It resides in the top-level application ruleset.
It comes from a built-on Case or Data Type included in the top-level application.
Also ensure that “Allow querying any column (Pega connection only)” is enabled, which makes the Data Page available for picklist configuration. Data Pages created in App Studio typically include this setting.
Possible Fix: Open the Data Page and enable API status and/or Allow querying any column.
Ensure the Data Page’s ruleset is part of the top-level application stack so Constellation can access it.
2 Likes
Hi,
Thank you for the explanation.
In my case, “Allow querying any column ” is enabled in the Data Page. After For a work layer property like Case Status (pyStatusWork), the promoted filter dropdown is populated correctly with values from the grid.
However, TransactionType is a text property with a picklist defined in a Data Type, and although the filter appears as a dropdown, the values are not populated.
I also tried removing and re-adding the field to the view (since it was previously changed from Text to Picklist), but the issue still persists.
Could this behavior be related to the property being defined in a Data Type rather than the case class, or is there any additional configuration required for Constellation to populate dropdown values for such properties?
Thank you.