Skip to main content
Question

22.116: Bug in PXMultiSelector when using unbound fields?

  • June 26, 2023
  • 6 replies
  • 103 views

priekenberg40
Varsity I
Forum|alt.badge.img

I am working on a customization where i need a Multi-Selector on an unbound field.
But i am getting an error on adding the second option:
 

 

Here is the definition of the unbound field:

 

And here the code for the PXCustomSelectorAttibute:

 

ASPX:


Are there any know issues or am i doing something wrong?

6 replies

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

Curious about the ‘-1’ for the string length. Probably not what’s causing the issue, but I searched the source code for that and couldn’t find it anywhere. Best practice would probably be to put in an actual length.


priekenberg40
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • June 26, 2023

@darylbowman don’t remember where i’ve seen that first. Changing it to a defined value doesn’t change anything indeed.


priekenberg40
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • June 26, 2023

Changing ValidateValue to false as stated in https://asiablog.acumatica.com/2018/01/multi-select-selector.html let me assign more than one option.

But the SubstitutionKey doesn’t get substituted any more with more than one option.


priekenberg40
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • June 26, 2023

Can anybody confirm that SubstituteKey works on PXCustomSelectorAttribute with PXMultiSelector? Or on PXSelectorAttrribute?


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • July 13, 2023

Hi @priekenberg40 were you able to find a solution? Thank you!


priekenberg40
Varsity I
Forum|alt.badge.img
  • Author
  • Varsity I
  • July 31, 2023

I did not manage to get this working. I used the SubstitutionKey as Key and mapped/changed the values on saving and loading.
The PXSelectorAttribute needs an update from the devs to get working with SubstituteKey and PXMultiSelector.