cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Filter dropdown

Hello community,

 

is there a way to create a dropown from all distinct/unique records?

Entity attribut is a text.
I want to create a dropdown with all different values across entity as a filter.

 

Example:
apple | red

apple | green
tomato | red

tomato | green

lemon | yellow

lemon | green

cherry | red

 

Filter dropown for color has entries:
red, green and yellow

 

Filter dropdown for fruits has entries:
apple, tomato, lemon and cherry.

 

Thanks for help,

AndKan.

1 ACCEPTED SOLUTION

Accepted Solutions

I make a solution with JS-manipulating DOM. In this workaround a dropdown/select is displayed insteed of checkboxes.
Quite simple so far.


But only filter values are useable, which are already defined in FetchXML filter.
Filter is defined as:

 

<filter type="or" adx:uiname="Color">
  <condition attribute="cr847_bstatus" operator="eq" value="red" />
  <condition attribute="cr847_bstatus" operator="eq" value="green" />
  <condition attribute="cr847_bstatus" operator="eq" value="yellow" />
</filter>

 

Results in HTML:

 

<input type="checkbox" name="0" value="0">
<input type="checkbox" name="0" value="1">
<input type="checkbox" name="0" value="2">

 

 When first checkbox is clicked, it is submitted as:

 

metaFilter: "0=0"

 

You see 0=0
"0" is the number of filter condition in filter number 0 (first filter); in this case like red.

Submitting 0=3 is useless, because no fourth condition defined in filter.
When changing order of conditions in filter: 

 

<filter type="or" adx:uiname="Color">
  <condition attribute="cr847_bstatus" operator="eq" value="yellow" />
  <condition attribute="cr847_bstatus" operator="eq" value="red" />
  <condition attribute="cr847_bstatus" operator="eq" value="green" />
</filter>

 

then 0=0 is now yellow.

A real filter, as I expected, isn't possible this way.

A definition:

 

<condition attribute="cr847_bstatus" operator="neq" value=" " />

 

gives exactly one checkbox and not all results, which not contain " "

 

Each condition defined in FetchXML filter becomes one option in portal. That's all.

I think Microsoft can do a lot to expand functionality of such a filter. Couldnt be so much complicated ...

 

My solution is now a combination of JS/Liquid fetch/Textfilter.
Works fine 🙂

View solution in original post

5 REPLIES 5

Hello @AndKanPA.

 

You cannot set dynamic filters on text fields, but you can set up Attribute filter sets as dropdown. Then using text fields you will have to manually set up the filters you need and maintain the list as more values are added and deleted. Text Filter is also an option where you allow users to enter text strings as filter. 

 

Text Filter

For text fields I would use a "Text Filter" to allow users to filter results by entering text strings:

UlrikkeAkerbæk_0-1603269944957.png

This will display a text box where you can search for text values in a specific text field:

UlrikkeAkerbæk_1-1603270102949.png

 

Attribute filter sets

You can also set up Attribute Filter Sets on text fields to enable that drop down experience you wanted. Then you will have to maintain the options manually to make sure all possible options are found as a filter option.

 

attributefilterset.jpg

 

I used "check boxes" to easily display in this image - but choose drop down if you wish. 

UlrikkeAkerbæk_2-1603271427110.png

 

 

If you want to use dynamic filters you can have the colors and the fruit types as option sets or in a relational entity.

dynamicsets.png

Then the filters will automatically display the filter options that are available for your records.

dynamicresult.png

 

Hope this answer your question. If you gave more questions regarding filters the documentation might be helpful: https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/entity-lists#entity-list-filter-c...

OOlashyn
Most Valuable Professional
Most Valuable Professional

Hi @AndKanPA ,

 

If we are talking about unique records inside entity set you can use "distinct=true" in your fetchxml in fetch node. It will return only unique records in the set. If you want to return all records that have a unique value in some field or get all possible unique values from that field I don't think it is possible.

----------------------------------------------------
If you find this post helpful consider marking it as a solution to help others find it.

Thanks you @OOlashyn .
I'll try "distinct"; sounds good for the first.


But I ever get checkboxes instead of a dropdown, when I use the FetchXML filter.

 

Any way to change from checkboxes to dropdown?

 

Thanks,

AndKan.

@UlrikkeAkerbæk , sorry, I didnt see your reply yesterday.
Thank you for your detailed answer.


I saw different option for other filters, but where is such an option, when I use FetchXML Filter

AndKanPA_0-1603516200604.png

?
Perhaps there is a little attribute adx:uitype or something.

Thank you,

AndKan.

I make a solution with JS-manipulating DOM. In this workaround a dropdown/select is displayed insteed of checkboxes.
Quite simple so far.


But only filter values are useable, which are already defined in FetchXML filter.
Filter is defined as:

 

<filter type="or" adx:uiname="Color">
  <condition attribute="cr847_bstatus" operator="eq" value="red" />
  <condition attribute="cr847_bstatus" operator="eq" value="green" />
  <condition attribute="cr847_bstatus" operator="eq" value="yellow" />
</filter>

 

Results in HTML:

 

<input type="checkbox" name="0" value="0">
<input type="checkbox" name="0" value="1">
<input type="checkbox" name="0" value="2">

 

 When first checkbox is clicked, it is submitted as:

 

metaFilter: "0=0"

 

You see 0=0
"0" is the number of filter condition in filter number 0 (first filter); in this case like red.

Submitting 0=3 is useless, because no fourth condition defined in filter.
When changing order of conditions in filter: 

 

<filter type="or" adx:uiname="Color">
  <condition attribute="cr847_bstatus" operator="eq" value="yellow" />
  <condition attribute="cr847_bstatus" operator="eq" value="red" />
  <condition attribute="cr847_bstatus" operator="eq" value="green" />
</filter>

 

then 0=0 is now yellow.

A real filter, as I expected, isn't possible this way.

A definition:

 

<condition attribute="cr847_bstatus" operator="neq" value=" " />

 

gives exactly one checkbox and not all results, which not contain " "

 

Each condition defined in FetchXML filter becomes one option in portal. That's all.

I think Microsoft can do a lot to expand functionality of such a filter. Couldnt be so much complicated ...

 

My solution is now a combination of JS/Liquid fetch/Textfilter.
Works fine 🙂

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results |Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 1: Community MembersSolutionsSuper UsersSolutionsPower Pages @Inogic  1   @ragavanrajan  2 @aofosu  1 @Jcook  1Open  @OliverRodrigues  1Open  @Lucas001  1Open Open    Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 2: Community MembersSolutionsSuper UsersSolutionsPower Pages @taraubianca25  2 @EmadBeshai  2 @ALP2  2@Fubar 2 @ekluth1  2@ragavanrajan 1 @mandela  1@OliverRodrigues 1 @Ajlan  1Open   @elishafxx  1    @TA_Jeremy  1    @helio1981  1       Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower PagesInogic2@EmadBeshai 6Ajlan1@ragavanrajan 4CraigWarnholtz1@Fubar 4  @Jcook 3  @OliverRodrigues2   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower PagesHenryed071Fubar3Inogic1OliverRodrigues2JacoMathew1EmadBeshai2faruk11  TA_Jeremy1   shubhambhangale1   doug-ppc1   hubjes1  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

  On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Kudoed Authors
Users online (2,196)