Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Regular SSRS reports on our PowerBI Server have DATA Driven subscriptions EVERY single one after upgrade to the latest version (
15.0.1104.239). We started getting :
An error has occurred.
Something went wrong. Please try again later.
On DataSet Error: There's something wrong with your dataset, click below to edit.
Every Data-Driven subscription has this issue now.
Anyone have code or something that fixes this? The data sets work fine we validate and save them it's fine and works when scheduled. We get the error only when we Edit a data-driven subscription these errors above come up. If we don't touch subscriptions it works just fine but when we edit them we get an error, or if we create a new subscription we get the error.
Any fix in 2024 to this issue?
+1 running patched/updated October 2020 release
This week creating a Flow to export and email XLSX version from PBI Service Paginated Report, but that is a LOT more work than the built on-prem subscriptions. Also, PBI Service is not our production environment so I don't like having it be the odd-man out initially we plan to keep SSRS on-prem and just move PBI reports.
Anyone who has upgraded to the jan 2021 version of PBIRS? Who can confirm this is fixed? The changelog mentions the following: Fixed issue editing data driven subscriptions in portal.
+1
Having the same problem with datadriven subscriptions since the October 2020 update
Hi, we have the same issue here as well...
All Data driven subscriptions given an error on the dataset when editing. Validating the dataset is a workaround, so the subscription can be edited and works fine afterwards. But when going back to edit ... again same issue...
When I search in the logging i find this:
2020-11-23 11:20:15.1945|INFO|80|Received request GET /api/v2.0/subscriptions(42b6617f-aca4-40f5-9f8e-eb566b176d13)| RequestID = s_2de576fe-354a-4020-bde8-910b35a81efb
2020-11-23 11:20:15.3351|INFO|42|Sending response. Response code LOCAL\thvpu 200, Elapsed time 0:00:00.1426276| RequestID = s_2de576fe-354a-4020-bde8-910b35a81efb
2020-11-23 11:20:15.3507|INFO|80|Received request POST /api/v2.0/DataSources/Model.GetQueryFields| RequestID = s_83328432-b73e-4523-b0e4-165ec5b4832a
2020-11-23 11:20:15.3507|WARN|80|BadRequest, Errors: Value cannot be null.
Parameter name: item| RequestID = s_83328432-b73e-4523-b0e4-165ec5b4832a
Hi,
did you ever find a solution to this? I experience the same behavior...
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |