MATRIX GrandTotal calculation with TOPN multiples dimensions in same column (measure)

Hi Jose

I know you are trying hard to get help here, but I can't really start to help you with your DAX issues with the data model you have got.  This is the main model (for the benefit of others reading along)

In addtion there are 15 other tables that are not joined to the main model (not shown above to save space). 

This is not a good design for Power BI and looks to me like you have just loaded what is in your ERP system.  This is not what you should be doing.   Some questions I have for you:

1. why do you have a many to many relationship between RLSAplicacao and Movimentos?
2. and also between TKPIMestreV and TKPIMestre?
3. what is the purpose of the inactive relationship between CalendBase and TKPIObjMensal?
4. what is the purpose of the 15 tables not joined to the main model?
5. there are around 175 columns in the Movimentos.  What is the purpose of each of these columns in your report?

If you don't know the answers to these questions, then you haven't completed the first part of the data modelling process.

The way you should start the process is to look at the data table you need (presumably Movements in this case) and start from there. 

1. The purpose of columns in the data table are either to show transacitonal information or to provide a unique ID to a dimension (Lookup table)
2. The purpose of lookup tables is to provide more information about each transaction using the unique ID column
3. The purpose of relationships in Power BI is to propagate filters between the lookup tables and the data tables

Frankly I suggest you start again. 

• Read my article about how to load and structure tables in Power BI
• Start with the movements table and think about what you want to report on.  Load just the columns you need in the report
• Ask youself "who, what, when, where"  about each transaction in the table (these are the dimensions - there may be more)
• Make sure there is an ID column that uniquely identifies "who, what, when, where" 
• Load a look up table for each ID column.  Where possible consolidate other source tables into a single lookup table for each dimension

The bottom line is a Power BI reporting database is not the same as a transactional database.  If you simply load your transactional tables into Power BI you will be in for a world of pain.

Sorry to be the bearer of bad news.

Matt