OData Representation

1 minute to read Download PDF Edit
Mendix Data TypeEdm TypeAttribute ValueAtom XML Representation
IdEdm.Int6439406496739543873940649673954387
AutonumberEdm.Int6411
Binary (not supported) [1]   
BooleanEdm.Booleantruetrue
Currency (double with 2 decimal places) Deprecated.Edm.Double0.78823894889237840.79
Date and timeEdm.DateTimeOffsetFri, 19 Dec 2014 10:27:27 GMT2014-12-19T10:27:27.000Z
EnumerationEdm.StringColor.BlueBlue
Float (double with 16 digits precision)Edm.Double882389488923784.10000000003882389488923784.1
Big decimal Edm.Decimal0.33333333333333333333333333333333330.3333333333333333333333333333333333
Hashed stringEdm.StringHashPasswordHashPassword
Integer Edm.Int645050
Long [2]Edm.Int6439406496739543873940649673954387
StringEdm.StringJohnJohn
ReferenceEdm.Int6439406496739543873940649673954387
Reference set (not supported)   

1) Even though the Binary data type is not supported, FileDocument and Image system entities are supported and represented as Base64 encoded strings with type of ‘Edm.Binary’.

2) When using Excel to import an OData source, long numbers may seem cut off. This is due to a restriction in the data type Microsoft uses. See https://support.microsoft.com/en-us/kb/269370 for more information.

Additionally, the ‘updated’ field for an entry in OData comes from the system changedDate attribute of an entity. If this attribute is not available (because it is not exposed, the user does not have access rights, or it is empty in database) the default date (1-1-1970)  will be used.

Copyright © Mendix. All rights reserved. | Mendix.com | Terms of Use | Privacy Policy