Forum Discussion

Digger's avatar
Digger
Icon for Post Patron rankPost Patron
4 years ago

Query references other queries or steps, so it may not directly ac

Why after 1 year excellent work fck PBI begin show this error

 

Query (step 'Expanded _A_FullFilments') references other queries or steps, so it may not directly access a data source. Please rebuild this data combination.

 

only on refresh, no error in transform data, nothing was changed in database?

 

WTF?

8 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi  Digger ,

    Please review the following links which has the same problem as yours, hope the solution also can help you solve the problem.

    Power BI: Query references other queries or steps, so it may not directly access a data source.

    Go to File>Options/Setting>Options

    1. Uncheck Require user approval for new native database queries under Native Database Queries in Security options.

    2. Ignore Privacy level setting under privacy options


    Behind the scenes of the Data Privacy Firewall

    Power Query Errors: Please Rebuild This Data Combination

    Query references other queries or steps, so it may not directly access a data

     

    If the above ones can't help you solve the problem, please provide the applied codes of the query which get the error. If this query reference any other query, please also provide the related applied codes. Thank you.

    Query Editor – Editing M Code

    Best Regards

    • SDittmannFleet's avatar
      SDittmannFleet
      Icon for Advocate IV rankAdvocate IV

      This worked for me, but I am not sure it makes sense to me. Privacy settings were the same for both sources, so why that would start to pop up out of the blue at some point, who knows. Either way, thanks!

    • directvman67's avatar
      directvman67
      Frequent Visitor

      This did not work for me.  I am still having this error message despite having even separated things into 2 distinct queries (and Privacy Level checks are OFF).  Any thoughts?

       

      //Query Called Solution
      
      let
          Source = Excel.Workbook(Web.Contents("https://SHAREPOINT ADDRESS/Sample%20UPS%20Data.xlsx"), null, true),
          Sheet1_Sheet = Source{[Item="Sheet1",Kind="Sheet"]}[Data]
        in
          Sheet1_Sheet

       

      //Second query referencing the first query called Solution
      let
          Source = Solution,
          #"Promoted Headers" = Table.PromoteHeaders(Source, [PromoteAllScalars=true]),
          #"Added Custom" = Table.AddColumn(#"Promoted Headers", "Custom", each let
      
      Local_Access_Token = ACCESS_TOKEN,
      
          response = Web.Contents(#"UPS API Site", [
              
      RelativePath = "api/track/v1/details/" & [Ups Tracking Number] & "?locale=en_US&returnSignature=false&returnMilestones=false&returnPOD=false",        
              
      Headers=[Authorization="Bearer " & Local_Access_Token, transId="1", transactionsrc="PowerBI UPS Tracker"]]),
      jsonResponse = Json.Document(response)
      
      in
      jsonResponse)
      in
          #"Added Custom"

       

  • Anonymous's avatar
    Anonymous
    Not applicable

    Digger you are having this issue because you are merging two queries with a different privacy level. You can go to data source settings -> Edit permissions, and verify that all the sources are at either "None" or "Organizational" or "Public" privacy setting. Remeber, that not all privacy level sources can be merged.

    You can read more about privacy levels and which source can merge here https://learn.microsoft.com/en-us/power-bi/enterprise/desktop-privacy-levels

    • Digger's avatar
      Digger
      Icon for Post Patron rankPost Patron

      Anonymous no, you are worng im using same privacy levels

      • Anonymous's avatar
        Anonymous
        Not applicable

        Digger I had a similar problem which I resolved by in a similar manner. The error that I had was following

        Anyways, I hope you find a solution that fits your problem

  • Digger , Not very clear. If it using some reference table or some other tables are used in the refresh. Just refresh and check those tables on which this is dependent, are they giving any errors. If not post that refresh this and check

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi  Digger ,

    Whether your problem has been resolved? If yes, could you please mark the helpful post as Answered? It will help the others in the community find the solution easily if they face the same problem as yours. Thank you.

    Best Regards