New Power BI Reports from a Golden Dataset - Excelerator BI

New Power BI Reports from a Golden Dataset

This is a further (fourth) update/edit to this article I first wrote in Apr-17.  I then updated it again in Jan-18, Jun-18 and again now in May-20 (Jason did a full review this time around).  When I update my articles, I change the original post with the latest and best information available at the time – that way only the current/latest version is available online preventing people stumbling on old advice.

The original idea of a Golden Dataset was to

  1. Load a PBIX into a OneDrive or SharePoint folder
  2. Import the Golden Dataset into one or more workspaces (each workspace will have an identical duplicate copy of the dataset).
  3. Rely on the capabilities of PowerBI.com to automatically refresh the dataset in all workspaces everytime the source (step 1 above) is changed.

This is no longer the most effective way of achieving a Golden Dataset.  This article explains the more modern approach, which is to use shared datasets instead.  Further, the concept of the Golden Dataset now has very wide reaching impacts across concepts that include shared datasets, shared workspaces, certified datasets and  lineage views (to name a few).  This article has been broadened to cover all of these areas.  This is a very long article now, so strap yourself in.  Here is an overview of what is covered.

  • Statement of the problem to solve.
  • Solution overview and setup
    • The definition of a golden dataset.
    • Publishing a golden dataset options.
    • Using datasets across workspaces configuration.
  • The golden workspace.
  • The golden dataset.
  • Maintaining the golden dataset.
  • Creating thin Power BI reports, including local measures.
  • Publishing thin workbooks.
  • Impact analysis and lineage views.
  • Creating online only reports.

In the future, this will also include deployment pipelines (Microsoft recently announced this feature, however it is only available for premium users, and thus this information is still valid for those not in a premium space).

The Problem – Too Many Data Models

Power BI has so many great features it seems almost sacrilegious to raise problems that can surface when unleashing this fabulous self service BI tool to the user base.  Having said that, one of the problems that can occur in the world of self service BI is the proliferation of slightly different versions of essentially the same data model.  The problem is made worse by the fact that you can publish the same data model to multiple workspaces at PowerBI.com, essentially multiplying the problem.   Note: data model and dataset are essentially the same thing – I refer to data model when using Power BI Desktop, but when it is published to PowerBI.com it is officially called a dataset.

If you think about it, self service BI (using your own data models) has the potential to be the antithesis of enterprise BI. Instead of having one single data model that is used for all reporting (enterprise BI), you can build individual bespoke data models each time you have a new problem.  This is both powerful and problematic.  If you are not careful, before too long you can have an unwieldy mess of uncontrollable and unmanageable data models that are essentially the same at the core but with different reports sitting over the top.  The concept of a “Golden Dataset” (you heard the term here first in April 2017) is a elegant solution to this problem, allowing use of a single master source (dataset) across multiple reports in Power BI Desktop (and Power BI Service).  Let me explain further below.

Added note:  Microsoft has already announced the introduction of composite models (the ability for a user to create a new PBIX file that connects to a golden dataset and then allow the user to extend the model further in their own PBIX file (eg by adding local tables) – this will literally be another game changer, and will finally mean that self service BI and enterprise BI can both live closely together in a world approaching utopia.

Solution Overview and Setup

What is the Golden Dataset?

Golden DatasetThe Golden Dataset is a master Power BI Data Model that is loaded to PowerBI.com with or without a report attached. (Actually currently you must have at least a single page in your report, even if it is blank, but you can delete it once loaded to PowerBI.com if you like).  Once you have your Golden Dataset loaded to PowerBI.com, you can build as many new ‘thin’ reports as you need in Power BI Desktop by connecting Power BI Desktop directly to PowerBI.com with Get Data -> Power BI Service.

Note:
A Thin Workbook is one that doesn’t contain a data model itself, but links into a central data model (in this case stored on PowerBI.com).

The advantages of taking this approach are:

  • You only have one dataset/data model to maintain.  This will use less space, use less resources to keep the data up to date, and also eliminate the proliferation of slightly different versions of the data model.
  • You can maintain and improve the single data model in the Golden Dataset master PBIX and make the changes available to all users and dependent reports.
  • You (and everyone else with access rights) can simply build new ‘thin’ reports connected to the Golden Dataset as needed.
  • Anyone building a new report in Desktop using the Golden Dataset will be able to add their own “local” measures – local to their thin workbook.
  • With the implementation of a suitable business process, the best local measures created by users can be retrospectively migrated into the Golden Dataset for the benefit of all.
  • You get the benefits of an enterprise solution (kinda like using an SSAS Tabular data model) without having to invest in all that infrastructure.

Let’s explore how it works.

Publishing Your Golden Dataset Options

There are actually a few ways you can work with Golden Datasets in Power BI.  The first two options below have been discussed previously the last time this article was updated.  Option 3, using a Shared Workspace will be discussed in detail below.

Your options are:

  1. Save your Golden Dataset to OneDrive for Business and import to one or more Workspaces from there.
  2. Save your Golden Dataset to SharePoint Online and import to one or more Workspaces from there.
  3. Publish your Golden Dataset to a Power BI Workspace (Golden Workspace), create a new thin workbook pointing to the Golden Dataset, and then publish the thin workbook to a different workspace(s).  Power BI manages the link back to the Golden Dataset for you automatically.

Options 1 and 2 above effectively provide the ability to impact multiple workspaces and reports while maintaining only one dataset, however in order to use the dataset across multiple workspaces, the dataset needs to be loaded multiple times into each workspace where you need the data.  This also means that each copy of the dataset needs to have its own refresh schedule configured adding duplicate refresh effort to the systems.   The advantage of using option 3 is that you can have multiple workspaces and reports/apps linking back to one common source of data, without the need to duplicate to models.  This goes a long way to addressing the restriction that currently exists where only one app can be produced per workspace.  The concept of working with a Golden Dataset published into a Golden Workspace is illustrated in the image below.

Golden Workspace

Using Datasets Across Workspaces Configuration

In order to be able to use a common dataset across multiple workspaces, your service tenant needs to be configured to allow it.  In the Admin Portal, select Tenant Settings, and scroll down to Workspace Settings.  Here you will find an option to Use datasets across workspaces.  This can be enabled for either the entire organisation, or specific security groups.

Use Datasets Across Workspaces

It is also recommended that if you are intending to work with Golden Datasets, you should have a system in place for certifying the datasets so that your report builders know that this is an official data source.  A certified dataset is simply a label that confirms this dataset is the real deal.  This feature can also be configured in the Admin Portal, Tenant Settings.  Now that your workspaces are configured to allow datasets to be used across workspaces, continue to scroll down until you get to Certification.  Click to expand, allowing you to enable this setting.  Once enabled you have two fields requiring attention. The first field asks you to specify URL for documentation page.  This is where you link your dataset certification process protocol, so when a report developer clicks the “Learn More” link in the Endorsement settings of their dataset, this documentation will guide them in the process for requesting certification.

Certify Datasets

The second field requiring attention is the “Apply to:” field.  Here you will allocate the appropriate security group(s) responsible for dataset certification (In this example, I am in the Golden Data Admin group).  This field can be applied to the entire organisation, but that seems counter productive considering the purpose of certifying a dataset is to ensure report developers they are working with a controlled and approved dataset.  You should therefore only give access to a sub set of users who are allowed to certify datasets.

Now that we have an appropriately configured tenant, we can proceed with setting up the Golden Workspace.

The Golden Workspace

With an appropriately configured tenant, the first step to establishing your Golden Dataset is to create a Golden Workspace for it to reside in.  For demo purposes, I am going to create an Adventure Works Golden Data workspace in my PowerBI.com account.  This is no different to creating an ordinary workspace as far as creation is concerned, but I would recommend you establish appropriate protocols so that only “Golden Data Admin” security group users create and maintain these workspaces.

In this example, I am using a Golden Dataset logo to visually illustrate that this is a Golden Workspace, with an appropriate workspace name and description.  We are now ready to publish our Golden Dataset.

Golden Workspace Settings  Golden Workspace Open

The Golden Dataset

In Power BI Desktop, I have built the master data model for my colleague report developers to use in building their reports.  This PBIX file only contains my model (including necessary calculated columns, tables and measures).  The report page is blank.  I can simply publish this workbook into my new “Adventure Works Golden Data” workspace as I normally would.

Model1

Now that I have my Golden Datset in my Golden Workspace, I need to make a few minor adjustments before it is ready for production use.  First, I need to consider whether or not to remove the blank report from this workspace (#1 below), as I only want to maintain my Golden Dataset(s) in here (more on this later). Then I need to promote and certify the dataset (#2 below) as being ready for production (I will release an article on certifying a dataset soon, for those of you who are unsure how to do this).

Gd In Workspace

The Golden Dataset is now ready for production.

Gd Certified

Making Changes to The Golden Dataset

The real benefits of this approach are realised when you need to make changes to the Golden Dataset.  To demonstrate how this works, when I first published the dataset to the Golden Workspace it had 5 tables.  You can see there is now an additional table in the model being published to replace the existing dataset in the Golden Workspace.

Model2

At this point it is important that I draw your attention to the fact that if you update a Golden Dataset in a Golden Workspace, it does not reset the certification level of the dataset.  Depending on the data policies in your organisation this may or may not cause complications.  If you do not have the authority to re-certify the updated dataset, you should have protocols in place to get the updated model certified before your publish it to the Golden Workspace and overwrite the approved dataset.

Note: The re-certification process is likely to be addressed in the future once deployment pipelines are made available.

Gd Updated

With your updated dataset loaded into your Golden Workspace, you will need to delete the blank report again.  This is of course optional, providing everyone who uses the Golden Workspace is aware that it is not intended for building reports in.  Another option to consider, is to load a single image into the report page that illustrates the model design (this will make more sense below).

Creating a Thin Power BI Desktop Report

OK.  We now have a Golden Dataset in our Golden Workspace, its time to create a new thin report using Power BI Desktop.  To do this, simply open a new blank PBIX file in Power BI Desktop, and opt to Get Data when the splash screen welcomes you.  Navigate to the Power Platform option and select “Power BI datasets” as the data source (shown below), then click Connect.

Connect To Gd

If you are not logged in when you do this, you will be prompted to log in before proceeding.  Once logged in, you will be presented with a list of datasets that you can access from your various workspaces.  This is one reason why having official datasets promoted and certified is recommended, as these will appear at the top of the list, with certified datasets appearing before promoted datasets.  Simply select your Golden Dataset and click Create.

Selecting Dataset

After building my report, I saved the Power BI Desktop file with the name “Thin Sales Report”.  The new thin workbook does not have a data view or relationship view, only the report view as shown below.  Also the thin workbook doesn’t have a copy of the data, so it will only work when you have direct access to PowerBI.com (keep that in mind if you want access when you are out of Internet coverage).

Thin Sales Report

Local Measures

As mentioned earlier, one of the benefits of this approach is that a report builder can connect to the Golden Dataset but still create local measures when needed.  Here is my thin Power BI Desktop workbook below (#1 below).  I can right click on a table in the Fields List and create a new Measure (#2 below), but notice you can’t create calculated columns or new tables (they are not in the drop down list and are greyed out in the modelling tab), only measures are available (#3 below).

Thin Local Measure

Any new measures you create in a thin workbook are stored as part of that thin workbook and are not visible in the Golden Dataset.  If, down the track the Golden Dataset is updated with a measure using the same name as the one you created locally, your local measure will show an error in your thin workbook and the new measure will appear, working in place of your local version.

You will also notice that any ribbon buttons relating to the dataset in your thin workbook are also locked.  Among other things, this means you cannot currently add additional data to the model your thin workbook is built on, however there are moves afoot to enable the building of composite models in thin workbooks as shown in the image below.

Below is a screen shot of new composite models coming soon (not available as of this update in April 2020)

Composite Model

In this image, we can see a workbook that is connected to 3 different datasets (indicated by the colours, Red, Green and Blue).  This is going to be huge!  To find out more, watch Christian Wade’s Business Applications Summit presentation on Modern Enterprise BI (The Business Analyst view of the Enterprise Semantic Models begins at ~14mins).

In the meantime, the only advice I can offer in this regard is to add an image of the dataset model into the Page1 report of your Golden Dataset.  Then you simply need to connect to PowerBI.com and look at the report attached to the Golden Dataset to understand the underlying data model.

Model View

Publishing the Thin Workbook and Workspace Lineage

Once you’re ready to publish your thin workbook to PowerBI.com you will normally publish this to another workspace (it can be the same one, but normally it will be different).  In this case, I have published my thin workbook into a new workspace called “Adventure Works Sales”.  I have also published a regular workbook into a workspace called “Adventure Works Territory Sales” so that we can compare the difference between the two.

Note: I now have both a desktop PBIX file AND a new PowerBI.com thin workbook each containing a report pointing to the same Golden Dataset in the Golden Workspace.

After publishing I can see the new Thin Sales Report (Adventure Works Sales) and Sales Report (Adventure Works Territory Sales) in their respective workspaces.

This is the Thin Workbook

Thin Report In Think Workspace

This is the Regular (Golden) Workbook

Regular Report In Workspace

In comparison between the two, there is an obvious absence of a dataset in the Adventure Works Sales workspace, and no I didn’t just photoshop it away.  To understand this, let’s explore the new Lineage View offered in the new experience workspaces.

To view your workspace contents in Lineage View, simply expand the View tab (1) and select Lineage (2).

Lineage View

Let’s first look at the lineage of a standard workspace.

In the Adventure Works Territory Sales workspace, the lineage view reveals that the Sales Report (page 1 with the image of the data model) is in the workbook containing the Adventure Works dataset (golden) which is connected to the 5 Tables in Excel data source via a Gateway.

Lineage Of Regular Workspace

In contrast, the lineage of the Thin Adventure Works Sales workspace containing the thin report, reveals a General Manager dashboard that stems from the Thin Sales Report, which is connected to the Adventure Works Golden Data in another workspace.  Looking at the image below we can see two significant flags relating to the Adventure Works Golden Data.  The icon for this dataset contains a link in the bottom right hand corner (1), letting you know this is a shared dataset.  The green icon to the right of the dataset name reveals that this is a certified dataset (2).

Lineage Of Thin Workspace Tagged

To explore the source of your Golden Dataset, simply click on the dataset name or on the hyperlink provided (see above). This will redirect you to the lineage view of the shared Golden Workspace.

Lineage Of Gd Tagged

The lineage of the Adventure Works Golden Data workspace reveals that there is an Adventure Works Golden Data report (containing only our data model image mentioned earlier) stemming from the Adventure Works Golden Data dataset, which is connected to the 5 Tables in Excel data source via a Gateway.  In this view there is also a small icon immediately to the left of the “Show Lineage” icon that reveals the dataset’s impact across workspaces (1).

Understanding Impact Analysis

Note: Before proceeding in this next section, I created a second workspace and uploaded another thin workbook connected to the Golden Dataset, so that I could illustrate the Golden Dataset’s impact across multiple workspaces more effectively.

To open the impact analysis report, I clicked on the link (shown as 1 in the image above). The Impact Analysis report is an important feature to allow you see what will be effected when you make changes to your Golden Dataset.

Exploring the Impact Analysis pop-out shows you how many workspaces, reports, and dashboards will be affected by your change, and provides easy navigation to those workspaces where the affected reports and dashboards are located so that you can investigate further if required.

Golden Data Impact Analysis Tagged

The Impact Summary (1) shows you how many workspaces, reports and dashboards and the number of views there are on those potentially affected items. This helps you determine the overall impact of the change for downstream objects.  Thus, it is probably more important to investigate the effect of a change to a dataset that has 500 views than on a dataset that has 10 views.
The Notify Contacts link (2) opens a dialog where you can create and send a message about any dataset changes you intend to make to all the contacts for all impacted workspaces, including workspaces you don’t have access to.
Finally, the Usage Breakdown (3) shows you, for each workspace, the total number of distinct viewers and views for the potentially impacted reports and dashboards it contains, and allows you to further break that down for each report and dashboard.

Power BI Online Only Reports

Of course you can use the Golden Dataset to create a PowerBI.com service only report (as you can with any dataset), however to maintain the effect of the shared Golden Workspace, we need to do this in a slightly different way.

When working in Adventure Works Territory Sales, a regular workspace, we simply need to click on the Dataset in the navigation pane (1) and we can build our new report (2) and save it into the reports area of the workspace.  After the report has been saved (top right hand corner of PowerBI.com) you will see the new report in the Reports list in the navigation pane (3).

New Report Regular Wksp

If required, you can download a desktop version of this report by clicking Download the .pbix file as shown below.  Which will download both a copy of the report and a copy of the underlying dataset associated with that report.  But what about when we’re working in thin workspaces?

Download Report

To illistrate, I have used our training profiles below. 

Looking at the Adventure Works Sales thin workspace,  we don’t have any datasets available to build reports on, and our collaborators who have appropriate access to build reports in the Adventure Works Sales shared workspace cannot currently make any adjustments to the Thin Sales Report.  

Gd Manage Wksp Can't Build On Report

The solution to this is to ensure your collaborators are given build access rights on the Golden Dataset.

Even if you wish to keep your collaborators access to the Golden Dataset limited to viewer status, with build enabled, they will be able to edit and modify reports in other workspaces that use the Golden Dataset.

The first step to enable this is for you as the administrator of the Golden Dataset, to click on the elipsis next to the dataset name, and select Manage Permissions.

Gd Manage Permissions

You can now assign build rights to those users you wish to give editing rights to in the Golden Workspace.  Simply click the elipsis next to the user’s permission level, and select Add Build.

Gd Manage Build

Now that I have given my collaborator build access to my Golden Dataset, how will this impact their access in the Golden Dataset Workspace?

As a viewer of the Golden Dataset, the content available to your collaborators doesn’t change in the Golden Workspace.  Here, they will still only have access to view that “Page1” report that was published alongside the Golden Dataset.

Gd Manage Still View Only

 

When my collaborator views the Adventure Works Sales workspace however, they are now able to modify the existing Thin Sales Report or Save a Copy and start building a new online only version.

Gd Manage Wksp Can Build On Report

With build authority granted to my collaborator they are also now able to connect to the Golden Dataset in Power BI Desktop, and build a new thin report that they can publish up to the shared Adventure Works Sales shared workspace, but the Golden Workspace is protected from them accidentally publishing a new workbook into it.

Gd Manage View Can't Publish To Wksp

Some of you may have noticed that the Download the .pbix file is once again available to my collaborator, however rest assured that attempting to download a PBIX copy of the report is not enabled.

Gd Manage Can Build, Can't Download

 

As the administrator of both the Golden Workspace and the shared workspace however, I am able to download the updated Thin Sales Report.pbix file once changes have been applied, should I have the need, however I am not able to download any new online generated reports added to the shared workspace created by either myself or a collaborator using the Golden Dataset (Golden Data Report below).

Gd Manage Download

Switch Reports to a Different Golden Dataset

Now for some really good news.  It is possible to repoint an existing thin Power BI Desktop workbook to a different dataset if you so required. Now of course you wouldn’t want to repoint a Sales report to a Finance dataset, but if you take this Golden Dataset approach and later change your mind which workspace to point to, you can easily repoint the thin workbook to a new dataset.

“But all the Data buttons on my ribbon are locked out!” I hear you cry.  That is only half true.

While previously you may have taken an approach of repointing the data source via right clicking a table in the fields pane and editing the data acquisition query, this is not available to us in a thin workbook.

Thin Right Click

Instead, we need to look to the “locked out” ribbon to achieve this.

It is true that most of the Data buttons are locked out in the ribbon, however there is one that still has limited functionality in a thin workbook: Transform data.  While the top Transform Data button is greyed out and unavailable, the bottom Transform data button (1) can still be interacted with, and offers only a solution to adjusting Data source settings (2).

Repointing Thin Workbook

Clicking on the Data source settings returns the Power BI datasets picker to view, where you can select a new remote dataset.  Note that you cannot change the data connection type however, so you are still limited to another source of data present on PowerBI.com.

Repointing Thin Workbook New Ds

Summary of Key Points

  • You can upload a PBIX file to the service and use it as a Golden Dataset (one dataset to rule them all).
  • You can also set up a Golden Workspace to hold your Golden Dataset(s) that you can then link many reports and workspaces to the Golden Dataset.
  • You can create as many new reports as you want remotely connected to this Golden Dataset.
    • Connect a new blank Power BI Desktop file effectively creating new thin workbooks.
    • Indirectly create new reports online in the Power BI Service.
  • If you create a thin workbook connected to the Golden Dataset and create a report, you can publish it to a different workspace and it will work.
  • Anyone with build access to the Golden Dataset and a local copy of the desktop generated thin report (PBIX file) can work with the file on their desktop and successfully interact with it on their Power BI Desktop. If you later remove their build rights to the dataset, then the local thin workbook (PBIX file) will stop working because it can no longer access the Golden Dataset – very cool!
  • Online generated thin workbooks can’t be downloaded.
  • You can modify and update your Golden Dataset and republish at any time, and the changes instantly affect any thin workbooks that you have created connected to the Golden Dataset, and you have the Impact Analysis tool to help you manage this –sweet again.
  • Any user with access rights can build local measures to a thin Power BI Desktop workbook without impacting the Golden Dataset.
  • With a suitable business process, end users can advise the owner (admin) of the Golden Dataset of any useful local measures that have been created.  The administrator can then migrate these measures to the Golden Dataset for the benefit of everyone, a task made simpler when you copy the measures between two PBIX files with Tabular Editor.
  • If needed, you can repoint any thin workbook to a different copy of the Golden Dataset.  This can be good if you started your journey without using a Golden Dataset but now want to backtrack and sort this out.

Let me know what you think of sharing Golden Datasets via Golden Workspaces in the comments below.  I also would love to hear any other ideas you have on how to get the most from the Golden Dataset.

110 thoughts on “New Power BI Reports from a Golden Dataset”

  1. We have copies of reports from Golden Datasets, but when the original report is changed, the others coming off that aren’t. It would be great if the copied reports could just refer to the original (and so change upon report update/changes), rather than being one-time copies.

    1. Something sounds wrong. You only maintain 1 Golden Dataset. All other reports should be “thin workbooks”. Thin workbooks don’t have their own dataset, but instead use the Golden Dataset. All changes in the Golden Dataset should be available in any thin workbook.

      1. That’s right – it is more about the report changes, really – keeping the copied report the same as the new one (that is in the same workspace as the GD).

  2. Great article Matt.
    I am starting to get into using Incremental Refresh. While the service may have accrued 5 years of data, my desktop pbix only gets a couple weeks of data. This makes it easy to modify the report without the pain of queries pulling 5 years of data. Problem is that when I publish, it overwrites my 5 years with 2 weeks of data. I’m trying the ALM Toolkit but haven’t found a way to publish the report but leave the dataset (5yr) alone.

    Your article here makes me wonder if I should use the golden dataset instead. My question is, is there a way to connect to the golden but have desktop just get the last couple weeks to keep development manageable, but when I publish, open the door again?

    1. ALM Toolkit will do what you want, but only for Power BI Premium (currently). Deployment pipelines are very close to being released (Microsoft announced this at MBAS – you can watch the Christian Wade Enterprise video to see it In action) I saw a blog post recently from Chris Webb showing how to solve this problem with deployment pipelines. https://blog.crossjoin.co.uk/2020/05/24/limit-the-amount-of-data-you-work-with-in-power-bi-desktop-using-parameters-and-deployment-pipelines/

      1. Trying to set up a Golden Dataset, but in desktop my “Get Data” -> Power Platyform only has 3 options. It does not show an option for “Power BI Datasets”.

  3. Great post Matt. The concept of a golden dataset and publishing reports across workspaces is very powerful indeed.

    I implemented something very similar but running into some problems. In my case the Golden Dataset has RLS and is published to the Golden Workspace and a Thin Report 1 is created from this Golden Dataset and published to the same workspace and published as an app. All well and good.

    I have a Thin Report 2 which connects to this Golden Dataset and is published to another workspace and distributed as an app. But the users cannot view the report as it says permission is required to access the report. I have tried everything, I have given users permission on the Golden Dataset app as well and they are assigned roles in RLS but still the same issue. Both the workspaces have been upgraded to the modern workspace. Any ideas ?

    1. Mmmm, tough. There are lots of touch points. I believe it should work but I can’t say I have actually configured this. Do the users have access to the Golden Workspace? And the Golden Dataset? These are both different to the RLS settings

      1. The users dont have access to the Golden Workspace but they do have access to the app and hence I would have thought they had access to the Golden Dataset. I thought that should have been sufficient. Thanks for your reply, its got me thinking in trying out a few options.

  4. Hi Matt,

    Interesting approach. We’re tring to move our set-up to something similar, but are running into two issues: we wan’t our users to be able to download the .pbix file of a report in a thin workspace that was built on a dataset in the “golden workspace”, and we also want them to be ably to access “Analyse in Excel” through the app. Both options are unavailable however, even when the users have build permissions on the dataset. Do you have any suggestions as how to fix this? Are there any settings that control this behaviour?

    Thanks in advance!
    Best,
    Eva

  5. If you add the “build” permission on the golden dataset to the user/group that has viewer access to the workspace, then they can built a “online thin report” in any v2 workspace or desktop without the workaround you outlined.

    To do this: On the dataset, click the three dots, select “Manage Permissions”. Then on the user or group line, click the three dots on the right and then select “Add Build”.

    1. Jason Cockington

      Thanks for your suggestion. This is a better way of managing the online report generation with workspace collaborators. I have updated the post.

  6. Well, you have your certified Enterprise Golden Dataset (one version of the truth) used by hundreds of thin reports, related dashboards, and thousands of users. Impact analysis will give you these figures (including views), but it won’t tell you how many sophisticated thin reports might become unusable or wrong due to a potential change of the underlying Golden Dataset. Of course, you can inform all report authors of the upcoming change, the impact of which will be immediate, but that’s a bit like changing the company name with short notice. You don’t want to do that regularly. Thus, again business users will have to wait for IT to make required changes to the data model.

    1. Matt Allington

      Do you mean in a thin workbook? Currently no, but it is likely to work when composite models are released in the coming months.

  7. Wouldn’t we take a hit on refresh performance using this method? I have several data sources that are required across multiple report, and each report also has a set of additional data sources unique to that report. So if I wanted to use this technique, I would have to combine all the data sources into a single file, even those not required, since a report can only connect to a single data source when using this shared dataset method, correct?

    So now with my previous 4-5 datasets that take anywhere from 5-25mins to refresh individually, wouldn’t that now make this single golden dataset’s refresh time, take hours rather than minutes?

    1. There is a refresh hit – each copy needs to be refreshed, but this is not a “performance” issue per se. And this approach you cannot have different data sources, and hence yes, you would need them all in one. As I have mentioned in the comments below, I am in the process of updating this article. Check back in a week or so for the latest advice.

    1. Jason and I are currently updating this blog. It will be updated shortly (maybe even next week). Yes you can use Dataflows but that just gives you access to the tables, not the model. The best way to do this now is using shared datasets (watch for the updated blog)

  8. I just came across this article after creating a dozen reports off of the same dataset. I would like to transition everything to the golden dataset idea, but I have a Question.

    My golden dataset is a combination of 2 Oracle sources, a SharePoint document library, and an Excel file saved on SharePoint. How do I convert my reports to point to the Golden Data Set without recreating the reports?

    1. Hi Scott. 2 things. Firstly, this blog is desperately in need of an update. It is now better to use shared datasets than the approach I describe here. https://docs.microsoft.com/en-us/power-bi/service-datasets-share

      In short, you load 1 golden dataset into a golden workspace. From there you can create new thin workbooks directly to the golden dataset without having to replicate them (albeit automatically) to other workspaces.

      Second, you can’t copy and paste pages between workbooks, but you can cut and paste all visuals on your page. So create your new thin workbook connected to the shared dataset, then open a duplicate copy of your old workbook containing the visuals, click on a page, Ctrl+a to select all, Ctrl+c to copy, then paste on the thin workbook.

  9. Hello Matt,
    Brilliant article!
    “Any new measures you create in a thin workbook are stored as part of the thin workbook and are not visible in the Golden Dataset. (Note, you can’t create calculated columns or new tables, ONLY MEASURES)”
    (I capitalize the latter sentence).
    This is enlightening for me. I’d like to explain my work scenario (currently in a PBI **FREE** environment)
    I use this approach to model and analyse costs of my company fleet vehicles: this is the golden dataset, with imported data, ETL, data model and general-purpose measures. Then I created one thin report and add a few local measures. Later, I will create a few more thin reports.
    I miss the lack of permission to add tables (in general: to edit data model) of thin reports, but I understand the reason and accept it.
    Now the company requirements have changed: they need to analyse cost of products IN GENERAL, not only vehicles. In order to leverage several analysis reports, I should add differents tables and relationship to “children-models”. For example: despite vehicles reports just need one table (purchases, and not much more than this), FOOD PRODUCTS report needs an addictional table (i.e. registered number of customers – we call it “occupancy” – ) and local measures. Well, everything is fine with local measure, but what about custom addictional table? I’m not able to add it at thin report level, and oppositely if I add it to golden dataset there is risk to grow it unnecessarily. Further, addictional custom tables aren’t limited to one, but there are several ones in order to provide specific dimensions to various analyses.

    So, the challenge is to generalise golden dataset in order to provide not only MEASURE but also TABLE and RELATIONSHIP, at the same time the golden dataset could not became TOO general and complex.

    I still can’t figure out in which layer I could “inject generalization”.

    Thank for your attention.

    1. In SSAS (the big brother of PBI) there is a concept called perspectives. You can have additional tables in the GDS and deploy them separately in different cubes. My guess is that this will come to PBI in the coming years. Until then, just add the new tables to the GDS. if it is less than 500MB, it is not really “big” anyway. JMO

  10. First attempt at PowerBI here – a simple 2 table SQL Server join query. Found out apparently that there is no way to create a connection to a SQL Server and reuse it for multiple data sets.

    Do we really have to create and store credentials for each and every query that needs to be done?

    We use a ReportUser SQL Server login, not AD, with access to only the databases and tables needed for reporting.

    No AD account to manage, nothing to expire, and a lot less management problems.

    What’s MS thinking, everyone needs to manage hundreds of individual database connection credentials in all the PowerBI reports for our large enterprise?

    What needs to be done when me, the analyst, moves to a different position in the company and the dozens of PowerBI reports I’ve created are owned by another employee?

    Visual appeal is great though where is the TCO considerations? Lightswitch again?

    1. I am sure you are missing something. Credentials can be stored for SQL Server at the DB level and the server level

  11. Interesting question. I can’t say I have ever tested this, but I am surprised to hear it. There is no data in the thin workbook, but it would store the last query in the visuals, I guess. What happens when you interact with the workbook. It then must send a refresh request.

    1. I ended up working with Microsoft Power BI Support. It took a week or more of testing with them. We found that the underlying Master Data Set, if stored on one-drive must be refreshed a minimum of 5 times during the day, even though the underlying data itself had no changes. Now any measure changes in the master set will be immediately updated in the thin client report. Also, If I add/modify/delete visuals in my thin client report, they will now update on the Power BI Service immediately. It was hard to problem solve as the thin client always was updated with the values from the data from the master data set, just new measures and visuals would take a long time. I was waiting up to 5 hours sometimes for a visual modification to show up on my thin client report.

      1. Hi Angela. I am really interested to find out more about this. What do you mean it must be refreshed a minimum of 5 times per day? Do you mean if you refresh it once, then nothing happens?

  12. If I open my thin report on my Power BI Desktop, why does it not update automatically from the Golden Dataset?

  13. I have gone with option #2 of the golden dataset and it has worked very well until recently. Before my golden dataset grew in size, my thin report would update pretty quick. All of my reports are created through Power BI Desktop. Now I am waiting up to 2 or more hours. This has proven a little frustrating as I update or add measures. I can’t utilize the revisions or updates on my thin report visuals for awhile. Would option 1 work quicker? Also, if I went to option 1, can you create a report on the Golden Dataset and save it to a different workspace. I’m not clear on this one.

    1. Yes, option 1 would make the published version immediately available (after it is published). All you lose is the ability to automatically publish to more than one workspace. But you can still manually publish to multiple. You should be able to switch – just publish it manually. If the dataset is duplicates ( same name, twice), you should be able to repoint your existing thin workbook to the new one.

  14. Patrick McMonagle

    Hi Matt, thanks for sharing the approach – just what I’d been looking for.
    Trying to implement it now, creating some thin workbooks but have been experiencing some issues while creating thin workbooks in the Desktop. Just wondering if you’d experienced anything similar or had any ideas?
    “Cannot load model. We couldn’t connect to your model in the Power BI service. The dataset may have been deleted, renamed, moved, or it is possible that you don’t have permission to access it. Failed to connect to the URL ‘https://api.powerbi.com’ white attempting to call cluster connection”

    I cannot see what I have changed to affect this, and it seems intermittent across thin workbooks. I’m guessing it could just be a temporary connection error to the website, though the most frustrating part is any combination of trying to ‘Cancel’ or ‘X’ the dialog box does not work, so each time requires a forced shutdown of the desktop. Luckily recovered files are pretty good but would be good to understand what’s happening.

    Thanks, Patrick

    1. No, I haven’t seen this before. If you are sure you have not changed anything, I suggest you use the diagnostic tools inside desktop and create a support request. File\Options and Settings\Options\Diagnostics

  15. Hi Matt
    Super useful trick!
    Thanks for sharing.

    If you set everything up like this, do you know a way to keep track of which dataset & reports actually link back to a certain ‘golden dataset’? Can we see the original link or something somewhere?

    Thanks!
    KR
    Tom

  16. Calvin Francart

    We have actually been talking about this solution for our instance of PBI – so very, very glad to come across your blog. But something came up today that I was wondering if you have any experience with. We have a group of datasets that feed individual reports. The report author left the company, and when their AD account was removed, we found ourselves having to scramble to assign ownership of every dataset to someone else because the reports could not load. Have you ever tried assigning ownership of a Golden Dataset to a non-person AD account? Just wondering if assigning to a group would allow anyone within that group to make changes rather than having to go to just one person all the time – and also not having to manage the ownership in the event they exit.

    1. I’m glad this has helped Calvin. Yes what you describe is a common problem. There is a solution to moving ownership using the Rest APIs. https://docs.microsoft.com/en-gb/rest/api/power-bi/ I am not an expert and have never used the API, but I understand you can solve most issues like the one you refer to. Regarding of assigning ownership to a non-person, that may be a licensing issue. Regardless, I think if you follow my advice and always use a workspace with multiple administrators then you wont have a problem. This problem only occurs when people share from their own MyWorkspace. I always recommend people never do that, for this exact reason.

  17. Hi Matt,
    Given that MS has introduced Dataflows, will Dataflow replace as the solution for Golden dataset?
    What scenarios do you think the solution outlined in theis blog will be still useful?
    I am trying to understnad scenarios where the solution here can be used.
    Thanks,
    Anand

  18. Hi Matt,
    How is this Golden Data approach different from creating an App or App workspace?
    Or when should we consider App vs. your suggested approach #2 or #3?

    1. One thing Microsoft is often bad at, is its naming of things. I think App Workspace is a dumb name. It is just a workspace – a place to collaborate with others. An App is a “package” of a dataset, reports and dashboards packaged up as an “app” that can be distributed to others, including people outside your organisation. The Golden Dataset is something different. It is a “master” version of the data model that can be deployed into 1 or more Apps and 1 or more Workspaces without having to create duplicate copies. You create 1 golden dataset and the reuse it in may places. Sharepoint and OneDrive keep all uses in sync.

  19. This is a further (third) update to an article …
    Interesting information, I definitely like the idea of a master data set that everyone works from. (not too keen on giving private data to MS, Azure, yes I’m paranoid… )

    You said this is the third version of the article. Presumably it would be useful to read the earlier articles, but like too many other authors you make it too hard to find. You provide the dates of the earlier articles, but when I look on your blog list, THERE ARE NO DATES, just titles! WHY NO LINKS in this article to the ones you refer to. It is so easy for you to do …

    1. Fair point Ron. The issue is that I didn’t make it clear – obviously. I edited the original articles and re-released them. The old versions therefore don’t exist anymore – that is why there are no links and you can’t find them. I do this deliberately because the alternative is I would have stale content (in this case 3 articles about the Golden Dataset) and I run the risk that people don’t read the latest and greatest. I will try to make it clearer that the originals have been edited.

  20. You are right, these options don’t auto refresh. You need to do it manually, or you can use a tool like power update. I’m thinking now that you could create the golden dataset with connections to dataflows, and schedule dataflows to keep the data refreshed. I might write an update about that.

  21. This is a great article – maybe there is a new way doing this with Power BI dataflows?

    It wasn’t that clear to me – how do you refresh your golden dataset for options 2 and 3?
    I really just want to create this one ‘golden’ dataset and publish it to Powerbi.com and then have reports in 2 other workspaces using it.

  22. One thing to note is that if you click “save as” on a thin report connected to a golden dataset in the Power BI service, then the new report will no longer be thin as it will have copied and attached the golden dataset to itself. I found this to be a problem when I published a report on a clients tenancy. He made a copy of the report by clicking “save as” and then he did a bit of work on this new copy. His work had to be later redone as you don’t seem to be able to separate the two again

  23. I guess that the new Composite Model functionality is another answer to the question “How can I build 1 master dataset, use it as the 1 version of the truth, but still allow people to do their own thing?” Because now you can use DirectQuery to provision the equivalent of the ‘Golden Dataset’, while still allowing users the flexibility of doing additional modelling via Import.

    1. @Jeff Weir – I was thinking the same thing. Many of my users “do their own thing” but just adding that one or two additional Excel worksheets that are there to just enrich the golden dataset with a few columns of their own. In Excel they used these sheets for “VLOOKUP” purposes. Prior to the July 2018 update, doing the live connection to the Power BI Service meant that users were unable to add their own imported data to this published data model (just as you said.) So that has caused me to shy away from recommending this as a best practice for everyone.

      A possible enhancement to this approach could be to store Power BI template files (.pbit) of your saved pbix files in SharePoint as well. If users needed to get a local copy of the golden dataset, they could then get this pbit and refresh. However, they would have to know that they were making a copy of the golden dataset (a fool’s gold dataset?) and there would need to be a clear method to handle these multiple data models with slight mutations.

    2. There is a BIG difference between Direct Query mode and Import Mode, and I wouldn’t want to give up the benefits of Import just to use it as a control mechanism for standardisation – JMO

  24. Kamil Kaleciński

    One thing that worries me from the very beginning – Once I will change my position in the company, is there a way to smoothly transfer the dataset (either loaded to OneDrive or directly to PBI account) to one of my colleagues account, without losing highly developed set of workspaces, reports and group of recipients?

    1. Always create a new App Workspace. That way admin rights can be shared and transferred. Use an internally public OneDrive or Sharepoint folder to store the Golden Dataset. Do those things and all will be fine. Even if you do it in your personal workspace, Power BI admins have tools to make changes and repoint workspaces and workbooks

    1. Report server is a whole different topic. You need 1) Report Server (of course) and 2) the specifically edition of power bi desktop that is used to publish to the server

      1. I have both conditions, the Reports server and the PowerBI desktop optimized for the report server.
        I am not able to import the dataset to the server.

        1. Sorry for the confusion in my reply. You “publish” a report to report server by using the optimised Power bi desktop version. But report server is not Powerbi.com, and I guess you can’t use his technique with report server.

  25. Thanks Matt … this is a very helpful article.
    I’ve been using a golden dataset for a while now – loading it to 3 different workspaces and having a separate refresh schedule in each workspace. Had no idea till I found your article that it could be a single dataset “serving” the 3 workspaces.
    I’m a bit unsure how this would work with refreshing the dataset via a PBI Gateway. Jerry’s comment earlier suggests this can work, but how would one configure this? Would you configure the dataset in all 3 workspaces to refresh via the Gateway? Or, if you setup the refresh schedule in just one of the workspaces, would all 3 workspaces reflect the refreshed data? Has anyone tried this?

    1. When you load to OneDrive and then import to a workspace, the workspace has its own copy of the data set (3 workspaces means 3 copies – hence 4 in total). Power BI and OneDrive talk to each other. When the OneDrive version is updated, any workspace versions will automatically be updated. So you have 2 options. 1) refresh the OneDrive version and hav eit auto flow through, or 2) configure the gateway for all workspace copies (3 gateway configurations in your case). OneDrive doesn’t have the ability to refresh itself. The file needs to be “opened” and then refreshed and saved. You could do this with Power Update ($500) or just use the gateway on all copies.

  26. Is the only difference between storing the model (ie dataset) in the cloud (onedrive/sharepoint) verses on premise with a gateway (when you want to publish to multiple workspaces): When changes are made to the model the cloud options will automatically update the model in ALL workspaces and the on premise version would have to be published manually to each workspace where the model has been previously published?
    There is no difference in the refresh scheduling, correct?
    For both on premise and cloud datasets deployed to multiple workspaces you still have to setup maintain the refresh schedules in each separate workspace, correct?
    There is no difference in permissions to make changes to the dataset, correct?
    The users have to have edit permissions in the workspace, they therefore can download the dataset, make changes and republish and override it?
    Thank you.

  27. Hi Matt,
    Great article.
    I just want to add some demo I have done so far based on your article.

    I’m always looking for this kind of Golden data set, but also a Golden reports (then customize for each app). So with the help of your article, I finally “almost” there. I have tried to pass by the tabular model but all the reports are disappear (pbix > Azure Analysis Services > obtain tabular model) so I dont really appreciate this method.
    So my approach to have golden dataset and reports is :
    1/ I have a golden dataset with all the reports for different group of users but each group will use only a subset of reports and I dont want to have them in different places so I have only one pbix file (the viz works perfectly with RLS so I dont need to apply filter on group of business users)

    2/ With the help of your article, the onedrive master pbix file synchronizes with their “Import pbix” ‘s file. But I dont want them to sync (I dont want the users see reports that are not belong to their business) so I turn off the sync One Drive option, activate Schedule Refresh.

    3/ By doing that, every time I want to modify the report, I can just go and modify the original and then activate sync, and by the end I will delete the non-necessary reports for this app.

    Let me know what do you think about this approach!
    Thanks again for this great article.
    Dung Anh

  28. Nice article, Matt. I work in an organisation that hasn’t yet fully come to exploit what Power BI has to offer and hence didn’t really have the chance to see this being used. I created something similar to what you have described before the connect to Power BI feature was made available

    The inability to view the data model and the relationships will be a pain-point to create custom measures. You mentioned about migrating measures to the Golden Dataset? Is this something as trivial as sending an email to the “owner” of the Golden Dataset to add in the desired measures? Or is it something that will be uploaded to the thin report on PowerBI.com

    Also, if the golden dataset as row level security enforced, would that affect creating custom measures in some way?

    Thanks

    1. Yes, I think the process to migrate measures could be a simple as an email. They key is that everyone needs to know what to do. As for RLS, that is a great question – I have never tested this, but I assume that the new thin workbook would have the golden dataset RLS applied for the user of the thin workbook. Nothing else would really make any sense from a design perspective.

  29. I voted for the idea to make a schema visible in these cases. In any case, a couple of best practice suggestions would be to (a) always avoid hiding key fields and (b) maybe also duplicate the golden model side by side as a fully imported dataset option. To often analysts just want to make small variations but will abandon the golden model if they can’t and then will have a dead end.
    By the way I tested importing all tables directly into Power Pivot tables from a golden model and it works fine; just fYI but again would need the keys to enable relationships to be recreated.

  30. Hi Matt,
    I think this is a really good idea and a great concept. But it feels like Microsoft has some way left before this can be fully used in production. For example, in my case I have 7 similar reports, with only minor modifications. I want to base all the reports on the same data model, for all the benefits you mention above, but also to minimize the workload on the database.

    However, I want some differences in e.g. target values etc. that I wanted set up as parameters. But to my understanding, this cannot be done when designing a “thin” report. I also have some measures designed as indexes, based on the target values. The only solution I can come up with is to hardcode the values into the measures in each report, but it doesn’t seem like a very sustainable alternative. Do you have any ideas how I can tackle this?

    1. I’m not sure what you mean by “measures designed as indexes”. Yes parameters are part of Power Query so cant be in a thin workbook. For your hard coded measures, how about you load a table of all the possible values. Eg with 2 columns (Report name, value). Place a Report level filter in each report as appropriate to match each report. Then a generic measure myMeasure = selectedvalue(table[Value]) should work for all reports, and you can just change the values in the source table when needed.

  31. Maybe I’m missing something but you can connect to a golden dataset if your starting from fresh with a new pbix, but what happens if you already have a pbix and you simply want to cherry pick some data / measures from another data model? My attempts at this proved unsuccessful (cannot recall the message, something about multiple online sources) but am happy to be proved wrong.

  32. Not sure if this is already well know, in my scenario I am making this Golden Dataset available to use in multiple App Workspaces, to maximize the application of “single source of truth”. This is done by using Sharepoint to house the Golden Dataset (PBIX), then in each of the App Workspaces use Get Data –> Get Files –> Sharepoint Teamsites, then point to where the PBIX file is uploaded.

      1. Hi Matt, I haven’t see any documentation or blog from anyone on this scenario, it seems pretty basic so I just assumed it was common knowledge. The setup is pretty straightforward, using Sharepoint as the cloud storage for PBIX files, and by using the Get Files from Sharepoint method as I mentioned, in each App Workspace, the Golden Dataset is now available for use in each App Workspace, and subsequently production Apps. Future updates in the Golden Dataset (data refresh, measures, relationships) will reflect to each App Workspace. If this is not common knowledge, it might be great if you can mention this in your blog post, and also recommend Microsoft to add to their documentations. What do you think?

        1. I agree. I will check it out and update this article. Are you using SharePoint Online? I don’t use it much, so this is part of the reason I don’t know about it. Are you just sharing to a SharePoint Library?

          1. Hi Matt, for smaller datasets I am using a data gateway to refresh the dataset in Sharepoint. The dataset appears in PBI Service the same way as if it were an direct publish from desktop, and has the same refresh options on the Service.
            I have a couple more complex datasets that the data gateway can’t handle just yet due to timeout issue, so I am manually refreshing them in Desktop on a daily basis, then upload the PBIX file to Sharepoint. The Sharepoint file will sync with PBI Service within an hour, then the updated data will show up in the Service for various Apps and Reports.

            Our team hasn’t moved into more enterprise-grade platforms (such as Informatica or SSAS) for dataset management yet, so this solution with PBIX and Sharepoint works well for now to manage our datasets.

  33. I like this idea, but have a hard time seeing how end users will be able to write anything other than the most basic reports and measures if they don’t understand the structure of the model. This puts a real burden on the model designer to put a tremendous amount of attention to, for example, naming fields and tables to relay that information. Even then, I’d have a concern that they may create a measure that does not work as they expect and, as a result, report incorrect BI because of it.

    1. The way I dealt with one of those issues was to duplicate some measures in the form of a ‘semantic later’, if you will. A set of friendly names for users completely separate to the base measures as I call them

      1. I have been circulating a pbit thin template with a screen grab of the relationships diagram on page 1. Users then save a thin pbix.

  34. Sorry, the reason I turned off from this idea in the past is that the the measures in the golden model weren’t ‘exposed’ for usage, is this now the case?

    They are when you use Analyse in Excel so I’m hoping yes?!

      1. By exposed, i mean you can see the list of pre-defined measures created in the Golden Report from within a thin PBI desktop file following connection. (in the same way as you can see them in Excel). Let me try….

  35. Take a bow Sir!

    This is fantastic and I’ve felt in my bones I’ve needed to arrive at this place for a while now. I don’t have the facility to set up SSAS and nor do I have the inclination

    This is a superb alternative and does the job very nicely indeed!

  36. My wish for the next advancement on this feature is to allow connection to multiple “golden dataset” in the same report, to allow the most flexibility in data steward process, with PBI as the convenient single platform to manage the data modeling of various data sources.

  37. You can create a content pack of the dataset and report that connects to the service and share the pack with the new group. The data refreshed in the original dataset and group is reflected automatically in the new group via content pack.

  38. Excellent new feature! Very well described. Casual users can benefit from Power users’ modelling skills much better now ! It sounds like it is Microsoft’s goal for each enhancement of Power BI. Power users drive the development and production that Casual users can enjoy peacefully.
    When you talk about a “shared workspace”, it is actually an Office 365 Group accessible in any 0365 application right ?

  39. The Game changers are yet to come.
    1. Connect to Data model in Power BI Desktop file from Excel (w/o all the hacks)
    2. Connect on an Excel/Access DB stored in One Drive personal
    3. Password protect the Queries / Data model – to give some sense on security.

      1. @mim – Voted – The problem with the voting system is the same idea is there is several places.
        For example the Original Idea by Avi Singh mentioned connecting to both Power BI and Power BI Desktop.
        Microsoft conveniently forgot the Power BI Desktop part and declared the idea as completed.
        And Avi did not use his good offices with MS to push the agenda further

  40. Gary Lanzafama

    Yes! It’s a game changer. An issue I have with a single model is the number of measures has increased over time, which can be confusing for the developer and user. I am hoping that this will allow a “modular” approach. Each report can focus on a specific dimension table or Time Intelligence each with a more limited number of measures.

  41. “however from experience loading data from a SSAS model into Power Pivot is pretty painful.” yes indeed, but it is one of the most cost effective way to distribute large numbers of reports, of course assuming you have Excel 2013+

  42. Would you consider this a golden “Data model” instead of a dataset? I’ve usually referred to a dataset as a single table…

    1. Yes I agree Joe. I just called it a dataset because that is the term used by Microsoft on the PowerBI.com It is a golden data model until it is published to PowerBI.com and then it becomes a Golden Dataset

  43. Matt, yes Excellent, but i am chasing a different scenario, I Want to query the “Golden” dataset from Excel/Powerquery , not live connections but load some data into a local Powerpivot Model.
    Live query is nice and all, but it is a pro feature as you have pointed out, it requires a shared workspace.

    i tried to play with the string connections but not luck so far.

    but i agree it is a game changer for pro users.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top