Passed from 26361 to 03-Mar-1972 is the result of an interpretation in timestamp then the formatting of this timestamp in date.
From the start, this value is handled well as an integer in EasyMorph.
I deduce that if we do not force data’s format, interpretation/formatting can change on its own depending on the data present.
In the present case, parsing JSON from Magento result to 387 columns with differents formats.
Other columns can be added dynamically according to options used by customers.
I must create tests cases for all cases to fix format to each columns.
And this is just the interface to pick up an order. We have plenty of other JSON to read like customer, items, stock or price.
In return, I create JSON send to Nav and receive another JSON.
Same ID is used several time in all these JSON. And only one is parsed in date.
It’s going to take a long time, but we can do it. I don’t understand why, only in one place, formatting change.
It would have made more sense if format used was automatically saved to avoid random operations.
Maybe this would be a problem when building the morph.
In this case, a button allowing to freeze file formats would be the easiest.
For your information, this morph have 369 actions in 10 modules, call 12 web services and call 2 other morph.