There is a really neat feature in the tenant settings that allows you to put a custom message on the PBI Desktop screen when selecting a workspace to publish to. It supports markup too! Ours has, in nice bold letters, a warning to not use My Workspace. Not 100% effective but it's another tool alongside the scan api and sternly worded emails :)
I published report in there because it's easier to start with, but now I'm a consultant which needs get the reports to a lot of users that don't have a pbi account. My workspace helped me to go through this
Do not call Premium workspaces "regular". I learnt it the hard way while working on a project for a very cheap client - Microsoft want a penny for everything you do (duh). Non-premium workspaces are such a castrated version of workspaces that I don't want to see them, ever. And you'll only know the difference if you face-plant into it and then notice a little blurb in the documentation that tells you - "Uh-uh-uh, cha-ching, please!"
I do my testing and build in my own workspace so that my users don’t see it and get confused to what report they need to use, once it's ready I publish to my premium capacity and within the app space, within the app I then use the new audience feature where certain reports are grouped and one audience group for external consumption. I do not like have multiple workspaces because I lose track where reports are located, I love the new app feature with audience.
Basically your still using 2 workspaces, if you create a workspace just for your stuff in development, you'll be better able to have another dashboard builder helping out.
can you comment on a secondary publication to a structured SharePoint site that allows broader consumption? We are not publishing to apps due to the added complexity and limits of setup, but I have honestly nit played with deployment pipelines so would love to hear comments/ best practices from others in this forum.
So the only reason is so they can access the reports if I’m fired or in vacation? I still don’t find it useful. I publish all to my workspace and then embed it in the company’s web page. That’s how we do it and it works fine.
The reason I publish to My workspace is because I want to share each report with specific people. Otherwise anyone who is in the workspace has access to all the reports. Is there a better way to have published reports that can each be accessed by a specific set of people?
When deploying to the App, how can others update while I'm on vacation? It has to be updated twice daily. Currently unsuccessful using ShareNow. Only able to update using the desktop version.
Huh? You ony need to update the app when you like build a new visual in your dashboard, so users will see the changes in the dashboard. You can setup a schedule refresh in your workspace on your dataset, which will automatically refresh the data, also in the app.
@@Catarax28 the only issue I have with this is, Pro workspaces can auto refresh 8 times a day which is not a lot for reports used in operations. Premium offers 48 times a day which is more suitable for Apps.
My users generally want to export the detailed data. Like many more columns which I don't bring in the power bi model. I thought of using agg+direct query type of model, but that won't work due to some complex measures used in model. Can someone help me on this, how can I fulfill this exporting large data requirement.
I usually never allow users to use PowerBI as an export to Excel tool. Why do they need so much detail, have you asked? If they want to do one-time analysis, why not just get the raw data from your datasource? If they can't get the insights from their dashboard, are they clear about their KPI's?
They are clear with the KPIs. They just want the more detailed kind of table whenever they find some insight in dashboard. Let's say they slice and dice some 4-5 dimensions and now they are seeing some outlier. Now they want the full info about these filtered items which are currently not coming in the model. They want 10-15 more fields to look into. Currently they are not in the model as they are never used to show some visual and if I bring them as import will increase the model size to large extent.
@@nikhil1888 If this is really rare, maybe make a seperate dataset for these drillthrough purposes, using direct query if too big too import? It's a bit of extra work for the end user to get to the outliers again, but it keeps your current model running faster. You could also see if the end-user can request extra data from your data-engineer? Give them one-time data-dumps that contains their outliers directly from the database? Outliers can also be caused by errors in the data, sometimes it's a matter of cleaning up in the database, after your end-user have noticed the problem, and get them to trust the data again. If it's something they need to inspect on a regular basis, then you might consider putting it in your model.
Hi. How can I share my report with a customer that is not inside my organization with his own username and password to log in. It is only one customer from another organization.
There is a really neat feature in the tenant settings that allows you to put a custom message on the PBI Desktop screen when selecting a workspace to publish to. It supports markup too! Ours has, in nice bold letters, a warning to not use My Workspace. Not 100% effective but it's another tool alongside the scan api and sternly worded emails :)
I published report in there because it's easier to start with, but now I'm a consultant which needs get the reports to a lot of users that don't have a pbi account. My workspace helped me to go through this
Do not call Premium workspaces "regular". I learnt it the hard way while working on a project for a very cheap client - Microsoft want a penny for everything you do (duh). Non-premium workspaces are such a castrated version of workspaces that I don't want to see them, ever. And you'll only know the difference if you face-plant into it and then notice a little blurb in the documentation that tells you - "Uh-uh-uh, cha-ching, please!"
Love your videos. Can you cover semantic models in workspaces and why you may or may not want to have the semantic model in the same workspace.
I do my testing and build in my own workspace so that my users don’t see it and get confused to what report they need to use, once it's ready I publish to my premium capacity and within the app space, within the app I then use the new audience feature where certain reports are grouped and one audience group for external consumption. I do not like have multiple workspaces because I lose track where reports are located, I love the new app feature with audience.
Basically your still using 2 workspaces, if you create a workspace just for your stuff in development, you'll be better able to have another dashboard builder helping out.
@@Catarax28 I wish I had help 🤣 I'm a one man band and it took a lot of education that most reports are not 10min jobs 🤣
@@philipmead3575 Ugh ..yeah .. I always have to tell the business that the graphs themselves are just the top of the iceberg of my work 🤣
Thank you mr cube for this enlightening.
Please do the same for datasets.
can you comment on a secondary publication to a structured SharePoint site that allows broader consumption? We are not publishing to apps due to the added complexity and limits of setup, but I have honestly nit played with deployment pipelines so would love to hear comments/ best practices from others in this forum.
Hi Ray, I use SharePoint a lot when sharing reports. I use the embed feature.
@@shinellebovell4251 as do I.
To consume reports, would you recommend Apps rather than embedded reports and/or sharing through MS Teams?
I deploy my user consumable reports as apps. It is easier for them and looks cleaner.
How do you do that? Any links mate?
@@georgegray2712 it's done by default as soon as you have an app setup for the workspace
I publish to my workspace and will try publishing to the general workspace. Apps are disabled by admin of my organization.
So the only reason is so they can access the reports if I’m fired or in vacation?
I still don’t find it useful. I publish all to my workspace and then embed it in the company’s web page. That’s how we do it and it works fine.
The reason I publish to My workspace is because I want to share each report with specific people. Otherwise anyone who is in the workspace has access to all the reports. Is there a better way to have published reports that can each be accessed by a specific set of people?
Maybe do the same thing but publish to a workspace and then get shareable links for that workspace, I don’t think that means you have to add them
Thanks Adam,I am wondering why you did not even mention a publication on Report Server ? My company provide only pto licence with PBI RS. Any advice ?
When deploying to the App, how can others update while I'm on vacation?
It has to be updated twice daily.
Currently unsuccessful using ShareNow. Only able to update using the desktop version.
Huh? You ony need to update the app when you like build a new visual in your dashboard, so users will see the changes in the dashboard. You can setup a schedule refresh in your workspace on your dataset, which will automatically refresh the data, also in the app.
@@Catarax28 the only issue I have with this is, Pro workspaces can auto refresh 8 times a day which is not a lot for reports used in operations. Premium offers 48 times a day which is more suitable for Apps.
My users generally want to export the detailed data. Like many more columns which I don't bring in the power bi model.
I thought of using agg+direct query type of model, but that won't work due to some complex measures used in model. Can someone help me on this, how can I fulfill this exporting large data requirement.
I usually never allow users to use PowerBI as an export to Excel tool. Why do they need so much detail, have you asked? If they want to do one-time analysis, why not just get the raw data from your datasource? If they can't get the insights from their dashboard, are they clear about their KPI's?
They are clear with the KPIs. They just want the more detailed kind of table whenever they find some insight in dashboard.
Let's say they slice and dice some 4-5 dimensions and now they are seeing some outlier. Now they want the full info about these filtered items which are currently not coming in the model.
They want 10-15 more fields to look into. Currently they are not in the model as they are never used to show some visual and if I bring them as import will increase the model size to large extent.
@@nikhil1888 If this is really rare, maybe make a seperate dataset for these drillthrough purposes, using direct query if too big too import? It's a bit of extra work for the end user to get to the outliers again, but it keeps your current model running faster.
You could also see if the end-user can request extra data from your data-engineer? Give them one-time data-dumps that contains their outliers directly from the database?
Outliers can also be caused by errors in the data, sometimes it's a matter of cleaning up in the database, after your end-user have noticed the problem, and get them to trust the data again. If it's something they need to inspect on a regular basis, then you might consider putting it in your model.
😨 I genuinly never came across an organization where people put shareable reports in their own workspace.. wow..
Are apps available for Power BI pro licenses?
Yes
Yes on the PowerBI Service, (you need to publish it from desktop).
We publish reports to Power Bi report server..! Why that is not covered in this video??
Stop it
Hi. How can I share my report with a customer that is not inside my organization with his own username and password to log in.
It is only one customer from another organization.