Support relative path to excel/csv sources
Currently, when excel file is loaded to Power BI, the absolute filepath is captured in the M query. It would be nice if relative filepath was supported. Thus we could place excel file next to pbix and not worry about the file location (local machine, shared folder on server or onedrive)
Jeremy Faverjon commented
I've been using this feature with Excel/Power query by creating a cell containing the current file location (basic excel formula). By including the file location in my query model, I was able to share the tool with my colleagues. They only had to update the data templates, save everything in one folder and they were able to run the tool without adjusting sources in query editor!
This would be a great feature that would enable us to create scalable visualization tools using only standard data templates. That would be simply AMAZING!
Peter Gunardi commented
Hi, I need this feature. It will make my work scalable.
Stephen Paul Wright commented
It would be useful if the addition of relative paths also made it easier to switch between data stored locally or in the cloud. Currently different commands are needed for files in the 2 places and the paths also differ because one uses \ and the other /!
This would be a nice usability feature. A simple checkbox on the file dialog box would suffice.
Dudes, sort this out! It's killing me!
Please support Relative paths. I loose a lot of productivity hours at the moment by not having this available.
I have the same issue with Access files
It is beyond my comprehension how this seemingly obvious ask goes unanswered all this time given the consistent updates PowerBI enjoys. .\ ..\ following symlinks is not rocket science. And there is a valid use for this which the service does not address. Consider proof of concept design phases, or grassroots level projects that incubate innovation before online data services exist. I love this tool but the archaic design choices like this are unnecessarily annoying at times and are an impediment to user innovation.
My non-technical users constantly fight with this issue, it's consuming lots of our resources.
We need a way to easily accommodate per-user pathnames at data query time.
[Deleted User] commented
Indispensable feature when multiple people need to develop and development on a server is not a possibility
This is becoming a deciding factor in choice of BI.
Please add this!
Please add this feature.
Bilal Mansoor commented
Surprising that this isn't already available
Thomas Reasoner commented
Absolute paths are rarely ever useful. Relative paths should be the default.
This capability exists in Excel. . .should also exist in Power BI
I have many pbix files about 50 where I manually filter out the data using a text value. If I can have that value in the pbix file name I can get the file path and then parse it and pass it to the filter in power query. Something like var = thispbix. path
In response to the last suggestion:
1 - create a parameter in PBI containing the 'single place' filepath
2 - save and send PBI file as template (to get prompted for the parameter)
3 - adjust your queries so your recepient can simply copy paste from explorer address bar (meaning "\filename.ext" included in your queries)
4 - recepient will open PBI template + get parameter = filepath prompt. Copy paste from explorer and all sourcefiles will work.
5 - Don't forget to save as for the PBI file (since it was a template which created a no name new file. And it does not even have to be in the same folder as the data.
But totally agree that an automated option is much more prefered.
Something like a "current PBI filepath" variable in powerquery.
Caio Proiete commented
Whilst we wait for this feature to be implemented, in order to to ease the pain, you can define a variable that contains the folder, so you only have to change a single place: https://stackoverflow.com/a/52895973/211672
Pretty standard feature that is required here. It makes it so that I can't send the file and the data source to colleagues and off-load the refreshing responsibility to them. I need to edit the data source every single time I make a change to their project.