Anonymous's avatar
Anonymous
Not applicable
3 years ago
Status:
Needs Info

Merge Queries 2 Tables from Dataverse gives "Query references other queries or steps, so ..." error

I have 2 tables from Dataverse that I have used "import data" to load into Power BI Desktop (Apr 2023, 64-bit). I then use Merge Queries to join the tables on a PK/FK column. When I try to refresh data I get the error: "Query 'Survey Response' (step 'Expanded Response') references other queries or steps, so it may not directly access a data source. Please rebuild this data combination." Both tables are from the same Dataverse database.

To fix the issue I selected “File”, “Options and settings”, and “Options”, “Current File” select “Privacy”, select Privacy Levels “Ignore the Privacy Levels and potentially improve performance”, and select “OK”.

However, I don't think this is a best practice and I shouldn't have to do this because the 2 tables are from the same data source. This bug appeared sometime between Dec 2022 and Apr 2023 version of 64-bit desktop.

4 Comments

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous 

    So this happens only occasionally when you have a version between Dec 2022 and Apr 2023 version of 64-bit desktop, right? It's not like this error is reported every time you merge table, right?

     

    Best Regards,
    Community Support Team _ Ailsa Tao

  • Anonymous's avatar
    Anonymous
    Not applicable

    No, the issue occurs everytime I try to do a data refresh. I tried doing a merge between 2 other tables and I get the same error for those 2 tables as well. I have only tested this when the data source is Dataverse.

  • jjrscorpio's avatar
    jjrscorpio
    Frequent Visitor

    Hi,

    We were having the same issue with several reports where Dataverse tables were merged. We managed to solved the issue by setting the privacy level of the data source to Private instead of organizational. 

    I hope this help.

  • Anonymous's avatar
    Anonymous
    Not applicable

    I have changed the privacy level to Private and I still get the same error.