v1.5.9

Fixes:

• @odata.bind now does not add a full Web API url, instead it adds / if it is not present. This change is crucial for on-premise organizations.
• added expand property RetrieveMutlipleRequest type definition for TypeScript.
• inconsistent removing of curly braces in guids during a bind operation @odata.bind.

Known Issue (On-Premise only):

• DynamicsWebApi uses GlobalContext.getClientUrl() to get the URL of an organization, therefore @odata.id operations (for example associate) are not going to work if the client is running outside of the local network and the client cannot resolve the name of the server that runs Dynamics 365 organization.
  @odata.id operations require an absolute uri to the resource and because the operation runs at the server it also needs to be a service route uri which contains a server machine name and therefore it is not resolvable for clients outside a local network. If this happens, you will get an error "AbsoluteUri should contain ServiceRouteUri".

v1.5.7

Changes:

• Use Content-ID reference in a batch request payload.
• Fixed type definitions.

v1.5.6

Changes:

• Added contentId in a request object to reference requests in a Change Set.
• Merge #48

v1.5.5

Fixes:

• #47. Make it work for older js versions.

v1.5.4

Changes:

• Added a timeout configuration option. Thanks to @ncjones #46

v1.5.3

Added:

• TypeScript declaration files. Can be found here. #29

Fixes:

• #45 Issue with parsing object arguments in a buildFunctionParameters function.

v1.5.2

Changes:

• Merge #44 "Add support for http proxy environment variables".

v1.5.1

Fixes:

• #41 Upsert with AlternateKey causes "TypeError: Cannot read property '1' of null"error

v1.5.0

Changes:

• Added Batch operations.

Fixes:

• #38 Alternate keys does not allow to use integer value (it is forcing to use a string).

v1.4.7

Fixed:

• npm update; added .npmignore file

Other minor changes.