Filter propagation, incomplete display

[Syndicate_Admin]

Good!!
I bring the following query, since I assume that by Filter Propagation the information is incomplete. I can't pass the pbi but being guided will be a great help.

I have a table with the clients distinguished by DNI and Cod.Ext.2 and another of Payments or Recovery in which there is also DNI and Cod.Ext.2, relating them by Cod.Ext.2 because there is DNI with several Cod.Ext.2.

The question is this when applying some segmentation to oper. the visualization is incomplete to me. The total payments of 4.4 Mill and when using a matrix with some segmentation of Oper the result is 3.4 Mill

Analyzing I see that in oper there are about 20000 accounts (Cod.Ext.2) different, that Recover has 514 (Cod.Ext.2) but only 462 are related to some of Oper. That is, there are 52 Cod.Ext.2 in Unrelated Payments to Oper. I have no way of looking at it by Related and I'm not finding another way to append it because the tables contain different information just matching in DNI and Cod.Ext.2. It is also difficult to make a single cod.ext.2 table because the required segmentations can find ambiguous information between the other tables in the model.

Please, if anyone has any solution or guidance you can give me it will be of great help. Thanks a lot!

[PaulDBrown]

It sounds like there is a problem with the model.
First of all, you should avoid using many-to-many relationships. You should create a dimension table for values of DNI ( containing all the DNI values present in the model) and a column including the corresponding unique Cod.Ext.2 values. Create 1-to-many relationships between this dimension table and the Oper and Recupero tables (delete the current relationship) via the unqiue Cod.Ext.2 field. Now build your measures, slicers, filters and visuals using the fields from the dimension table.
If the Cod.Ext.2 column contains duplicates, you will need seperate dimension tables for DNI and Cod.Ext.2 unique values. Both must  include unique values covering all the values present in the model.

EDIT/ you mention you have a table with DNI etc. if this table has unique values for Cod.Ext.2 you should use this as the dimension table to both the fact tables in one-to-many relationships. It is crucial that it contains all values present in the model

[vanessafvg]

sorry strugging to fullly understand what you are asking.     Are you able to actually show the data and show the problem properly and then show what you can expect.

Also have you looked at the lookupvalue function?   

https://docs.microsoft.com/en-us/dax/lookupvalue-function-dax