collection field not always working properly

asked on May 29, 2017

This collection field on an application form was working perfectly until recently. Now, occasionally, it does not populate the programmed data into the Burn Site collection box as desired. It will leave the Burn Site field empty in those cases, resulting in a Fire Permit with a blank Burn Site field. Why would this happen?

This is what it is supposed to do. After filling in the top four boxes, it fills out the last box which is then used further in the BP:

This is what is showing up on the application in the cases where the burn site is left empty (there is a fifth field for Meridian, but it is supposed to be hidden all the time as that piece of the location is always W4):

And this is a normal submitted application that worked:

Programming:

0 0

replied on June 4, 2017

Can you give the details on how you put value to the "Burn Site" field? Formula or custom script?

And for the screenshot "This is what is showing up on the application in the cases where the burn site is left empty", I didn't see the "Burn Site" field; instead the "Meridian" field showed up with empty value, while you said it should be always hidden with default value "W4". Did you modify the form to bring it up?

0 0

View 2 previous replies

replied on June 6, 2017

Rui, sorry it took so long to get back to you on this.

For the Burn Site, the Advanced tab has this in it: =IF(OR(LEN(INDEX(Legal_Address.Quarter,ROW()))=0,LEN(INDEX(Legal_Address.Section,ROW()))=0,LEN(INDEX(Legal_Address.Township,ROW()))=0,LEN(INDEX(Legal_Address.Range,ROW()))=0,LEN(INDEX(Legal_Address.Meridian,ROW()))=0),"",CONCATENATE(INDEX(Legal_Address.Quarter,ROW()),"-",RIGHT(CONCATENATE("000",INDEX(Legal_Address.Section,ROW())),2),"-",RIGHT(CONCATENATE("000",INDEX(Legal_Address.Township,ROW())),3),"-",RIGHT(CONCATENATE("000",INDEX(Legal_Address.Range,ROW())),2),"-",INDEX(Legal_Address.Meridian,ROW())))

And for the other thing you're asking about, yes that is an oddity as well. In each case where this Burn Site field does not result in a proper collection, the hidden Meridian field shows up and the Burn Site field does not show up on the submitted application.

The Meridian field just has a default value of W4 and has a Rule to keep it hidden.

0 0

replied on June 6, 2017

So the issue actually is not on the "Burn Site" field, but is on the "Meridian" field:

Somehow the default value in the "Meridian" field was not submitted. As a result, the field rule condition "hide field when is not blank" was not met so the field showed up, and the condition LEN(INDEX(Legal_Address.Meridian,ROW()))=0) in formula was met so the "Burn Site" field calculation result is empty.

Can you check if there is any rule/script that changes the "Meridian" field value? Why would you use a hidden field instead of hard-code "W4" in the formula? Also it might be a bug if there is no rule/script editing the field.

1 0

replied on June 7, 2017

What do you recommend to eliminate the problem? We could get rid of the Meridian field entirely and have the Burn Site always add it. How would I add it to the coding?

0 0

SELECTED ANSWER

replied on June 7, 2017

Just replace it with "W4" like this:

=IF(OR(LEN(INDEX(Legal_Address.Quarter,ROW()))=0,LEN(INDEX(Legal_Address.Section,ROW()))=0,LEN(INDEX(Legal_Address.Township,ROW()))=0,LEN(INDEX(Legal_Address.Range,ROW()))=0),"",CONCATENATE(INDEX(Legal_Address.Quarter,ROW()),"-",RIGHT(CONCATENATE("000",INDEX(Legal_Address.Section,ROW())),2),"-",RIGHT(CONCATENATE("000",INDEX(Legal_Address.Township,ROW())),3),"-",RIGHT(CONCATENATE("000",INDEX(Legal_Address.Range,ROW())),2),"-W4"))

1 0

replied on June 8, 2017

Thanks so much Rui! I'm going to do that, delete the field for Meridian and just add the W4 to the Burn Site field! Hopefully, that will eliminate the problem.

0 0

Question

Question

collection field not always working properly

Answer

Replies

Sign in to reply to this post.