Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Mike Schmitt — Thu, 11 Sep 2025 17:53:41 GMT

[quote userid="293911" url="~/discussions/f/user-interface/39698/currency-input-field-rounding-issues-with-decimal-values-above-10-000-ex-200-300-57---need-plugin-recommendation/151474"]Appian is not understanding user typed commas as decimal[/quote]

If push comes to shove, I would suggest perhaps using a TEXT field for the input of the numerical value, and cleaning the user input upon SaveInto (converting it to proper decimal type at that point) - this would depend on the user using YOUR numbering system, but would NOT depend on user locale (for what it's worth).

Looks like that's about what you've done with your Currency Sanitizer rule. I would suggest you check out the "cleanwith()" function, it takes a little bit of the work out of "substitute" when you're substituting something for "blank".

Anyway thanks for confirming - will appreciate a "verify answer" on any that you feel like giving me props on. Gotta claw my way back into the Top 3 somehow, I still haven't made up for taking a week of vacation last month 😅

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Silas. B. Ferreira — Thu, 11 Sep 2025 14:55:17 GMT

Well, I was able to create a workaround and I will share with you all

rule!_RFind:

a!localVariables(
  local!reversed: joinarray(char(reverse(code(ri!string))), ""),
  local!findIndex: find(ri!substring, local!reversed),
  find(
    right(ri!string, local!findIndex),
    ri!string
  )
)

rule!_CurrencySanitizer:

a!localVariables(
  local!findComma: rule!_Process_RFind(string: ri!value, substring: ","),
  local!findDot: rule!_Process_RFind(string: ri!value, substring: "."),
  if(
    local!findDot < local!findComma,
    todecimal(
      substitute(
        substitute(trim(ri!value), ".", ""),
        ",",
        "."
      )
    ),
    ri!value
  )
)

rule!MoneyField (BRL):

a!textField(
  label: ri!label,
  labelPosition: a!defaultValue(ri!labelPosition, "ABOVE"),
  value: a!currency(
    isoCode: "BRL",
    value: ri!value,
    decimalPlaces: 2
  ),
  placeholder: ri!placeholder,
  saveInto: {
    a!save(
      ri!value,
      rule!_CurrencySanitizer(save!value)
    )
  },
  disabled: a!defaultValue(ri!disabled, false),
  readOnly: a!defaultValue(ri!readOnly, false),
  refreshAfter: "UNFOCUS",
  validations: { ri!validations },
  showWhen: a!defaultValue(ri!showWhen, true),
  instructions: ri!instructions,
  helpTooltip: ri!helpTooltip
)

Special thanks to Mike Schmitt . If any of you have any other suggestion, please don't hesitate

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Silas. B. Ferreira — Thu, 11 Sep 2025 14:31:52 GMT

Mike Schmitt I really appreciate your help.

There is still only one more point I have to deal, which is: Appian is not understanding user typed commas as decimal. Even though the LOCALE of the user I am testing substitutes dots for commas and vice-versa

a!localVariables(
  a!textField(
    label: ri!label,
    labelPosition: a!defaultValue(ri!labelPosition, "ABOVE"),
    value: a!currency(
      isoCode: "BRL",
      value: ri!value,
      decimalPlaces: 2 
    ),
    placeholder: ri!placeholder,
    saveInto: {
      ri!value,
      ri!saveInto 
    },
    disabled: a!defaultValue(ri!disabled, false),
    readOnly: a!defaultValue(ri!readOnly, false),
    refreshAfter: "UNFOCUS",
    validations: { ri!validations },
    showWhen: a!defaultValue(ri!showWhen, true),
    instructions: ri!instructions,
    helpTooltip: ri!helpTooltip
  )
)

So, the issue I am still facing is to make Appian recognize dots as commas and vice-versa.

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Mike Schmitt — Thu, 11 Sep 2025 14:07:51 GMT

[quote userid="293911" url="~/discussions/f/user-interface/39698/currency-input-field-rounding-issues-with-decimal-values-above-10-000-ex-200-300-57---need-plugin-recommendation/151472"]What if, my record type value is a Decimal? How am I going to handle it if the value is always being casted[/quote]

You're overcomplicating this. Store the decimal value only, and only worry about formatting it anytime it's output to a user-facing display. That should be it.

[quote userid="293911" url="~/discussions/f/user-interface/39698/currency-input-field-rounding-issues-with-decimal-values-above-10-000-ex-200-300-57---need-plugin-recommendation/151472"]Appian will always displays the imprecise value. There is no other way without using a string.[/quote]

The correct decimal value is stored correctly in a decimal type variable, whether that's a record field or CDT field. Remember that what's "displayed" is liable to be different from what's there in the underlying data, when just looking at the default output. Casting the output to text and using the formatting string merely forces the displayed value to look like what you're expecting (but of course this is still a representation of the underlying data).

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Silas. B. Ferreira — Thu, 11 Sep 2025 13:47:12 GMT

What if, my record type value is a Decimal? How am I going to handle it if the value is always being casted and not showing precisely on the input?

I would like to show the value not casted, on the input, so, there is no way without using a Text value. But what if my record.field is a Decimal? Appian will always displays the imprecise value. There is no other way without using a string. Is there?

Ex.: If I pass a decimal as a rule input, it's over, it will display the imprecise value again.

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Mike Schmitt — Wed, 10 Sep 2025 19:10:51 GMT

[quote userid="293911" url="~/discussions/f/user-interface/39698/currency-input-field-rounding-issues-with-decimal-values-above-10-000-ex-200-300-57---need-plugin-recommendation/151441"]However, I am wondering as well if Appian is gonna pass the real value when it's expected to be a decimal[/quote]

The "real value" is what's being stored in Appian, which is what I'm trying to show you. The rounded value you're seeing in the local variables panel is merely a "user facing" output, not the internal value.

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Silas. B. Ferreira — Wed, 10 Sep 2025 19:06:26 GMT

a!localVariables(
  local!amount,
  local!amountDecimal,
  a!textField(
    label: "Amount in Text",
    /* Instructions  show the saved datatype*/
    instructions: "Type of local!amount: " & typename(typeof(local!amount)),
    value: a!currency(
      isoCode: "BRL",
      value: local!amount,
      format: "SYMBOL"
    ),
    /* Instead of saving the value as text, a!save() is used to store to the desired datatype*/
    saveInto: {
      a!save(
        local!amountDecimal,
        text(todecimal(save!value), "#.##")
      ),
      a!save(local!amount, save!value)
    }
  )
)

Right, this method text() casts the value to text.

However, I am wondering as well if, whenever it casts, Appian is gonna pass the real value when it's expected to be a decimal, or, it is simply going to round, and miss the decimals digits.

For example: a recordType's field is a Decimal, so, when appian automatically converts the value to the decimal field in my grid `fv!item.field` (which expects a decimal but receives a casted value), is it gonna simply round or is it going to preserve the original value as sholud be (ex.: 400300.37 instead of 400300.4)?

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Mike Schmitt — Wed, 10 Sep 2025 18:59:17 GMT

So basically my prior answer is correct:

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Silas. B. Ferreira — Wed, 10 Sep 2025 18:56:08 GMT

I was just about to provide it

I will try what you suggested in just a sec

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Mike Schmitt — Wed, 10 Sep 2025 18:54:36 GMT

Could you provide a screenshot of an example of the output you're seeing and the actual underlying value that you'd expect to be seeing?

Have you tried formatting the output through functions like 'text(value, "0.00")' to signify that you want the displayed output to show the entire number including 2 decimal places at all times? Because as I said, when just displaying decimal data, Appian (badly) guesses at what level of significant digits should be displayed to the user.

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Silas. B. Ferreira — Wed, 10 Sep 2025 18:51:04 GMT

Yes, the currency formatter is meant to handle it, but it's automatically rounding the value when I convert it back to decimal, even though I don't want it to.

RE: Currency Input Field Rounding Issues with Decimal Values Above 10,000 (Ex.: 200,300.57) - Need Plugin Recommendation

Mike Schmitt — Wed, 10 Sep 2025 14:22:02 GMT

Appian's default way of displaying decimal numbers takes some sometimes unintuitive liberties with the number of significant figures shown - in ways that are a little unintuitive and opaque to not only the end user but also the designer (frustratingly). I'm not exactly sure I'm comprehending the manual conversions you're with your utuility rule, but I was under the impression that a!currency() was supposed to handle things like "dots instead of commas and commas instead of dots" automatically for currencies that use opposing systems (though i haven't tested this). BTW, are users not using locales that support the proper number entry system inherently? I thought it worked without manual conversion when the locale was set right (also haven't personally tested though).

My general advice at this point would be to go back to basics and make sure you're doing any manual conversion on a displayed number (versus the underlying decimal value) only at the very end, to avoid it becoming confused.