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.
I am unsure how to model my data...
I have a model where in my Project dimension, I have an attribute (AgreedReturn), which is a number. Its been part of my model for months; all good!
My problem just appread now; I have a requirement where users want a SUM of that attribute.
This is very confusing to me... AgreedReturn clearly belongs to the Project dimension, but, it messes it up that they want ‘math’ applied on it. What is the right modeling approach to this? Am I forced to move this attribute to the fact somehow??
@Anonymous , You can have like
Sumx(Project , Project [AgreedReturn])
or
Sumx(Fact, related(Project [AgreedReturn]))
or
Sumx(Summarize(Project , Project [AgreedReturn]), Project [AgreedReturn])
Yes, but for this:
Sumx(Fact, related(Project [AgreedReturn]))
I would have to change the direction to filter to BOTH TABLES, right?