Forum Discussion

AmazingRandom's avatar
AmazingRandom
Helper II
1 year ago
Solved

Incremental Refresh failing

I am trying to set up an incremental refresh for a dashboard that has a massive load of data for our API to handle within its 1 hour time out limit. I managed to set up paramaters and it seems I can ...
  • Poojara_D12's avatar
    1 year ago

    Hi AmazingRandom 

    The issue you're encountering while setting up incremental refresh in Power BI appears to stem from differences in how Power BI handles query folding and schema recognition between Desktop and the Power BI Service. While everything works locally—because Power BI Desktop executes the full query in-memory—it fails in the Service, which relies on the data source's query folding capabilities and often interprets the M code more strictly. The error message suggests that Power BI Service is expecting a column named Column1 or Column1.ecoli, but cannot find it in the returned dataset from your API. This could be due to a few reasons: the structure of the API response might be dynamic (i.e., column names change or appear conditionally), or the use of hardcoded column names in your M code doesn't match what's returned at runtime in the Service. Also, if your incremental logic relies on relative date filters or dynamic parameters (like RangeStart and RangeEnd), and the schema isn't fully defined before those filters are applied, the Service might not be able to validate the final output. To fix this, ensure that the column names are stable and consistent, explicitly define your schema using Table.TransformColumnTypes or Table.SelectColumns, and test your queries step-by-step using "View Native Query" to confirm folding. Also, avoid referencing nested fields unless they've been expanded and renamed clearly. Debugging this often involves simplifying the query to just return a few rows, publishing it, and gradually reintroducing complexity until the error appears again.