Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello,
Few of our Power BI subscription run successfully for few after configuration. But, stop working after that with te below error under result:
"The subscription contains parameter values that are not valid."
When I check the subscription settings, I see that two of the parameters get reset to default .
Any idea about teh root cause please?
Solved! Go to Solution.
I'm assuming this is actually for an SSRS (paginated) report in report server?
Here is what happened when I had this same issue
I developed a report in the test environment. I had a parameter which took it's available values from a query. That query looked up all the values in "CreatedByUser" column from table ABC in SQL. Great so now I have 10 users in the report drop down.
When I published to the live environment, i setup a subscription and changed the parameter to "User10". problem was, "User10" hadn't created any data in our table in live yet! so the subscription failed with the same reason you have listed above.
I changed my code to the below, to now populate the username dropdown:
SELECT distinct username FROM table_ABC
union
'User10".
No longer matters if there is no data in there for this user when I deployed and setup the subscription. Just means they'll get no data in the report.
I'm assuming this is actually for an SSRS (paginated) report in report server?
Here is what happened when I had this same issue
I developed a report in the test environment. I had a parameter which took it's available values from a query. That query looked up all the values in "CreatedByUser" column from table ABC in SQL. Great so now I have 10 users in the report drop down.
When I published to the live environment, i setup a subscription and changed the parameter to "User10". problem was, "User10" hadn't created any data in our table in live yet! so the subscription failed with the same reason you have listed above.
I changed my code to the below, to now populate the username dropdown:
SELECT distinct username FROM table_ABC
union
'User10".
No longer matters if there is no data in there for this user when I deployed and setup the subscription. Just means they'll get no data in the report.
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
1 |
User | Count |
---|---|
8 | |
4 | |
4 | |
3 | |
3 |