Question

22.116: Bug in PXMultiSelector when using unbound fields?

  • 26 June 2023
  • 6 replies
  • 80 views

Userlevel 2
Badge

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

Badge +11

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.

Userlevel 2
Badge

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

Userlevel 2
Badge

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.

Userlevel 2
Badge

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

Userlevel 7
Badge

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

Userlevel 2
Badge

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.

Reply


About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved