AnsweredAssumed Answered

Date format mapping behaviour

Question asked by donkhuth on Sep 7, 2018
Latest reply on Sep 7, 2018 by donkhuth

Hi all,

 

I've come across an odd issue with the mapping of a date field and I'm not sure if the results are correct.

When mapping a valid date, the results are as expected, but when mapping an invalid date, rather than throwing an error, the dates are automatically calculated.

 

For example, format: dd/MM/yyyy

01/01/2018  = 01/01/2018
but

32/13/2018 = 01/02/2019

 

 

I have a small process as follows:

Small Boomi test process

The message shape has the following data:

01/01/2018
31/12/2018
00/00/2018
32/13/2018
01/13/2018
32/12/2018
365/120/2018

 

The data process shape splits the document by line.

The map shape just has a test profile with a single date element whose data type is Date/Time.

Running the process will result in the following:

01/01/2018         01/01/2018
31/12/2018         31/12/2018
00/00/2018         30/11/2017
32/13/2018         01/02/2019
01/13/2018         01/01/2019
32/12/2018         01/01/2019
365/120/2018      29/11/2028

 

I couldn't find the answer anyway but is this the way Boomi handles invalid dates? By automatically correcting them to a date that's valid?

 

Thank you,

Don

Outcomes