Since yesterday, we experience a caching problem with some of our customers. The first opened report works without any issues while the next reports give the underneath error. The data set is cr...
We are currently experiencing the same issue in a similar setup and are seeing this on multiple tenants. I've noticed that for some reports we can sort of get around the issue by refreshing the directquery SSAS dataset.
Seems to me like this is a Power BI Service caching issue. 2 years ago the exact same issue was reported by Koen Verbeeck which was then solved (http://www.sqlservercentral.com/blogs/koen-verbeeck/2016/04/22/power-bi-service-error-this-visual-has-unrecognized-fields/). Did an old bug resurface?