Forum Discussion
Issue with autorefresh while publishing PBIX file
amitnhpBIPublishing the Desktop file with the same name as the dataset will always update the data in the Service immediately. I would recommend one of the following if you don't want an immediate publish.
1) Publish to a Dev workspace if you need to verify output in the Service
2) Save the PBIX as a different name and publish before publishing the original
Both these assume you want some level of data verification in the Service prior to pushing the change to the dataset that is shared. There is no Dev->Prod rolled approach at the moment.
If you are talking about the visual layout, then there is a 3rd option which is better. You could publish an App, this would allow you to use a Dev->Prod roll out for changing visuals etc in that you have to manually publish the changes to the shared App prior to the end user seeing them.
Thanks for your response. In my case, i have to make changes directly in my production PBX file which is triggering the job on the server .
One weird issue i noticed today is same file when my colleague is publishing on the server,it is not triggering On Demand refresh.
Do you know if there is any user setting which can cause the difference in behaviour.
amitnhpBI I am not aware of any setting, but if your colleague is not refreshing the data set in the PBIX file, and just making visual changes or adding metrics without refreshing then the dataset in the PBIX file wouldn't be new, and thus not refresh the data in the Service upon publish.