March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
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
Solved! Go to Solution.
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
@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
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
@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
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 😊
Now has strangely resolved itself........
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
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
User | Count |
---|---|
93 | |
90 | |
86 | |
76 | |
49 |
User | Count |
---|---|
166 | |
149 | |
99 | |
73 | |
57 |