Issue with Single-Select Data Reference Displayed as Cards/Dropdown in Constellation

Hello Everyone,

I am facing an unusual issue in Constellation (Infinity v25.1.3) and wanted to check if anyone else has encountered something similar.

Background

We have a data type that acts as a centralized repository for various application values used across dropdowns, radio buttons, and other selection controls. The data type contains fields such as:

  • Category
  • Key
  • Value
  • Supporting Text

All records are stored in the Pega database.

This design originated from a traditional application and has been carried forward into Constellation after migration.

The primary keys for this data type are:

  • Category
  • Key

To support read operations on data type, we have configured a single-record lookup data page using the above primary keys as well.

Use Case

We have a Delivery Type field that should allow users to select one of the following options:

Display Value Supporting Text Key
Standard 4-10 business days STD
Fast 2-5 business days FST
Next Day 1 business day ND

The requirement is to display these options as cards, where:

  • The display value appears at the top
  • The supporting text appears underneath
  • The user can select only one option

Below is a mock up of how the setup should like (of course the radio buttons on the right side though),

Implementation

To achieve this, we created a single-select data reference property and sourced it from a list data page, passing the category Delivery Type.

The cards are rendered correctly and all three options are displayed as expected.

Issue Observed

When a user selects any one of the cards, all cards become selected simultaneously.

Initially, this seemed like a configuration issue, but after verifying the setup multiple times, no errors or misconfigurations were found.

To isolate the problem, I tested the same data reference property using different presentation types.

Results

Not Working

  1. Cards

    • Selecting one option selects all options.
  2. Dropdown

    • The list loads correctly, but no option gets selected.

Working Correctly

  1. Autocomplete

    • Selection works as expected.
  2. Table

    • Selection works as expected.
  3. Simple Table

    • Selection works as expected.
  4. Search and Select

    • Not explicitly tested, but I expect it to work since it is table-based.

For the working display types (Autocomplete, Table, Simple Table), after saving the case, the clipboard correctly contains the page corresponding to the selected record.

Conclusion

Based on the testing:

  • The data type configuration appears to be correct.
  • The data pages are resolving properly.
  • The data reference property is storing the selected record correctly.
  • The issue seems to be specific to the Cards and Dropdown presentation types in Constellation.

At this point, I am hesitant to conclude that this is a product defect, but the behaviour appears inconsistent given that other display types work correctly with the same configuration.

Has anyone faced a similar issue with:

  • Single-select data references
  • Data pages backed by data types with composite keys
  • Cards or Dropdown presentation types in Constellation

Any insights, workarounds, or confirmation would be greatly appreciated.

Thanks in advance!

Regards

JC

Strange one. I’ve done cards and dropdowns in '25 with no problem. The one thing in your setup that’s not so common is the use of composite keys. I wonder if this is related to your problem. Can you test with a different data page using records with pyGUID as key or a single key? I would also suggest creating an INC since this sounds like it should be supported behavior, but it’s not working right.

@JayachandraSiddipeta

I’ve faced a similar issue in 25 version. Selecting the single card, all cards are selected though the configurations are correct as you suggested. I recreated the views and data model to move forward since the issue happened on my lab instance. I agree with @len01 to create the INC ticket.

Yes, with single pyGUID it works fine. The difference is with the composite keys. I will raise an INC ticket

Regards

JC