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 (12)
RE: Publish a report without updating Dataset
This is a simple feature to implement with huge gains for the Power BI developer community.This feature request aligns with the two part "Visualization / Data Developer" model where the two specialists in separate fields of BI can collaborate on the same report. Without the ability to deploy either of the two sides separately, it is difficult to implement Microsoft's recommended best practice for developing at scale.Using a Live Connection does not provide the same experience to the end users. The drill into details when analyzing in excel only works via Direct Import mode.CI/CD is hindered from long data update times when only a visual is needed quickly during business hours.Publishing a report visual should be as quick as a simple update statement of a small row, but what we have to do now is the equivalent to dropping and reloading all tables in a database.
RE: Publish a report without updating Dataset
This makes total sense we spend a lot of time uploading the data with the report for the Power BI service to immediately perform a refresh. it would make sense to:publish report only (without data)include an option to refresh the data in the Power BI service or not (especially if the schema didn’t change)
RE: Publish a report without updating Dataset
This feature is a must, please rollout
RE: Publish a report without updating Dataset
This feature is a must, please rollout
RE: Publish a report without updating Dataset
we really need this solution because sometimes we don't need the dataset published when you or User or Capacity Premium.
RE: Publish a report without updating Dataset
when you crate a report connected to a data set to overcome this, you can't edit the calculated field as it would be stored as value in the dataset which is fraustrating.
RE: Publish a report without updating Dataset
I'd love to have a selection when i click "Publish" in PowerBI Desktop, that allows me to selectAllData onlyReport onlyI have big reports regarding Pages, Functionality and Data Size. Changes to the frontend only require currently someworkarounds to either separate the dataset from the report or making the changes in the service only and doing them again in the local file are tedious.Thank you!
RE: Publish a report without updating Dataset
We are receiving an error when publishing a larger PBIX from a Report that sources data from a Data Flow. The initial publish works usually, but a republish fails 4/5 times. Decoupling report publishing from the data especially when the data and/or model has not changed in any meaningful way (e.g. label or color change) is the main objective of this request. This is especially relevant for more and more customers working from home over non-corporate internet connections. This change would avoid the wait times of reuploading data that has not changed and any accompanying errors due to size, network interruptions or time. It would increase customer satisfaction and reduce support requests.
RE: Publish a report without updating Dataset
This option is in Power BI. Import data with POWER BI dataset service. When publishing it won't create a new datasets. Also you cannot refresh the dataset from the desktop POWER BI app.
This option enable to create reports on a desktop POWER BI app with no change in dataset. Perfect!
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?