Fields not saving in a collection when form is submitted

replied on January 30, 2020 • Show version history

Hi Kristen.

When you say 'not saving' do you mean that the instance variable for Specific Amount is blank? Or is there still a value in the instance variable?

You can see this by going to 'Monitor', selecting an instance of the Form submission which you know hasn't 'saved', and then viewing the instance variables (probably {dataset/Specific_Amount}?). If the Specific Amount variable is blank, then that means it's likely something happening in the Form.

Or if by 'not saving' you mean it's in the Form variable, but not getting through to a database or to a metadata field, then we need to look somewhere else (like the 'Save to Repository' task in the Business Process, or maybe a workflow that's being kicked off; or the field/cell constraints being mismatched between the form field and the target location for the data).

Also - is the behaviour of the field that, when you selct the Specific Amount radio button, the field appears and the user manualy enters the value?

0 0

replied on January 31, 2020

Hello Duncan,

the variable is blank when I look at an instance.

0 0

replied on January 31, 2020

The other thing I have noticed is if I have JUST the Specific Amount checked with an amount it works, but since it is in a collection if I click add to add another account that is when it seems to be blank?

0 0

replied on February 1, 2020 • Show version history

Hi Kristen,

I tend not to use collections; preferring to use tables with rows acting as a 'collection'. However, I did find this information at the bottom of this page:

Collections and variables

When you add an existing field to a collection, the field will lose its variable. Since a collection is a set of repeatable fields, the collection itself will have a variable with sub-values for the fields it contains.

So I would imagine it's a variable that already existed when it was added as a single field on its own (i.e. not part of a collection). Then later when you added a 'collection' you then added the 'old' variable (field) to the collection. This might mean it won't work.

Sounds like you'll need to add a new variable with a unique name that hasn't been used before (e.g. 'coll_specific_amount'). You just won't be able to use a variable that's existed before as single, standalone field.

You could try deleting the 'specific_amount' variable (both the field from the collection group; and the variable from the variable list), then adding it back to the collection group (so it thinks it's a 'new' variable)?

0 0

Question

Question

Fields not saving in a collection when form is submitted

Replies

Sign in to reply to this post.