Forum Discussion

tenfingers's avatar
tenfingers
Advocate II
5 years ago
Solved

Strange error message with calculation item

Hi all,

I just started getting this error message with a calculation item. Ive never seen it before and cant think of anything that has changed in the model that would affect this. I couldnt find any reference to it with google. Any ideas?

CHeers

  • I ended up discovering the cause of this and so thought I would post it in case someone else comes across this error.
    The calculation item in the error referenced a measure which had stopped working because a column data type had changed. Seems simple but there were quite a few measures in the calculation item and it took a while to find the broken one. Also the error message seemed to me to point to a different issue. Not sure how it was working for me and not another user when one of the measures referenced was broken and a column data type was changed.
    Cheers

6 Replies

  • I ended up discovering the cause of this and so thought I would post it in case someone else comes across this error.
    The calculation item in the error referenced a measure which had stopped working because a column data type had changed. Seems simple but there were quite a few measures in the calculation item and it took a while to find the broken one. Also the error message seemed to me to point to a different issue. Not sure how it was working for me and not another user when one of the measures referenced was broken and a column data type was changed.
    Cheers

  • Some further details:
    The sames visuals and report work in the file containing my model in desktop but when published or in a live connected report they return the error. 
    Cheers

  • tenfingers , One is clear cache and try.

    2. How is this connected. You have updated the crendential in power bi service or it is using gateway.

    See like some security on a object is issue. Not very clear on that

    • tenfingers's avatar
      tenfingers
      Advocate II

      Thanks amitchandak 

       

      The issue resolved by itself. Not connected through a gateway , source is OData and credentials correct. I think you may be right on the cache as it was fixed for me but persisted for a different user. Thanks for replying 😊

  • Anonymous's avatar
    Anonymous
    Not applicable

    tenfingers 

    Thank you for share your findings. You may mark it mark solution so others can find it more quickly. 

     

    Paul Zheng _ Community Support Team