I have a problem calling a webservice with a decimal value. At a certain height

moritzw over 11 years ago

I have a problem calling a webservice with a decimal value. At a certain height of the decimal value the internal encoding of the value becomes something like "1.0E8". I can still make this readible using the text() function. However if I send it to a webservice the service throws an error message that this is not a valid value for a decimal.

Is there a way to fix this other than using a string in the xml and have the service convert it internally?...

Discussion posts and replies are publicly visible

0 Diana Chavez
Appian Employee
over 11 years ago

Moritz, what is the error that you get when the web service receives the value? You can see this error in the application server log.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 moritzw over 11 years ago

the error doesn't happen in Appian, but at the web service side.

It's as follows: ext:CHARACTER:cvc-datatype-valid.1.2: The value "1.0E8" is not a valid value for the "decimal" datatype
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Diana Chavez
Appian Employee
over 11 years ago

The issue has been reported to our Product Team. Your reference number is #AN-47157.
Convertign this value to text also fails because the conversion only happens at Appian level, once it is received by the Web Service it is still interpreted as a decimal and as such it fails.
The workaround available would then be to receive the value as text.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bojant over 10 years ago

I'm having the same problem. We are using Appian 7.
Is this issue resolved in the newest versions?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 ashleyb over 9 years ago

Has this been resolved? Currently on version 7.6 and am seeing similiar behavior
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 moritzw over 9 years ago

as far as I know it hasn't been solved. I am using a text field instead now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 miteshp over 8 years ago

Hi Moritz, Do you have any update on this issue? I am running into the same and converting the data type to text doesn't seem possible.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 moritzw over 8 years ago

Hi, I am still working with the workaround to use text.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel