Forum Discussion
Report not updating
Hi Greg_Deckler - this is in Desktop, but it's the same in Service as well and I've checked the filters.
My route for creation was to create a new report > copy visuals from an existing report (now deleted) > connect new report to the shared semantic model as the other working report.
The visuals etc are all good, but the underlying data from SharePoint when changed is not coming through to the new report, but is for the other report.
As mentioned, the other report from the semantic model has a table view, the new report doesn't.
When you hit refresh in Desktop, you get a 'working on it', but it doesnt mention the lists it's getting the updates from, which it does do in the other report
SteveMForm OK, so if the 2nd report is linked to the semantic model of the 1st report and you refresh the 1st report in Desktop, the 2nd report will not reflect the new data until you publish the 1st report to the Service and then refresh the visuals on the 2nd report. The reason you are not getting the updates from the same way in the 2nd report is that the only connection is the semantic model, not the actual source systems. Refreshes do not "pass through" going from a connected semantic model back to the source systems when done from a report that is using the semantic model as a source.
The type of visual is not likely to be an issue.
Hi Greg_Deckler erm- did that, and it's gone a bit loopy and the Horizon report still updating values.
Seems like the publishing back has created a new semantic model for the other report- Front Door Report
SteveMForm Did you, at some point, rename the report? If you do that, the original report will not be overwritten but instead you will get a new report and a new semantic model in the Service. And, if you connected your 2nd report to the original, original semantic model for the 1st report then, yes, nothing is going to get updated because when you republish, it is going to the 2nd version of your 1st report. Essentially, if you did a rename, you've got 3 reports and 2 semantic models at this point. Not sure if that's the issue but could be.
Hi Greg_Deckler - I think you might be onto something- it's almost pythonesque in its convulutedness.
I did rename the report- and the semantic model at one point (BA Core).
Would it be best to delete the newly created semanitc model and report (front door), create a new report dirctly to the sources and then delete the 2nd report (Horizon, so they both have their own direct link to SharePoint.
Managing workspaces, reports and models seems to be a bit light on MS documentation (ie what not to do, what to do, and the consequences of your actions/ things to avoid/ best practice)?