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

Question

Question

Cannot set column "Field" to be null

Workflow Version 10
Updated January 26, 2017
asked on February 29, 2016

I've recently changed one of my workflows to use the new Update Word Document feature and I've ran into an issue. When populating fields in a table on the document it throws an error when the date field doesn't have a value.

"Cannot set Column 'Date' to be null. Please use DBNull instead."

 

Below is a screen shot of the process in Workflow and it's coming from a table in forms.

 

Has anyone else ran into this issue before?

0 0

Replies

replied on February 29, 2016

This is a known issue. Currently, Update Word Document can't handle columns with no data in table merges. We're looking into it.

1 0
replied on March 18, 2016

Is this something I should open a support case for? Or just wait?

0 0
replied on December 7, 2016

This is a bug (#140206). A fix will be available in the next version of Workflow. There is currently no workaround in Workflow 10.

1 0
replied on February 29, 2016

Maybe you can add a blank space into it?

0 0
replied on February 29, 2016

Is there any work around temporarily? For example if I were to put a field before the Date field in the table that would always have a value do you think that would fix it? It seems that if the Date is filled out, which is the first field, other fields can be blank.

0 0
replied on December 7, 2016

Is there any update to the status on this?  Currently looking at a process and is not working because of this issue.

 

Thanks

0 0
replied on January 25, 2017

Is this fixed in Workflow 10.2?

0 0
replied on January 25, 2017

Yes, it was fixed for 10.2.

2 0
replied on January 26, 2017

Great news, thank you Miruna.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...