Forum Discussion

Sam_Jain's avatar
Sam_Jain
Helper III
2 years ago
Solved

Power BI Dataflow - response too large to return

Hello Community,   I have run into a PowerBI dataflow issue. My source table is in Big Query and is a table that gets updated daily and has data for the last 90 days in a rolling fashion.   What ...
Dataflow
Need Help
Tips and Tricks
  • lbendlin's avatar
    lbendlin
    2 years ago
    Can't use direct connection to BQ for access reasons

    Challenge that assumption.  Tell them that 650 GB is too much.

     

    If they don't budge, use Incremental Refresh. Start VERY small, with a day or so.  See how many rows you get.  Recommended partition size is around 8 to 20 million rows.

  • lbendlin's avatar
    lbendlin
    2 years ago

    Please explain "import does not work"  - are you getting an error message?

     

    Direct Query on a dataflow = datamart = lipstick on a pig  (Azure SQL db being the lipstick and the dataflow being the pig).  Possible, sure,  but a travesty nevertheless.

     

    You can consider switching the incremental refresh to the dataset instead and to completely remove the dataflow from the equation.

     

    You can consider dataflow Gen2 and store the results as Delta Lake in Fabric.

lbendlin's avatar
lbendlin
Super User
2 years ago

But if you consume the dataflow you only see two days worth of data?

Sam_Jain's avatar
Sam_Jain
Helper III
2 years ago

Not sure if i mentioned before but the source data does run on a 2 day delay (including today), meaning today i only have data on that table till 08/12/2024 
And since i kept the inc refresh at refresh rows from past 1 day since refresh date - it will not get any data because it just does not exist?
As for consumption of data once loaded into PBI or even on power query to begin with i just see data from 05/01/2024 to 07/08/2024