WR REST API syntax for DATETIME

Kinch · 2024-02-05T17:14:09+00:00

There was an error rendering this rich post.

Hi folks

We are initiating a Workflow from a Web Report and starting the web report from a REST API call. One of the attributes is a DATETIME and I am able to send the appropriate string to get the DATE part set, but all my efforts at setting the time are failing.

I've tried "02/05/2024 09:42 AM", "02/05/2024 9:42 AM", "02/05/2024 09:42:00", and even using slashes instead of colons "02/05/2024/09/42/00" (not that I expected that to work) — in all cases the time part is ignored but the workflow does get initiated.

Both the WR attribute and the WF attribute have been set to "Enable Time" / "Include Time Field" — can anybody provide the correctly formatted string to put in the "/v1/nodes/$($WRID)/output" REST body?

$reqdate = [uri]::EscapeDataString('02/12/2024 9:49 AM')

Dave

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

Hans Stoop

Have a look at the TODATE subtag to convert your inout dat eto a date.

Hans

Kinch

Thanks Hans, as helpful as always! It didn't work right out of the box but definitely something I can work with:

[LL_REPTAG_&ReqDate /] = "2023-10-31 08:38:52"

[LL_REPTAG_&ReqDate TODATE:"%Y-%m-%d %H:%M:%S" DATE:INPUT SETWFATTR:'Requested Date' /],

Still no time in the workflow attribute :-( I'll play around a bit more tomorrow, maybe DATE:INPUT isn't right?

In any case, definitely appreciate the reply.

"Kinch"

Greg Griffiths

Looking at the online help for the Define Attributes page, it doesnt appear that they currently support the level of precision for 08:38:52, but would need to check the OScript to be sure :