When I pass a Choices table into a custom component as an input variable, the is converted from containing values of type "OptionSetValue" to type "Text" value.
This means if I want to create a custom component that wraps around say a radio button input, or checkboxes input - and accept "Choices()" data as an input to drive the choices, when I output the selected "Choices" from the componet, they are returned as text values (or table of text values), rather than as OptionSetValues or table of OptionSetValues.
This in turn means there's some inefficent coding I need to when trying to convert the output value, to convert it back to an OptionSetValue, before it can be patched back to the Choices column.
For an example of the work around required, please see below blog post:
https://www.linkedin.com/pulse/power-apps-canvas-app-demystifying-patching-dataverse-sultan-alsharfi
on:
Get Container Scroll Position
EricRegnier
on:
Power Apps should consider Dataverse Keys
on:
”Edit data in Excel ” is missing from Dataverse fo...