Hi,
I have posted this in another thread as a reply but would like to ask this in separate thread. We are currently working with the following products:
Power BI desktop (June edition) for report server
SSAS Tabular on-premise
SQL Server version: 13.0.4206.0.
The issue we are facing is that measures tend to get broken and returning unexpected exceptions as a result from using Power BI desktop. After a redeploy or full processing of the model everything is working as intended. After a while the error occurs again. I have noticed that if I build measures inside Power BI desktop (outside of the model) the measure that I’m using inside a new measure is the one that starts returning unknown exceptions.
We have used a simple SUM() measure that stops working when used with Power BI Desktop during a live connection to a SSAS Tabular Model. It is however working if you browse the SSAS Tabular Model on the server and in a a Excel connection. It has happened that it stops working both in the model and in excel. Then as mentioned above, a process full or redeploy has been necessary.
What is really strange is that if we recreate the same measure formula inside Power BI as a new measure, that measure work, but not the one from the model.
It seems that there is a problem with the live connection and tabular model that is throwing unexpected errors.
It would be really good if we could give some feedback on this. I have used profiler and the result is as follows:
*******
An unexpected exception occurred.
Query Text:
EVALUATE
ROW(
"TableName", 'TableName'[Measure]
)
*******
For the Measure that is created in Power BI the message is this:
EVALUATE
ROW(
"Measure", 'TableName'[Measure]
)
Any help would be appreciated
Best regards
Gustav
on:
URL is not filtering on field parameter
on:
URGENT!! Paginated Report not loading on Mozilla F...
on:
In desktop, 'Recent Sources' is not retaining new ...