PowerApps多条件Filter数据加载慢，是否改用Lookup/Search？

Hey there! Let's break this down for you. First off—don't switch to Lookup or Search for this scenario. Here's why:

• Lookup is built to fetch a single matching record, but you need a set of records that fit multiple complex And/Or conditions. It won't work for your use case.
• Search only handles fuzzy text matching on specific columns, which can't support the combination of status checks (Actual_Status, Contractor_status) you're working with.

Your core issue isn't using the wrong function—it's how you're implementing Filter and adding unnecessary overhead that's slowing things down. Let's fix this step by step:

1. Fix Your Filter Logic (Critical!) #

Your current filter has ambiguous operator precedence (Or vs And) which not only might return incorrect results, but also stops your SQL backend from optimizing the query (like using indexes). Let's clarify your intended logic:
From your code, you want records where:

• Action_user matches the input text, AND
• One of these is true:
  • Actual_Status is empty, OR
  • Actual_Status is "Yes" and Contractor_status is "No" (this automatically includes the subset where Recheck_Const is also "Yes", so you don't need to repeat that condition)

Rewrite the filter with explicit parentheses to make logic clear and delegable (delegated queries run on the SQL server instead of pulling all data to your app first—huge speed win):

2. Optimize Query Order #

You're using ShowColumns before Filter—this means you pull all columns from the table first, then filter, then trim down columns. Reverse this: filter first (to shrink the dataset size), then grab only the columns you need. This cuts down on data transfer and speeds things up.

3. Cut Unnecessary Overhead #

• The Refresh('[dbo].[table2]') call forces a full table reload every time—only use this if you absolutely need real-time updates. Skip it most of the time.
• Your final UpdateContext sets the load text to the same value—change that to clear the message once loading finishes.

Optimized Code Example #

UpdateContext({LoadText:"Loading Data... Please Wait..."});
// Remove Refresh unless you need instant real-time data
// Refresh('[dbo].[table2]'); 
ClearCollect(
    table1,
    ShowColumns(
        Filter(
            '[dbo].[table2]',
            Action_user = TextInput1.Text,
            // Explicit parentheses to define logic priority
            Actual_Status = "" || (Actual_Status = "Yes" && Contractor_status = "No")
        ),
        "ID","Description","Room_Type","ActionBy","Action_user","Area","Room_no","Building","Floor","Topic","SubTopic","Snag_Item","userid","Attachment","Actual_Status","Desc_Const","Desc_QC","Desc_Client","Client_status","Contractor_status","Recheck_Const","Recheck_QC"
    )
);
UpdateContext({LoadText:""}); // Clear loading message when done

Extra Tips for Even Better Performance #

• Add SQL Indexes: Create indexes on the columns you filter by (Action_user, Actual_Status, Contractor_status). This makes the SQL server's query execution way faster.
• Use Direct Delegation: Instead of loading everything into a ClearCollect, bind your gallery/control directly to the filtered data source. PowerApps will paginate results automatically, which is faster than pulling all records at once.
• Check Delegation Status: In PowerApps Studio, use the delegation checker to ensure all parts of your filter are delegable (no warning icons). Non-delegable logic means the app pulls data locally to filter, which is slow for large datasets.

To recap: Stick with Filter—it's the right tool for your complex multi-condition needs. The problem is just in how you're structuring the query and handling data flow. Fix those, and you'll see a big speed boost!

内容的提问来源于stack exchange，提问作者osama