Gravity Forms Advanced Calculations

How do I enable this functionality?

After installing and activating Gravity Forms Advanced Calculations,

	Add a Number field to your form.
	Check Enable Calculation.
	Insert advanced calculations into form. Use the Formula Cheatsheet for a primer on calculations.

Feature Details

Merge Tag Shorthand

The true power of calculations with Gravity Forms comes from being able to reference other fields to create calculations from what users have entered. Gravity Forms uses merge tags to reference fields. Merge tags are referenced using the field ID, with or without the descriptor, such as {Field A:1} or {:1}.

Gravity Forms Advanced Calculations adds shorthand for fields to clean up your calculations and make it easier to keep track of everything. The shorthand for the same field shown above is written as F1.

Shorthand offers more readable calculations, especially for complicated functions.

Conditional Statements

Advanced Calculations supports conditional statements such as if/else and if/elseif/else. Use these statements to evaluate calculations based on field values.

Usage Examples

• How to Set Up Dynamic Pricing in Gravity Forms

if/else

if( F1 > 1.25 && F1 < 5.5 ):
	F1 * 50
else:
	0
endif;

if/elseif/else

if( F1 < 5.5 ):
	F1 * 50
elseif( F1 >= 10 ):
	F1 * 25
else:
	0
endif;

Supported Operators

The following comparison operators are supported:

• == Equal to
• != Not equal to
• > Greater than
• < Less than
• >= Greater than or equal to
• <= Less than or equal to

Comparing String Values

Comparison values can be either a number or a string (e.g. 123 or hello world).

A few things to note when comparing strings:

• Comparisons are case-sensitive. hello world won’t match Hello World.
• Comparisons are not sensitive to whitespace at the beginning and end of strings. Strings are trimmed by Gravity Forms before comparison so a condition like this would match still match a value of hello (no whitespace).

  if ( F1 == ' hello ' ):

• Comparisons can be made with any any single-value text-based field type, including choice-based fields like Drop Down and Radio Button fields.

Multiple Expressions

Conditional statements support multiple expressions within a single condition via the the && (and) or the || (or) operators.

To require both expressions to be true for the condition to match, you would use the && operator. In this example, the condition will only be true if Field #1 is greater than 5 and less than 10.

if ( F1 > 5 && F1 < 10 ):

If you would like your condition to match if any of the conditions are true, you would use the || operator. In this example, the condition will return true if Field #1 is greater than 5 or if Field #2 is greater than 5.

if ( F1 > 5 || F2 > 5 ):

While these examples are simple, this functionality is quite robust and can handle conditions that contain expressions with both && and || operators.

Worth noting that string-based conditions can be combined with number-based conditions.

if ( F1 == 'Package A' && F2 > 100 ):

Condition: Field Has Value

You can easily check if a field has a value like so:

if ( F1 ):

Condition: Field Is Empty

You can check if a field is empty (has no value) like so:

if ( F1 == '' ):

Condition: Field Values Match

You can check if the value of two different fields match like so:

if ( F1 == F2 ):

This works with both numeric and string values.

Syntax Highlighting

Advanced Calculations adds syntax highlighting and autocompletion to the calculation text area. Syntax highlighting drastically improves the readability of calculations, especially complicated ones that use conditional statements and functions.

Autocompletion aids you when inputting a function or conditional statement. When you start typing any supported function, the editor will suggest a completion. Click the suggested function (or hit return) to insert the full function with placeholder values.

The editor also automatically closes parentheses and merge tag braces. Say goodbye to invalid formulas because of an errant parenthesis!

Tooltips

When hovering over shorthand field variables and merge tag field variables with no descriptor in the formula editor, you will see a tooltip displaying the field’s label.

Functions

Advanced Calculations adds support for common functions to both save you time and effort and provide more accurate results.

abs( -78 )

abs( F1 )

abs( value )

abs( -14 )

acos( 1 )

acos( F2 )

acos( value )

acos( 1 )

asin( 1 )

asin( F2 )

asin( value )

asin( 1 )

atan( 1 )

atan( F2 )

atan( value )

atan( 1 )

average( F1, F2, 26 )

average( 1, 2, 3, 4, F1 )

average( value1, [value2, ...] )

average( 12, 58, 35 )

ceil( 25.4 )

ceil( F1 )

ceil( value )

ceil( 35.8 )

cos( 1 )

cos( F2 )

cos( value )

cos( 1 )

exp( 25.4 )

exp( F1 )

exp( value )

exp( 5 )

floor( 75.763 )

floor( F3 )

floor( value )

floor( 323.78 )

fv( F1, F2/12, F3, 10000, 1 )

fv( 0.05, 10, F1, F2 )

fv( rate, numberOfPeriods, paymentAmount, presentValue, [endOrBeginning] )

fv( 0.0311, 60, 450, -25000, 0 )

ln( 23 )

ln( F4 )

ln( value )

ln( 491 )

log( 7 )

log( F2 )

log( value )

log( 49 )

max( F1, F4, 67 )

max( 108, F7 )

max( value1, [value2, ...] )

max( 36, 49 )

min( F3, 56, F8 )

min( 3, F1 )

min( value1, [value2, ...] )

min( 18, 6 )

pi()

pi()

pi()

round( 12.7 )

round( F2 )

round( value )

round( 8.68 )

sin( 1 )

round( F2 )

sin( value )

sin( 1 )

sqrt( F12 )

sqrt( 72 )

sqrt( value )

sqrt( 144 )

tan( 1 )

tan( F2 )

tan( value )

tan( 1 )

Troubleshooting Issues

If the calculations aren’t working as expected, here are some troubleshooting tips you can try.

• As a first step, ensure that your formula follows all of Gravity Forms’ core calculation rules.

• Double check this core Gravity Forms rule as it is commonly overlooked:

  ​​​​​​Fields referenced in a calculation formula (1) must be positioned before the calculation field, and (2) must not be hidden by logic. This is because calculations are rerun during submission using saved values, and if the field hasn’t been saved yet or has been ignored due to logic at form submission, it won’t have a value available for the calculation, leaving the result either incorrect or empty.

• Use the “Validate Formula” feature that appears directly below the formula setting to ensure that your formula is valid.

  

• Make sure there are no JavaScript errors appearing in the browser console, as they can disrupt calculations on the frontend.

• When referencing the price of a Product field, the merge tag syntax is {Product:1.2}.

Known Limitations

• Single and double quotes cannot be escaped in string-based conditions.

  • Solution: Wrap the string in double quotes if it contains a single quote or single quotes if it contains double quotes.

    Example: 'Don't try to escape.' becomes "Don't try to escape."

• When targeting top-level Checkbox fields and Paragraph Text fields in conditional statements, you must use shorthand syntax as Gravity Forms does not listen for these fields in calculations by default.

• List fields are not supported in calculations.

• Nested conditional statements are not supported.

  • Solution: Combine the nested conditions into multiple if/elseif/else statements. Here’s an example where we take an unsupported nested conditional statement and convert it into supported if/elseif/else statements.

    Unsupported:

    if( F1 > 10 ):
    	if( F2 > 20 ):
    		2
    	else:
    		1
    	endif;
    else:
    	0
    endif;

    Supported:

    if( F1 > 10 && F2 > 20 ):
    	2
    elseif( F1 > 10 && F2 <= 20 ):
    	1
    else:
    	0
    endif;

• By default, a product choice’s value includes both the label and price, formatted as: Product One|10. This can cause issues when using the product in conditional statements.

  To resolve this, enable and set a custom value for the choice field. Once set, use the value merge tag modifier to explicitly retrieve the value, as shown below:

  if( {Product:1:value} == 'Product One' ):

• When using complex formulas inside if statements, extra spaces between characters can cause the formula to fail, even if it works fine on its own.

  For example, this standalone formula works as expected:

  F1 * (1 + F2)

  However, when included inside a conditional block with an extra space before the parenthesis, it can fail:

  if(F3 == 'Yes'):
  	F1 * (1 + F2)
  else:
  	0
  endif;

  In the example above, the space between * and the (1 block can break the formula.

  Solution (spaces removed):

  if(F3 == 'Yes'):
  	F1 *(1 + F2)
  else:
  	0
  endif;

  Tip: When embedding formulas in conditional logic, double-check for unintended spaces around *(, +(, or any operator followed by a parenthesis.

• GP Advanced Calculations only supports numeric results, returning a string value is currently not supported.

• A calculation cannot contain multiple conditional statements.

  Unsupported:

  if( F1 > 10 ):
  	1
  else:
  	0
  endif;
  if( F1 == 5 ):
  	6
  else:
  	0
  endif;

  Supported:

  if( F1 > 10 ):
  	1
  elseif( F1 == 5 ):
  	6
  else:
  	0
  endif;

• Numbers in conditionals can’t be surrounded by quotes.

  Unsupported:

  if( F1 == '279' ):
  	4
  endif;

  Supported:

  if( F1 == 279 ):
  	4
  endif;

Integrations

Invoicing Templates by Gravity PDF

GP Advanced Calculations integrates with Gravity PDF’s Invoicing 2.0+ templates. These templates allow for business-ready invoice generation from Gravity Forms submissions. They’re highly customizable, translatable, support conditional logic, and are GST/VAT compatible. This integration allows for GP Advanced Calculations’ mathematical functions and formulas to be leveraged while working with Gravity PDF’s Invoicing templates.

There’s a variety of sleek templates to choose from and all templates integrate with GP eCommerce Fields, GP Inventory, GP Conditional Pricing, GP Unique ID, and GP Price Range. Learn more about Gravity PDF’s invoicing templates here.

Translations

You can use the free Loco Translate plugin to create translations for any of our Perks. If you’ve never used Loco translate before, here’s a tutorial written for beginners.

FAQs

How can I create a condition based on the label of a selected choice?

Use the :choice_label merge tag modifier to explicitly get the label from a choice in a formula. (There is also the :label modifier, but it returns the label of the field rather than the selected choice.)

Example:

if ( {Package:1:choice_label} == 'Premium' ) :
	{Options:2} * 0.5
else:
	{Options:2} * 0.1
endif;

Hooks

• gpac_functions
  
• gpac_functions (JS)
  
• gpac_should_clean_merge_tag_value
  
• gpac_should_clean_merge_tag_value (JS)
  
• gpac_should_process_calculation (JS)
  

Related Resources

• How to Do Calculations with Gravity Forms
  If you’re using Gravity Forms on your WordPress website, you might need an easy way to do Gravity Forms calculations on form fields and user submissions.
• How to Set Up Dynamic Pricing in Gravity Forms
  Make your prices mathe-magically adapt to customer input!
• Spotlight: Building a Loan Calculator with GP Advanced Calculations
  See how James Roberts built a loan calculator for an auto-financing company using GP Advanced Calculations.
• Spotlight: Creating Dynamic, Customizable Quoting Forms with Jennifer Erdman
  We explore how Jennifer Erdman built a quote calculator — based on highly customizable product offerings — step by step.
• Spotlight: Diviguy's Cloud Hosting Cost Calculator
  See how Diviguy.com uses Advanced Calculation's conditional formulas to tackle complex monthly cloud hosting pricing logic with ease.
• Spotlight: Gasol Foundation Incentivizes Donations with a Tax Break Calculator
  See how Jordi Anglada built a tax break calculator to encourage donations for The Gasol Foundation, without knowing how to code.
• Spotlight: Powering Up Cost Estimate Forms with Advanced Calculations
  Jessica Carter took a free estimate calculator from zero to hero with GP Advanced Calculations.
• Spotlight: Works Digital's Magic Land Value Calculation Formula
  Works Digital built a land income calculator as a marketing tool for one of their customers. See how it makes sorcerous use of GP Advanced Calculations.