Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
PBIM
Helper I
Helper I

Best practice for location and referencing of data files

HI

 

I have managed a 'proof of concept' by setting up a pbix file and associated xml data files on the c drive of the computer where the enterprise Power BI gateway has been installed.

 

However, as I roll this out in my establishment, I ideally want to move the pbix file(s) onto an exisiting network driev but want the xml data files to remain where they are and I'd create a new network drive so that I can access them as needs be.

 

To save any confusion with drive letters and data connections and sources, am I right in saying that I should change all source references in Power Query to use a UNC?  Or is it still possible - and maybe more efficient? - to have the data connections referring to the C Drive but the Power Query in the pbix file referrring to the files using the network drive?  

 

I'm thinking that if I did the latter then, if I were to save and publich from PBI Desktop, it would muck up the connections.

 

Please can someone advise on best practice here.

 

Many thanks

1 ACCEPTED SOLUTION
djurecicK2
Super User
Super User

I have not used UNC that much myself, but you do need to have the same path to the data source on the desktop and the gateway machine. So using c:\... in PBI desktop will give an error on service refresh if the gateway does not have the files in its c:\... folder.

 

If the local desktop and the gateway machine are both using \\server-name\path you should not get an error with service refresh through the gateway.

 

Also a mapped network drive will not work, so looks like UNC is the way to go for you.

https://community.fabric.microsoft.com/t5/Service/Enterprise-Gateway-mapped-network-drive-issue/m-p/...

 

View solution in original post

4 REPLIES 4
djurecicK2
Super User
Super User

I have not used UNC that much myself, but you do need to have the same path to the data source on the desktop and the gateway machine. So using c:\... in PBI desktop will give an error on service refresh if the gateway does not have the files in its c:\... folder.

 

If the local desktop and the gateway machine are both using \\server-name\path you should not get an error with service refresh through the gateway.

 

Also a mapped network drive will not work, so looks like UNC is the way to go for you.

https://community.fabric.microsoft.com/t5/Service/Enterprise-Gateway-mapped-network-drive-issue/m-p/...

 

OK.  Thanks.  Will try that.  Accepting as solution for now....

djurecicK2
Super User
Super User

Hi @PBIM ,

 I agree with your statement below. If possible, you could also look at using OneDrive or Sharepoint online.

 

I'm thinking that if I did the latter then, if I were to save and publich from PBI Desktop, it would muck up the connections.

Thank you.  Unfortunately, my establishment is not yet into SharePoint or OneDrive so I don't want to introduce anything new that will confuse but you're probably right in that that is the best way to go.

However, given that I won't immediately be going down this route is UNCs my second best - only?- choice?

 

Presumably, on the server, a UNC pointing to itself is not prolematic or a particular detrimet to performance?

 

Tahnks in advance for any further confirmation you (or someone else) are able to provide on that front.

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors