Slider's selected value is invalid even after refresh

[jbrandt]

While developing a report in a dev environment, a slicer value is selected.  Upon completing the report the report is promoted to a QA environment and published into PBI Service where the data set is refreshed.  Upon opening the report the slicer still shows the value that was selected in the development environment, a value that does not exist in the current dataset. 

The impact from this issue is that the user will see an empty report since the selected value doesn't exist.  Not a great first impression ;-). 

The obvious solution/workaround (manual) is to clear all slicers before promoting or publishing.   However, a better solution would be for the PBI Service to validate slicer values whenever the data set is refreshed and clear them, or have a setting to enable clearing them if that is the desired behavior.   Going one step further, it would be best to allow some logic to dynamically select a slicer value for that initial presentation, e.g. set the first value found as selected, i.e. instead of starting with 'All' values selected, which can be similarly meaningless, enable just one value to be selected. 

[v-qiuyu-msft]

Hi @jbrandt,

The report published to Power BI service should be the same as the last saved status in Power BI desktop before publish. In your scenario, when you move the report to QA environment, please open the report in Power BI desktop firstly to make sure all are good then publish to service. 

For your requirement, you can submit a idea: https://ideas.powerbi.com/forums/265200-power-bi-ideas

Best Regards,
Qiuyun Yu

[jbrandt]

That doesn't make any sense.  You're assuming the data in imported, which it is not. Data is retrieved from a REST API.  The data source in QA is different from what it will be in production so the situation will still persist and the slicer will still have values that don't exist in the underlying dataset. 

[v-qiuyu-msft]

Hi @jbrandt,

Did you mean you get data from REST API in Power BI desktop then publish to service? Would you please share some screeshots to clarify the issue so we can test it? 

Best Regards,
Qiuyun Yu 

[jbrandt]

Initially,yes, the data comes from a REST API call from the desktop, then is published to a workspace with new credentials, pointed at a new source (same type of data, but a different client domain - we are an ISV).  The report is immediately refreshed when published so the imported data is replaced from the new data source, we can't have one client see data from another.  However, the slicer hangs on to values from the imported data, filtering on a value that doesn't exist.  Once the slicer is clicked, the old value disappears and only current, valid values remain, but the initial view of the report is empty.  

Kind regards, 

John

[v-qiuyu-msft]

Hi @jbrandt,

For this issue, I would suggest you create a support ticket to let Microsoft engineer look into your environment to see if there is any workarounds. 

Best Regards,
Qiuyun Yu