First Part:
The idea would be to allow a Condition using the "Contains" or "Equals" filter. As multiple values can be chosen in a multi-select field, the "Contains" or "Equals" would allow for choosing specific criteria.
If "Equals" is chosen, then a window would appear with the list of values in the option set. One or more values could be chosen.
Second Part:
The idea would be to allow a Condition using the "Contains Data" or "Does Not Contain Data". This would allow for checking if values exist.
Comments
Just posting to show this is still very relevant and needs to be addressed.P.S.Can we also get these available to use in Business Process Flows as well as a step option? Find it odd we cant even use the field type in all places.
Category: Unified Experience: Search, navigation and performance
Why, oh why, hasn't this been resolved yet! What's the point with multi-select fields if you cannot do anything with them?
Category: Unified Experience: Search, navigation and performance
One alternative that you can do for this is by using a multi-select lookup field if it's not an issue for you to create another table as container of your values. I tried this and this worked with business rules.
Category: Unified Experience: Search, navigation and performance
I was really surprised not to find the multi-choice column in the field list of my new business rule. Shocked to see no feedback from Microsoft for 5 years now!
Category: Unified Experience: Search, navigation and performance
Hello Redmond? Anybody there?Please add this functionality :)xoxo
Category: Unified Experience: Search, navigation and performance
How many more votes are needed? How many years do we need to wait?There are an additional 115 votes in Power Apps Ideas (probably more across a number of ideas): https://ideas.powerapps.com/d365community/idea/d2582a12-7df7-4672-bd57-6944b44f5663
Category: Unified Experience: Search, navigation and performance
Please make it available soon.
Category: Unified Experience: Search, navigation and performance
Come on get this sorted - with agile development and move to low code this and similar issues should be resolved. I should not have to write code to do something so basic as hide a form field/column of any type anymore.
Category: Unified Experience: Search, navigation and performance
This is clearly needed. So dissapointed this hasn't been addressed yet.
Category: Unified Experience: Search, navigation and performance
Urgently needed! How is the current low-code and no-code initiative supposed to work out if this is not addressed?!Please add:Business rule supportChart supportCalculated field support (at least allow to retrieve the content as string, setting a text-field)Thank you!PS: This topic is especially frustrating because all these missing features have been promised since the introduction of multi-option set fields at least five years ago. Unfortunately, still no update - and worse - not even a response or any kind of roadmap.
Category: Unified Experience: Search, navigation and performance