Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Filtering corrupts visuals: Returns unexpected error

From one day to the next, all of a sudden a bunch of visuals in a PBI desktop file displays this error:

"Can't display the visual."

with details: "Couldn't load the data for this visual. An unexpected exception occurred."

The file worked fine the day before.

 

The error only happens when a visual has a filter applied, but it is not just caused by missing relationships in the model, as filtering only on columns in the same table produces the same error. If I filter by removing values (is not selection) the error does not occur, and the visuals are displayed correctly, so the data model works as it should. It is just when I filter by positive selection that visuals are corrupted.

 

If I try to browse the model in SSMS I can filter just fine getting the right data. I can't see how this is not a problem with Power BI?

 

The file connects to data through DirectQuery to a cube on a SQL server.

Updating PowerBI desktop to the newest version (see error details), did not remove the issue.

 

 

EDIT (moved from comments):

Yes, I use the connect live option to a SSAS cube in Power BI Desktop.

 

The operating system is 2012 R2 and the SQL server is 2017.

The project has compatability level: SQL Server 2016 RTM (1200)

 

I am told that the server has been updated with CU13, so I presume this is the issue. I am also told that this update cannot be rolled back, so we have to wait for a hotfix/new update. Any ETA on when the next update is released? I would love to give my client some useful info.

 

 

Error details (copied):

 

Feedback Type:
Frown (Error)

Timestamp:
2019-02-28T13:55:26.0968486Z

Local Time:
2019-02-28T14:55:26.0968486+01:00

Session ID:
429b61c5-190f-491d-a59b-363148096a84

Release:
February 2019

Product Version:
2.66.5376.2521 (19.02) (x64)

OS Version:
Microsoft Windows NT 6.3.9600.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 461310]

Peak Virtual Memory:
33.8 GB

Private Memory:
351 MB

Peak Working Set:
511 MB

IE Version:
11.0.9600.19267

User ID:
54214fae-781d-43f1-9671-e98a8e3c51dc

Workbook Package Info:
1* - da-DK, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

AS Live Connection:
True

Enabled Preview Features:
PBI_improvedFilterExperience

Disabled Preview Features:
PBI_shapeMapVisualEnabled
MIntellisense
PBI_SpanishLinguisticsEnabled
PBI_PdfImport
PBI_ColumnProfiling
PBI_variationUIChange
PBI_PythonSupportEnabled
PBI_showIncrementalRefreshPolicy
PBI_showManageAggregations
PBI_FuzzyMatching
PBI_EnableWebDiagramView
PBI_qnaLiveConnect
PBI_keyDrivers

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
100%

Supported Services:
Power BI

Status: Needs Info
Comments
v-yuezhe-msft
Employee

@Anonymous ,

Do you connect to SSAS cube in Power BI Desktop using "Connect live"option? If so, do you use SSAS 2017 installed with CU13? And what DAX functions do you use in the Power BI report?

Currenly, there is an issue with SSAS 2017 CU13 as described in this KB.

Regards,
Lydia

v-yuezhe-msft
Employee
Status changed to: Needs Info
 
Anonymous
Not applicable

@v-yuezhe-msft 

 

Yes, I use the connect live option to a SSAS cube in Power BI Desktop.

 

EDIT: The operating system is 2012 R2 and the SQL server is 2017.

The project has compatability level: SQL Server 2016 RTM (1200)

 

I am told that the server has been updated with CU13, so I presume this is the issue. I am also told that this update cannot be rolled back, so we have to wait for a hotfix/new update. Any ETA on when the next update is released? I would love to give my client some useful info.