LightningFlowComponents icon indicating copy to clipboard operation
LightningFlowComponents copied to clipboard

*DualListBox3* - Doesn't advance to next Flow element

Open ianhunter2018 opened this issue 3 years ago • 9 comments

Steps to reproduce

Steps to reproduce the behavior:

  1. Build a Screen Flow that uses DualListBox3 and uses Two Strings configuration
  2. After the screen with the DualListBox3, put another screen with a DisplayText that says "Made it to screen"
  3. Set up Collections to catch all the outputs (if you don't do this you get a different error)
  4. Run the Flow, get to that Screen and hit Next
  5. You will see the same screen again, the one with the DualListBox3, instead of the next screen with the identifying note

Expected behaviour

Should advance to "Made it to screen" screen

Actual behaviour

Goes back to DualListBox3 screen without any error message

Screenshots

N/A

Debug Logs

N/A

ianhunter2018 avatar Jun 08 '22 13:06 ianhunter2018

I pulled out the manual assignments of the output and as expected, I get the error I had last time:

The Lightning Component c:fsc_dualListBox3 generated invalid output for field selectedOptionsFieldDescriptorList. Contact your administrator with these details: Flow encountered an error when processing and converting between data types. Please check the flow and ensure all data types are matched correctly.

If no items are selected, it works as expected.

ianhunter2018 avatar Jun 09 '22 13:06 ianhunter2018

@ericrsmith35 any ideas?

adwhitesf avatar Jun 09 '22 13:06 adwhitesf

I've seen this type of issue before that has been caused by browser caching issues. Try clearing the cache and/or running in a different browser.

On Thu, Jun 9, 2022 at 9:40 AM adwhitesf @.***> wrote:

@ericrsmith35 https://github.com/ericrsmith35 any ideas?

— Reply to this email directly, view it on GitHub https://github.com/alexed1/LightningFlowComponents/issues/1128#issuecomment-1151134948, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4UHX5NIB5SCWVFEVELY7DVOHX5NANCNFSM5YGUM6LA . You are receiving this because you were mentioned.Message ID: @.***>

ericrsmith35 avatar Jun 09 '22 18:06 ericrsmith35

No luck. I still get the "The Lightning Component c:fsc_dualListBox3 generated invalid output for field selectedOptionsFieldDescriptorList. Contact your administrator with these details: Flow encountered an error when processing and converting between data types. Please check the flow and ensure all data types are matched correctly." if there are any values selected,

ianhunter2018 avatar Jun 09 '22 20:06 ianhunter2018

Additional note: I created a test flow with just an assignment element and a screen element, where the assignment element sets up three collections of strings (id, label, selected) and the screen element ONLY has a DualListBox. If there are any selected items when I click next, I get the error. Can no one duplicate this?

ianhunter2018 avatar Jun 16 '22 16:06 ianhunter2018

This is still failing miserably -- you cannot use DualListBox3 with Strings at all in any browser, it's completely dead.

ianhunter2018 avatar Jun 29 '22 15:06 ianhunter2018

I've got someone taking a look at this shortly...stand by

alexed1 avatar Jul 21 '22 13:07 alexed1

I just encountered this error on the most recent version (running FlowActionsBasePack Version 3.15 and FlowScreenComponentsBasePack Version 3.3.2 on a Winter '24 sandbox using API level 60), and I found a workaround to the issue:

It seems that the dual list box component is not using the correct output value when it's configured to "two string collections". It's trying to use either the "selectedOptionsCSV" or "selectedOptionsFieldDescriptorList" output variable, and store it into the text collection variable specified in the "Select List Values" field. When this happens, Salesforce sees a data type mismatch and throws an error.

To get around the issue, specify the output text collection variable as normal (so that the selections can be read back in if you navigate back to this screen later), and also enable the "Manually assign variables" checkbox under "Advanced". In the advanced section, specify your 'selected values' text collection variable again in the "selectedOptionsStringList" output variable field. Leave the other two output variables blank. Doing this will force the dual list box component to output the selected values as a text collection, and Salesforce will be able to store it into your text collection variable.

MHzBurglar avatar Feb 20 '24 00:02 MHzBurglar