Error on apply Power Query: Expression in partition n/a in table n/a references an unknown entity

[Anonymous]

let
Source = AzureStorage.DataLake("https://xxxxx.dfs.core.windows.net/contoso-retail-dw/rssfeed/rawdata/date=" & DateTime.ToText(Date.AddDays(DateTime.LocalNow(), -1), "yyyy-MM-dd")),

This PowerQuery Source gives a preview without any error, but when "close and apply" this error is shown:

Failed to save modifications to the server. Expression in partition n/a in table n/a references an unknown entity

When I change the source to static string it works fine!?

let
Source = AzureStorage.DataLake("https://xxxxx.dfs.core.windows.net/contoso-retail-dw/rssfeed/rawdata/date=" & "2020-03-29"),

[v-qiuyu-msft]

Hi @Anonymous, 

Please modify the URL in your Power Query like below then try it again: 

let
Source = AzureStorage.DataLake("https://xxxxx.dfs.core.windows.net/contoso-retail-dw/rssfeed/rawdata/date=" & ""&DateTime.ToText(Date.AddDays(DateTime.LocalNow(), -1), "yyyy-MM-dd")&""),

Best Regards,
Qiuyun Yu

[Anonymous]

same error...

[nicg]

I get the same error with an on-premise SQL Server source. Even if I simply duplicate a working query, the new duplicate causes this error.

[Anonymous]

Tried also this - also does not work! (PowerQuery Preview perfect, "Apply" gives error):

let
DateString = DateTime.ToText(Date.AddDays(DateTime.LocalNow(), -1), "yyyy-MM-dd"),
#"SourceString" = Text.Combine({"https://xxxxxxx.dfs.core.windows.net/contoso-retail-dw/rssfeed/rawdata/date=", DateString, "/data"}),
#"Source" = AzureStorage.DataLake(SourceString),

[v-qiuyu-msft]

Hi all, 

Please update Power BI desktop to the latest version 2.79.5768.1082 then test again. 

Best Regards,
Qiuyun Yu

[Anonymous]

Same error!!!
I made a completly new report with latest version.
This desperate guessing does not help, please come up with a solution!

[nicg]

Updated, but still encountering the same error.

[v-qiuyu-msft]

Hi all, 

Please create a support ticket to let engineers look into the issue on your side. 

Best Regards,
Qiuyun Yu

[nicg]

In our case, this problem seems related to enabling the "Enhanced Metadata Format" preview feature on an existing dataset.

[Anonymous]

Same here! The "enhanced metadata format" preview feature has some sort of critical bug in it. It will mess up your PBIX file and I could not reverse it by simply turning the feature back off. I had to revert to a previous version. Thankfully, we use source control and I had one.