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

Question

Question

Multi-value field in workflow

asked on November 6, 2016

In my workflow I build a multi-value token that has exactly what I need.  When I try to put the value of the token into a template field I get an error:

The data assigned to field 'Sheet Metadata All' is not valid. 9020 [The parameter is out of range or too long. [9020]] [0265-WF10]

 

Is it not possible to do that?  I have a list of values that I want to put into the template field.  It formats perfectly in the multi-value token.  How do I get it into the template field?

 

Thanks!

0 0

Replies

replied on November 6, 2016

Hi Janice,

You should check your the settings on your field.   You are probably trying to insert more characters into your field that it allows ( or inserting a different type that it is configured for,  i.e. text into a numeric field ).

I had this same error when my field setting was set to a width of 40 and the text that I tried to place into the field was 60+ characters.   Adjust the type and/or field width and I bet your error is gone.

1 0
replied on November 6, 2016

I forgot to mention in the original post that I was able to copy and paste the value of the multi-value token into the field just to ensure that the width and character length would be enough to hold the value.  It is a text type field.   I can't use a list field because this is not for a drop down box. 

So this is for a text field set to 4000 characters.    I suspect that the line feeds in the token are the problem but I need the text to have the line feeds.

0 0
replied on November 7, 2016

Hi Janice , can you show us how yo do it?

Maybe we can see something more on the worflow  exercise

0 0
replied on November 7, 2016

Janice,

There's a good chance you are correct about the newlines being an issue. Each field in LF is created as a column in an SQL table on your SQL server. I don't know about Oracle, but in MSSQL you need to do some extra work to insert a newline into a field defined to contain strings. If the programmers at Laserfiche never anticipated that any of us would try to put newlines into those fields, it will be impossible to do what you want.

You could do something like that with text box or sticky note annotations or linked documents assuming that's something that would work for what you want to do.

0 0
replied on November 7, 2016

I can't reproduce this error with a token containing newline characters or with a multi-value token separated with newlines. So that's unlikely to be the cause.

Are you sure the data doesn't exceed 4000 characters? It's probably easiest to troubleshoot if you send a copy of your workflow to Tech Support.

1 0
replied on November 7, 2016

I don't insert a newline character.  It's just that the token goes to a new line when I add another value.  That's what I want.   I want the field to look like a Table of Contents.  I am able to copy the value of the token into the field so I know it's not too long. 

The only problem is that the Assign Field value workflow activity won't put the value in the field. 

0 0
replied on November 7, 2016

Janice do you check if the field has "Multi-value" enabled?

0 0
replied on November 7, 2016

So here's what the workflow looks like:

 

Here is the error:

Here's the token value.  I can copy the text from the token into the template field manually so I know that the field is long enough to hold the data. 

0 0
replied on November 7, 2016

I think you can save 2 steps.

Just make sure the field has "Multi value" enabled and you can delete this nodes


and insert directly like this 

 





A multiple value field has the propierty to index your appends by his own way do not have to worry about put in in a token and then insert it.

0 0
replied on November 7, 2016

I think you're actually over the limit. Each row in your screenshot is around 100 characters and you have at least 38 of them. Workflow truncates token values to 3700 characters when it logs them to the workflow instance details, so copying and pasting from there is not necessarily proving that the actual value wasn't longer.

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

Sign in to reply to this post.