Answered

Dropdown values from entity showing enum names, not labels

(0) Share

Report

Posted on by Maximilian

Hey guys.

I'm working with Dynamics 365 entity and I am trying to display possible options that can be chosen in a dropdown. An issue I ran into which is more about user-friendly side - it is displaying enum technical names from dev side, not the labels. Dropdown is being used to change types and patch it back to entity.

Here is an example of how the dropdown options look:

Steel
WroughtIron
BrushedCopper
BrushedSteel
AlkalineMetal

And here is how I'd like it to look (it looks like this in D365 dashboard since it is displaying labels):

Steel
Wrought iron
Brushed copper
Brushed steel
Alkaline metal

Here is the expression I am using to display the dropdown options to choose from:

DataSourceInfo(D365Entity, DataSourceInfo.AllowedValues, "Metals")

Is there a possibility to display the labels instead?

Categories:

Building Power Apps

All responses (3)

Answers (1)

Sort by

Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

adding in @EvanChakiMSFT to assist with this question
Verified answer

Maximilian 20 on at

Like
a
(0)

Report
Copy link

Link copied!
Hey @Anonymous, thanks for looking into this.

An update: I figured out a workaround. I created two dropdowns, one dummy one and one using the entity enums.

In the dummy dropdown I stored intended labels for the enums and in the other were stored the enum names. What I did was make a switch expression that makes corresponding entity dropdown option get selected whenever dummy one option is chosen. Then I simply made only the dummy dropdown with the labels visible.

Example: "Wrought Iron" in dummy dropdown selected -> "WroughtIron" triggered to be selected in the real dropdown.
Then I was able to patch values back to entity from the real dropdown with no problem, since it still returned back enum value.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

@Maximilian That's awesome, great work! What lead you to the workaround? @Anonymous