Donot recall problem RRS feed

  • Question

  • I have a MA (MA1) that had Donot recall checked.

    LastName had highest preference to MA1 and least to FIMMA. Even when the object is removed from the MA1 inbound, lastname value had the value of last synced from MA1 eventhough a new value was entered in FIM portal.

    Now, i unchecked the Donot recall attribute. FIM portal is still showing the value from the MA1. (the object is not in MA1 and the donot recall is unchecked).

    what am I missing?

    Wednesday, June 21, 2017 2:19 PM

All replies

  • To give more info - when i double click the object in metaverse serach, I donot see MA1 listed in connectors but in the attributes list, I could see that as contributing MA. Donot Recall is unchecked.

    Thanks in advance.

    Wednesday, June 21, 2017 2:53 PM
  • you need a full sync

    Nosh Mernacaj, Identity Management Specialist

    Wednesday, June 21, 2017 4:57 PM
  • I did FS. The new objects are working fine but the old objects that had donot recall checked before are still changing back to MA1 data.
    Wednesday, June 21, 2017 6:14 PM
  • I may be wrong, but I thought a FI and FS would fix it.

    If a FI and FS do not change that, This may be by design and the next option is to change those values in FIM Portal with a simple action Workflow.

    Nosh Mernacaj, Identity Management Specialist

    Thursday, June 22, 2017 2:39 PM
  • How do you do that? Whatever value we key in FIMportal is overridden in next fimma di /ds because of the precedence rule set for the attribute. MA1 gets high precedence than fimma  for that attribute.
    Thursday, June 22, 2017 3:27 PM
  • FI = Full Import, FS=Full Synchronization.
    These are different from DI=Delta Import and DS=Delta sYnchronization.

    Your Deltas will not change anything, but the full will.

    So the FI and FS should be ran on the MA1.  Run these please and let me know how it goes.

    Nosh Mernacaj, Identity Management Specialist

    Thursday, June 22, 2017 5:54 PM