Skip to main content

#Quick Choice Set Component2 人正在讨论

I am using the Quick Choice component from the Flow Base Pack (the app exchange version) The data source is Picklist Field, I have it set to required and in the Value field, I have Default, as I have a default value set on the record type and picklist field. The default value is "Employer", however, when running the flow the default value is not showing up and even though it's marked as "required" it's still progressing in the flow and then erroring out as "Default" is not an acceptable value. It just started happening to my knowledge, so any ideas on what could be causing the issue? 

 

Here is a screen shot of the settings, notice that it's set to required as well  

 

Quickchoice not displaying

 

Here is what it looks like in the screen flow, notice there is no value in the quickchoice field, it should be set as Employer. 

Quick Choice Default 2.png

 

In debugging I did not put in any value for the field, and it advances, even though there is no value. and then errors out as "Default" is not a valid option. 

 

Any thoughts/suggestions are welcome 

#Quick Choice Set Component #Unofficial SF #Salesforce Admin #Flow

1 个回答
  1. Steven Trumble (Strum Consulting) Forum Ambassador
    8月7日 00:27

    When you type "Default" you are passing the literal string of "Default" to the quickchoice.  

    There is no label associated with "Default" which is why it appears blank in the UI,but then tries to save as "Default". 

     

    Check out the documentation on unofficialsf. Notice how they are passing in variables from the flow 

     

     

    When you type

     

     

0/9000

First, very cool component! However, either I am not understanding or there is a bug. I created two string collection sets—one for labels and one for values—so I can use the Visual Cards. When trying to get the 'value' from what was selected, it is returning the 'label'

Getting 'value' from Quick Choice component returns 'label'

 

Now that I am thinking through it more, I think it's just an issue with the naming. In the setup, when using Two String Collections, it says the second one is for Description, but also says Value, but this is not the value that is returned in the output, the label is returned. 

 

Screen Shot 2022-05-15 at 9.06.06 AM.png

 

Perhaps the naming of these items can be aligned to prevent others from this confusion.

 

#Quick Choice Set Component #Quick Choice FSC #Quick Choice 

1 个回答
  1. Eric Smith (Retired) Forum Ambassador
    2022年5月15日 20:25

    @Ryan Schierholz

    I realize this can be confusing.  I added Visual Cards as an enhancement to an existing component and at the time I felt that the card label would be a better result to return on selection than the card description, which was optional and could also, when used, be a much larger string of text.

0/9000

@Eric Smith I am using the Quick Choice Set Component in a flow and am making it visible with Yes/No Radio button.  It appears that the required language does not go away if I try to go forward without selecting an option, then selecting the no radio button to hide the quick choice question.  I am using version 1.4.

3 条评论
  1. 2020年6月16日 23:56
    Have you tried this on Summer '20? I looked into a similar report but wasn't able to reproduce it on Summer '20
0/9000