Question

Read Only Fields cause Form to not submit + Double Look up Row

Forms

Updated September 14, 2017

asked on July 6, 2017

Good day all,

After the recent update to Forms, we have encountered the following issues -

1. A read-only field that calculates the SUM of a column in a table will not submit. The user receives the error of "Invalid Formula Expression [LFF1000].

2. If I remove the read only option, the form processes but the next task and then subsequent tasks show duplicate data lookups. Eg. 1st Task loads with 3 lines items. User submits. Next task has each of the 3 line items duplicated. As per the screenshot.

This relates to the read-only field options as well as javascript attributes.

Regards

Ian

Duplicate.png (33.09 KB)

| Download

0 0

Replies

replied on July 6, 2017

Hi Ian,

I tried with lookup rules but still could not reproduce the issue.

Can you open a support case and provide your process to us?

0 0

replied on July 6, 2017

Good day Rui,

Support Logged - https://support.laserfiche.com/supportcases/tracker?caseid=188213

0 0

replied on July 6, 2017

Hi Ian,

I was able to reproduce your issues with your process. We are really sorry for inconvenience and we will release new update for these issues.

0 0

replied on July 6, 2017

And another thing, we found the issue seems to be related with lookup with current user, did you use lookup match current user in your form?

0 0

replied on July 6, 2017

Hi Rui,

The look up matches on Account Number, Statement Date and Claim Check fields.

It doesn't match to the current user. The values are pushed from a workflow to the form

Regards

Ian

0 0

replied on September 6, 2017

This bug has been fixed in 10.2.1 Update 2, you can go to https://support.laserfiche.com/kb/1013880/list-of-changes-for-laserfiche-forms-10-2-1-update-2 to check details

0 0

replied on September 14, 2017

Thank you

0 0

You are not allowed to follow up in this post.

Question

Question

Read Only Fields cause Form to not submit + Double Look up Row

Replies

Sign in to reply to this post.