none
Another question related to Expected Rule Entries RRS feed

  • Question

  • I have a basic scenario. I just import a user from csv-file to Fim Portal and then import it to Ad. Then I removed the user using Fim Portal and then export modifications to the Ad. So basically I am in the situation where the whole system should be untouched.

    But still Expected Rule Entries stays in the metaverse. I thought EREs should be removed also.

    So when EREs are removed from the system?

    Thursday, February 12, 2015 1:01 PM

Answers

All replies

  • Hello,

    You have two ways to delete them in the MV:

    • Simple delete them in the Portal (manually or with the Expiration workflow)
    • Use a workflow to set an ERE in "Remove" mode. Once it's imported to MV, the system will delete the previous "Add" ERE and the second one "Remove" in the MV and then in the Portal.

    Regards,


    Sylvain

    Thursday, February 12, 2015 1:43 PM
  • Hello,

    EREs are only removed by your rules, pre FIM 2010 R2 SP1 there where a Stored Procedure to remove "orphaned" EREs (ERE with no object reference) but this was gone in SP1.

    I remember there is some debug.RemoveObjectByType SP but never used that.

    There are some hints to avoid orphaned ERE, look at the following article:

    http://social.technet.microsoft.com/wiki/contents/articles/2019.how-to-avoid-orphaned-expectedruleentry-objects.aspx

    I still use the "housekeeping" OOB method, with a Set/Workflow/MPR combination letting the Expiration Workflow delete ERE with no Resource Parent.

    This method is described here:

    https://social.technet.microsoft.com/Forums/en-US/1af6cf77-4c55-4a3e-93cc-0baae80bc88f/expiration-workflow-cannot-delete-ere?forum=ilm2

    -Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    • Marked as answer by 2xTsei Friday, February 13, 2015 10:06 AM
    Thursday, February 12, 2015 1:50 PM
  • Hello,

    EREs are only removed by your rules, pre FIM 2010 R2 SP1 there where a Stored Procedure to remove "orphaned" EREs (ERE with no object reference) but this was gone in SP1.

    I remember there is some debug.RemoveObjectByType SP but never used that.

    There are some hints to avoid orphaned ERE, look at the following article:

    I still use the "housekeeping" OOB method, with a Set/Workflow/MPR combination letting the Expiration Workflow delete ERE with no Resource Parent.

    This method is described here:

    -Peter


    Peter Stapf -  - My blog:

    Thanks!

    According to this, how much these EREs will affect to the FIM performance. Of course there is not right answer for this but what I mean is do I need to care about removing EREs?

    Friday, February 13, 2015 6:13 AM
  • Hello,

    hard to guess how much the impact is on performance.

    Depends also on your SQL configuration as well as the amount ob objetcs and Connectors you have. but over the time there will be a impact. So you should care about this.

    The more objects you have, and the more connectors (MA) you export to, the more you should care on remove orphaned EREs and better design system to avoid the amount of those EREs.

    -Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Friday, February 13, 2015 8:58 AM
  • Hello,

    hard to guess how much the impact is on performance.

    Depends also on your SQL configuration as well as the amount ob objetcs and Connectors you have. but over the time there will be a impact. So you should care about this.

    The more objects you have, and the more connectors (MA) you export to, the more you should care on remove orphaned EREs and better design system to avoid the amount of those EREs.

    -Peter


    Peter Stapf -  - My blog: 

    Ok, thanks.
    Friday, February 13, 2015 10:06 AM