Power BI Composite model on AAS (in DirectQuery) and other source - An unexpected exception occurred

[MWojcicki]

Hi,

Simple case o using Power BI with composite model. Model is based another AAS model (Azure Analisys Services, Tabular Model - DirectQuery Mode) and something else like table in Power BI or imported csv file which enrich dimension structure.

Semantic Model (in Power BI) is prepared in Mixed Mode:

* model A from AAS is in DirectQuery

* additional source is imported

Between table [Date] from model A na other imported table [_Year dict] there is relation :

... and it doesn't work. When I use on the same visualisation attributes from [Date] and [_Year dict] tables I get error:

OLE DB or ODBC error: An unexpected exception occurred.

from Power BI error tracking there is something more:

ProviderGenericMessage=[OLE DB error: OLE DB or ODBC error.], ErrorSourceOrigin=MsolapWrapper, OnPremErrorCode=, InnerErrorDetails=[Type=MsolapWrapper.MsolapWrapperException, Message=Failure encountered while getting the next row in the result-set]

Model in AAS work fine it if is alone. I tested with 1500 and 1600 compatibility mode.

Power BI is in newest november 2024 version.

I'm 100% sure that it was OK few weeks ago (til end of october 2024).

Something what I noticed extra:

If AAS model is in InMemory model - it works fine

When it is in DirectQuery (Tabular) model - there is problem as You read.

[MWojcicki]

Hello,

Someone cen confirm if it is possible to build composite model on AAS with model in DirectQuery (no Inmemory) ?

[rohit1991]

The issue arises because Power BI struggles to handle relationships between DirectQuery (AAS) and Imported tables in composite models, especially in DirectQuery mode for Tabular models. This was likely caused by a recent update (November 2024) since it worked previously.

Possible Solutions:

1. Switch to Import Mode: Use Import mode for the AAS model if possible.
2. Optimize Relationships: Ensure relationships between [Date] and [_Year dict] are properly configured with correct cardinality and filtering directions.
3. Check Compatibility Mode: While 1500 and 1600 are supported, ensure your AAS model aligns with the expected compatibility level.
4. Test in Prior Version: If it worked before, try rolling back to the October 2024 Power BI version.

[MWojcicki]

1. Switch to Import Mode - It is only workaround. I don't want to use full import mode because of: access to fresh data in AAS model, RLS on AAS level, 
2. Optimize Relationships: I'm sure that it is OK 
   
   
3. Check Compatibility Mode: While 1500 and 1600 are supported, ensure your AAS model aligns with the expected compatibility level - Checked - -it's OK
4. Test in Prior Version: If it worked before, try rolling back to the October 2024 Power BI version - checked on  2.131.1203 (July 2024) version - the same effect - it doeasn't work

So there is strong suspicion that the issue exists on the AAS side.