We are running 14.0.600.398 and are seeing an issue with query backed parameters in subscriptions. The report will run and the parameter dropdown will work in the regular report. However, when trying to create or change a subscription "entity" parameter above shows no options. I was seeing the other issue of "Something went wrong" but that seems to have been resolved in .398.
I can also reproduce the issue in Power BI report server August preview version 14.0.600.398. If the parameter values comes from a dataset query, parameter values will not be listed when we create a subscription.
But if the parameter values is specified values, parameter list is available for us to choose when we create a subscription.
In your scenario, if the Entity doesn't have too many values, you can try the specified values for parameter temporarily.
Any updates on this, we are running the Oct 2017 release and are still experiencing this issue with being able to Enter a Value for a parameter that references a Shared Dataset. All we see is the Select All option like the issue posted here and no values like we currently see in our SSRS 2016 environment.
1. Build number - Version1.1.6514.9163(October 2017)
2. No Error messages are being put in the ReportingServicesService*.log file with any information details, just every time we go into the subscription it states the following:
An error has occurred.
Something went wrong. Please try again later.
3. Get the same issue in Chrome and IE
These reports are referencing Shared Datasets and the values are cascading, so based on another parameter value selection that is filtering the list of values. This works in SSRS 2016, but not working in PBI RS Oct 2017.
So maybe it is because of the filtering from the first parameter value? Does that work for you if you set a parameter up like that?
Thanks Dan, that helped! We are able to repro the issue with cascading parameters now; its a product bug. Only workaround I can think of is to specify values in report definition as suggested earlier in this thread. Apologies for the inconvinience caused. We will fix the issue soon and will let you know once a newer build is available to download.
:'( figures. I am glad I was able to assist with the details. Keep me posted once the fix is available (hopefully in the Dec preview...haha). Thanks for looking into this so quickly, greatly appreciated.