Hi there Patrick. Nice video. Im working with PBI as a Junior consultant in a ferry company in Sweden (still a student) and i Will definitely use this approach since i have been asked to create a New architecure for Power BI due to all the similar reports with 1 different dataset each. Keep doing what you do - putting a smile on many faces and giving awesome tips.
Great idea to promote, we have been using this approach for a couple of months, and the fact that reports can be re-pointed to different models later on certainly made this feature more usable. That being said, there are improvements that would make this even better: 1) Ability to connect across different workspaces (also to avoid having to have the "master" model in multiple workspaces if necessary) 2) Ability to separate the permission to access dataset from being either a "Modify" member or Admin of a workspace (only 2 scenarios where connecting to live PBI source works for a user) Thanks!
We've been using this for a few months now. It's an amazing way of working and has really given us a great model for success. We've built on this slightly because everyone who builds needs to have admin access to the reports and sometimes you want to be able to lock down reports so we have a "Development" or "QA" workspace were everyone can be an admin and then promote these secondary reports to the "Production" workspace (and app) once it's fit for release.
Wow, never thought about it that way.... a great way to separate out the data/data model from the visualizations. This is the type of thing any organization with more than one or two people should do. I can even see doing this for things only I touch so I don't have to recreate the wheel every time.
I came back to watch this because you referred to it in another video. You should have Kaelen star in some of your videos. She did great! You two make a great team!
Ha, great timing! I was just about to send a note to a couple of customers I noticed were doing this exact behavior with a report/model I created for them. Once again, GIAC to the rescue! Thanks guys and keep up the great work!
5:45- I don't think this is a possibility anymore, is it? Because when I try and import data from a report someone else made from the service, all that's available to click on is the data. I'd have to re-build the whole visual.
Great Effort with video presentation...it interests many of us GUYS :P keep up good work fellas and Kalyn! Silos are common in most businesses, its a big battle you are starting !
This is how we develop but their are a few limitations of the current design which prevents this from scaling. It's not possible to cross workspaces and we cannot connect to more than 1 model at a time.
Very relevant video, thanks! For this exact situation I have the need to keep all the data but each new report needs slightly different relationships between the tables. Anyone have a good solution for this? When connecting to the PBI Service for the data, Relationships are not available to edit from files built upon the dataset.
Great video. I also use a tabular SSAS I created for the school I work for. I'd be really interested to compare how US education data compares with here in the UK.
Hi Patrick,great video though i have a question on this-you can only use PBI service as connector when you give access to your users to PBI workspace, right?If yes then there is a risk of modifying the reports by users on PBI.com workspace which we don't want to have plus we cannot grant access to outlook distribution list in workspace yet?Pls comment on this.
Awesome, this is a Huge problem with self-service data. Now, how can I do the same thing, with On-Premises. We have not migrated to the cloud YET, but we have Silo issues, is there something I can do, that will mimic this (short of SQL Server Based -- data marts) that will allow my customer base to no continue to create data Silos throughout my company...
Great video, thanks! Your scenario works only within the same workspace, right? Because everybody needs to be at least a member to be able to use the model with the "Power BI service" source, there is a great chance that someone is going to break the original model and thus break all the reports that are based on it. It would be great if we could provide datasets in a way that they can be used outside the "home" workspace. Is that the purpose of the "manage permissions" menu option for datasets that's been around for a while now?
Navigate to any dataset in any of your workspaces in the cloud service > Click on the three dots below ACTIONS > In the menu, choose "Manage Permissions". There, we can add and remove users and give permissions to Read and Read/Reshare (the dataset?). But I couldn't figure out how this works exactly and I couldn't find any documation about it.
What happens if you connect to a shared dataset but need a slightly different model each time e.g. you need one or two extra tables/columns or need to change the relationships? Does that mean you have to create lots of different variations of the model? Or do you just have one model and pull in as many tables as possible to cover as many different reports as you can?
Hi Patrick, Great Topic & lesson for the business users! Is there a limitation of 1GB of the data model to be published? How about the incremental loading? It would be the best if these data models can be combined quickly to the Azure Analysis Services with out the hassle so there is always an upgrade path open for customers while they are starting on the small models and going big if the model size will be increased.
This is great information. My organization doesn't allow anything in the cloud though. What would you(or other viewers) recommend as a best practice since I can't use Power BI Service?
Appreciate that Tj! Yes this video was made before dataflows, although still relevant as dataflows aren't a dataset. You still need a dataset and could pull data from a dataflow. Dataflows are a great way to reduce the data silos also though.
Nice video, never thought about it that way. BUT, isn't the main issue here that you should really separate the dataset from the visual presentation e.g. reports? As I understand it, you cannot publish just a dataset to the service but you always publish the dataset AND at least one report. Sure you can delete the report but every time you re-publish it will re-appear. If you really want self-service BI you should allow your users to build reports based on a number of ready-made datasets that are verified and quality assured by a data steward or the like. Am I missing something here?
If you are working within the clients Power BI tenant, then I would create a workspace for the consultant. As the consultant completed work I would suggest cloning content between workspaces until it reached the Production workspace. At that point I would suggest creating and App for distribution of the content.
That sounds like a workable approach, requiring the consultant to be configured and licensed within the client's tenant. It would be nice touch if the consultant's own O365 credentials and Power BI Pro license could be used within the client's Power BI tenant, but that seems to be both a licensing and credential limitation.
As a consultant we sometimes also need to manage and develop their reporting systems over time among many PBI tenants. It would be helpful if the consultants can use their Pro BI license with any client tenant. Can the B2B option help here GIAC for consultants own license to access a clients tenant for development and management of BI solutions? I do this with software i manage for cients...one central login to access all my clients systems.
@@GuyInACube Hi,. Thr video dates from 2 years and It seems this option for connecting/editing pbix file is no longer available. I couldn't find it. I can only connect to a dataset now. Can you help?
Yooooooooooooooo! Is there a way to deploy a PBIX in the Report Server version of PowerBI to be used as the Data Source or is this feature only for the app.powerbi.com builds?
Hello, how do I export reports that are already published and embedded into my custom website? I want users to export into power point from my site as they will not have access to the power bi service.
Very relevant info, and your Daughter was excellent....she's ready for Hollywood. Question: Is this relevant for on-premise data sources that you get to through Gateways?
Yes. You would create the data model connected to your on-prem data, publish it to the Power BI service, then use the Power BI Desktop to connect to that model and build reports.
Hi Patrick. I think users who want to get data from Power BI service must have Admin permissions over the workspace in which the data model is hosted. Is that correct?
You are correct. Individuals that want to connect and build reports based on the model must be administrators. Those that want to consume must have access through the model via the workspace and/or row-level security.
Hi, are you sure? It seems to me that to connect to the data set it's enough to be a workspace member who can edit Pwer BI content. A member who can only view Power BI content in a workspace cannot connect do the data set from workspace. Do you agree?
It's a great video, but Power BI really need a feature where you can create dataset that is shared between workspaces, so you can create different reports on it and share it with different users. I believe this would be the most effective way to avoid data silos. Also a very nice feature would be to only publish the dataset instead of a dataset and a report.
A very important feature but there is not enough govenance controls for datasets, MS need to seperate the dataset governance and permissions from the reports. If you really want to enable the enterprise to prevent dataset chaos then allow controls which will allow only a select group of users to publish and configure datasets, users wanting to create content from these are free to do so but should be optionally restricted to not being allowed to create and publish new datasets. Additionally, these governed datasets should be available in as many workspaces as required. This idea has been proposed since 2015 but seems to have been sitting on the shelf for far too long: ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/6969065-data-governance-tools-so-published-datasets-can-be
@@GuyInACube Or how about this? 'We' have only 'her' in the video?!!?!? JKD mate, there is so much that I learn from what you guys put up. Power (BI) on......
You can do that. Our experience is that usually leads to models starting to differ and then hard to update all of them, and/or keep track of all of them.
Hi there Patrick. Nice video. Im working with PBI as a Junior consultant in a ferry company in Sweden (still a student) and i Will definitely use this approach since i have been asked to create a New architecure for Power BI due to all the similar reports with 1 different dataset each.
Keep doing what you do - putting a smile on many faces and giving awesome tips.
You are a genious, Patrick!!! Presenting so funny and clearly this BIG problem :) Applause for Kalyn to!
Great idea to promote, we have been using this approach for a couple of months, and the fact that reports can be re-pointed to different models later on certainly made this feature more usable.
That being said, there are improvements that would make this even better:
1) Ability to connect across different workspaces (also to avoid having to have the "master" model in multiple workspaces if necessary)
2) Ability to separate the permission to access dataset from being either a "Modify" member or Admin of a workspace (only 2 scenarios where connecting to live PBI source works for a user)
Thanks!
We've been using this for a few months now. It's an amazing way of working and has really given us a great model for success. We've built on this slightly because everyone who builds needs to have admin access to the reports and sometimes you want to be able to lock down reports so we have a "Development" or "QA" workspace were everyone can be an admin and then promote these secondary reports to the "Production" workspace (and app) once it's fit for release.
A full Development Life Cycle. Awesome!
Wow, never thought about it that way.... a great way to separate out the data/data model from the visualizations. This is the type of thing any organization with more than one or two people should do. I can even see doing this for things only I touch so I don't have to recreate the wheel every time.
I came back to watch this because you referred to it in another video. You should have Kaelen star in some of your videos. She did great! You two make a great team!
Ha, great timing! I was just about to send a note to a couple of customers I noticed were doing this exact behavior with a report/model I created for them. Once again, GIAC to the rescue! Thanks guys and keep up the great work!
5:45- I don't think this is a possibility anymore, is it? Because when I try and import data from a report someone else made from the service, all that's available to click on is the data. I'd have to re-build the whole visual.
Great Effort with video presentation...it interests many of us GUYS :P keep up good work fellas and Kalyn!
Silos are common in most businesses, its a big battle you are starting !
I love the acting! Keep it up, very engaging presentation of an incredibly important concept.
This is how we develop but their are a few limitations of the current design which prevents this from scaling. It's not possible to cross workspaces and we cannot connect to more than 1 model at a time.
Awesome video, can I publish the new model in a different workspace?
I like the idea. Would the subscribers of the shared model be able to to Refresh the dataset interactively ?
Very relevant video, thanks!
For this exact situation I have the need to keep all the data but each new report needs slightly different relationships between the tables. Anyone have a good solution for this? When connecting to the PBI Service for the data, Relationships are not available to edit from files built upon the dataset.
Have you tried using dax USERELATIONSHIP to fix that problem?
You can use DataFlows if you have sufficient licensing rights. Only available to Premium per User or Premium Capacity.
Great video. I also use a tabular SSAS I created for the school I work for. I'd be really interested to compare how US education data compares with here in the UK.
Thanks for the idea Patrick!
You're welcome Miguel! Thanks for watching.
Hi Patrick,great video though i have a question on this-you can only use PBI service as connector when you give access to your users to PBI workspace, right?If yes then there is a risk of modifying the reports by users on PBI.com workspace which we don't want to have plus we cannot grant access to outlook distribution list in workspace yet?Pls comment on this.
Awesome, this is a Huge problem with self-service data. Now, how can I do the same thing, with On-Premises. We have not migrated to the cloud YET, but we have Silo issues, is there something I can do, that will mimic this (short of SQL Server Based -- data marts) that will allow my customer base to no continue to create data Silos throughout my company...
Great video, thanks! Your scenario works only within the same workspace, right? Because everybody needs to be at least a member to be able to use the model with the "Power BI service" source, there is a great chance that someone is going to break the original model and thus break all the reports that are based on it. It would be great if we could provide datasets in a way that they can be used outside the "home" workspace. Is that the purpose of the "manage permissions" menu option for datasets that's been around for a while now?
which manage permission?in workspace- we need to give edit permission else you cannot access model.
Navigate to any dataset in any of your workspaces in the cloud service > Click on the three dots below ACTIONS > In the menu, choose "Manage Permissions". There, we can add and remove users and give permissions to Read and Read/Reshare (the dataset?). But I couldn't figure out how this works exactly and I couldn't find any documation about it.
What happens if you connect to a shared dataset but need a slightly different model each time e.g. you need one or two extra tables/columns or need to change the relationships? Does that mean you have to create lots of different variations of the model? Or do you just have one model and pull in as many tables as possible to cover as many different reports as you can?
Hi Patrick,
Great Topic & lesson for the business users!
Is there a limitation of 1GB of the data model to be published? How about the incremental loading? It would be the best if these data models can be combined quickly to the Azure Analysis Services with out the hassle so there is always an upgrade path open for customers while they are starting on the small models and going big if the model size will be increased.
great channel!!!!! thanks so much for sharing your data knowledge
Thanks for watching Paul! 👊 Appreciate the kind words.
This is great information. My organization doesn't allow anything in the cloud though. What would you(or other viewers) recommend as a best practice since I can't use Power BI Service?
Maybe a centralized data warehouse or SSAS database. The idea is to try and centralize a much as possible to prevent the islands.
Got it, thanks
Awesome! Made my day! Thank you! So is this b4 data flows?
Appreciate that Tj! Yes this video was made before dataflows, although still relevant as dataflows aren't a dataset. You still need a dataset and could pull data from a dataflow. Dataflows are a great way to reduce the data silos also though.
Very good Patrick, awesome channel : )
Does Row Level Security also flow through to the linked dataset ?
Omg your daughter is so beautiful.
what was the first technique to prevent data silos? Tha one you didn't explain.
Nice video, never thought about it that way. BUT, isn't the main issue here that you should really separate the dataset from the visual presentation e.g. reports? As I understand it, you cannot publish just a dataset to the service but you always publish the dataset AND at least one report. Sure you can delete the report but every time you re-publish it will re-appear. If you really want self-service BI you should allow your users to build reports based on a number of ready-made datasets that are verified and quality assured by a data steward or the like. Am I missing something here?
Nice job Patrick! What thoughts would you add if you want to use this across organizations, e.g. a consultant working with a client?
If you are working within the clients Power BI tenant, then I would create a workspace for the consultant. As the consultant completed work I would suggest cloning content between workspaces until it reached the Production workspace. At that point I would suggest creating and App for distribution of the content.
That sounds like a workable approach, requiring the consultant to be configured and licensed within the client's tenant. It would be nice touch if the consultant's own O365 credentials and Power BI Pro license could be used within the client's Power BI tenant, but that seems to be both a licensing and credential limitation.
As a consultant we sometimes also need to manage and develop their reporting systems over time among many PBI tenants. It would be helpful if the consultants can use their Pro BI license with any client tenant. Can the B2B option help here GIAC for consultants own license to access a clients tenant for development and management of BI solutions? I do this with software i manage for cients...one central login to access all my clients systems.
@@GuyInACube Hi,. Thr video dates from 2 years and It seems this option for connecting/editing pbix file is no longer available. I couldn't find it. I can only connect to a dataset now. Can you help?
Yooooooooooooooo! Is there a way to deploy a PBIX in the Report Server version of PowerBI to be used as the Data Source or is this feature only for the app.powerbi.com builds?
Yes, Power BI Service is good host of model for Power BI Desktop
This is a very serious comment. This was helpful and great. Thumbs up.
Glad it was helpful for you. Thanks for watching! 👊
Great video, I am going to give it a shot!
Excellent! Thanks for watching!
Hello, how do I export reports that are already published and embedded into my custom website? I want users to export into power point from my site as they will not have access to the power bi service.
Great idea!
Thanks Patrik!!💻
Most welcome!
Kinda skipped over the important bits. Where was Incidents created (in which pbix)? Is that measure now in Attendance as well?
Very relevant info, and your Daughter was excellent....she's ready for Hollywood. Question: Is this relevant for on-premise data sources that you get to through Gateways?
Yes. You would create the data model connected to your on-prem data, publish it to the Power BI service, then use the Power BI Desktop to connect to that model and build reports.
And your daughter is VERY smart too! Great job Patrick!!😃
Hi Patrick. I think users who want to get data from Power BI service must have Admin permissions over the workspace in which the data model is hosted. Is that correct?
You are correct. Individuals that want to connect and build reports based on the model must be administrators. Those that want to consume must have access through the model via the workspace and/or row-level security.
Hi, are you sure? It seems to me that to connect to the data set it's enough to be a workspace member who can edit Pwer BI content. A member who can only view Power BI content in a workspace cannot connect do the data set from workspace. Do you agree?
Step 1 : Favorite the video
Step 2 : Get it out each time someone ask why we still need A.S. when we do PowerBI
hahahaha love it!
A very helpful video, thank you.
Yo, this is cool, learnt something new today
YES! Every single day. 👊
Great tip, thanks
Awesome video!
Nice vlog 📹
Cool!
Thank you for this
Most welcome! Thanks for watching!
Great idea! Why I did not guess myself...
It's a great video, but Power BI really need a feature where you can create dataset that is shared between workspaces, so you can create different reports on it and share it with different users. I believe this would be the most effective way to avoid data silos.
Also a very nice feature would be to only publish the dataset instead of a dataset and a report.
Søren Jensen That exists. Its called Analysis Services.
Dustin gives a good option. If that is something you are passionate about, be sure to submit it on Ideas.powerbi.com.
Pats daughter calls him Patrick ? huhh !!! you could do that calling Dad by name reaction video !
A very important feature but there is not enough govenance controls for datasets, MS need to seperate the dataset governance and permissions from the reports.
If you really want to enable the enterprise to prevent dataset chaos then allow controls which will allow only a select group of users to publish and configure datasets, users wanting to create content from these are free to do so but should be optionally restricted to not being allowed to create and publish new datasets.
Additionally, these governed datasets should be available in as many workspaces as required.
This idea has been proposed since 2015 but seems to have been sitting on the shelf for far too long:
ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/6969065-data-governance-tools-so-published-datasets-can-be
Thanks! nice intro :D
Well I learnt something new today!
Love it!!!
Beautiful!!!
Millions thanks
OMG! You are funny, but your daughter is totally adorable!!!
She is a natural. We need to get her in another video.
@@GuyInACube Or how about this? 'We' have only 'her' in the video?!!?!? JKD mate, there is so much that I learn from what you guys put up. Power (BI) on......
Not a horrible idea :)
Top!!
I like data silos because I don't want other people messing with my stuff.
You can do that. Our experience is that usually leads to models starting to differ and then hard to update all of them, and/or keep track of all of them.
Grain silos are good. Data silos are bad.
Cute
I hope your daughter gets paid for her appearances!