Forum Discussion
Assistance Required for Resolving URL Character Limit Issue in Paginated Report
- 1 year ago
Hi Heena_9980400
If your datasSource (e.g., SDRDS_wali) is already configured and connected to your database, you do not need to create a new one. Try to create a new dataset under this data source.
Please follow the below steps to create a New Data Source (If required):Step1: If no data source exists or if you want to use a different one:
- Right-click on Data Sources (in the left panel).
- Click on "Add Data Source".
- Give it a name (e.g., MyDataSource)
- Select "Use a connection embedded in my report".
- Choose your database type:
- SQL Server → Select "Microsoft SQL Server"
- Enter connection details (server name, database name, authentication).
- Click "Test Connection" → OK.
Step2: Create a Dataset with a Query
- Right-click on "Datasets" → Click "Add Dataset".
- Enter a dataset name (e.g., MyDataset).
- Select "Use a dataset embedded in my report".
- Choose the data source you created (or an existing one).
- Enter the SQL query, adjusting for your database type:
SELECT * FROM my_table WHERE Zone1Wo IN (SELECT value FROM STRING_SPLIT(@Zone1Wo, ','))
If the above information helps you, please give us a Kudos and marked the reply Accept as a Solution.
Thanks,
Cheri Srikanth
Hello Heena_9980400
The problem seems here because of encoding overhead of url.
URL Encoding Overhead
• Special characters (spaces, commas, symbols) are URL-encoded, adding extra characters:
• Example: A space becomes `%20` (3 chars), and `&Zone1Wo=` becomes `%26Zone1Wo%3D` when encoded.
• Impact: A URL with 1800 visible chars can exceed 2040 after encoding
Try these
Configure your paginated report to use default parameter values from the dataset. This ensures parameters are omitted from the URL unless explicitly selected by users, significantly reducing URL length:
• Set parameters like `Zone1Wo`, `ShiftList`, etc., to default to “Select All” values in the report itself.
• Modify your URL generation logic to only include parameters where users have made selections, avoiding unnecessary duplication
Instead of `&Zone1Wo=value1&Zone1Wo=value2`, use `&Zone1Wo=value1,value2`.
• In the child report, split the comma-separated string back into individual values using expressions like `Split()`
https://www.kerski.tech/bringing-dataops-to-power-bi-part42/
Hope this helps
Please accept the solution and give kudos if this is helpful