Multi Select Dropdown Issue
Comments
-
[font=Roboto, Arial, Helvetica, sans-serif]When configuring a Multi Select Drop Down control (in release 6.5.0) there are a few options to consider... [A] Constant Pick List vs Flow-Based Pick List and [B] String items in the pick list vs Compound items (e.g. flow structure or Account entity) The cross-product offers four different configurations. In one out of four configurations, we have problems. The problematic configuration is: Flow-Based Pick List with Compound List Items[/font]
[font=Roboto, Arial, Helvetica, sans-serif]------------------[/font]
[font=Roboto, Arial, Helvetica, sans-serif]The problems we have with this arrangement are: We are unable to load prior selections into the form control when the form loads The output list from this control will never include more than 1 item. In the attached demonstration project, we use a debug run of CLL Multi-Drop-Down Flow and then inspect the results within the debugger to see the second problem. Am I missing a configuration bit? Or, is this a bug?[/font]0 -
[font=Roboto, Arial, Helvetica, sans-serif]After some testing, I have identified that the reason the selected items are not populating in the multi-select dropdown in the form is that the second forms values for the dropdown list were immediately being overwritten by the source flow for the component. I have put together an example of best practice for a dynamic, searchable, multi-select dropdown list on a form. Using typed text as an input to a flow-sourced multi-select dropdown will cause the flow to run again whenever a user resumes typing, which results in the selected items being removed as the components data is reset.[/font]
0 -
It looks like the Allow external Values to be selected is broken on this. I can only select the populated options on a multi-select dropdown list. Is this a bug? Or is there another way to do this?
0