I am receiving this warning when doing a Full Import/Full Synchronization on my FIM MA after doing an Export on my FIM MA. I have 2 attributes (MiddleName and RoomNumber) that may not have values coming from my source data store. My source data store (SQL table) writes a <space> (" ") in the value because it does not allow NULLS. Exporting this <space> to the FIM Portal appears to work fine but my suspicion is that the FIM Portal does not allow a <space> to be written into the data store and the reimport is actually a NULL. If I am correct, in my ISR do I check for a <space> and write a NULL (which still doesn't work)? Example: (IIF(Eq(MiddleName," "),Null(),MiddleName)) ADDITIONAL INFO: I did the ILM implementation of this entire IDM system. I am now upgrading the ILM environment to FIM and having to convert the ILM data flows to FIM Portal. I only have problems with data flows going to FIM Portal (not the Synch Service only). SO I know this has somethign to do with data stored in the FIM Portal.

Hi Jb I think you should take a look at you FIMMA Attribute flow and and check if the export flow for middlename has checked the "Allow nulls" option. regards

if possible, you could also write EMPTY in that attribute in your SQL data store. Then using an advanced inbound attribute flow translate that EMPTY in the connector to a NULL value in the MV -- Cheers, (HOPEFULLY THIS INFORMATION HELPS YOU!) # Jorge de Almeida Pinto # MVP Identity & Access - Directory Services # BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx ------------------------------------------------------------------------------------------ * This posting is provided "AS IS" with no warranties and confers no rights! * Always test ANY suggestion in a test environment before implementing! ------------------------------------------------------------------------------------------ ################################################# ################################################# ------------------------------------------------------------------------------------------ "jbwilliams11" wrote in message news:0095aaf9-ac8a-4cd0-84a1-3177f968f2ca... I am receiving this warning when doing a Full Import/Full Synchronization on my FIM MA after doing an Export on my FIM MA. I have 2 attributes (MiddleName and RoomNumber) that may not have values coming from my source data store. My source data store (SQL table) writes a <space> (" ") in the value because it does not allow NULLS. Exporting this <space> to the FIM Portal appears to work fine but my suspicion is that the FIM Portal does not allow a <space> to be written into the data store and the reimport is actually a NULL. If I am correct, in my ISR do I check for a <space> and write a NULL (which still doesn't work)? Example: (IIF(Eq(MiddleName," "),Null(),MiddleName)) Jorge de Almeida Pinto [MVP-DS / AD DS TechNet Forums Moderator] [Sr. Technical Consultant @ Oxford Computer Group] (http://blogs.dirteam.com/blogs/jorge/default.aspx) (http://www.oxfordcomputergroup.com/)

The source data source (SQL Table) stores a <space> if no value is entered in the value from the application. Then this <space> is mapped to an attribute in the FIM Portal via the Inbound Sync Rule and this also populates the MV. Then I run the Export on my FIMMA to the FIM Portal with no issues (so I am assuming the <space> is being written b/c of lack of error). Only when I do the confirming import do I get the issue. The Allow Nulls option is on the Outbound Sync Rule (Destination tab) and I do not have that configured yet to the eventual target data source. I am just populating the FIM Portal at this point.

I am not able to modify the application to write an empty in the database.

Could you give mor infor about if I got it right you have: FIMMA and SQL MA, then you have some Flow attribute config in your fimma an a ISR for SQL MA. ? regards

Hi Jb I as trying and I did the follow function in my ISR. IIF(CustomExpression(Ispresent(MiddleName)),MiddleName,"") or IIF(CustomExpression(Ispresent(MiddleName)),MiddleName,Null()) Hopefully it works for you. regards

This is a known issue and we are working on it. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

This is a known issue and we are working on it. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation Markus, is there any update on this issue? I have applied the Update 1 and the hotfix for 2477714 (to solve the problem of case changes causing the exported-change-not-reimported error), but now I am also getting bitten by this bug where a NULL or empty ("") MiddleName attribute causes an exported-change-not-reimported error as well.

Build 4.0.3573.2 fixed the case sensitivity issue. If you're getting errors because of an empty string in your attributes you should look to fix your data. If you can't do that at source, use an IIF statement in the SR to not flow an empty string, e.g. [untested, check for syntax] IIF(IsPresent(MiddleName), IIF(Eq(MiddleName, ""), Null(), MiddleName), Null()). I used this approach. I had to look for both an empty string "" and a space " ". :(