Forum Discussion
Power BI Composite model on AAS (in DirectQuery) and other source - An unexpected exception occurred
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 impor...
rohit1991
Super User
Super UserThe 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:
- Switch to Import Mode: Use Import mode for the AAS model if possible.
- Optimize Relationships: Ensure relationships between [Date] and [_Year dict] are properly configured with correct cardinality and filtering directions.
- Check Compatibility Mode: While 1500 and 1600 are supported, ensure your AAS model aligns with the expected compatibility level.
- Test in Prior Version: If it worked before, try rolling back to the October 2024 Power BI version.
- 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,
- Optimize Relationships: I'm sure that it is OK
- Check Compatibility Mode: While 1500 and 1600 are supported, ensure your AAS model aligns with the expected compatibility level - Checked - -it's OK
- 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.
