Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Count Rows based on dynamic column value

Hi, I have a stacked bar chart with a line graph on and as a tooltip, I want to show the percentage value of each stack. I've tried various solutions, but to no avail. For example, for 2019, when I h...
ALLEXCEPT
COUNTROWS
distinctcount
Anonymous's avatar
Anonymous
Not applicable
5 years ago

No, I'm referring to the schema.

Anonymous's avatar
Anonymous
Not applicable
5 years ago

It's quite large, but the attached screenshot shows the two tables I'm using.

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    OK, I can tell you straight away you should change the way you model your data. It would take a small book to explain to you why the model is bad. But the fact is: it's very bad. I mean VERY. And I'm not talking about the tables. I'm talking about the relationships. Bi-dir relationships have been thought to solve some very specific issues. Namely, those with many to many relationships that require a bridge table. Nothing else. Second, the *-* (many-to-many) relationships have been designed to solve the issue of granularity and bi-dir filtering should never be enabled on them. If you leave the model as it is right now, very soon---or even now but without being aware---your model will start producting figures nobody will be able to explain and understand. Including you.

     

    I'm almost sure this model is ambiguous but the engine does not signalize it.

     

    Please do not make the mistakes other have. Change the model according to Best Practices of PBI modeling and dimensional modeling. This advice is all I can do for you right now. Ignore it and you'll be in for troubles later on BIG TIME.