Forum Discussion

Otavio_bhz's avatar
Otavio_bhz
Regular Visitor
9 years ago
Solved

The query referenced column ****** which depends on another column

Hi all,

 

I have updated done my query in power bi destop and worked well.

But when I upload that, works well to, but when I update from the web, it appear the foollowing message:

 

The query referenced column ******** which depends on another column, relationship or measure that is not in a valid state.

 

Does someone know why that is happening ?

 

- Power bi destop ok and update (ok)

- Power bi web after upload (ok)

- Power bi after update (Appear that problem)

 

Thank you very much,

 

KR

 

Otavio

  • Otavio_bhz's avatar
    Otavio_bhz
    9 years ago

    Hi All,

     

    I could solve the issue with the Power Bi update via WEB update.

     

    The problem was that on desktop, if you use int values on imported files those “variables” works fine.

     

    But when you upload that and update, the web system don’t understand as int, and the problem come when you use related() and calculation.

     

    Then I have changed all the columns from integer to number % and everything is fine now on the Web.

     

    Thank you very much for your help,

     

    Kr,

     

    Otávio

23 Replies

  • David_Monivas's avatar
    David_Monivas
    Frequent Visitor

    In my case, the web update was a temporary fix. After a few hours, the problem reappeared, and it was really frustrating.

    I tried almost everything: checked column types, references, formulas... and then I started to backtrack through my panel until I found the "change" that I think triggered everything.

    My panel had a table with one column serving as an index to centralize all relations between tables in a star. This table was constructed in DAX by joining all the IDs from all the tables and ensuring that we had all possible IDs. But to prevent errors, I introduced a FILTER in that formula to remove empty values. It was working fine (although terribly slow and inefficient). To improve efficiency, I removed the Filter, relying on DISTINCT.

     

    Since then, I've been experiencing troubles, and here's my theory: the index isn't being calculated correctly online in DAX, which is causing the problem. Any duplications, empty values, etc., and the panel crashes. How come that it happens only online? My guess again. In desktop is not case sensitive. Online IT IS. That's leaving duplicated values in the Index column which leads to the error.

     

    My solution: I moved the creation of the index table to Power Query (Power M) before actually using the panel. It's not as efficient (takes more time), is case-sensitive, and more complex, but the benefits are the same, and now the panel is stable.

    I apologize if any of what I'm saying sounds like nonsense to experts; I'm a total newbie in Power BI. I just wanted to share my experience in case it gives any ideas to anybody with better insight into the actual workings of Power BI.

    Thanks!

  • Anonymous's avatar
    Anonymous
    Not applicable

    Otavio_bhz

     

    Do you use on prem sources or online sources for your model?

    And what kind of sources? (Excel, SQL etc.)

  • This seems to be happening to me too and I just updated to the latest version on the desktop to see if that was the problem.  

    Creating the report in PowerBI Desktop, then publishing to Cloud is fine.  Once you do any type of refresh, whether manually or through the scheduled refresh - the visuals just bomb out.

    The only way that seems to be a workaround is refreshing the report in the desktop then publishing to the cloud.

    Not sure if this is a bug or if it's relating to all those date/time reference problem or something else I'm missing.

    I have 2 datasets, one from SharePoint Online (from a list) and one from SQL Server On Prem. The SharePoint Online is imported and then a relationship made to get some end reporting.  When I had split these two datasets to two different pbix files and refreshed them through the cloud scheduling - it works fine.  

    Even tried converting the direct queries to imports and that still didn't work.  The part that is frustrating is that the message isn't very helpful and on top of that the refresh works - it doesn't throw an error, but the visuals aren't loading.  (really?!)

  • PSG83's avatar
    PSG83
    Frequent Visitor

    IncursioML1  - do you solved your Issue? Facing the same right now for my Update on the Service. I only have a Dataset Live Connection and an Databricks Connector setup in this Dataset.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi all, I am facing this error "The query referenced column 'data'[sample] which depends on another column, relationship or measure that is not in a valid state. Additional information: ''.

    The vissuals are showing in Power BI Desktop but not displaying in the Power BI service. Appreciate your quick response on this. Thank you

     

     

     

     

     

  • Anonymous's avatar
    Anonymous
    Not applicable

    Is there any news about latest issues?

    Couple of visuals in Power BI Service also show errors:

    The query referenced calculated column 'Table'[Column] which does not hold any data because evaluation of one of the rows caused an error.


    The query referenced column 'Table'[Column] which depends on another column, relationship or measure that is not in a valid state. Additional information: ''.

    In Power BI Desktop no errors occoured.

    • Anonymous's avatar
      Anonymous
      Not applicable
      Same issue

      Hi I also get an issue like this. Has this issue been resolved?
      Thankss..

       

  • RHOU's avatar
    RHOU
    Icon for Advocate III rankAdvocate III

    I have the same issue. My model includes imported tables as well as a live connection to an additional PowerBI dataset with relationships between the two. When I use the calculated field directly in a visual, the error changes slightly: "The query referenced calculated column XXX which does not hold any data because evaluation of one of the rows caused an error."

     

    The issue started, when I added a calculated column in my imported tables that pulls data from the live connection dataset. 

     

    Therefore, I'm guessing that the refresh on Desktop can properly handle this, but on the Service the calculated column is not properly calculated. 

    For the other ones that have this issue, do you also have calculated columns that access some tables that are connected via live / direct query model? 

  • Jay95's avatar
    Jay95
    Regular Visitor

    I have the same problem. Could you please help? 

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi I have a similar Issue. I have a master data where i have price field. I joined this with Transactional data with a joining key. and then used related function to bring price in transactional table. I have given data type as decimal number with 2 decimal places. It works fine in Power BI desktop, but wehn kept on schedule in service, it is blowing off the visuals. Can some body help this??

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi All. I used look up value function as an alternatiive and did not face this issue.