Assistance Required for Resolving URL Character Limit Issue in Paginated Report

[Heena_9980400]

Hi Team,

I hope this email finds you well. I am reaching out for assistance in resolving an issue I am encountering with a paginated report.

The report is designed such that, after selecting multiple parameters, clicking on the Reject column record redirects to a child report.

However, an error is displayed:

"The report parameter list exceeds the limit of 2040 characters. Please reduce the selected values for Zone 1, 2, 3 WO# dropdown."

To provide more context, I have attached the expression currently being used to achieve the functionality:

=IIF(LEN(Globals!ReportServerUrl + "?%2fBRS+Singapore%2fPA+Reports%2fTIJ4%2fSGP_Falcon%2fProduction+Reports%2fReject_Pen_summery_yield&rs:Command=Render&rc:Toolbar=False&StartDate= " & Parameters!parstartdate.Value & "&EndDate= " & Parameters!parenddate.Value & "&ShiftList= " & Join(Parameters!parshiftinclude.Value, ",") & "&moduleky= " & Fields!MODULE_DIM_KY.Value & "&pruntype= " & Join(Parameters!paruntype.Value, ",") & "&Zone1Wo= " & Join(Parameters!Zone1Wo.Value, "&Zone1Wo=")) <= 2083, "javascript&colon;void(window.open('" + Globals!ReportServerUrl + "?%2fBRS+Singapore%2fPA+Reports%2fTIJ4%2fSGP_Falcon%2fProduction+Reports%2fReject_Pen_summery_yield&rs:Command=Render&rc:Toolbar=False&StartDate= " & Parameters!parstartdate.Value & "&EndDate= " & Parameters!parenddate.Value & "&ShiftList= " & Join(Parameters!parshiftinclude.Value, ",") & "&moduleky= " & Fields!MODULE_DIM_KY.Value & "&pruntype= " & Join(Parameters!paruntype.Value, ",") & "&Zone1Wo= " & Join(Parameters!Zone1Wo.Value, "&Zone1Wo=") + "'))", "")  

The main concern is ensuring that even after selecting "Select All" for the parameters, the report does not exceed the character limit and continues to function without errors.

If this issue cannot be resolved due to known limitations, I would appreciate any suggestions for alternative approaches. Specifically:

1. Is there a way to handle this within the report itself, avoiding the need to jump to a child report?
2. After publishing to Power BI Service, can any modifications be made to overcome this limitation?
3. Are there any other workarounds to ensure that selecting "Select All" does not lead to an error?

Looking forward to your valuable suggestions and assistance!

Thank you.

Best regards,
Heena Kousar

[Poojara_D12]

Hi @Heena_9980400 

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.

[Anonymous]

Hi,rohit1991 and tharunkumarRTK ,thanks for your concern about this issue.

Your answers are excellent!
And I would like to share some additional solutions below.

Hello,@Heena_9980400 .

I hope my suggestions below will help you

There is a known issue with the url parameter length exceeding the limit.
Could you try adding a new column for your data source to pre-process the data at the data source. I noticed that you have multiple fields that need to be filtered.
You could try combining URL combinations of certain parameters into one specific type. For each type, you tag it with the corresponding index.
like this.

parshiftincludeB+parenddateC =newcolumnValuesBC
parshiftincludeN+parenddateM =newcolumnValuesNM
...

Map each different URL combination to new parameter values of shorter length. (use the values of “newcolumnValues”)
Report query data using these actual shorter values of the parameters for paginated reports.
This might shorten the length of the final URL parameter.

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Heena_9980400]

hi @Anonymous ,

Thanks for your reply!

you mean to say adding these details in expressions or in the backend.

if you could please help me understanding this for better implemtation. that would be very helpful thank you.

[Anonymous]

Hi,@Heena_9980400 .Thank you for your reply.

If your URL parameters are only used for querying data, you can try processing the data source.
1.Parameter Compression: Add multiple marker columns and use short identifiers or codes to replace the original long parameter URLs. For example, you can convert long string parameters into short hash values or unique identifiers. Use these identifiers as new query parameters to reduce the likelihood of exceeding the URL parameter length limit.
2.Identifier Replacement: Replace multiple long parameter combinations in the URL by generating a unique identifier to replace the original long parameter combinations.
(1) Generate Identifiers: Generate a unique identifier for each parameter combination. This identifier can be a short string, hash value, or UUID. For example, you can use MD5 or SHA-256 hash functions to generate identifiers.

(2) Store Mapping Relationships: Store the mapping relationships between identifiers and actual parameter combinations on the server or in the database. Create a mapping table that contains the identifiers and their corresponding parameter combinations.

(3) Replace Parameters: Use the generated identifiers in the URL to replace the original long parameter combinations.


I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[rohit1991]

Hi @Heena_9980400 ,

Your report exceeds the 2040-character limit due to long parameter lists.

Solutions:

1. Reduce URL Length:

   • Pass IDs instead of names
   • Use abbreviations
   • Limit selections instead of "Select All"

2. Use Drillthrough Reports:

   • Avoid long GET URLs
   • Pass parameters through report actions

3. Store Selections in SQL:

   • Save selected values in a temporary table
   • Pass a Session ID instead of long lists

4. Optimize "Select All":

   • Pass a default value ("All") instead of listing all selections

[tharunkumarRTK]

@Heena_9980400 

If I am not mistaken you are drilling through from one paginated reort to the other using URL parameters and all the filter values are within the URL. You are hitting the max character limit due to which you are facing an error.

I have a couple of suggestions, 

1. Instead of using URL paramters and constructing a Child report URL, cannot you use the "Go to report" and pass the filter values? You can follow the instructions explained here 

https://www.youtube.com/watch?v=k7pZzwgXW-g

2. Incase if you are passing the actual field values within the URL parameter cannot you try reducing the number of charaterts by passing their IDs. IDs will have less number characters than the actual values.

Need a Power BI Consultation? Hire me on Upwork

Connect on LinkedIn

Did I answer your question? Mark my post as a solution!
If I helped you, click on the Thumbs Up to give Kudos. Proud to be a Super User!