Ive searched community and have not found anything describing the conversion anomaly Im experiencing, or the background cause.
We all have seen serial dates from excel, dates represented as numbers.
I have a set of data where often dates are represented as serial numbers from the source excel, but often are represented in "yyyy-MM-dd hh:mm:ss" format.
Easy to use the DateTime Parse tool.
This is string data so I looked to convert those in the "yyyy-MM-dd hh:mm:ss" format first, then catch the others that do not convert, Serial Date, and convert them using something along the lines of a formula like...
DateTimeAdd('1900-01-01',ToNumber([Name],1,1)-2,'days')
The anomaly is that certain groups of "numeric only" strings will convert with the DateTime Parse tool set on "yyyy-MM-dd hh:mm:ss" mode.
I have found these and think it strange they convert to all Jan 1, yyyy with that tool configuration.
10-54 convert to 2010-2054
55-99 convert to 1955-1999
1400-9999 convert to 1400-9999
Any dev's know why?
Any designers know the best work around?
(workflow attached)