Forum Discussion
Assistance Required for Resolving URL Character Limit Issue in Paginated Report
You're encountering a URL length limitation when linking from a parent report to a child report in your paginated report. This happens because selecting many parameters, especially "Select All" for Zone1Wo, creates an extremely long URL that exceeds the limit Report Server and browsers can handle. The best solution is to avoid building the URL altogether and instead use Report Server's built-in parameter passing. Configure the drill-through action in the parent report to directly pass parameter values to the child report, which should have corresponding parameters defined. This eliminates the URL length issue as Report Server handles the transfer behind the scenes. If direct parameter passing isn't possible, use a stored procedure in the child report. Pass a small identifier from the parent to the child, and the stored procedure uses this identifier to retrieve the full parameter values from a temporary table or database table. Avoid URL shortening services if possible. Consider redesigning parameter selection if feasible, perhaps using cascading parameters or improved multi-select controls. After publishing to Power BI Service, you can't fix this by modifying the report definition directly; you must implement a server-side solution (parameter passing or stored procedure) before publishing. For passing multiple values, instead of joining with commas, pass a single comma-separated string of IDs and then split this string in the child report's query using a function like STRING_SPLIT to use it in an IN clause, further reducing the URL length and improving efficiency.