Forum Discussion
Best Practise question for Modelling in Powerbi/Tabular - Avoiding Chained/Nested Chasm Traps
Another recommended approach is to merge your Client and Matter table into one single denormalised table. Since both of your tables need to link via the Matter ID, this relationship will still work and you can still organise filters by the Client data.
I was considering that idea, however my matter and client dimensions are pretty big. So for end users i think i need to keep them split up.
Being big is actually the reason to merge them. The way the engine stores and compresses the information will likely mean it won't make a large change to the model size, but there is likely to be a performance gain.
From an optimisation standpoint, you can remove unnecessary columns, although from your screenshot you seem fairly lean already, which is a good thing.