Using negative <> can trigger the delegation warning Filter(list,‘Title’ <> “No”) Using = instead makes the delegation warning goes away Filter(list,‘Title’ = “No”)

Here’s a step-by-step guide to implement your Power Automate flow: 1.Trigger: Add a PowerApps trigger (manual) to start the flow and accept two inputs: SearchInput (text) and Database (text_1). 2.Get Items from SharePoint: Add a “Get items” action for SharePoint. Set the site address and list/table. Use a filter: substringof(’@{triggerBody()[’text’]}’,Title) and Database eq ‘@{triggerBody()[’text_1’]}’ and InsiderList eq ‘No’ 3.Select Action: Add a “Select” data operation. From: @outputs(‘Get_items’)?[‘body/value’] Map fields: ID, Title, Team, Channel, Folder Status, Database, Path.

I had a requirement to enable Search on clicking on Enter key on a text box or clicking explicitly on the button to trigger the search. Upon investigation and playing around, I discovered the OnChange trigger works well. So that I don’t duplicate logic across two triggers, I wrapped the logic of the search into a hidden button on the form Referenced the logic into the textbox and icon On Change referencing button from Textbox On Select from Icon