There appears to be a problem with the End to End Attribute Flows Summary tables. I'm not seeing that the table handles Outbound flows where a Metaverse attribute contributes to multiple Outbound flows within a single sync rule.
Using the provided Contoso data to generate a report and looking at the Contact Import Flows as an example, the Metaverse attribute sourceAnchor provides 2 outbound attribute flows within the 'Out to AAD - User Join' sync rule.
- Metaverse sourceAnchor flows out to dn with expression "CN={" & ConvertToUTF8Hex([sourceAnchor]) & "}"
- Metaverse sourceAnchor (and cloudSourceAnchor) flows out to sourceAnchor with expression IIF(IsPresent([cloudSourceAnchor]), IIF(Word([cloudAnchor],1,"_")=[sourceObjectType],IIF([cloudSourceAnchor] = [sourceAnchor],[sourceAnchor],Error("SourceAnchor attribute has changed.")),[sourceAnchor]),[sourceAnchor])
The same 2 attribute flows happen with the 'Out to AAD - Contact Join' sync rule.
This would lead me to believe there should be a total of 4 outbound flows from Metaverse sourceAnchor attribute. However each are represented only once in the table generated. I do understand that essentially the unique transformation and flows are displayed, however this isn't a true representation of every outbound flow used by Metaverse sourceAnchor.
There appears to be a problem with the End to End Attribute Flows Summary tables. I'm not seeing that the table handles Outbound flows where a Metaverse attribute contributes to multiple Outbound flows within a single sync rule.
Using the provided Contoso data to generate a report and looking at the Contact Import Flows as an example, the Metaverse attribute sourceAnchor provides 2 outbound attribute flows within the 'Out to AAD - User Join' sync rule.
The same 2 attribute flows happen with the 'Out to AAD - Contact Join' sync rule.
This would lead me to believe there should be a total of 4 outbound flows from Metaverse sourceAnchor attribute. However each are represented only once in the table generated. I do understand that essentially the unique transformation and flows are displayed, however this isn't a true representation of every outbound flow used by Metaverse sourceAnchor.