07-20-2018 11:12 AM - edited 07-20-2018 11:27 AM
I have been running into a publish issue with several reports on various workspaces over the last few months where I make changes in Desktop View, save, and re-publish, but the changes don't actually make it to the workspace. I get a 'Publishing succeeded' message in Desktop View, and when I click the link in the 'succeeded' message, it takes me to the Report on the workspace, but it takes me to an old version of the Report on the workspace, and no matter how many times I try, or how many days I wait, the changes do not actually ever make it up.
There are no errors reported on the workspace that I can find. I've confirmed the service and my Desktop client are both running latest versions.
The only work around I've found so far is to delete the Reports from the workspaces entirely and republish, however this breaks the links to the Reports and we have a wide variety of folks across our org using this links, sometimes for well over a year, and I don't want to break their setups by deleting and republishing. This will also reset the usage metrics on the Report, and we use those metrics a lot internally to gauge Report priority.
This has happened for both Direct Query workbooks and Import Query workbooks, and seems like it starts happening after the first dozen pushes or so. Our Reports go through a lot of churn with new visuals, etc being added and/or tweaked, so most of our Reports will go through a few dozen 'changes' over the years.
07-23-2018 09:03 AM
I have tried refreshing the page, using a browser on someone else's PC that shouldn't have any history with the site already, waiting many days, etc.
For further information, any changes to the data do make it up, it's only changes to the report part that don't make it. So if I change colors on a visual, change the page size and add extra parts, add extra pages entirely, swap values on an axis, or something like that, those changes don't make it up, but if I change the definition of a calculated column, the new calculation within the calculated column makes it up.