Forum Discussion
Refresh failed due to missing column
This will be considered a model change. You can either download the report and open it in desktop, or if you are an admin in the workspace, you can enable the ability to edit data models in the service. Workspace Settings > Power BI > General > Data Model Settings
I don't understand wy there are restrictions on large transfers. That seems a bit arbitrary. If that is the case you should move to splitting this report to a thin report that is just a few MB in size pointing to the model in the service you manage by Tabular Editor. You make all changes in the service directly and publish a revised report only. That link would never change.
You could also split to a thin report and model and do this:
- Point the thin report to current semantic model
- update semantic model and do your publish thing, which creates a new semantic model in the service.
- Change the thin report on your PC to point to the new semantic model
- Publish the report
In this case, the report link never changes so your users dont know there has been a change.
But if you continue the current path of a new semantic model and report with each publication, you will have to give a new link every time, a major hassle.
The report isn't shared through app, it has been shared using the link to the report. When I reupload I need to share that link with anyone who had access to the previous version. Unless there is something simpler that i'm missing?
Is it in a workspace? It should not require a new link, it should just work. Is it in "My workspace?" That still shouldn't require a new link, unless you are sharing it via Publish to the Web, which has no security but it does require a new link with each republish.
It's in a private workspace that my immediate team have access to - I then grant access and share the link for this specific report to other people or groups so they only have access to this one report.
I should also add that I can't 'publish' this report through Power BI desktop as we have internal restrctions on large file transfers. I have to upload through sharepoint and refresh the report in PBI service so when I reupload, it uploads as a brand new version rather than replacing the one already there.
I don't understand wy there are restrictions on large transfers. That seems a bit arbitrary. If that is the case you should move to splitting this report to a thin report that is just a few MB in size pointing to the model in the service you manage by Tabular Editor. You make all changes in the service directly and publish a revised report only. That link would never change.
You could also split to a thin report and model and do this:
- Point the thin report to current semantic model
- update semantic model and do your publish thing, which creates a new semantic model in the service.
- Change the thin report on your PC to point to the new semantic model
- Publish the report
In this case, the report link never changes so your users dont know there has been a change.
But if you continue the current path of a new semantic model and report with each publication, you will have to give a new link every time, a major hassle.