You are viewing limited content. For full access, please sign in.

Question

Workflow Insert/Update Data not writing SQL DateTime properly that is retrieved via Query Data

Workflow

Updated July 16, 2015

asked on July 15, 2015

I have a workflow that Queries Data from SQL. It processes the records and writes to a table. The issue I am having is with SQL DateTime fields. The original table has dates that go to the second. When I write that field to the second table the seconds are set to 00. See attached image.

Has anyone seen this? If so, do you have a fix/work around?

Thanks,

Jim

DateTimeDifference.JPG (41.06 KB)

| Download

0 0

Answer

SELECTED ANSWER

replied on July 16, 2015

You could also try formatting the token to include the seconds when specifying it in the insert/update: %(Token#"hh:mm:ss tt"#) or %(Token#"HH:mm:ss"#)

1 0

Replies

replied on July 15, 2015

Hi Jim,

We'll look into adding the handling of seconds in a future release of Workflow. As a workaround, instead of querying the datetime from one table, storing it as a token, and then inserting/updating that token value back into a second table, perhaps you can just write a custom query to directly set the value from the first table into the second table.

Regards

1 0

replied on July 15, 2015

Sorry forgot to mention:

Workflow 9.2.1.227

0 0

replied on July 16, 2015 • Show version history

Thanks for the suggestions!

Unfortunately, due to the workflow SQL NULL handling issue (missing token), I've had to scrap the workflow and start over using stored procedures.

Although I did not get to test it, I marked Ed's suggestion as the answer since that would have fit my scenario better.

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow Insert/Update Data not writing SQL DateTime properly that is retrieved via Query Data

Answer

Replies

Sign in to reply to this post.