Endpoint differences

The object models for the legacy and native endpoints for the Dynamics GP service are almost identical. However, there are some differences that you need to be aware of when you use each endpoint.

Data type naming differences

The base data types, such as string, integer, and boolean use names that are different in the legacy and native endpoints. The following table lists the base data type name used in the legacy endpoint and the corresponding name used in the native endpoint:

Legacy endpoint	Native endpoint
Boolean	boolean
DateTime	dateTime
Int32	int
Decimal	decimal
String	string

You will see these naming differences where the base names are used, such as restriction criteria. The datetime restriction type is a good example. In the legacy endpoint, the datetime restriction type has this name:

BetweenRestrictionOfNullableOf*DateTime*

In the native endpoint, the datetime restriction type has this name:

BetweenRestrictionOfNullableOf*dateTime*

Notice that the base data type (in italic text) has a slightly different name, due to a difference in the casing.

Object name differences

Collection objects for enumeration values use different names in the legacy and native endpoints. In the native endpoint, these collection objects are nullable. The the legacy endpoint, they are not.

For example, in the legacy endpoint the object representing a collection of ApplicationStatus objects has the following name:

ArrayOfApplicationStatus

In the native endpoint, the object representing a collection of ApplicationStatus objects is nullable. It has the following name:

ArrayOfNullableOfApplicationStatus