Forum Discussion
Open the data model
Hi b-kopik ,
We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.Thank you.
Hi b-kopik ,
Thank you for your follow-up questions. To clarify, taking over the dataset will not affect the existing modelling work tables, relationships, and measures will all remain unchanged. The only difference is that the previous credentials are removed, so you’ll need to enter your own SharePoint credentials for the dataset to refresh. If you see multiple SharePoint items, it’s likely because several reports or dataflows are connected to the same SharePoint source. To identify the exact file(s) linked to your dashboard, go to your semantic model settings and select Gateway and cloud connections. There, you can view the full SharePoint file path(s) associated with the dataset and match them with your SharePoint folders. After updating your credentials in this section, your dataset will connect successfully without altering the existing model logic.
Thank you.
Hello,
Thank you so much for looking into this. I spent the last week trying to understand the model but the current setup is complex, prone to errors, contains lots of old data, causing slow updates and difficult maintenance. Also, all managers want to make updates to the dashboards.
Since my team is only using 4 relatively simple dashboards (each using about 2 data files with no more than 10,000 rows of data each), I think I will do the following:
I’ll keep things simple and editable in Power BI for now while managers provide feedback and we finalize the updates. Once everything is locked in, I’ll transition the cleaned data to Fabric's Lakehouse for better structure, performance, and long-term scalability.
Any thoughts on this approach? I would appreaciate any recommendations.
Thanks again.
Hi b-kopik ,
Thank you for sharing information about your current setup and proposed approach. Your plan seems practical and keeping the models simple and editable in Power BI at this stage will make it easier for managers to give feedback and for you to make adjustments. When the design is stable, moving the cleaned data to Fabric’s Lakehouse is a solid option for scalability and performance, as it offers a centralized and governed data layer that can efficiently support multiple dashboards.
As additional recommendations, as you move to the Lakehouse, it’s a good idea to establish clear naming conventions and folder structures early so your team and managers can easily navigate and maintain the data.
For performance, when your datasets become larger or more complex, enabling incremental refresh in Power BI will help improve refresh times. Since multiple managers require editing capability, you may also want to use workspaces with clearly defined roles (Viewer, Contributor, Member) to manage permissions and prevent unintentional changes. Looking ahead, Fabric Lakehouse will give you the flexibility to scale beyond SharePoint files and integrate with other enterprise data sources if needed.
Overall, your approach of starting simple and then moving into Fabric for structure and performance later is aligned with best practices.
Hope this helps, Please feel free to reach any further assistance.
Thank you.
Hi,
Thank you so much! That makes sense. Will users be able to download the Excel files from Lakehouse though? I think the preference would be to use Sharepoint for that reason. What I am struggling now is that I can see the file name on Lakehouse but I can't locate it anywhere.
Thanks again.
Bruna
