none
Combining values from two MAs in a multi-value attribute RRS feed

  • Question

  • Hello,

    Is it possible to combine values from two MAs (e.g. an SQL MA and an AD MA) in the metaverse and export these back out to the AD MA for a multi-value attribute?

    Basically I want to set some standard email addresses from SQL, and combine these with any that might be added in AD (in other words not overwrite anything in the proxyAddresses attribute), but updates from SQL should be flowed through too.  

    Any ideas?

    Thanks,

    Henry

    Wednesday, May 8, 2013 7:08 PM

Answers

  • I'm not quite clear on the flows here.

    It seems to be one of two scenarios:

    1) You want to take a value from SQL and a value from AD, and flow them into a DIFFERENT multivalue field in AD (eg, SQL.mail, AD.mail and AD.proxyAddresses)

    2) You want to take a value from SQL and a value from AD, and flow them into THE SAME multivalue field in AD (eg, SQL.mail, AD.proxyAddresses and AD.proxyAddresses)

    It SEEMS like you want to do #2... you want people to be able to add values to proxyAddresses in AD, but also to add them via the SQL MA. You -might- be able to achieve this with equal precedence, but I wouldn't advise it.

    How:

    - Set direct import flow from SQL.mail->MV.proxyAddresses
    - Set direct import flow from AD.proxyAddresses->MV.proxyAddresses
    - Set direct export from MV.proxyAddresses->AD.proxyAddresses
    - Go to Metaverse Designer, select the user.proxyAddresses attribute, "Change Attribute Flow Precedence" and check "equal precedence"

    The default behaviour of equal precedence for multi-value attributes is that the values will combine. This works 'okay' if you combine two source attributes into a third destination attribute, but may have some problems if the destination attribute is also a source attribute. (how would you know when the SQL attribute should be removed?)

    It might work a bit better if you were using scenario #1.

    But, equal precedence has been deprecated (thankfully), so you're best off not using it.

    If I was doing #1, I'd flow the two source attributes to two attributes in the MV, then use an advanced export attribute flow with a rules extension that combined them (you could configure something similar if you use portal-based Sync Rules)

    What are your target and destination attributes?

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    • Marked as answer by henryblackman Thursday, May 9, 2013 12:33 PM
    Thursday, May 9, 2013 7:49 AM

All replies

  • I'm not quite clear on the flows here.

    It seems to be one of two scenarios:

    1) You want to take a value from SQL and a value from AD, and flow them into a DIFFERENT multivalue field in AD (eg, SQL.mail, AD.mail and AD.proxyAddresses)

    2) You want to take a value from SQL and a value from AD, and flow them into THE SAME multivalue field in AD (eg, SQL.mail, AD.proxyAddresses and AD.proxyAddresses)

    It SEEMS like you want to do #2... you want people to be able to add values to proxyAddresses in AD, but also to add them via the SQL MA. You -might- be able to achieve this with equal precedence, but I wouldn't advise it.

    How:

    - Set direct import flow from SQL.mail->MV.proxyAddresses
    - Set direct import flow from AD.proxyAddresses->MV.proxyAddresses
    - Set direct export from MV.proxyAddresses->AD.proxyAddresses
    - Go to Metaverse Designer, select the user.proxyAddresses attribute, "Change Attribute Flow Precedence" and check "equal precedence"

    The default behaviour of equal precedence for multi-value attributes is that the values will combine. This works 'okay' if you combine two source attributes into a third destination attribute, but may have some problems if the destination attribute is also a source attribute. (how would you know when the SQL attribute should be removed?)

    It might work a bit better if you were using scenario #1.

    But, equal precedence has been deprecated (thankfully), so you're best off not using it.

    If I was doing #1, I'd flow the two source attributes to two attributes in the MV, then use an advanced export attribute flow with a rules extension that combined them (you could configure something similar if you use portal-based Sync Rules)

    What are your target and destination attributes?

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    • Marked as answer by henryblackman Thursday, May 9, 2013 12:33 PM
    Thursday, May 9, 2013 7:49 AM
  • Thanks so much for your answer - I really appreciate it.

    You're right, I was thinking of attempting #2 - and I was still wondering if it would work.  The background is that we set 'standard' email addresses when we create accounts in Exchange, but the Exchange team often need to give people (based on their needs) additional addresses.  So the complexity of deleting an address from SQL wouldn't be there.  However as equal precedence is deprecated, then an advanced export flow with a rules extension seems the way forward - I was hoping to avoid it ;-)

    Thanks,

    Henry

    Thursday, May 9, 2013 12:33 PM
  • Word on the street is that equal precedence is going to be around for a while, even though it's deprecated.. however, use of it is generally an indication of a poorly designed solution.

    But yes, to achieve what you're trying to do, it would either be a Rules Extension or a SR that combines the two in the portal... My personal preference is for a Rules Extension - Don't be afraid of them!

    - Ross Currie


    FIMSpecialist.com | MCTS: FIM 2010 | Now Offering ECMA1->ECMA2 Upgrade Services

    Friday, May 10, 2013 3:32 PM