However, if the field on the profile was set as a character field (rather than a datetime) then the 'date' would be passed into the date format function as a string and the actual format would need to be set.
1. It is recommended to keep the Date field type in the profiles and to avoid using a Date Format function. This way, if you are mapping from a source profile element to a destination profile element and both elements in have the date type defined, you do not have to set the Date Format using a function at all.
2. A sample use case where you would need to specify the AtomSphere internal format of (yyyyMMdd HHmmss.SSS) could be when you make a connector call in a map function. In this instance the date will be returned in the AtomSphere internal format of (yyyyMMdd HHmmss.SSS) and you may need to convert this format (for example, yyyy-MM-dd) to be used in a custom scripting step. You can then specify (yyyyMMdd HHmmss.SSS) as the source date mask in a subsequent date format step where you convert the AtomSphere internal format of (yyyyMMdd HHmmss.SSS) to the new format.