Like many customers, we are having issues dealing with Daylight savings time and parsing this information. While we expect data to come in properly, only the DATE function goes a step further in its validation - is it a legitimate time/date.
While its understandable that the tool is just doing its job, we know that data coming in can use different timezones. It seems best practice for everyone to choose UTC as their default timezone.
1. Can we have an enhancement to allow us to set timezone (ASDATE) within the import job rather than just being system wide? [or if it exists, to highlight it]
2. Can we have an enhancement within Import to kick out those entries which do not validate so they could be imported during another action?
Folks can also refer to:
Please sign in to leave a comment.