Issue with Decomposition tree in Desktop

[steven-myers]

Hi, I get an error when adding fields to Explain by to the Decomposition tree in Power BI Desktop.  

I am connected to SQL Azure Analysis Services database.   I also sent a frown. 

Feedback Type:
Frown (Error)

Timestamp:
2021-04-20T12:58:18.0783577Z

Local Time:
2021-04-20T08:58:18.0783577-04:00

Session ID:
15382f42-495f-4f96-bc2a-da9e2906d753

Release:
April 2021

Product Version:
2.92.706.0 (21.04) (x64)

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

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

Peak Virtual Memory:
38.5 GB

Private Memory:
703 MB

Peak Working Set:
921 MB

IE Version:
11.630.19041.0

User ID:
309b8ad6-3052-4afa-ae5e-b99d8d9a9cbe

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Enabled, runBackgroundAnalysis: True.

Telemetry Enabled:
True

Model Default Mode:
DirectQuery

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_shapeMapVisualEnabled
PBI_JsonTableInference
PBI_NewWebTableInference
PBI_ImportTextByExample
PBI_ExcelTableInference
PBI_qnaLiveConnect
PBI_eimInformationProtectionForDesktop
PBI_azureMapVisual
PBI_dataPointLassoSelect
PBI_compositeModelsOverAS
PBI_narrativeTextBox
PBI_dynamicParameters
PBI_anomalyDetection
PBI_newFieldList
PBI_cartesianMultiplesAuthoring

Disabled Preview Features:
PBI_SpanishLinguisticsEnabled

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
100%

Supported Services:
Power BI

[v-chuncz-msft]

@steven-myers 

You may check Known limitations and try earlier versions from Power BI updates archive.

[steven-myers]

Thanks  @v-chuncz-msft 

Strange I am using Azure Analysis Services with AI splits turned off which should work.  

As I am using a lot of the newer features going backward is not an option. 

[steven-myers]

This issue seems to be from using Direct query.  I use a live connection to the same analysis database and the decomposition tree works fine.  

[joel_gibby_csc]

Hello @v-chuncz-msft 

The documentation for Decomposition Tree says it now works with DirectQuery. 

We are using a DirectQuery to AS "local model" dataset with the underlying connection being an AAS model. 

There's no mention of this not being supported, but we're getting the following error:

Any insight or next steps to resolve is appreciated.

Thanks!

[MakalRD]

Exactly the same than @joel_gibby_csc is happening to us:

We have a Decomposition tree visual into a report where is connected to an AAS and also we have a Local Model because where are using the Fields Parameters feature.

@v-chuncz-msft any suggestion?

Thanks!