Forum Discussion
Dynamic subcription parameter not saving
I have a dynamic subscription to a paginated report that has been running for a year and turned off due to reaching the end date.
But when I try to restart it, the default parameters will not update back to dynamic.
I tried a new dynamic subcription and connented to the data model and set up the parameters but I see this error "to save this subscription, return to the report and set all required parameter values". I did not have this issue last year.
If I save the report it keeps the default parameter of the report instead of the dynamic logic.
How do I fix this issue?
I found the solution for this while waiting for our Mircosoft Partner to submit a ticket on my behalf.
The issue was a Hidden Parameter that just grabbed yesterdays date as the AsOFDate. The data is always from a snapshot taken each night at end of day.I removed this parameter and added a query to get Datetime for my local timezone. And now the Dynamic subscription will save and run as it was for the past year.
Important note that parameter was used in the subcription for that past year without issue. so Mircosoft has changed something.
This is the reply I got from our Microsoft Partner but, I told them I found a fix before they submitted a ticket to Mircosoft"The reason this started failing now is that the validation for all required parameters has changed since the original subscription as started. That validation only happens when the report is set up.Changing the "Start" and "End" dates for the subscription required the new, more complete validation to run. Power BI dynamic reports are "all or none" validation and, as you noticed on our call, it was calling attention to this but not directly naming which required parameter was breaking.Older subscriptions were often allowed to:- Use GETDATE() / CURRENT_TIMESTAMP
- Use dataset‑derived “today” values
- Use non‑deterministic default expressions
Newer validation paths:- Expect deterministic, scalar, subscription‑safe parameters
- Reject parameters that can’t be resolved at save time
- Do so silently
When validation fails, the report config defaults to a single parameter. So that was a red herring.Here is suggestions for how to add As of Date again:- Hard‑code relative date logic in the query (e.g., “last completed week”)
- Push the date into the dynamic subscription dataset as a resolved value
- Use a non‑required date parameter with a literal default
- Remove the parameter and compute date internally "
@RyanMcBride Hope this helps you.
9 Replies
Hi tbuttars
What I would recommend doing is looking to create a dynamic report paid subscription again could potentially since you created it over a year ago there could have been some changes and that is why when you try and edit the existing one it is not working. Create a dynamic subscription for a paginated report - Power BI | Microsoft Learn
I appericiate the reply but I stated in my post that I tried a new dynamic report paid subscription and still getting the same issue.
I checked the data source as well, I dont see any issues.
I even tired uploading the report to a new workspace, still get that error message.Hi tbuttars
Can you please confirm are you using a Power BI Pro license, Premium per user license or Fabric license? Create a dynamic subscription for a paginated report - Power BI | Microsoft Learn
I found the solution for this while waiting for our Mircosoft Partner to submit a ticket on my behalf.
The issue was a Hidden Parameter that just grabbed yesterdays date as the AsOFDate. The data is always from a snapshot taken each night at end of day.I removed this parameter and added a query to get Datetime for my local timezone. And now the Dynamic subscription will save and run as it was for the past year.
Important note that parameter was used in the subcription for that past year without issue. so Mircosoft has changed something.
This is the reply I got from our Microsoft Partner but, I told them I found a fix before they submitted a ticket to Mircosoft"The reason this started failing now is that the validation for all required parameters has changed since the original subscription as started. That validation only happens when the report is set up.Changing the "Start" and "End" dates for the subscription required the new, more complete validation to run. Power BI dynamic reports are "all or none" validation and, as you noticed on our call, it was calling attention to this but not directly naming which required parameter was breaking.Older subscriptions were often allowed to:- Use GETDATE() / CURRENT_TIMESTAMP
- Use dataset‑derived “today” values
- Use non‑deterministic default expressions
Newer validation paths:- Expect deterministic, scalar, subscription‑safe parameters
- Reject parameters that can’t be resolved at save time
- Do so silently
When validation fails, the report config defaults to a single parameter. So that was a red herring.Here is suggestions for how to add As of Date again:- Hard‑code relative date logic in the query (e.g., “last completed week”)
- Push the date into the dynamic subscription dataset as a resolved value
- Use a non‑required date parameter with a literal default
- Remove the parameter and compute date internally "
@RyanMcBride Hope this helps you.
