Forum Discussion
URL: query string too long
- Anonymous5 years ago
Hi v-kelly-msft ,
thank you for your help!
None of the above-mentioned conditions seemed to be violated. However, I found a solution, albeit by accident rather than on purpose.
It was decided that the report was to be published in a different workspace. Additionally I now use the link for embedding, rather than the direct link to the report. So the link looks like https://app.powerbi.com/reportEmbed?reportId=<...>&filter=<...>instead of https://app.powerbi.com/<...>/reports/<...>/ReportSection?filter=<...> .
I don't know which of the two changes resolved it, and I still don't know what caused it in the first place, but maybe this still helps some other reader in the future.
Best Regards
Hi v-kelly-msft ,
thank you for your reply.
For question 1: I have already seen that thread (and similar ones) during my previous research but could not figure out where to find the web.config in question. I am developing a Power Apps canvas app, not a portal app. Maybe I should post this in the PowerApps forum instead?
For question 2: My filter works just fine and I am accessing the report, not the dashboard (which was the problem in your linked thread). The problem only occurs, when there are too many items in the list to filter by.
Best Regards,
DefinitelyNoBot
Hi Anonymous ,
For question 1:
If you could post a thread also in PowerApps forum,it would be a better choice for you as our related personnel would give you a better solution.
For question 2:
Check the limitations below:
- Report URL filters have a 10-expression limit (10 filters connected by AND).
- The long data type is (2^53-1) due to JavaScript limitations.
- Power BI doesn't limit the number of characters in URL query strings. Different browsers have different length restrictions.
Below is the related reference:
Best Regards,
Kelly
Did I answer your question? Mark my post as a solution!
- Anonymous5 years agoNot applicable
Hi v-kelly-msft ,
thank you for your help!
None of the above-mentioned conditions seemed to be violated. However, I found a solution, albeit by accident rather than on purpose.
It was decided that the report was to be published in a different workspace. Additionally I now use the link for embedding, rather than the direct link to the report. So the link looks like https://app.powerbi.com/reportEmbed?reportId=<...>&filter=<...>instead of https://app.powerbi.com/<...>/reports/<...>/ReportSection?filter=<...> .
I don't know which of the two changes resolved it, and I still don't know what caused it in the first place, but maybe this still helps some other reader in the future.
Best Regards