Hi,
I would like to filter a collection that is used to populate a DropDown (Items). The collection should contain all items, except the items that exist in an other collection. Example: List1 [1,2,3,4,5], List2 [2,4], Items shown in the DropDown [1,3,5].
To test this scenario I created 2 SharePoint lists:
And created this and works as intended:
In the actual app, there are two lists; Planning_Line and Time_Option. In Planning_Line, there is a LookUp column to Time_Option. This LookUp column in Planning_Line is called Tijd. The column with the time value in Time_Option, is called Title.
Now I try to do almost the same as the example above with the collections in the actual app, but I cant get it to work. (I don't think I fully understand the syntax of this filter...):
I also have tried to create an extra connection to the Time_Option list and use that as source collection in the function above, to be able to try different syntax in the Not() function but that also didn't work. I clearly do not fully understand the syntax here so any help is welcome.
Solved! Go to Solution.
@Power_Robert last night when I was researching your question I thought Planning_Line and Time options were collection variables but this morning when I re-read your post I believe these are actually Sharepoint Lists instead, correct? In that case there's a different answer and I'll try to explain it with a small demo app I wrote. You might find re-creating this demo app will help you figure out what to do for your own specific situation.
My 1st step was to create a blank canvas app and make 2 connections to my Sharepoint Lists called Assignments and Time Options. Then I add btn called "btn_collect" and set OnSelect property to the following code to bring them into collection variables called List1 and List2.
ClearCollect(List1,ForAll(TimeOptions, {Tijd: Tijd}));ClearCollect(List2,ForAll(Appointments,{Tijd: Tijd.Value}));
You can see the contents of List1 and List2 in the image of my app below. This is just a nice visual for the purpose of explaining. You don't need to do this in your app.
Finally, I created a dropdown control called "drp_list" and used this code in the Items property.
Filter(List1,Not(Tijd in List2.Tijd))
I believe the main issue we had was with the lookup value in the Appointments table. Powerapps reconigizes this as an object data type but we want a number instead. That's why I used the code {Tijd: Tijd.Value}. We didn't use the Choices function here at all. You would use Choices when referencing a single column in a datasource (i.e. Sharepoint) but when we are combining multiple tables its not necessary.
Hello there Robert,
My suggestion would be to remove the Choices function so the Items property of your drop-down control looks like the formula below. Depending on your schema you might have to swap the position of Planning_Line and Time_Option. Give it a try and let me know how it goes.
Filter(Planning_Line.Tijd,Not(Tijd in Time_Option.Tijd))
---
Please click "Accept as Solution" if my response helped to solve your issue so that others may find it more quickly. If your thought the post was helpful please give it a "Thumbs Up."
Hi @mdevaney,
Thanks, but it doesn't work. ".Value" can't be added when removing the Choices() function and without ".Value" it doesn't work either.
@Power_Robert when researching your issue last night I thought that Planning_Line and Time_Options were names of collections but they must be Sharepoint List names instead. In that case, the 1st step is to create single column collections having Tijd for both Planning_Line and Time_Options.
Here's what I did to reproduce your issue. I created an app with 2 Sharepoint list data sources: Appointments and TimeOptions. Next I created a button called "btn_collect" and put the following code in the OnSelect property:
ClearCollect(List1,ForAll(TimeOptions, {Tijd: Tijd}));ClearCollect(List2,ForAll(Appointments,{Tijd: Tijd.Value}));
Now once the button is clicked the collections appear in the two data tables below. This is only to show a nice visual of what the collection looks like but its not necessary to do in your app.
Next I created a drop-down control and input the following codes into the Items property:
Filter(List1,Not(Tijd in List2.Tijd))
When the drop down is clicked I was able to achieve the desired result. (See image below).
I think one of the pain points we both had while troubleshooting this issue was the lookup column. A lookup column is an object data type but we need a number instead. That's why I had to loop over Tidj.Value instead of just Tijd.
Let me know if you are able to get the same result
@Power_Robert last night when I was researching your question I thought Planning_Line and Time options were collection variables but this morning when I re-read your post I believe these are actually Sharepoint Lists instead, correct? In that case there's a different answer and I'll try to explain it with a small demo app I wrote. You might find re-creating this demo app will help you figure out what to do for your own specific situation.
My 1st step was to create a blank canvas app and make 2 connections to my Sharepoint Lists called Assignments and Time Options. Then I add btn called "btn_collect" and set OnSelect property to the following code to bring them into collection variables called List1 and List2.
ClearCollect(List1,ForAll(TimeOptions, {Tijd: Tijd}));ClearCollect(List2,ForAll(Appointments,{Tijd: Tijd.Value}));
You can see the contents of List1 and List2 in the image of my app below. This is just a nice visual for the purpose of explaining. You don't need to do this in your app.
Finally, I created a dropdown control called "drp_list" and used this code in the Items property.
Filter(List1,Not(Tijd in List2.Tijd))
I believe the main issue we had was with the lookup value in the Appointments table. Powerapps reconigizes this as an object data type but we want a number instead. That's why I used the code {Tijd: Tijd.Value}. We didn't use the Choices function here at all. You would use Choices when referencing a single column in a datasource (i.e. Sharepoint) but when we are combining multiple tables its not necessary.
Hi @mdevaney ,
Thanks a lot!
Now this is working, the situation is getting even more difficult. The Time_Option list also has a LookUp column Reserved_For. I'am trying to add this to the collection, but I have no option to do so.
Example of what I was expecting to work:
ClearCollect(TimeOption_Col,ForAll(Time_Option, { Id: ID, TimeOption: Title, Customer: Reserved_For}));
Or
ClearCollect(TimeOption_Col,ForAll(Time_Option, { Id: ID, TimeOption: Title, Customer: Reserved_For.Title }));
Do you know if it possible to add the lookup object, id or title to the collection?
Have you tried the Value property of the Reserved_For lookup column?
ClearCollect(TimeOption_Col,ForAll(Time_Option, { Id: ID, TimeOption: Title, Customer: Reserved_For.Value }));
In your original question I was actually using a LookUp column and getting the Value. Here's the previous example.
ClearCollect(List2,ForAll(Appointments,{Tijd: Tijd.Value}));
@mdevaney wrote:In your original question I was actually using a LookUp column and getting the Value. Here's the previous example.
ClearCollect(List2,ForAll(Appointments,{Tijd: Tijd.Value}));
Hi @mdevaney ,
Yes, that is true. But for some reason Gereserveerd voor is not available in the "intellisense" underneath the function input:
I've also done a refresh on the connection a few times. But that didn't help either.
I noticed your Sharepoint column Gereserveerd voor is two words separated by a space Intellisense did not find it because you have to reference it with single quotes like this:
Customer: 'Gereserveerd voor'
If its a LookUp column you'll need to go one step further
Customer: 'Gereserveerd voor'.Value
For this reason, when I build a Sharepoint List for myself I always make the columns one word (e.g. GereserveerdVoor)
@mdevaney wrote:I noticed your Sharepoint column Gereserveerd voor is two words separated by a space Intellisense did not find it because you have to reference it with single quotes like this:
Customer: 'Gereserveerd voor'
If its a LookUp column you'll need to go one step further
Customer: 'Gereserveerd voor'.Value
For this reason, when I build a Sharepoint List for myself I always make the columns one word (e.g. GereserveerdVoor)
I do agree that it is better to name the columns without a space. I'll rename them as I see them. I removed the space from this one as well and refreshed the data source, but still no solution. I tried the single quote as well. The column just don't show up...
---- Edit ----
I just tried the same in a sandbox and it worked just fine. I think I'll remove and recreate the connection to the data source and see what happened. To be continued...
--- Solution ---
When comparing the two SP Lists and lookup columns, I found a difference. When looking at the column settings, there is a field "In this column". The name of the column I wanted, was there in 2 versions; as "ColumnName" and "ColumnName (linked to item)". I used the last one, which was causing the issue:
Unfortunately I can't tell why this is causing an issue, but hopefully this info will help others as well.
@mdevaney Thank you for your time and effort!
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!
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 in the Forums 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. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (tie) 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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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.
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