AnsweredAssumed Answered

When using an OData API, why are INTs showing as Doubles in the profile?

Question asked by stinkybuffalo on Apr 25, 2017
Latest reply on Apr 25, 2017 by stinkybuffalo

I imported a schema to use as an XML profile for an integration, and the API has an OData listener set up.

 

In my XSD schema definition file, my integer values are defined like this:

<xs:element name="element1" type="xs:int" minOccurs="0"/>

However, at the OData endpoint, these are advertised as doubles.

<Property Name="element1" Type="Edm.Double" Nullable="false"/>

I don't understand why this is happening - Here is how that field is set up in the profile editor - note that the implied decimals are set to zero:

Int Settings

Any ideas of what is happening, and how to work around this?

Outcomes