Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi Community Users,
I am getting one error in Power BI desktop while pulling the dimension column in the table visual against a measure using direct query mode connected to snowflake database.
Error Message:
The resultset of a query to external data source has exceeded the maximum allowed size of '1000000' rows.
Whatever dimensions been pulled don't have much rows to think of it should throw more than 1 million records.
The same dimesion used in slicer and the measure is not throwing any error
Below find the dax definition used in measure :
Solved! Go to Solution.
Hi @Anonymous,
This is a known issue that appears on directquery mode datasource when it return rows more than 1M.
Use DirectQuery in Power BI Desktop#limitations-of-directquery
This is caused by 'return' rows, have you apply any t-sql queries or functions that will increase the return row amount? (e.g. join functions)
In addition, it seems like you are nested multiple iterator functions in your measure which will multiple its row contents amount.
I'd like to suggest you try to remove them from your visual to confirm if this issue is caused by these multiplied row contents.
Notice: iterate tables will obviously increase the calculation table row contents amount.
for example, iterator three tables with 1k, 2k, 5k rows.
Actual calculated row contents= 1000*2000*5000=10^10 rows that obviously over 1M(10^6) rows.
Optimizing nested iterators in DAX
Regards,
Xiaoxin Sheng
Hi @Anonymous,
This is a known issue that appears on directquery mode datasource when it return rows more than 1M.
Use DirectQuery in Power BI Desktop#limitations-of-directquery
This is caused by 'return' rows, have you apply any t-sql queries or functions that will increase the return row amount? (e.g. join functions)
In addition, it seems like you are nested multiple iterator functions in your measure which will multiple its row contents amount.
I'd like to suggest you try to remove them from your visual to confirm if this issue is caused by these multiplied row contents.
Notice: iterate tables will obviously increase the calculation table row contents amount.
for example, iterator three tables with 1k, 2k, 5k rows.
Actual calculated row contents= 1000*2000*5000=10^10 rows that obviously over 1M(10^6) rows.
Optimizing nested iterators in DAX
Regards,
Xiaoxin Sheng
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
106 | |
93 | |
75 | |
62 | |
50 |
User | Count |
---|---|
147 | |
107 | |
105 | |
87 | |
61 |