Comma as “Decimal Separator” does not work in a numeric field

Err sorry what do you mean? The numeric field doesn’t has an option to set a decimal separator. It has an option to include the number of decimals but not a comma separator.

Sorry, I didn’t exactly specify the location of the Decimal Separator option. I only wrote “In plugin settings”. It was necessary to clarify that this is in the general settings of the plugin. This is where “Currency”, “Google Maps”, “Recaptcha”. Since this is a more general settings section, I assumed that these settings should (or could) apply to all numeric values on the form, including numeric fields. I was wrong? It is impossible?

Oh sorry, actually those settings are only used for format numbers, the numeric field can only work for native numbers so it is not possible to format them.

I will create a new field that can format numbers, please have in mind though that currently all new fields are added within the “Essentials” add on so this new field most likely will be also included there.

Regards!

Hello!
I conducted the “Currency” test.
The coma is displayed as a decimal separator – ok.
But when using the field value in another field (Simple Text, HTML), a coma is converted to a dot.
Is this expected behavior? Can this be corrected?
Regards!

Hello!

Yes that is the expected behavior as the currency field only use the formatted value in its field but in everything else it uses the unformatted value (this is needed as otherwise there would be a lot of conflicts with formulas and conditional logics that uses this field).

If you want to use the formatted value in a html or simple field you would first need to add a new field that has this formula:

[RNF “8” RNF].GetFormattedText()

Change the 8 for the id of the number format field, this will make this field to have the formatted value of the number format field. Then you can use this field in the html or simple field.

Regards!

Hello!

Thinking more about this, i think it makes more sense that the simple field and html field uses the html representation of a field rather than the text representation so i will do this change in the next release.

This will fix the issue with the number format field, have in mind though that your current html and simple fields might look a little different as they would now use the ‘html’ representation of the fields but at the end i think this would be better as other fields would also benefit from this, for example, a signature field inside a HTML or simple field would now show the signature image instead of not showing anything.

Regards!