CodePeople2

Hello @rotertal

No, the problem is that when you use iframes, only the plugin’s styles are applied to the form. Otherwise, the theme and active plugin styles on your website also affect the form. Please provide a link to the page so that we can examine the website’s behavior.

Best regards.

Hello @pengage

Thank you for reaching out via our plugin website. We apologize for the inconvenience you experienced. We’ve identified the cause of the issue and released an update to address it. Please install the latest version of the plugin, then clear both your site and browser caches before testing your form again. If you run into any further problems, let us know right away.

Best regards.

Hello @pengage

Please provide the link to the page with the form so I can see it in action. The use of DS fields is similar to other fields in the form, whether they are Number fields or Number DS fields. Also, include the equation and the name of the calculated field in your answer.

Best regards.

Hello @victoriei101

If you have been satisfied with both the plugin and our support, we would be immensely grateful if you could leave us a review on the plugin ( https://ww.wp.xz.cn/support/plugin/calculated-fields-form/reviews/ ). Your feedback will help us reach more users. 

Best regards. 

Hello @borlee123

If you have been satisfied with both the plugin and our support, we would be immensely grateful if you could leave us a review on the plugin ( https://ww.wp.xz.cn/support/plugin/calculated-fields-form/reviews/ ). Your feedback will help us reach more users. 

Best regards. 

Hello @saralanda,

Thank you for using our plugin! When writing your equation, please don’t wrap field names in single or double quotes. Instead, apply one of the three built-in modifiers |n, |r, or |v directly to the field name. These modifiers tell the plugin how to interpret and process each field within the calculation context.

The plugin scans your equation for any placeholder in the format fieldname# and substitutes each with its corresponding field value before performing the calculation. By appending the |n modifier (for example, fieldname2|n), you instruct the plugin to treat that placeholder as the literal field name rather than its numeric value. In your case, the equation should be written as:

getField(fieldname2|n).setVal(123);

The plugin automatically sanitizes and converts formatted field values into plain numbers before running any calculations. For instance, if you have a currency field called fieldname1 whose value is $1,234.56, the plugin will strip out the currency symbol and commas and turn it into the valid number 1234.56 so it can be used in a math expression. If, however, you want to work with the raw, unprocessed input, $1,234.56 in this example, you can append the |r modifier to the field name (e.g. fieldname1|r), and the plugin will pass the original string through instead of its numeric equivalent.

The plugin always substitutes each field placeholder with that field’s value when evaluating an equation. However, For radio buttons, checkboxes, and dropdowns fields, every option has both a value and a display text. If you’ve configured such a field to submit its display text rather than its underlying value, you can append the |v modifier to the field name in your equation to retrieve that text. For example, suppose your dropdown field is named fieldname1, and the selected option has a stored value of 123 but a display text of ABC. Normally, using fieldname1 in your equation would yield 123. If you instead write fieldname1|v, the plugin will return the display text ABC.

Best regards.

Hello @borlee123

Your solution is correct. However, I prefer to use the function structure for the equation instead of nesting multiple “IF” operations, because it is more readable and easier to maintain in the future.

(function(){
	let f8 = fieldname8;
	if(f8 <= 10) return 5985;
	if(f8 <= 21) return 11555;
	if(f8 <= 31) return 16880;
	if(f8 <= 41) return 22205;
	if(f8 <= 51) return 27530;
	if(f8 <= 61) return 34175;
	if(f8 <= 71) return 39500;
	if(f8 <= 81) return 44825;
	if(f8 <= 91) return 50150;
	if(f8 <= 101) return 55475;
	if(f8 <= 111) return 62780;
	if(f8 <= 121) return 68105;
	if(f8 <= 131) return 73430;
	if(f8 <= 141) return 78755;
	if(f8 <= 151) return 84080;
})()

Keep in mind that your equation needs multiple “if” conditional statements because there is no straightforward algorithm for your request.

For example, if your slider step is 10, and every step represents an increment of 5325 in the calculated field’s equation, and the base value is 660 (note these values are hypothetical, I’m using them based on your code values). The equation could be implemented as follows:

660+MAX(1,CEIL(fieldname8/10))*5325

The previous code is an hypothetical example for an equation that represents a specific process for value calculation.

Best regards.

Hello @adeelali38

Thank you for your contribution. Unfortunately, that is not valid for our plugin. You should not use quotes in the equations to refer to field values or use a “field” function.

In fact, our plugin does not include a “field” function.

The plugin identifies the fields in the equation and replaces them with their values. So, the process is even simpler. Unfortunately, your recommended code is not valid.

Please check our response to @lchang79; you will see that the equation is straightforward.

(function() {
    if ( fieldname5|r == '' ) return '';
    let selectedDate = DATEOBJ(fieldname5);
    
    if ( selectedDate <= DATEOBJ('2009-05-30', 'yyyy-mm-dd') ) return 'U16';
    if ( selectedDate <= DATEOBJ('2010-05-30', 'yyyy-mm-dd') ) return 'U15';
    if ( selectedDate <= DATEOBJ('2011-05-30', 'yyyy-mm-dd') ) return 'U14';
    if ( selectedDate <= DATEOBJ('2012-05-30', 'yyyy-mm-dd') ) return 'U13';
    if ( selectedDate <= DATEOBJ('2013-05-30', 'yyyy-mm-dd') ) return 'U12';

    return 'Not eligible';
})()

Best regards.