Skip to main content
Solved

Selector with SubstituteKey gets confused when identical substitute keys exist

  • Dec 5, 2025 5:23 PM UTC
  • 3 replies
  • 85 views
  • Translate All

darylbowman
Captain II
Forum|alt.badge.img+17

I recently ran into an issue with a PXSelector. I defined the selector to use a unique key as the actual key, but to display a different value. The problem is the selector became confused when there were multiple identical display values.

I can kinda understand why this would be a problem, but it seems to me that the selector should be smart enough to differentiate between the options based on the underlying key value. Is this a core limitation of a selector or simply in mind when it was designed?

​@Dmitrii Naumov 

Best answer by darylbowman

I did eventually discover I could change the SelectorMode to PXSelectorMode.DisplayModeValue which solved the issue.

View original

3 replies

KrunalDoshi
Pro I
Forum|alt.badge.img+9

Thanks ​@darylbowman for the prompt reply. Glad you found the solution.

Translate

darylbowman
Captain II
Forum|alt.badge.img+17
  • Author
  • Answer
  • Feb 20, 2026 1:11 PM UTC

I did eventually discover I could change the SelectorMode to PXSelectorMode.DisplayModeValue which solved the issue.

Translate

KrunalDoshi
Pro I
Forum|alt.badge.img+9
  • Pro I
  • Feb 20, 2026 12:44 PM UTC

Hi ​@darylbowman,

Have you found the solution yet? Can you post your DAC and sample data which you are trying into your PXSelector, so I can review and provide you with the best possible solution?

Translate