Import Attribute Flow not applied for an attribute on equal precedence RRS feed

  • Question

  • I have a direct Inbound attribute flow for attribute proxyAddressCollection in metaverse from FIM MA and AD MA. In the metaverse designer I have set the attribute flow precedence as Equal Precedence. I have imported the value for the attribute from FIM portal and the value shows well in FIM MA connector space. When I run a preview, I see that the import attribute flow is not applied and the value is not flowed into the metaverse. It behaves like there is no inbound flow rule from FIM MA to metaverse

    Any suggestions would be highly appreciated

    Wednesday, June 14, 2017 6:39 PM

All replies

  • Hi Mohith,

    Firs of, let me start by saying how bad the equal precendence is. It is really tricky and unless you cannot do without, I strongly suggest getting away from it.  This means the last MA who made the change wins. Are you sure AD was not the last to write to it? 

    Secondly, since you are using the equal precendence, order of operations is very important.

    So, You need to see who wrote last to the MV and if the value in FIM is not changed, nothing will happen really.

    I think you have done already, but double check these steps

    1- Import Mapping in FIM MA for proxyAaddressCollection --> proxyAddressCollection

    2- Import Mapping in AD MA for proxyAaddressCollection --> proxyAddressCollection

    Do you expext these addresses to flow to AD? if yes, you need to run the jobs in this particular order,

    • DI in FIM MA
    • DS in FIM MA
    • E to AD
    • DI in AD MA
    • DS in AD MA

    Maybe a little background on what the business case is for this would help us help you.

    Nosh Mernacaj, Identity Management Specialist

    Wednesday, June 14, 2017 7:19 PM
  • Hi Mernacaj,

    Yes. we are populating proxyAddressCollection to AD. 

    The situation is that initially the value for proxyAddressCollection is not in metaverse yet. The request comes for an email on the FIM Portal, we populate proxy address collection through a workflow.

    On Equal Precedence:

    We run FIM DI. This job is populating the value for proxyAddressCollection in FIM MA connector space well.

    We run FIM DS. This job does not apply the value into the metaverse. It is behaving like there is no Import attribute flow rule.

    Remove Equal Precedence and put FIM MA on top:

    We run FIM DI. This job is populating the value in FIM MA connector space well.

    We run FIM DS. This job does  apply the value into the metaverse. Everything works perfect

    My question is why is it not working on Equal Precedence?

    Thursday, June 15, 2017 6:49 PM
  • Hi Mohith,

    True or false.

    - A brand new user. You run FI-FS in FIM MA, and nothing gets written to MV?

    Nosh Mernacaj, Identity Management Specialist

    Thursday, June 15, 2017 7:16 PM
  • False
    Friday, June 16, 2017 12:59 PM
  • So why not follow these steps all the time, then, First run FIFS in FIM MA and then AD stuff.

    This is what I was telling you earlier about the order of operations being important.

    In some cases, Deltas may not work and you would have to do FS.  A little trial and error.

    Nosh Mernacaj, Identity Management Specialist

    Friday, June 16, 2017 1:51 PM