Why SUMMARIZE can achieve many-to-one filtering and more

[FreemanZ]

hi All, 

I have some thinking about the many-to-one filtering. Wish to be commented:

Observation: one-to-many single direction relationship is always suggested. Many-to-one filtering can be achieved with SUMMARIZE. Expression like SUMMARIZE(FactTable, DimTable[DimCol]) ensures only those in DimCol that also appears in the fact table will be counted. 

What i have in mind: achieving many-to-one filtering with SUMMARIZE relies on an unspoken precondition - filtering is possible in any direction, as long as the columns are in one table (natively or virtually like expanded table). I guess this is also the case with denormalized flat table, where people don't need to care or even be aware of which is one and which is many. 

Does that make sense? How do you think about this? Is there better ways to understand this behavior?

[Anonymous]

Hi @FreemanZ ,

It's been a while since I heard back from you and I wanted to follow up. Have you had a chance to try the solutions that have been offered? If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

[lbendlin]

Mandatory reading:  https://www.sqlbi.com/articles/all-the-secrets-of-summarize/