Forum Discussion
Refresh not possible after Join in Query
Hello all,
i did a simple Table.NestedJoin of two tables in the Power Query and a Table.ExpandTableColumn (extended the table with two columns after join).
Result is that in Power BI Service the refresh no longer works. I get following error message:
- Fehler bei der Datenquelle{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Informationen werden benötigt, um Daten zu kombinieren. Geben Sie eine Datenschutzebene für jede Datenquelle an."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"SQL\",\"path\":\"SQL;DWH\"},{\"kind\":\"SQL\",\"path\":\"sql;dwh\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"PrivacySetting"}}],"exceptionCulprit":1}}} Table: NEW_JOINED_TABLE.
I checked all in Service (Settings) and in Desktop (Data source settings) but nothings works until now. Someone more ideas?
Best regards
What are the data sources from the two joining tables? From my experience, certain mixed of data source types dont work.
Also, check the privacy setting for both joining tables/queries/data sources, just for testing, try setting both to "none". "Datenschutzebene" is mentioned in the error, this could be it.
3 Replies
- Tutu_in_YYCSuper User
What are the data sources from the two joining tables? From my experience, certain mixed of data source types dont work.
Also, check the privacy setting for both joining tables/queries/data sources, just for testing, try setting both to "none". "Datenschutzebene" is mentioned in the error, this could be it. - Pikachu-PowerImpactful Individual
Hi Tutu_in_YYC
the data sources are the same with the only difference being lowercase and uppercase. Adjusting that helped. Thanks!
Best regards.
- Tutu_in_YYCSuper User
interesting. We know that M is case sensitive, but SQL shouldnt. Anyway, good that its solved it.