Attribut precedence RRS feed

  • Question

  • Hello,

    I have some issues with precedence 

    I have this situation

    MA1  MV FIM Portal

    Att1   mvAtt1 prtAtt1

    MA2  MV FIM Portal

    Att2   mvAtt1 prtAtt1

    In flow precedence i have this for mvAtt1 ( MA1,MA2)

    When i run a import from MA2 first with and i run a synchro and export in FIM , i have skipped not precedent ? 

    Can someone explain me this ? And how can i manage this 



    Friday, March 27, 2015 12:05 PM

All replies

  • Precedence works as follows.

    1. MA with the highest precedence has the final say. No matter what order you run them. IF MA1 has the highest precedence, only value provided by MA1 makes it to MV.  If MA1 is disconnected, the second on line provides that value, and so forth.

    2. If you have equal precedence, then it the MA who had changed last takes over.  This is tricky business and depends on what you run when.  I do not recommend it.

    3. Manual precedence, is based on code.  Pretty much anything you code.

    I am not quit sure what you are trying to accomplish, but it this is not clear, please let me know what your requirement is. What you need to accomplish?

    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Nosh Mernacaj Thursday, May 28, 2015 6:48 PM
    Friday, March 27, 2015 2:08 PM
  • Thanks for your reply

    This is my problem  : 

    I have the attribut displayName 

    The precedence is AD MA,File MA

    I import a user from the file MA with a displayName but when i run a synchronisation i have skipped not precedent and the value is not exported to FIM portal.

    Friday, March 27, 2015 2:26 PM
  • That is correct because AD has the higher precedence, it means AD will override it.

    You need to remove mapping for displayName from AD --> MA Import.  Or simply make AD second, not first.

    Nosh Mernacaj, Identity Management Specialist

    Friday, March 27, 2015 2:31 PM
  • I thought that even i have AD as higher precedence and the value is blank in the metaverse the file MA will write the value in the metaverse. 
    Friday, March 27, 2015 2:40 PM
  • Precedence does not care what the value is, NULL or NOT. It simply sees who has the authority. It simply updates the filed with the value from the MA with the higher precedence.

    Nosh Mernacaj, Identity Management Specialist

    Friday, March 27, 2015 3:01 PM