Forum Discussion
PBIRS Subscription Parameter Reverts to “Leave NULL” After Saving
Thank you for the detailed explanation. I would like to add some important context from our side.
We recently completed a large‑scale migration from SSRS SharePoint Integrated Mode to Power BI Report Server (PBIRS), and we have thousands of paginated reports that all follow the long‑established pattern where:
- NULL parameter value = “ALL”
- Default value of the parameter is also NULL
This design has worked perfectly in SharePoint Integrated Mode for many years, including for interactive execution and for subscriptions. Subscriptions always respected the report’s default parameter settings.
However, in PBIRS (May 2025 release), subscription parameter values are automatically changed from “Use default value” to “Leave NULL” immediately after saving—regardless of how the RDL is defined. This creates functional inconsistencies and makes it extremely difficult to manage subscription behavior across so many migrated reports.
Because of the scale of our environment, modifying each report or redesigning parameter patterns is not feasible.
Could you please clarify:
- Is this issue fixed in the September 2025 release or any more recent PBIRS release?
- If not, is this behavior planned to be fixed in an upcoming release?
This subscription behavior worked reliably in SharePoint Integrated Mode, so we want to understand whether PBIRS will eventually bring parity, especially for enterprises with large SSRS workloads.
Thank you again for your support—we appreciate any additional guidance you can provide.
Community SupportHi mohanmoni1,
Thanks for the follow-up question.
Thank you for providing the additional migration context that clarification is very important. You are right that in SSRS SharePoint Integrated Mode, subscriptions reliably respected report-level default parameter values, including the long-established pattern where a NULL default represents ALL. In Power BI Report Server (PBIRS), subscription handling was redesigned, and parameters are currently stored as explicit values at the time the subscription is saved, rather than re-evaluating the report’s default definitions at execution time. This architectural difference explains why subscriptions now normalize “Use default value” to “Leave NULL,” even when the RDL itself has not changed, and why this behaviour becomes especially disruptive in large, migrated SSRS environments.
At present, there is no public confirmation that this behaviour has been changed or fixed in the September 2025 PBIRS release or any later release, and we don’t have visibility into a committed timeline for restoring full parity with SharePoint Integrated Mode for this scenario. This is understood as a platform behaviour difference rather than a report-specific issue, and we recognize the operational impact it has at enterprise scale.
Hope that clarifies. Let us know if you have any doubts regarding this. We will be happy to help.
Thank you for using the Microsoft Fabric Community Forum.
Community SupportHi mohanmoni1,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.
Thank you.