Support relative path to excel/csv sources

[borlip]

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)

[WayneH]

I'm amazed still that after 5 years that this still isn't there! - I'm up voting this for two reasons, yes to the original idea of relative paths but also to be able to query where the currently opened PBIX file was loaded on, that way there is a small change to go update the content of the 'variable' work around that's been used FOR THE LAST FIVE YEARS to just read where the PBIX was loaded from instead. Best of both worlds then!

[Mircea_Ontanu]

This is so basic but missing for such a long time. How should I teach a non technical person to update the path that points to a file next to the template full of pivots. Such a pain. I just want to send to the client a template report and the data csv file. They should open the report but it will fail because the path to the data is not the same as on my computer. Yeah one solution would be to put the data in the same excel file, but then.. they have to copy paste the new data when is necessary and click refresh all.

[amr_ibrahim]

This needs to be Implemented ASAP, we can't even get the path of current folder........

[amedinafamilia]

Please add relative path capabilities. This is such a powerful tool, but without relative path, non technical users need to manually set sources when sharing or moving the files. this introduces a lot of friction and more chances of things breaking.

[Y0003974]

Need to package up a report and a folder with excel files in for a consumer. They have no technical expertise. Once they unzip the query will break due to the file paths. This is a basic requirement, c'mon!

[a_buffing]

Absolutely bizarre that this hasn't been implemented years ago!

[alejandro_contr]

PowerBI is an exceptional tool, BUT developers need to change their mindset: advanced users? we are enthusiastic but too few to blow other tools (like QlikView or even think-cell) out of the water. The average user will always be unable to get inside the model and make changes without making a mess, but they are the many. I spend a good part of the day explaining (among other basic things, like resetting filters) why they shouldn't change the folder the files are stored in, and how to change file paths, problems I didn't have with QlikView (Oh how I miss the old . and .. folder commands) At this point, basic features such as this one should've been addressed.

[guilherme_costa]

How come this is a not feature... This should've been implemented years ago.

[James_Bartlett]

Power BI Desktop should have a Power Query keyword (like #shared), called something like #workingdirectory, which returns the current report file's working directory as an absolute path. That way, you wouldn't even need to use the report parameters at all. You'd just edit the Source line in the M query to look like this:

Source = Excel.Workbook(File.Contents(#workingdirectory & "ExcelFile.xlsx"), null, true)

Then, as long as the report PBIX and its data source files are kept together, and the source file names stay the same, the report will just work automatically, no matter who opens it or where it's saved in the filesystem. 😎thum

[jzhang104]

I can't believe this is not implemented yet!