Hello,
I am trying to filter a Data Table utilizing 4 Text Input Boxes and 1 Date Packer Input Box. I am able to successfully filter utilizing the 4 Text Input Boxes (code A noted below). The code below is built specifically this way to allow users to filter on any combination of Text Input Boxes that they wish (that is why I have the or setup for if the Text Input Box is left blank by the user).
A
Filter(PO_Requests,And(PO_Num=PO_Num_Input.Text||PO_Num_Input.Text="",Requestor=Requestor_Input.Text||Requestor_Input.Text="",Request_Type=Request_Type_Input.Text||Request_Type_Input.Text="",Request_Result=Request_Result_Input.Text||Request_Result_Input.Text=""))
I cannot get the Date Input Picker box to successfully work in the code below. I tried the two code versions below (B & C) and neither work.
B
Filter(PO_Requests,And(PO_Num=PO_Num_Input.Text||PO_Num_Input.Text="",Requestor=Requestor_Input.Text||Requestor_Input.Text="",Request_Type=Request_Type_Input.Text||Request_Type_Input.Text="",Request_Result=Request_Result_Input.Text||Request_Result_Input.Text="",Created=Created_Input.SelectedDate||Created_Input.SelectedDate=""))
This one causes an error. I believe it is because I am using "" on the last part of the date filter string and date is a number, not text. I am not sure how to say that the Created_Input.Selected date is left blank (in number format).
C
Filter(PO_Requests,And(PO_Num=PO_Num_Input.Text||PO_Num_Input.Text="",Requestor=Requestor_Input.Text||Requestor_Input.Text="",Request_Type=Request_Type_Input.Text||Request_Type_Input.Text="",Request_Result=Request_Result_Input.Text||Request_Result_Input.Text="",Created=Created_Input.SelectedDate||Created_Input.SelectedDate=0))
In this one, I did not use the "" on the last part of the date filter and instead used a 0. This does not cause an error, but it does not filter my data correctly. I think this is because the DefaultDate setting on my Date Picker Input Box is not zero (it is ""). I tried setting my DefaultDate to zero, but it defaults to a 1970's date. I then tried setting the DefaultDate to Today() and then updated my code above to be equal to Today(), but that didn't work either.
Any help would be appreciated. Thank you in advance for any assistance provided.
-Chris
Solved! Go to Solution.
I think your issue is a date with blanks. No created date is blank thereby you are never going to find a record based on a date with that filter even if it works. It must contain a date for that filter to work. You are wanting the filter to find on any, some or all the inputs, but each time it runs with a blank date it will never find any as none exist.
You could try something that uses the date only if one is selected. Put the last date section in an IF statement
If(!isblank(Created_Input.SelectedDate),Created=Created_Input.SelectedDate)
This might work but then the filter breaks the delegation rules
You can also try
If(Created_Input.SelectedDate<>Blank(),Created=Created_Input.SelectedDate)
Working with dates in filters are a real pain as they quickly become non delegable if you use <>.
Lastly you can have two filters. One when date is selected an one when not. EG
If(!isBlank(Created=Created_Input.SelectedDate),
Filter(PO_Requests,And(StartsWith(PO_Num,PO_Num_Input.Text),StartWith(Requestor,Requestor_Input.Text),StartsWith(Request_Type,Request_Type_Input.Text),StartsWith(Request_Result,Request_Result_Input.Text),Created=Created_Input.SelectedDate)),
Filter(PO_Requests,And(StartsWith(PO_Num,PO_Num_Input.Text),StartWith(Requestor,Requestor_Input.Text),StartsWith(Request_Type,Request_Type_Input.Text),StartsWith(Request_Result,Request_Result_Input.Text))))
Your filet is some what confusing.
I would change lot to something like:
Filter(PO_Requests,And(StartsWith(PO_Num,PO_Num_Input.Text),StartWith(Requestor,Requestor_Input.Text),StartsWith(Request_Type,Request_Type_Input.Text),StartsWith(Request_Result,Request_Result_Input.Text),Created=Created_Input.SelectedDate))
The startswith will filter on blanks and data.
Not sure about the selected date. I assume that is it is blank the above may do the same - The "" is not valid for a date column and also I would have thought that the Default created (which is that field) in never blank so impossible to find a blank
@leyburn19 I like your approach. The code is alot cleaner and the functionality to search based on a partially input value is fantastic.
I utilized your code, but it still errors out due to the filter on the date. I removed the filter related to the date and it worked fine. I am not sure what to do in regards to incorporating the date portion into the filter. I've seen another post where somebody mentioned converting the date to a text to be able to search for it in the data table, but I haven't been able to get that to work either.
If you have any additional suggestions, please let me know. Thanks for your help so far!
I think your issue is a date with blanks. No created date is blank thereby you are never going to find a record based on a date with that filter even if it works. It must contain a date for that filter to work. You are wanting the filter to find on any, some or all the inputs, but each time it runs with a blank date it will never find any as none exist.
You could try something that uses the date only if one is selected. Put the last date section in an IF statement
If(!isblank(Created_Input.SelectedDate),Created=Created_Input.SelectedDate)
This might work but then the filter breaks the delegation rules
You can also try
If(Created_Input.SelectedDate<>Blank(),Created=Created_Input.SelectedDate)
Working with dates in filters are a real pain as they quickly become non delegable if you use <>.
Lastly you can have two filters. One when date is selected an one when not. EG
If(!isBlank(Created=Created_Input.SelectedDate),
Filter(PO_Requests,And(StartsWith(PO_Num,PO_Num_Input.Text),StartWith(Requestor,Requestor_Input.Text),StartsWith(Request_Type,Request_Type_Input.Text),StartsWith(Request_Result,Request_Result_Input.Text),Created=Created_Input.SelectedDate)),
Filter(PO_Requests,And(StartsWith(PO_Num,PO_Num_Input.Text),StartWith(Requestor,Requestor_Input.Text),StartsWith(Request_Type,Request_Type_Input.Text),StartsWith(Request_Result,Request_Result_Input.Text))))
@leyburn19 thank you for providing those multiple options. I tried the first two and they didn't work (which I think you mentioned you might have expected to happen).
I tried the third option with the double filter. I dropped in your code and it errored. I looked at the code and I think you included the create date filter in the wrong part of the if statement. If the Created_Input is blank, we do not want to filter on it (your code said to filter on the Created_Input when it was blank). I moved this piece of the filter to the second part of the if statement (Created_Input is not blank). The code did not error out when I did this, but it would not return any values.....so I am not sure what is going on.
You did give me an idea for a workaround though. In one of my sharepoint list fields, I have a timestamp embedded in a string. I am wondering if I can add a calculated field to my sharepoint list that extracts this into its own field and then I can use the same filter logic like I am using for the other filter items. The user would be inputting the date in a text format into a text input box and could try searching this way.....I am going to give this a try and will get back to you. Thank you for all of your help!
@leyburn19 Since I couldn't get the data to work as a date with the date input text box, going back to my source data and creating a text field for the date allowed me to then filter the data in my powerapp easily. My code is below. I appreciate all the help. This date thing seems to be real finnicky, this work around will work.
Filter(PO_Requests,And(StartsWith(Requestor,Requestor_Input.Text),StartsWith(PO_Num,PO_Num_Input.Text),StartsWith(Request_Type,Request_Type_Input.Text),StartsWith(Request_Result,Request_Result_Input.Text),StartsWith(Created_Date2,Created_Input.Text)))
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