Passing Items to a Radio Inside a Component

(0) Share

Report

Posted on by Salem

187

I have a radio inside a component, I want to pass:

1- choices of a dataverse option set "YesNoChoices" to the radio items

2- radio default value

I tried adding a table input custom property to the component (leave it with no values by default) and set radio items to it.

In the app , when I use choices function in that custom property, I always get errors.

Is that possible? Am I doing this wrong?

Categories:

Building Power Apps

All responses (16)

Answers (1)

Sort by

CNT 10,921 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

@Salem Firstly, Items is a reserved word in PowerApps. So, using that for a custom property is not advisable as it can cause a bit of confusion.
Secondly, the syntax to refer to Yes/No choices in a dataverse choice column is,
Choices('ChoiceColumName (TableName)')

Please remember to give a 👍 and accept the solution as it will help others in the future.
Salem 187 on at

Like
a
(0)

Report
Copy link

Link copied!

@CNT Thanks for tips, changed the property name to "InpProperty" and changed the choices formula to table and column names. Now I get this:

Edit: changed the choice column to match the original post.
CNT 10,921 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Salem Well you are not following the syntax that I gave. Keep the single quotes and brackets in exactly the same position. Furthermore, your choice column name has brackets which is not advisable as this will cause further confusion.
Salem 187 on at

Like
a
(0)

Report
Copy link

Link copied!
@CNT
Thanks for the quick reply.

To clarify "YesNoChoices" that I am using is a custom "choices/option set" as the defaul YesNo must have a default value that does not work for my use case which allows for blanks.

Back to the example, I hope I used the exact sytax this time with another table and column names that have no special charachters but using the same "YesNoOptions".
I am trying to follow your syntax: Choices('ChoiceColumName (TableName)')
Here is what I have
Choices('Completed(Shifts)')
Table is "Shifts"
Column is "Completed"

Powerapps does not like it:

When I use the regular "Table.column" I get the previous error
CNT 10,921 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Salem The syntax I gave was for the Yes/No Choice column. If you have your own Choices, The formula will be Choices(Completed).
I noticed that in this Choices, you have only one choice YesNoChoices. You need to have one choice as Yes and the other as No.
Salem 187 on at

Like
a
(0)

Report
Copy link

Link copied!

@CNT I happy we are on the same page now.
Choices(Completed) gives this:

Choices(Shifts.Completed) gives this:

Do I need to fill anything in that input property in the component mode, I have it empty now:

For the choices, I do have one choice for yes and another for no:
CNT 10,921 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Salem Hey! u'r a bit mixed up!
You don't need 2 Choices (1 yes/no and another custom choices). You need just one of them. I would use the yes/no. To make sure this is working, test it with a dropdown. Set its Items property to Choices('YesNoChoices (TableName)'). Replace TableName with the name of the table. Don't change anything else.
Salem 187 on at

Like
a
(0)

Report
Copy link

Link copied!
@CNT tried the formula
Choices('YesNoChoices (TableName)')
in a dropdown "Items" property with no luck, all combinations of this formula do not work.

Here is what works on a dropdown:
(the column "Comleted" below is a choice column that uses "YesNoChoices")

Referencing "YesNoChoices" directly also works

The default"Yes/No" also works, the column "LateStart" is a choice column that uses the default"Yes/No"
CNT 10,921 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@Salem Could you send me a screen shot of all the custom columns in the shifts table.
Salem 187 on at

Like
a
(0)

Report
Copy link

Link copied!

Here we go.
Would you try this on your side, try passing choices to radio or dropdown inside a component and let me know if it works?