Forum Discussion
Aggregations between SQL and Lakehouse
Hi,
Considering I have a table called Fact_Table (Year, Month, some more fields and numeric detailed values) and another called Fact_Aggr containing the aggregation of the Fact_Table records by Year and Month, I have the following problem:
Let's consider I get fact_Table from the lakehouse (direct query) and fact_aggr from SQL (Import), and configure fact_aggr as an aggregation from fact_table. The aggregation is ignored and the DAX direct query is always executed.
If I do exactly the same. loading both tables from SQL (one using direct query and the other using import), the aggregation works perfectly.
I know in the past it was not possible to make aggregations between different data sources, but nowadays we can make the aggregation configuration, however it doesn't work.
Am I missing something? Is there something else needed for the aggregation to work?
I know about the limitation to not use SSO connections, but I don't think the connection is using SSO, in fact, it works if the direct query table comes from SQL.
What else could I try?
3 Replies
- AnonymousNot applicable
Hello DennesTorres ,
Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.- AnonymousNot applicable
Hi DennesTorres ,
Apologies for the delay in reply from our side.
Unfortunately we didn't get any update from the internal team regarding the ask.
I kindly request you to raise a support-ticket here. Our team will coordinate with you and help you with the same.
After creating a Support ticket please provide the ticket number as it would help us to track for more information. Hope this helps. Please let us know if you have any other queries.- AnonymousNot applicable
Hi DennesTorres ,
We haven’t heard from you on the last response and was just checking back to see if you got a chance to create a support ticket.
Incase if created, please provide the ticket number as it would help us to track for more information.
Thanks,
Gopi Krishna Chenna