on 30 Nov 2017 20:15:34
When a report is published from PowerBI Desktop, there is no way to publish without publishing the dataset as well.
This forces me to update the dataset again on my Desktop (which sometimes takes a lot of time) before publishing it.
Why can't I publish the new report and have it use the dataset that is already uploaded?
- Comments (13)
RE: Publish a report without updating Dataset
I understand the potential workaround of referencing a dataset already on the service, but this problem does need to be addressed. If I decide to only change the color on a visualization (on the souce .pbix, not editing in the service), why do I need to replace the whole dataset (especially when the one I loaded into Power BI Desktop may be older than the one on the service using a gateway connection).
It also is a "wonky" user experience to have the extra "Replacing dataset" pop up when publishing - one saying "Do you want to replace the existing dataset with this one?" with only the options of "Replace" or "Cancel". The answers should be "Yes" or "No" based on the question.
So, if the workaround of using a pre-existing dataset and recreating the pbix for a report change is going to remain, can we at least change the question on the "Replacing dataset" pop up to avoid implying that there is another option to publish WITHOUT replacing the dataset?
RE: Publish a report without updating Dataset
The problem with that is that PowerBI Service has a ram limit of 1GB and the reports that connect directly to VertiPaq work fine.
RE: Publish a report without updating Dataset
I get around this by building a dataset report (the delete the report) . Then I make new report only views with a direct connect to my data model in power bi service. That way you can have multiple reports hinged off one dataset and can just publish the report on its own