The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have been asked to separate the dashboard file from the semantic model on the web service because a contributor doesn't like the way it looks. It makes it more clumsy for me to manage, but I can get used to that. I can't find any documentation anywhere why this would be done or if it should be. Does anyone know what implications this may have downstream?
Solved! Go to Solution.
There could be another way to achieve it. You can create a workspace for dataset where you can publish the semantic model and you can create a new workspace which store your reports. Then you can connect the reports through live connection to the semantic model that is published on the other workspace. Once you refresh the semantic model, your reports get automatically refreshed.
Tha failures could occur in many ways. The common example are if you changed the name of column in the semantic model and a different column name is used in the report, then it will result into an error which can be visible in the transform data in power query.
Let me know if you want any further help on this.
There could be another way to achieve it. You can create a workspace for dataset where you can publish the semantic model and you can create a new workspace which store your reports. Then you can connect the reports through live connection to the semantic model that is published on the other workspace. Once you refresh the semantic model, your reports get automatically refreshed.
Tha failures could occur in many ways. The common example are if you changed the name of column in the semantic model and a different column name is used in the report, then it will result into an error which can be visible in the transform data in power query.
Let me know if you want any further help on this.
Thank you so much v-jtian-msft. They are looking for the models to be stored in a separate folder in the workspace on the web application. I had to do a manual refresh for someone yesterday and it took a LONG time. Not sure if there is a correlation or simply coincidence. I also had several refresh failures since they have been separated. I'm trying to determine if I should just drop this single user to view only access and put every back the way I designed it.
If my post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,@GretchenRW I am glad to help you.
According to your description, your team would like you to manage the semantic model and the reports (dashboard) separately?
The first thing to note is that reports and dashboards in workspace are dependent on the semantic model, so if you want to achieve this separation, you need to create a new dataset in desktop and process it, then publish it to service, then continue to use the original dataset on desktop, and use a copy of the new dataset on the service. service with a copy of the new dataset (the new dataset after copying).
This accomplishes your need to manage the dataset separately from the reports, although it adds complexity and is generally best to keep the versions consistent.
However, this also helps you to achieve separation of duties and version control (if the version needs to be updated)
This can lead to situations where the version the user sees (the old version on the service) is not the same as the report creator's version (the new version on the desktop).
If you want to unify the management and control of the version, you can try some management tools, according to your needs to choose the appropriate management tools.
1. Azure DevOps
Azure DevOps provides two version control models: Git and Team Foundation Version Control (TFVC). They both help you manage versions of your code and data models and provide collaboration capabilities.
URL:
What is version control? - Azure DevOps | Microsoft Learn
2. Visual Studio
Visual Studio is great for managing AS models and code and Visual Studio integrates with Git and Azure DevOps for easy version control and team collaboration. You can use Visual Studio to manage your code base and collaborate with your team members in real time.
URL:
Visual Studio Version Control - Code Repository (microsoft.com)
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.