Discussion

Workflow unable to assign field value because it thinks the data is invalid

Workflow

Updated June 11, 2019

posted on May 9, 2019

I can't seem to find a solution here. I have a workflow that needs to assign a large amount of data into fields and it thinks the data is invalid so it does not assign it.

The problem starts with this assign field values task

Which throws this message

5/9/2019 2:56:49 PM Assign Field Values The data assigned to field 'INS Eligible' is not valid. 9017 [Bad field value. [9017]] [0265-WF10]

When I take the data it is trying to assign and copy it to the clipboard, on the clipboard it looks like this:

2009-12-01

Then I open up the Laserfiche client and paste right from the clipboard into that field, it goes right in.

The only way I can get it to work is to change the field to a text field, but this removes all abilities to sort, search, and select dates.

0 0

Comments 6
Follow-Ups 0

replied on June 11, 2019

Hi Chad,

I had similar issue while assigning date field value from a sql query. Tried the following and got it working.

1. Used assign token values to format date

2. Changed the system date setting (made sure its in the required format)

3. Changed the account running workflow service from local to service user

Hope this helps.

Thank you.

Bipin

0 0

replied on May 9, 2019

I'm guessing this data comes from a query? Testing the query gives Workflow a chance to figure out data types based on the data. Otherwise it's all strings and as a string yyyy-MM-dd is not a valid date on a machine where the date format is yyyy/MM/dd.

3 0

replied on May 9, 2019 • Show version history

Got it, so using test both generates the token names and sets the types. That would explain it, I guess it set the type as a string because it saw it was different than the original.

I even tried pushing the data into a date token calculator before I found the fix but it wouldn't take.

0 0

replied on May 9, 2019

Have you tried formatting the token before assigning it to the date field?

1 0

replied on May 9, 2019

I can give it a try but I know my formatting is supported, for example these values all work just fine going into a date field using assign field values. Also I copied it in that exact yyyy-mm-dd format to verify it would go in the field.

1999-03-01
2016-06-27
2006-05-15
2016-05-23
2016-04-25
2012-08-30
2011-09-13
2008-11-01
2015-01-05
2014-10-27
2013-12-01
2017-01-06
2014-08-27
2011-02-07

0 0

replied on May 9, 2019

I just found a fix, the query activity that pulls the data has a test option, I didn't think it was required for anything other than showing the names of the tokens you can use, but after using the test feature, suddenly the data was able to be assigned to the template, even though it didn't change in any way.

The database was storing this information as a datetime format when the workflow was originally built, and it was updated to use a date format since. It seems something about running test, changed the way workflow assigns the values it receives.

1 0

You are not allowed to follow up in this post.

Discussion

Discussion

Workflow unable to assign field value because it thinks the data is invalid

Comments 6

Follow-Ups 0

Sign in to reply to this post.