Problem with attribut changes in the Portal when the change is only a change in casing
I have a strange behaviour in my production FIM when i try to change a FirstName or Lastname or even a name on a MPR where the change is only about casing
Example a change from 'myname' to 'MyName' is ignored but a change to 'My Name' will work.
It's the same result if i edit the user through the Portal or i synchronize the value.
But my MPR's will be triggered and send my email notifying that a name change has occured, it's just dont write it to the database.
I have compared with a develop enviroment to se if i could find any diffrence in my SQL configuration, where this workes fine.
Hope someone has any input on how to track or solve this...
March 14th, 2011 8:26pm
This sounds like a known issue which is solved in the last build:
http://support.microsoft.com/kb/2417774
Issue 2
Case-only changes that are made to existing attributes are not applied to the FIM service database even though the Requests are marked as Completed.
So what versions are your dev/production on?
Also check:
FIM 2010 Build Overviewhttp://setspn.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
March 14th, 2011 9:44pm
Yes, I can confirm it's fixed in the latest build. Had that exact same issue. Created a workflow that fixed people entering their name in incorrect case and FIM didn't recognize a case change as a change. It's working fine in 4.0.3573.2
March 14th, 2011 10:47pm