SSRS to Powrer BI Builder

[RaedTattan]

We are currently working on migrating approximately 15 SSRS (v 2012) reports to the latest version of Power BI Report Builder.

The issue I'm facing is that everything works fine when I open the report in Power BI Report Builder on the desktop (data, connections, dataset, filters, etc.). However, after publishing the report to the Power BI Service, I encounter a problem:

Some filters become inactive and mandatory, making it impossible to execute the report. This is because some parameters appear as inactive and blank.

I would appreciate any help or suggestions if you have encountered this issue or know of a solution.

[v-dineshya]

Hi @RaedTattan ,

Thank you for reaching out to the Microsoft Community Forum.

Hi @AmiraBedh , Thank you for your prompt response.

Hi @RaedTattan , In addition to @AmiraBedh  response, I am adding some more points.

Please check below things.

1. Check each parameter has either default value or available values from a query. Avoid leaving required parameters without values. If parameters depend on each other, make sure the sequence and logic are correctly defined and tested.

2. After publishing, go to the dataset settings in Power BI Service and set up the correct credentials and check the gateway is configured. Use OAuth2, Basic or Windows Authentication.

3. Try to publish a version of the report with few or simple parameters to isolate the issue.

4. If the report logic is too complex for Report Builder, rebuild it in Power BI Desktop for better compatibility.

5. Check all datasets are properly configured to run without prompts. All parameters used in queries are mapped and have default values.

6. In Report Builder, for each parameter, Go to parameters properties --> Available Values, set "specify values" or check dataset query works in service. Add default values even if it is "All".

7. Some SSRS 2012 features may not be fully supported in Power BI service. Open RDL file in Power BI Report builder and rebuild parameter logic.

I hope this information helps. Please do let us know if you have any further queries.

Regards,

Dinesh

[v-dineshya]

Hi @RaedTattan ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @RaedTattan ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[v-dineshya]

Hi @RaedTattan ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.

Regards,

Dinesh

[AmiraBedh · Accepted solution]

Hello !

Thank you for posting on Fabric community !

Hard to tell without seeing the original file but here is my assumption so far :

• If parameters are dependent on one another (cashier list is filtered based on branch), and if one of the upstream parameters has no value downstream ones appear blank or inactive.
• In SSRS, default values might have worked fine via expressions or queries but in PBI service, if default values are missing or not set correctly, the parameter UI may break.
• If a parameter uses a dataset to populate available values, and that dataset errors out or returns no data on the PBI service, the parameter remains blank or inactive.
• If the dataset requires a gateway (on-prem SQL), and it’s not properly configured in the PBI service, then the datasets that feed parameters can fail.
• PBI Report Builder does not support cascading multi-value parameters the same way as SSRS. Also, expressions like =Today() in default values can behave differently.

Try to check the points I mentioned you will for certain find the issue ! 😄