Unsigned integers can be useful in many ways, such as representing data sizes, resource handles and so on. Though OData V4 only supports signed integer natively, the protocol offers a flexible way called type definition to allow users to ‘define’ unsigned integer types themselves.As an example, we know that any_ UInt16_ integer can be represented by the primitive type _Edm.Int32_. Thus by typ
Special care needs to be taken while copying mappings that have reusable mapplet. Below is an example where the copy did not go as expected. These are extremely difficult to troubleshoot later.