Forum Discussion
Assistance Required for Resolving URL Character Limit Issue in Paginated Report
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.
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.
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.