I have a datasource (HR DB) with some date strings that I need to export to FIM. This date is not in a format "understood" by FIM, i.e. it looks like "YYYY-MM-DD hh:mm:ss", while FIM expects "YYYY-MM-DDT hh:mm:ss.fff" (where the 'T' is a literal T, no special meaning). I would like to know which is the recommended way to handle this. 1) Format the dates to the proper format in the data source (possibly the easiest solution, maybe not always possible) 2) Parse somehow the date in the inbound flow and write in the MV in the correct format (please note that only FIM handles datetimes as "native" data types, in other MAs and in MV they are treated as strings). In case 2, how to parse the date and convert it to the appropriate format? I have found this solution: I have defined the inbound flow as: Word(MY_DATE,1," ") + "T" + Word(MY_DATE,2," ") + ".000" => myDate and this seems to work, but I wonder if there's a simpler and cleaner way. I think that the "DateTimeFormat" function is not intended to do this kind of parsing. Maybe a "ParseDateTime" function could be useful? And then, how are dates displayed in the portal ? If I have, for example "2009-11-18T00:00:00.000" in the Metaverse and in the FIM connector space, when I look at the date in the portal I see "11/18/2009 4:00:00 PM". Why 4 PM? Cheers, Paolo Paolo Tedesco - http://espace.cern.ch/idm

The dateTime format with the "T" is just an xsDateTime and it's what we expect in the FIM service. The "T" delimits the date's end and starts the time. Sync's native datetime format for its internal data (like when an MA configuration was last modified) is the same but without the "T" delimiter. For MV and CS attributes, there is no datetime data type. You must use a string. If you expect to send that string attribute's value to the FIM service and portal, you should convert it to the xsDateTime format so that the service can store it and display it appropriately. Note that the datetime display format may vary according to region settings.AhmadAW