Forum Discussion
Error Message: Input query length exceeding the supported maximum length
Hello,
in several of my reports I'm facing the issue of "input query length exceeding the supported maximum length".
My data is coming from several sources, including dataverse (CRM), windsor.ai (google ads, facebook ads) as well as static files.
This also affects reports that have previously worked but suddenly the visuals don't load anymore and the error message keeps popping up. Like in the example on the attached screenshot.
I've tried to reduce filters and make it less complex but it somehow doesn't work.
Sometimes this also happens when I simply rename field-values in a visual - and then the visual isn't display correctly and the error message keeps popping up.
That's really frustrating and very time-consuming...
Any idea about that?
Thanks in advance! 🙂
Hi cn4422 ,
Based on your description, your data source is probably connecting in import mode. You mentioned that these visualizations were working fine before, but recently there have been errors. This may be due to the fact that queries in published reports will be limited by the query runtime, as well as the amount of memory the query can use. These limits may change depending on where the data is hosted. This is to prevent any individual query from consuming too many resources.
You can set the limits on the amount of memory that can be used by a query in the
Select File > Options and Settings > Options
Under Current File, select Report Settings.
Scroll to the Query Limit Simulation section.If you choose to apply custom limits, enter specific timeout and memory limits in the input fields. When setting your own limits, you can use “0” for “no limit”.
After the setup is complete, you can re-upload the report to check.
Set visual query limits in Power BI Desktop - Power BI | Microsoft Learn
How to Use Query Limit Simulations to Optimise Your Power BI Reports | by Masego | Medium
Best regards,
Albert HeIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly
7 Replies
Hi cn4422 ,
Based on your description, your data source is probably connecting in import mode. You mentioned that these visualizations were working fine before, but recently there have been errors. This may be due to the fact that queries in published reports will be limited by the query runtime, as well as the amount of memory the query can use. These limits may change depending on where the data is hosted. This is to prevent any individual query from consuming too many resources.
You can set the limits on the amount of memory that can be used by a query in the
Select File > Options and Settings > Options
Under Current File, select Report Settings.
Scroll to the Query Limit Simulation section.If you choose to apply custom limits, enter specific timeout and memory limits in the input fields. When setting your own limits, you can use “0” for “no limit”.
After the setup is complete, you can re-upload the report to check.
Set visual query limits in Power BI Desktop - Power BI | Microsoft Learn
How to Use Query Limit Simulations to Optimise Your Power BI Reports | by Masego | Medium
Best regards,
Albert HeIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Anonymous thanks for your reply - I will definitely check that out and see if it can fix the issue.
I've also found out, that one thing that changed, was that a field I've already used in the previous report has now a lot more characaters in it, up to a few hundred... could this also be an issue with this error message?
Hi cn4422 ,
Your reference to hundreds of characters is probably not the reason for this question, as the “text” data type is a Unicode character data string, and the actual maximum string length is limited to about 32,000 Unicode characters.
You can do a distribution query to determine where the error occursData types in Power BI Desktop - Power BI | Microsoft Learn
Best regards,
Albert HeIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly
