Constellation UI – Why does a text property appear as a dropdown in promoted filters?

General
1

Hi Team,

I am working with a Data Table in Constellation UI and using the Promoted Filter option.

My configuration is as follows:

  • The Data Table is sourced from a Data Page.

  • The Data Page source is a Report Definition.

  • In the Report Definition, I have selected the following columns:

    • pyStatusWork (Case Status)

    • TransactionType – a text property with a picklist.

In the grid, I enabled promoted filters for both properties.

Observation:

  • For pyStatusWork, the filter appears as a multi-select dropdown, which I believe is because the dropdown values are derived from the distinct values present in the grid results.

  • However, for TransactionType, even though it is a text property with a picklist, it also appears as a dropdown.

My questions:

  1. How does the TransactionType text property appear as a multi-select dropdown in the promoted filter?
    Is Constellation automatically generating the dropdown based on the distinct values returned by the Report Definition results?

  2. I want to add another filter condition for TransactionType. Based on my understanding, this property should also appear as a dropdown with available values. However, the values are not getting populated with the different TransactionType values returned by the report.

    image
    image932×319 25.3 KB
    image
    image471×354 8.97 KB

Could someone please explain how Constellation determines the filter type and how the dropdown values are populated for text properties in promoted filters?

Thank you.

2

HI @Eranda_Weerasingha

Few more questions from my end

  1. What is the version of Pega Infinity are you using ?
  2. You mentioned that the TransactionType property has a source of Data page. Does this Data page has any Constant or Field Reference as parameters?

I have verified your issue in 24.2, 25.1 with below configurations,

  1. TransactionType as Picklist with Local source - Working
  2. TransactionType as Picklist with Data page without any parameters - Working
  3. TransactionType as Picklist with Data page with Constant parameters - Working
  4. TransactionType as Picklist with Data page with Another field reference as a parameter - Working

So, I am wondering what different would be your configuration. The only reason i can think of is that the Property definition might be corrupted or metadata is not generated properly, if the UI Control was modified from pxTextInput to pxDropdown.

Expect to hear more from you. May be as part of testing create a brand new field with the same configuration and see how it behaves.

Regards

JC

2 Likes
4

Hi,

Thanks for checking this on your end.

We are currently using Pega Infinity version 25.1.1.

Regarding the TransactionType property configuration:

  • The source is a Data Page.

  • The Data Page does not have any parameters (no constant values or field references).

Also, initially the UI control for this property was pxTextInput, and later it was modified to pxDropdown to support the picklist behavior.

Based on your suggestion, I will try creating a new property with the same configuration and test if the behavior persists, to rule out any potential property metadata or rule corruption.

Thanks.