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

Question

Question

DateTime Input Parameters in Cloud Workflow and Rules

asked on June 20, 2022

Hi all,

When we use a Rule that inserts data in a Look-Up table, and has fields that are DateTime; it seems as though the rule will fail when the Input Parameter for a DateTime field has a "(none)" (empty) value.

When we do the same thing for a 'String' Input Parameter there is no issue, and the Rule will accept an empty value.

With DateTime, an empty value will always get "String was not recognized as a valid DateTime".

If we 'force' some kind of default DateTime, then it will go in... but we want to essentially have a 'null value' be possible.

The only alternative is to make a second rule that conditionally doesn't attempt to use that Input Parameter when it has a null value, but it seems crazy to have to make a copy of the rule only to accommodate that possibility.

Am I missing anything? Is there a way to push a "(none)" value into a DateTime Input Parameter in an Insert Data Rule?

3 0

Replies

replied on January 10, 2023

I raised a support case for this. The support team have said that this is intended behaviour currently, but that dev are aware that this feature needs improving and they will update this post when they have more details.

2 0
replied on January 10, 2023

Thanks for the update mate yes

1 0
replied on March 1

Hi, is there any update on this?

0 0
replied on July 14, 2022

I would also like clarification to this.

0 0
replied on December 22, 2022

Hi,

We are also having the same problem. Is this a bug or is this intended behaviour?

Cheers,

Dan

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.