Search using Date and Incident ID

[rmaziwis]

Hi All 

I am still battling with search using Incident ID and date Iam currently using the following formulas 

1. My first formula only searches for text values only so I can’t search the ID and Date 

2.My second and 3rd formulas add those two fields as text so that it can allow me to search but I still cannot search the incident Id   the date works but I have to type it in a specific format.

3.I have changed the delegation limit to a max of 2000 thinking maybe it is what is causing the issue.

My users really need to search using the incident ID I know I have asked this before but it’s still not perfect any ideas could really help.

 

[yashag2255 · Accepted solution]

Hi @rmaziwis 

Search and in operator works at the sub-strings levels as well. That is why it is showing you multiple records when any input is captured. If you only want to get the items that starts with entered string, you need to update the formula to:

Can you update the second expression shared by you to remove in operator values and rewrite them in the way that you have used for the TextId and TextDate columns. 

Something like:

SortByColumns(

Filter(

AddColumns(),

StartsWith() ||

StartsWith() || 

StartsWith() ||

StartsWith()

),

"Id",

If()

)

Also, regarding the date field, if you donot want to type the value, you can add a date picker and based on selected date, you can filter the results as:

SortByColumns(

Filter(

AddColumns(),

StartsWith() ||

StartsWith() || 

StartsWith() ||

StartsWith() ||

'Date and time of Incident' = DatePicker1.SelectedDate

),

"Id",

If()

)

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[poweractivate · Accepted solution]

@rmaziwis 

---

@rmaziwis wrote:

3.I have changed the delegation limit to a max of 2000 thinking maybe it is what is causing the issue.

Did you get a delegation warning (yellow triangle where the warning message specifically states delegation warning along the lines of the query possibly not working on large data sets)?

If you did, you should try and get rid of it before using the app in most production scenarios. Please note - as long as your data source has more than 2000 records, lowering the number of results you return is not usually the right solution and tends to create misleading inconsistency. For example, suppose you have 200,000 records. So now suppose you got delegation warning and to try and solve it, you decide "hey if I limit the results you return to 500 I can get around it" - that would not be correct because your app will still not behave correctly. That is because you will be returning 500 results out of only 2000 random records PowerApps chooses to see out of the 200,000 - so the results will be missing and have holes in it.

You tried raising the limit to 2000, but the question is, why did you try to raise it? Did you get a delegation warning in the first place? If so, then you should try and get rid of the warning rather than attempt to raise the limit. You can leave the limit at 2000 now but what you should really do is make sure that if you got a delegation warning, to rewrite the query so you don't. We sometimes even go so far as to use a different data source if the data source we were using had no way of getting rid of the warning - because this can be quite important. For example, many times we changed over from SharePoint List to Common Data Service just to make sure we didn't get the warning in some cases. It is also possible to work around it and creatively redo the query and use tricks so that you don't have to change the data source as well. 

First, check if you got a warning of delegation in the first place. If you did, see if you can get rid of it. Getting rid of a delegation warning is scenario-specific and depends on your specific case and objectives.