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

Question

Question

SumIf Formula is an Invalid Expression

asked on March 25, 2019

First, I may already have my answer/the best solution.  We are using Forms 10.2.1, but have 10.4 installed on our test environment.  This issue exists in 10.2.1, but not in 10.4.  The solution may be as simple just needing to update, but I wanted to put out the question in case there may be something I can do until we are ready to upgrade.

 

We have a process where the initiator lists a number of transactions that they want to dispute:

 

At the next step, we add a column to the table and the processor chooses yes or no for each transaction, indicating if we have charge back rights.  I then have two different currency fields summing the values depending on the result of the Yes/No question.

The Write Off Amount field uses this formula:

=SUMIF(Disputed_Transaction_Details.CB_Rights,"No",Disputed_Transaction_Details.Amount)

The Charge Back Amount field uses this formula:

=SUMIF(Disputed_Transaction_Details.CB_Rights,"Yes",Disputed_Transaction_Details.Amount)

 

In general this works without any problems.  Sometimes there are times where the processor needs to remove a transaction from the dispute for various reasons.  If a row is removed, the fields still total correctly when the form is being fill out, but we get an error upon clicking submit.  (There is a lengthier, more detailed version of the error that I can post if desired.)

'=SUMIF(Disputed_Transactions_Details_Repeated.CB_Rights,"No",Disputed_Transactions_Details_Repeated.Amount)' is an invalid formula expression. [LFF1000-InvalidExpression]

Or:

'=SUMIF(Disputed_Transactions_Details_Repeated.CB_Rights,"Yes",Disputed_Transactions_Details_Repeated.Amount)' is an invalid formula expression. [LFF1000-InvalidExpression]

This error occurs if it is a mixture of yes/no as well as exclusively yes or exclusively no.  It also occurs if we have a default answer chosen to yes or no and the row is removed.

 

If no rows are removed, the form can be submitted without any problems and moves to the next step just fine.

 

If there is anything that I can adjust with our system and/or the formula expression, I would appreciate it.  Otherwise, I'll just remove the auto sum from those fields and they will total it by hand until we are ready for 10.4.

 

Thanks!

0 0

Replies

replied on April 19, 2019

I am encountering this issue as well.  It works fine so long as no rows are removed from a table but otherwise, we get the error below. 

We are on Forms 10.4 so it does not appear this was fixed in the next version.  Currently to get around this as this means we have to have a hidden field for calculation on each line that has criteria in it and then just sum that field at the bottom of the table.  A lot of extra work to get around something that should definitely be working.

0 0
replied on April 19, 2019

I'm a bit surprised and intrigued that the update didn't work for you with 10.4 .  We didn't have any problems with 10.4 and this issue in our test environment.  

 

We'll be doing the update to 10.4 shortly, and I'll post an update as to how the production environment fares.

0 0
replied on April 19, 2019

I found the issue is actually related to read-only fields, found via another Answers post.  I had switched everything over to "SUM" instead of "SUMIF" and ended up still having the issue.  By changing the fields to no longer be read-only via the check-box in their properties, it allowed them to be submitted even with removing rows.  I then used JavaScript to make those fields read-only and it is working now.  I haven't gone back and tested with "SUMIF" since it is working but imagine it would probably work fine now.

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

Sign in to reply to this post.