Attribute flows are shown duplicate when multiple csobject types flowing to a single mvobject-type

[mvaneijken]

Attribute flows are shown on each attribute flow that have a mapping to that same specific mv-object-type attribute:

So for instance I have 3 cs-objecttypes in my MA that flows to mv-object-type account:

1. normalaccount
2. adminaccount
3. serviceaccount

There are 5 attribute flows configured:

1. normalaccount (cs-object-type) - dn (attribute) --> account (mv-object-type) - dn (attribute)
2. adminaccount (cs-object-type) - dn (attribute) --> account (mv-object-type) - dn (attribute)
3. serviceaccount (cs-object-type) - dn (attribute) --> account (mv-object-type) - dn (attribute)
4. normalaccount (cs-object-type) - mail (attribute) --> account (mv-object-type) - mail (attribute)
5. adminaccount (cs-object-type) - adminmail (attribute) --> account (mv-object-type) - mail (attribute)

The effect is that attribute flows 1 - 3 are documented as they were configured for each cs-object-type - mv-object-type mapping, but with a different precedence.
Attribute flows that are configured with different source attributes are also shown on each cs-object-type --> mv-object-type attribute flow that have a flow to the same mv-object-type.

When a flow exists for that cs-object-type it seems to gather all flows from all cs-object-types that are linked to the same mv-object-type and includes those in the list. It does not check if this specific flow is linked to that cs-object-type in specific. When a specific cs-object-type is not having a flow to that mv-object-type, it's not shown in the list.

I would expect that it takes the cd-object-type into account to determine if that flow must be included in this specific attribute flow list. See screenshot of the MV.XML export using Export Server Configuration option: