How to handle Double and Long values in Appian?

RE: How to handle Double and Long values in Appian?

rp_balaji — Tue, 24 Jul 2018 06:49:54 GMT

Hi Srinath,

Yes I agree, the workaround to handle long or double values is to define datatype as Text but in certain cases like "If you want to compare the user entered value if it is greater than '2147483647' or not, then we don't have choice than going with todecimal() option".

If you have any better option or workaround plz let me know.

Regards,
Balaji.R

RE: How to handle Double and Long values in Appian?

yeswanththiyarir — Mon, 23 Jul 2018 19:10:40 GMT

Text would be the best option

RE: How to handle Double and Long values in Appian?

srinatha — Mon, 23 Jul 2018 17:45:33 GMT

Hi Balaji,
I had the same issue couple of days back. I need to store 18 digit value. So it was the same "2147483647" constant that will be stored in db table. So, I changed the type of the CDT field to "Text" and make the db field value as varchar.

The reason is Appian doesn't support long or double. If you would use decimal or float it would round it off to some values.

So, at this point I would suggest to make the field as text.

Thanks
Srinath

RE: How to handle Double and Long values in Appian?

Aditya — Mon, 23 Jul 2018 08:19:42 GMT

If you use todecimal(), all your long and double values will be rounded off , so you will always get an approximate answer even if your calculations are overhead.

RE: How to handle Double and Long values in Appian?

rp_balaji — Mon, 23 Jul 2018 07:48:07 GMT

Hi Shubham,

Thanks, In terms of displaying a Long or Double values we can use text but When there is calculation involved then we need to go with the workaround as mentioned in the previous comments.

Regards,
Balaji.R

RE: How to handle Double and Long values in Appian?

rp_balaji — Mon, 23 Jul 2018 07:46:01 GMT

Hi Aditya,

Thanks for your response, yes am doing that (point no.2) as a workaround for now, but if in case calculations involved with Long or double values then Appian not supporting Long and Double datatypes may become overhead.

Regards,
Balaji.R

RE: How to handle Double and Long values in Appian?

kaushala — Mon, 23 Jul 2018 07:36:48 GMT

Hi,
I was also facing the same issue and to overcome with this we used a!textfield instead of a!intergerfield.
but to restrict the user to enter only numeric values in the text field we created one more expression that removes alphabet and special characters from the value.
##ABC_Utils_RemoveAlphabetsAndSpecialCharacter
concat(
tointeger(
apply(
charat(
ri!String,
_
),
enumerate(
lenb(
ri!String
)
) + 1
)
)
)
Replace your integer field with this code
_____________________________________________________________________________________________________
a!textField(
label: "Amount",
value: rule!ABC_Utils_RemoveAlphabetsAndSpecialCharacter(
String: ri!String
),
saveInto: a!save(
ri!String,
rule!ABC_Utils_RemoveAlphabetsAndSpecialCharacter(
String: save!value
)
)
)

RE: How to handle Double and Long values in Appian?

Shubham Aware — Mon, 23 Jul 2018 05:42:13 GMT

Hello,

Appian does not support long or double value only solution is to use as text.

RE: How to handle Double and Long values in Appian?

Aditya — Mon, 23 Jul 2018 04:57:09 GMT

Appian does not handle Long and Double values very well. However there are few workarounds.

1. If you want the long or double values only for display purpose, like in a form or a record or a report, keep the value in the text form.
2. If you have to do some operation on that value like addition, subtraction etc., use todecimal(). For eg. todecimal("2147483647"). It will give you an approximate answer after rounding off certain digits.

RE: How to handle Double and Long values in Appian?

vetrivelk — Mon, 23 Jul 2018 04:01:02 GMT

Hi Team ,
has anyone sorted this one . if so please update .

Regards,
vetri

RE: How to handle Double and Long values in Appian?

jeremys — Thu, 19 Jul 2018 22:34:10 GMT

Depending on what you're using the values for, a workaround would be to just save them as text. This will allow you to view the exact value of the number.