The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
In the star schema shown below, it was possible to make one of the fact tables bidirectional in order to link the fact tables without the key of the master table. However, as the number of data and parameters increases, the calculation of the Power BI measure becomes very heavy. I would like to know how to deal with this problem
So I found "User-defined aggregations". Is it possible to reduce the load by this?
Solved! Go to Solution.
@Anonymous , You have a concept of aggregations, but the table need to be in direct query mode for an import aggregate
https://docs.microsoft.com/en-us/power-bi/transform-model/aggregations-advanced
@Anonymous , You have a concept of aggregations, but the table need to be in direct query mode for an import aggregate
https://docs.microsoft.com/en-us/power-bi/transform-model/aggregations-advanced
Thank you for your reply.
It turns out that this is not a relation issue, but a solution to the issue with direct queries.
thank you.
User | Count |
---|---|
65 | |
60 | |
55 | |
54 | |
32 |
User | Count |
---|---|
180 | |
88 | |
70 | |
46 | |
45 |