Forum Discussion
Dynamic subcription parameter not saving
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.
Hi tbuttars ,
We’d like to follow up on your support ticket. Has the issue been successfully addressed?
If a solution was provided, we’d truly appreciate it if you could share your experience or any relevant details, your input could be valuable to other community members.
Thanks again for being an active part of the Microsoft Fabric Community!
Hi, this exact issue is happening for me still. Can you please help?
Hi RyanMcBride ,
Just checking, did you get a chance to raise a Microsoft Support ticket as suggested earlier? If yes, feel free to share (if possible) the outcome or any updates from the support team that may also help other community members facing similar behaviour.
In the meantime, since the issue persists across new subscriptions and workspaces on a P1 capacity, it continues to look more like a service-side behaviour rather than a configuration issue. If you haven’t opened a ticket yet, I would recommend doing so, as the support team can review the backend logs for the subscription save operation.
Best Regards,
Community Support Team