Hello, I was trying to do multiple search in one button, considering that if the search is not found it return all the records, this would be usefull for do a search with multiple parameters. For example in my case I have 2 parameters for search in the table, lets say:
parameter1, parameter2.
I want to do the next:
Search(Search('Data source'; String1.Text; Parameter1); String2.Text; Parameter2)
In theory I would get all the records that satisfy parameter1 = String1.Text && parameter2 = String2.Text, if doesnt satisfy parameter1 but it does in parameter2 I would get all the records that satisfy parameter2 but in my case I got nothing. It seems I cannot use the result of the first Search as parameter of the second one even though the result is a table with records (that acts the same as a Data source). As an alternative I am doing right now 2^2 = 4 "if" sentences but this isn't scalable at all because if I got 6 parameters I would get 2^6 = 64 "if" sentences, thats why I want to use the search function.
Is this a bug or I just don't understand well the functionality of search?
If you have any doubts about what I am trying to explain I would answer thankfully.
Regards,
Solved! Go to Solution.
PPS The caching will work only for sources with up to 500 rows. If you have more than 500 lines then use this:
https://powerusers.microsoft.com/t5/PowerApps-Forum/500-item-limit-in-CDM-entity-search-filter-need-...
My solution is towards the end of the post
Hi @Brank
Could you please clarify what Parameter1 and Parameter2 are? Are they two different text fields in 'Data source'?
Assuming this is the case, what is the result you are looking for?
1) To satisfy parameter1 = String1.Text && parameter2 = String2.Text etc. etc.
OR
2) To satisfy parameter1 = String1.Text || parameter2 = String2.Text etc. etc.
Finally, are you looking to match letter cases or not?
Thanks.
Hello @Meneghino,
Parameter1 and Parameter2 in this case are Columns in the table of the data source. As we know the "data source" can be an external data source (Common data service, SQL Server, etc) or tables. Lets say 'Data source' is an entity in the Common data service, this entity has the next columns:
Parameter 1 l Parameter2
---------------------------------------------------------
Parameter value 1 l Parameter value 2
Parameter value 3 l Parameter value 4
Lets say I do:
UpdateContext({firstSearch : Search('Data source'; "Parameter value"; Parameter 1) }) In this case the variable context "firstSearch" will have a table with all the records because in the parameter 1 I have 2 records that start with "Parameter value" then I want to do:
UpdateContext({secondSearch : Search(firstSearch; "Parameter value 4"; Parameter 2)}) In this case I will get in the variable context "secondSearch" a table with just the second record because Parameter 2 has "Parameter value 4". But in my case the secondSearch variable has an empty table.
Regards,
Ok, I think I understand what you need. For example:
Filter('Data source', String1.Text in Parameter1 || String2.Text in Parameter1, String3.Text in Parameter2 || String4.Text in Parameter2)
You can combine as you like and use 'exactin' instead of 'in' if you need to match case
Hi @Meneghino,
The problem is that Filter doesn't return all the records if one of the Strings.Text is blank, it would just don't return any records because it doesn't satisfy the condition.
Regards,
Ok, you are right. "" will return all records but a null value will not.
Use this for all the tests of the Filter:
(IsBlank(MySearchText) || MySearchText in TargetTextField)
Please let me know how you get on
I think you didn't undertand why I want to use Search instead of Filter.
If I used Filter I have to do 2^numberOfParameters Filters with If senteces for know if one of the parameters string is Blank or not because the Filter function will change in everycase.
OK, it works, so I think you must have something wrong in your syntax. By the way, I would always avoid the use of spaces in column names. If you do have spaces, then you may need to wrap them in single quotes 'Parameter 1' etc.
Please note below that because you are in a different locale, you will need to substitute some , with ; and the ; with ;;
Here are the steps:
Table({Parameter1: "Parameter value 1", Parameter2: "Parameter value 2"}, {Parameter1: "Parameter value 3", Parameter2: "Parameter value 4"})
UpdateContext({firstSearch : Search(Gallery1.AllItems, "Parameter value", "Parameter1") });
UpdateContext({secondSearch : Search(firstSearch, "Parameter value 4", "Parameter2")})
secondSearch
Please let me know how you get on.
I see what you did there!
I have no errors in syntax, the only difference between yours and mine is that I am doing the search with a data source using "Common Data Service", can you replace the in the first search the "Gallery1.AllItems" for data source in Common Data Service?.
Thanks in advance.
Regards,
Hi @Brank, this may be a problem of delegation.
What you can try is to substitute this for the button OnSelect and eliminate Gallery1:
ClearCollect(CachedDataSource, 'Data source'); UpdateContext({firstSearch : Search(CachedDataSource, "Parameter value", "Parameter1") }); UpdateContext({secondSearch : Search(firstSearch, "Parameter value 4", "Parameter2")})
Please let me know.
PS I use caching often also for perfomance purposes. If the source does not change often you can just cache once after the user starts the app. I do this by having a welcome screen and a "Proceed" button that caches all necessary tabels and then navigates to the first real screen of the app
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