The record in the file is:
2011-10-21 15:43:11
The file stage shows the record as:
2011-10-21 15:43:11
I use the TimeStamp transformation:
Name: TIMESTAMP.TO.DATE
Definition: Timestamp(%Arg1%, "DATE")
Arg1 = Timestamp
and this warning comes up:
..LandXfrm (Timestamp) transform error: Invalid timestamp input '2011-10-21 15:43:11
'
Thank you for your help!!
Issue convertin date record from a file
Moderators: chulett, rschirm, roy
Looking at the help files for TIMESTAMP.TO.DATE, it expects only one parameter, never having used it, are you sure you are able to use two parameters?
That aside, is the single quote on the second line a fault in your formatting or is that the actual error? If that's how the error was output, you must have a newline being consumed as part of the field.
That aside, is the single quote on the second line a fault in your formatting or is that the actual error? If that's how the error was output, you must have a newline being consumed as part of the field.
Hello Kryt0n, as I understand, this "Built-In" Transform, the "DATE" word between quotation marks is to indicate to what data type is going to be transformed/converted the supplied parameter/argument.
About the single quote mark, is how the director shows the "Event detail".
That single quote mark is not in the origin file, I supose the begin/end single quotes marks are put by DS so I don't know why DS puts the last one in a next line neither...
About the single quote mark, is how the director shows the "Event detail".
That single quote mark is not in the origin file, I supose the begin/end single quotes marks are put by DS so I don't know why DS puts the last one in a next line neither...
Sorry, my fault, I thought you were specificying "DATE" in the TIMESTAMP.TO.DATE call, I didn't read properly!
It isn't the single quote I am interested in but whether it is picking up a carriage return as part of your field thus making the timestamp invalid. How have you defined your row delimiter? And do a hex dump of your data file and check the actual delimiter matches what you've defined
It isn't the single quote I am interested in but whether it is picking up a carriage return as part of your field thus making the timestamp invalid. How have you defined your row delimiter? And do a hex dump of your data file and check the actual delimiter matches what you've defined