Skip to main content

Date is not in proper format

David Paras
  • Updated

Issue:

Error message from the output text schema that I don't understand:

<ErrorDescription>Date is not in proper format: field name is RecordDate for defined format MM/dd/yyyy , field value = 09/16/2008</ErrorDescription>

It appears to me that 09/16/2008 matches the format MM/dd/yyyy. Am I missing something here?

Solution:

We assume you have set the date format to ‘mm/dd/yyyy’ for field : ‘RecordDate’ in the target text schema therefore data mapper and the text schema will take care of this format on its own.

Please try mapping the fields(‘EntryDate’ and ‘RecordDate’) one-to-one in data mapping without using ‘date-fomat()’ function of data mapper.

Related articles

Comments

2 comments

Date Votes
  • David Paras

    -

    I have an excel file as source and designed excel schema in UI, created a target file, target schema. I am facing problem converting string column in excel to date in output excel. In UI when I hit the test button, it's throwing errors.

    Here is a sample error record

    <ErrorRecord>

    <SourceRecord recordNumber="1">a,01/05/13,sai,20130220</SourceRecord>

    <ErrorDescription>

    Date is not in proper format, field name = generaltoDate and value = 20130220 for defined format MM/dd/yyyy.

    </ErrorDescription>

    </ErrorRecord>

    In source excel I have a column value as 20130220 and in target I am expecting it to be 02-20-1998 in target, but it's throwing the above error. How to achieve this?

    0
  • David Paras

    It looks like the defined input date format is MM/dd/yyyy, but you are passing yyymmdd. You can select this format in the input Excel schema.

    0

Article is closed for comments.