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

Question

Question

Inserting Forms Table Values to Multi-value FIelds

asked on March 14, 2017 Show version history

Hi,

We have a Form that contains a table and we would like to push the values into multi-value fields in a field group in the metadata. Some of the row values may be empty though and this is causing the data to be misaligned when saving the metadata.

 

Here is a picture of the test form:

Here is the output:

I have tried to setup the Workflow in two methods (both with the same results):

  1. By referencing the Table, and using a For Each Row
  2. By selecting the values from the form individually.

 

Any ideas?

 

Thanks,

Dom

0 0

Answer

SELECTED ANSWER
replied on March 15, 2017

@████████,

I see what you mean. Let me see what we can do to fix it and include it in the upcoming patch.

0 0

Replies

replied on March 14, 2017

Hi Dom

Have you considered putting a Condition after the For Each Row, where  you test to see if the field in question is empty, if so you would assign a value such as a "-" or "none", and if the value was present assign the actual value.

1 0
replied on March 14, 2017

Hi Steve,

Thanks for this - from Miruna's response below it appears this will have to be the way!

Thanks :)

0 0
replied on March 14, 2017

That's not quite what I said smiley How are you setting these fields? Are you using the column token from Retrieve Forms?

 

0 0
replied on March 14, 2017

Hi Miruna, in you example above you are not using For Each Row and Building up a Multi-field value but instead assigning the data directly from the Retrieve Business Process, and it is creating the grouping automatically? 

0 0
replied on March 15, 2017

Ohhh

I did try using the column variables Miruna :( I did the same test as yourself and it worked okay. Try missing out the first value "Column 2" of the form though, that appears to upset the alignment in my case - do you get the same result?

Thank you both :)

0 0
replied on March 15, 2017

@████████ ,

The token for a table column is a multi-value token already, I don't need to rebuild it.

0 0
SELECTED ANSWER
replied on March 15, 2017

@████████,

I see what you mean. Let me see what we can do to fix it and include it in the upcoming patch.

0 0
replied on March 14, 2017

This is expected behavior for multi-value fields outside of a multi-value field group. Multi-value fields on their own do not allow blank values.

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

Sign in to reply to this post.