Quick Choice selectedLabel null when using visual cards

[llsdtd]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Steps to reproduce the behavior:

1. Create Screen Flow
2. Create/populate three string collections for Id, value and icon
3. Create Screen with Quick Choice element, use collections from Add PlaySound component #2, visual cards and InstantNavigation Mode
4. Create screen to display selectedLabel

Expected behaviour

selectedLabel should return the value in the respective string collection

Actual behaviour

selectedLabel is null

This is very similar to #837 but only happens when using Visual Cards. Changing the display to Radio Button Group returns the expected results

[ericrsmith35]

I'm not able to reproduce this issue. Please share how you have the component configured.

[llsdtd]

Sure. Here's the setup for Visual Cards:

And the variables we're assigning the outputs to:

Then there's a screen where we're just displaying the variables:

And here's the output when debugging:

For comparison, here's the setup for radio button (the manual outputs are the same):

And the output when debugging (it looks like the values are transposed here too):

[ericrsmith35]

That is the expected behavior. For Visual Cards, the selected Label is returned in the Value attribute and nothing is returned in the Label attribute.

[llsdtd]

ah, ok. I suppose that means that there's no plan to allow for both values to be available? Even though that might be a dumb question, I think there's value in being able to utilize both - for this specifically, we'd want to use the common name ("Splitter") as the main display but be able to use the record ID to perform actions against it downstream.

The way it is, we have to have the record ID as the main display while the common name is secondary and it looks, well, like this:

[ericrsmith35]

Good point. I'll see if I can add that to a future release. Eric Smith

…

On Mon, Oct 18, 2021 at 1:52 PM llsdtd ***@***.***> wrote: ah, ok. I suppose that means that there's no plan to allow for both values to be available? Even though that might be a dumb question, I think there's value in being able to utilize both - for this specifically, we'd want to use the common name ("Splitter") as the main display but be able to use the record ID to perform actions against it downstream. The way it is, we have to have the record ID as the main display while the common name is secondary and it looks, well, like this: [image: card] <https://user-images.githubusercontent.com/47280674/137782105-477c014d-47b8-4184-842b-542add3ffb10.png> — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#940 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4UHX76GGN2LS2FKK2HOR3UHRNHDANCNFSM5F3LH73Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.