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

Discussion

Discussion

=SUM() Not Working as Expected in LF Cloud - Possible Bug

Laserfiche Cloud Forms
Updated March 28
posted on March 26 • Show version history

We have a table with an amount column and an additional shipping cost field, separate from the table, that get added together in a "Total" field using the =SUM() calculation rule. When you enter a shipping cost, then delete the value, the Total does not update and if the form is submitted, it will produce an error. This appears to happen in both the Classic and Modern forms designer.  This seems to be a bug since it has worked in on-prem by disregarding the field if it was empty.

0 0
replied on March 27

This has surely been an issue for us as well, I have been using JS to do calcs for tables otherwise users could not delete rows and have accurate data.

The bug number for this issue was bug 496600 and it was supposed to be fixed in the release on Jan 12th

https://doc.laserfiche.com/laserfiche.documentation/en-us/Default.htm#changelog.htm

If it is still happening with some functions, then I would send an example form to support.

0 0
replied on March 26

Hmm I am unable to reproduce this, you are summing outside of the table right? Are both fields used in the calculation number or currency fields? Also I know you mentioned it not working in either, which is the intended designer?

0 0
replied on March 28 • Show version history

All fields for the calculation are currency fields, and we are summing outside of the table. We are intending to use the modern designer.

For the screenshot below, I entered $123 in the table and $3 in the Extra field. That totaled to $126. Then deleting the Extra value of $3 does not update the total.

=SUM(Table.Currency,Extra) calculation on the Total field.

 

With some additional testing, if the Total field is not read-only it works as expected. However, we need the Total field to be read-only in our process.

0 0
replied on March 28 • Show version history

What if you use a field rule to disable the "Total" field instead of making it read-only?

0 0
replied on March 28

That seems to work. Going forward, is it best practice to use field rules over properties for fields, particularly when using the modern designer?

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

Sign in to reply to this post.

Details
Related Posts
Loading ...