CodePeople2

Hello @dealerprincipal

Thank you so much for using our plugin.

If fieldname1 is a number, and fieldname2 is a slider field from 1 to 50 that you want to treat as a percentage, the equation in the set equation attribute of the calculated field would be:

fieldname1*fieldname2/100

If you want to allow only two decimal places, you can edit the equation as follows:

PREC(fieldname1*fieldname2/100, 2, true)

PREC(x, y) rounds the number x with y decimals. Passing true as the third parameter tells the plugin not to include .00 when x is an integer number.

Once the first pair is created, you can duplicate it as many times as you want. To simplify the process, include them in a DIV field and duplicate it. Please watch the following video:

https://resources.developers4web.com/cff/tmp/2025/04/20/video.mp4

Best regards.

Hello @miya8713

Thank you so much for using our plugin. I assume you are referring to the commercial plugin “Spreadsheet Calculated Fields Form Connector” (https://cff-bundles.dwbooster.com/product/spreadsheet). Note that it is not the calculated field, but a complementary plugin. Please contact us directly through the plugin website. Contact Us

Best regards.

Hi @massimo1971

The problem you are referring to is that OpenAI is no longer free for inferences. Previously, it allowed you to create the API Key and test it before you needed to pay for its use. Unfortunately, this is no longer the case and requires you to purchase credits for its first use. We are considering modifying the wizard to use other models that allow free inference. However, you can ask your questions directly to ChatGPT for free: https://chatgpt.com/

Best regards.

Hello @sakis11111

The process is the same for other calculate fields.

The spinners are designed exclusively for number fields, while the equations can return text values.

Best regards.

Hello @sakis11111

The process is more or less complicated depending on the code of the calculated fields’ equations. The easier solution would be to untick the “Read only” checkbox in both calculated fields (depending on your project’s requirements, you should also untick the ” If value entered manually, no evaluate equation” checkbox).

Finally, use the fields as usual. However, based on your equations’ code, using the field A in the equation of field B, and field B in the equation of field A can provoke an endless loop because the result of each field will trigger the equation of the other field.

To prevent endless loops, you can use conditional statements in both equations. Assuming you have two calculated fields, the first field equation can be implemented as follows:

(function(){
if( 'flag_a' in window ) { delete flag_a; return __ME__; }
else flag_a = true;

/** The rest of the code here with the equations return **/
})()

In the second calculated field:

(function(){
if( 'flag_b' in window ) { delete flag_b; return __ME__; }
else flag_b = true;

/** The rest of the code here with the equations return **/
})()

Best regards.

Hello @ohtusabes

fieldname5 in your form is not the GDPR field; it is an HTML Content control, and the HTML Content fields are not submitted to the server. In your form, the GDPR field is the fieldname4. So, you must use the <%fieldname4_value%> tag.

Best regards.

Hello @sakis11111

That requires a more complex CSS rule. Assuming the fields’ values go from 0 to 100, you can edit the equation as follows to apply a gradient in the field’s background:

(function () {
    let fields = {
        fieldname1|n: fieldname1,
        fieldname2|n: fieldname2,
        fieldname3|n: fieldname3
    };

    for (let i in fields) {
        getField(i).jQueryRef().find('input').css('background', 'linear-gradient(to right, green 0%, green ' + fields[i] + '%, white ' + fields[i] + '%, white 100%)');
    }

})()

Best regards.