Unparseable Date

OL Connect Professional DataMapper
1

I have a date field in my data mapper (Ex ‘2015-12-15’). I changed the type to ‘date’ and format to ‘yyyy-mm-dd’. However, when I go to connect design and try to print proof, I get an error ‘unparseable date’ and I cannot print proofs. Any suggestions? Thank you for your assistance.

2

Note that the date format in the DataMapper is NOT the date format you want to use, but rather an indication on how the DataMapper must read the date from the input file. Once it has been read and parsed properly, the date actually gets stored in a standardised way in the Connect database and you can then decide how you want to display it on the Template.

3

Correct. Once in Connect Designer, I format as a long date and it looks perfect, however, when I attempt to proof print I still get an error message “Unparseable Date”.

Any suggestions?

4

I tried it here and it works properly.

Have you tried other date formats? What’s your Windows system date format?

5

When I try other formats, the data greys out.

My Windows system date format is m/dd/yyyy.

6

“_the data greys ou_t” ???

I’m sorry, but I just can’t figure out what you mean. Did you mean to say the “date” greys out, or the “data” itself? Or did you mean the other “date” formats?

And where does it grey out: in the data model panel, on the template, in the Script dialog editor, only in proof print mode?

You can attach screen captures if you want, that might be easier: click on the little link icon in the toolbar above, then select the Send tab and upload the image.

Here’s a screen capture of my own test system showing what you want:

1552×662 38.2 KB

7

I’ve attached screenshots below.

The first is a screenshot of the date in Datamapper. The second is a screenshot of when I attempt to print proof samples in Connect Designer…

8

Could you also add a screen capture of Script dialog for that specific date field?

In addition, you could try expanding the Script and replacing the

formatter.dateLong(value)

expression with

formatter.date(value, "M/dd/y")

and see if that works any better.

9

Unfortunately, that didn’t work. When I click on validate results, the outcome is unparseable date. I’ve attached a sample file. https://learn.objectiflune.com/qa-blobs/4111071234821194506.xlsx

10

As explained in this other thread by the same poster ( Multiple Date Format - DataMapper - Upland OL User community ), this issue was resolved by ignoring the header line at the top of the CSV file.