Azure API Management - Datatime conversion issues

Question

Azure API Management - Datatime conversion issues

Vivek Komarla Bhaskar 956

The API is performing an automatic format conversion, changing the expected format in input message (2022-07-12T06:00:00+00:00) to (12/7/2022 6:00:00 AM).

Accepted answer

0 additional answers

Your answer

Answer 1

Sonny Gillissen 3,751 Volunteer Moderator

Hi @Vivek Komarla Bhaskar ,

Thanks for reaching out!

From our previous contact I know you've been using liquid templates, so I assume you're still doing so.
I've tested it in my lab environment and I saw the same behaviour on my end.

What you could try is appending the code below to your liquid date tags:

| Date: "o"

You're code will look somewhat like this:

Then your dates are presented in the desired format, be it with miliseconds.
Within the possible formats this was the closest I could find.

Vivek Komarla Bhaskar 956 Reputation points

2022-12-14T07:56:05.223+00:00
@Sonny Gillissen ,

You have been extremely helpful. I apologize for asking so many questions (API Management service is completely new to me in the Azure stack, so your assistance has been extremely helpful).

As you said, I'm also getting milliseconds; is there any way we can slice / substring to the desired output?

In the case when the response output is just yyyy-MM-dd, I attempted to use | Date: "%y-%M-%d", but this doesn't work.

Earlier, our Json resulting from the API did not have a ',' after each row, resulting in an invalid parse error for the downstream system. To fix this I added a ',' to the body, but the last record also has a ',' which again results in an invalid parse error.
Sonny Gillissen 1 Reputation point

2022-12-14T19:04:24.273+00:00
Hi @Vivek Komarla Bhaskar ,

You're absolutely welcome!
I'm happy to help.

I've used "o" to provide the best fitting single string, and maybe neatest way, however you can also use "yyyy-MM-ddTHH:mm:ssK" instead to not show miliseconds

You can use "yyyy-MM-dd" for this :-)

I've been testing in my lab, it's within the statements of the loop: the word "for" should be "JSONArrayFor" and "endfor" should be "endJSONArrayFor", also find the image below. The last comma after the curly bracket shouldn't be added!
Vivek Komarla Bhaskar 956 Reputation points

2022-12-15T14:19:32.353+00:00

@Sonny Gillissen , Thank you so much. This works!

Share via

Azure API Management - Datatime conversion issues

0 additional answers

Your answer