Forum Discussion
Privacy / More Information Needed
I have published a report into the service that, In Power Query, combines data from AzureSQL tables and Power BI Dataflow (Legacy) tables. Everything works fine in desktop, but when I publish to the service I get this error
Data source error: {"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":"Information is needed in order to combine data"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"PowerBI\",\"path\":\"PowerBI\"},{\"kind\":\"SQL\",\"path\":\"azr01pepmazdb1.database.windows.net;EPMdb_Final\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"PrivacySetting"}}],"exceptionCulprit":1}}} Table: Pct Samples.
Cluster URI: WABI-US-NORTH-CENTRAL-H-PRIMARY-redirect.analysis.windows.net
Activity ID: 959e51e4-0517-4e2b-a02b-62f0dceb6198
Request ID: 4d64565a-66b9-2ced-9ec5-239cc0f4ac3b
Time: 2024-08-06 17:05:36Z
The AzureSQL connection goes through our PBI data gateway (and is used by many other reports in our environment), while the Dataflow connection does not.
I have tried clearing and re-adding the permissions on both data sources. I have gone to Report -> Options -> Global -> Privacy and selected "Always ignore Privacy Level settings" (which then disables the option under Options -> Current File -> Privacy) but still getting the same result.
Is there something I am missing that needs to be reset or otherwise edited?
Thanks,
David Edelman
I seems to have been able to do a workaround. In PQ I combined (appended) the tables from the DataFlow source, and separately combined the tables from the AzureSQL source and loaded those into the model. Then in DAX I did a UNION on the two pre-merged tables. Now it publishes and refreshes with no issues.
I know there is a restriction on combining tables inside of Dataflows if you don't have a Premium license - maybe this message was the Service telling me that I couldn't circumvent that restriction in PowerQuery at any point (tho I could combine tables from the same data source - who knows).
Thanks,
David
3 Replies
I am wondering about this sentence:
Information is needed in order to combine data
In your report do you have a merge/append with a table? Perhaps in Power BI or in SQL? And, maybe you have hidden or turned off enable load for that query? You don't have to turn that on but if that data is being used, you have to confirm that you have permissions to that data.Hi collinq -
Sorry if I wasn't clear. In PQ I bring in a few tables from AzureSQL and another few from the Dataflow and use "Append" to mash them together (the AzureSQL is "archive" data pre-2024, the Dataflow is current year data). There is a little bit of transformation on the "archive" data before combining, but mostly just adding and removing some columns to get the table structures to match.
I have permission to both data sets, and the whole thing works perfectly fine in Desktop. I do have "Enable Load" turned off on the "seed" queries, only bringing the combined data into the model. I've done that without incident in the past, but it was probably with data from the same sources. Do you think I will need to have them all load and then hide them from the model?
Thanks
David
I seems to have been able to do a workaround. In PQ I combined (appended) the tables from the DataFlow source, and separately combined the tables from the AzureSQL source and loaded those into the model. Then in DAX I did a UNION on the two pre-merged tables. Now it publishes and refreshes with no issues.
I know there is a restriction on combining tables inside of Dataflows if you don't have a Premium license - maybe this message was the Service telling me that I couldn't circumvent that restriction in PowerQuery at any point (tho I could combine tables from the same data source - who knows).
Thanks,
David
