DataSource.Error: Could not find a part of the path
I have an excel file as a data source for my pbix that used to work fine. After moving the source file to a different location and editing the path in the query manually I've started getting the message "DataSource.Error: Could not find a part of the path '\\ks-nt08\.............xlsm' "
I've tried to re-source the file through the NEW SOURCE dialogue - I browse and select the file but get the message "We encountered an error while trying to connect. Details: could not find a part ot the path....."
I've tried putting the path in a parameter and call the parameter (""¶m) - same same.
Here is a strange detail - I tried to read the data as a Power Query source in an Excel file located right next to my pbix. The queries in Excel and PBI are identical, but in the Excel query the file get read with no problem at all!
when I move the file back to previous folder, all becomes well again, but I need to keep the source file in this folder where it can't be read...
I can't imagine what the problem could be - anyone?
EDIT - The problem persists - I now have additional data sources in the new folder, and none of them can be read by Power-BI. I am forced to do this dumb workaround: (1) move all my queries to an Excel file - which is willing to read the sources in their present location (as opposed to PBI). (2) put this Excel file in a locaction where Power-BI is willing to read data, and get the data from it.
can anyone offer insight on this ridiculous situation?
click the file->Options and Settings->Data Source Settings, you will get the following data source settings navigator. Then select change source(highlighted in red line), please check the path and open file as right format.
Community Support Team _ Jay If this post helps, then please consider Accept it as the solution to help the other members find it.
@v-jayw-msft thanks for your reply. This gave me a new way to triple check that I have the right path in place, and the right format is selected, and yes - It was all correctly input in the query. So regretfully this doesn't solve the problem...