We are encountering a very weird behaviour with the custom object creation. It appears that when we push a new custom object with an empty datetime field (CheckoutDate), it actually gets populated with a fixed date (26/08/2019) and we have no idea why.
We now to the point where we have to ask for your help cause we've exhausted all our ideas on the why for this one.
How is it possible that this custom object get created with a default date when set to null?
Thank you very much in advance for your help.
Are you using a mock endpoint, or a network trace, to see the actual JSON put on the wire?
This is happening in a lambda function from AWS, so what you see is the object in the serialization of the object that gets sent through the in the marketo API client as we log it and retrieve through cloudwatch. Unless there is tools on Marketo sides that would allows us to look at what's coming in, we have no mean of having a network trace for that.
This c# client is automatically generated from the Marketo REST endpoint using a tool called Refit.
Is this the API Gateway log, or the Lambda log after transformations?
That is the custom log that we have on our code to display each object that gets sent to CustomObject. This log stores it in the cloudwatch log for that particular lambda.
Well, I can't repro what you're describing. I were you I'd make triple-sure by sending to a mock endpoint (in place of the Marketo API) and inspecting the payload.