Any update for when the FIM MA will be fixed? RRS feed

  • General discussion

  • There are quite a bit of issues that need to be fixed in this ma related to Exported-change-not-reimported errors.

    1.  Case changes for FirstName and LastName, could be others..  When Stepongzi changes to stepongzi... the error gets thrown, You can't fix it by manually changing it in the portal.

    2.  Blank spaces can also not be fixed.. They also cannot be deleted from the portal object.

    The only workarounds that I have found are to delete the portal objects and recreate...


    Joe Stepongzi - Identity Management Consultant,
    Tuesday, August 17, 2010 2:31 PM

All replies

  • I too get case-changes not updating in the Portal.

    "red rover" to "Red Rover" doesn't work, I have to change add/remove a letter to get it to work. I thought this was my configuration...

    Tuesday, August 17, 2010 3:19 PM
  • Yep, also adding a value to each name works to.. but this should not be needed to be done..

    I guess just becareful when your doing your inital export to the portal.. Otherwise your going to have to worry about this after..

    I have about 70k objects right now.. and 1000 of them have this issue.. can't say that I am happy about it..

    Joe Stepongzi - Identity Management Consultant,
    Thursday, August 19, 2010 4:49 PM
  • I exported 20k objects to the Portal a month or so ago and already have a few hundred with spurious "exported-change-was-not-reimported" errors due to case changes. Agree: annoying.
    Thursday, August 19, 2010 7:16 PM
  • did any of you try to change SQL collaction for the database or specific tables from *_CI?


    i just don't have a lab now to check it. it might solve the problem.

    cause my collation for fim.ObjectValueString is Cyrillic_General_CI_AS - which definitely doesn't see any difference between red and Red. 

    Friday, August 20, 2010 7:10 AM
  • Also looks like codeless is breaking alot of things.. I can't do a rule to clear out an attribute... Not to mention precedance..
    Joe Stepongzi - Identity Management Consultant,
    Thursday, August 26, 2010 12:34 AM
  • Joe,

    I am seeing the same issue.  It is not just "being careful" during initial load.  My issue is stemming from HR changing the case on employees first and last names after creation.  I have 156000 objects and just passed 1000 exported-change-not-reimported.

    Really need an answer; it is hard to convince the client that "everything is OK" when 1000 "errors" are showing in the run statistics.

    Bob T

    Thursday, August 26, 2010 3:42 PM
  • I too am observing the same problem at one of my FIM sites ... definitely looks to me to be a Portal issue rather than anything to do with the FIM MA itself though - since the problem can be reproduced without involving any FIM MA interaction.


    Monday, August 30, 2010 11:06 AM
  • I would agree Bob... :)  Seems like more people see it with the exported-change-not-reimported error.. ah man... Now I have to change the title... lol.


    Joe Stepongzi - Identity Management Consultant,
    Monday, August 30, 2010 12:56 PM
  • I'm having a problem with this warning too, related to this thread. Basically, I was suggested to set an empty string when a value becomes null in a MA so that the value from another MA is not taken in the MV.

    Is there an open bug / feature request somewhere? This is really annoying...

    Paolo Tedesco -
    Tuesday, September 21, 2010 11:59 AM
  • Hi, all

    Just an update on this; word has it that there is a hotfix being tested right now and it should be released by the end of January 2011.



    Regards, Soren Granfeldt
    Thursday, December 23, 2010 7:54 PM
  • There is news in the matter; I'm just about to test it.


    Regards, Soren Granfeldt
    Monday, January 10, 2011 9:13 AM
  • There is news in the matter; I'm just about to test it.


    Regards, Soren Granfeldt

    The linked package is not particuarly new...
    My Book - Active Directory, 4th Edition
    My Blog -
    Monday, January 10, 2011 3:26 PM
  • Hi, Brian


    You're right, I am sorry; however, now there is an update in the matter, in case you guys missed it. Sorry to have wasted your time earlier with the erroneous post.



    Regards, Soren Granfeldt
    Tuesday, February 8, 2011 7:27 PM