Skip to content

Releases: AleksandrRogov/DynamicsWebApi

v1.6.8

19 Jul 17:00

Choose a tag to compare

1.6.7 hot fix release

Changes:

  • Normalize response headers in a batch response

v1.6.7

19 Jul 16:42

Choose a tag to compare

Changes:

  • Added response headers to error object as requested in #69 . To access response headers use error.headers property.

v1.6.6

30 Jun 15:01

Choose a tag to compare

Fixes:

  • Formatted values did not have aliases in expand objects.

Changes:

  • Added response types to TypeScript declaration files.

v1.6.5

23 Jun 18:55

Choose a tag to compare

Changes:

  • Removed limitation where useEntityNames: true did not work if there was no cached metadata before executing batch request.

v1.6.4

10 Jun 16:50

Choose a tag to compare

Changes:

  • Added apply request option to advanced requests that allows to dynamically aggregate and group data. At this moment the parameter is a type of string, I will be looking into making it an object. More Info
  • Allow nested expand options. #67

v1.6.3

31 Mar 01:14

Choose a tag to compare

Fixes:

  • Issue #66 . Alternate Key can now contain a UUID value.

v1.6.2

12 Feb 04:14

Choose a tag to compare

Fixes:

  • Dynamics 365 Unified Interface Only: when useEntityNames set to true and a web api request is made with a collection name instead of a logical name of the entity, the request could fail because metadata for the entity cannot be found.

v1.6.1

03 Feb 23:31

Choose a tag to compare

Fixes:

  • Skip adding quotes for Web API type parameters in Web API Function operations: #65

v1.6.0

23 Nov 21:02

Choose a tag to compare

Changes:

  • Parse response of a failed batch request. Important! This is a breaking change for those who use batch requests because of changes in an error parameter type which is passed in the catch callback. Starting from v1.6.0 a parameter passed inside a catch callback of a failed batch request is an array of objects, one of those objects is the error that caused the batch to fail. Usually it is at the same index as a failed request in the batch. To get an error message, I would recommend looping though an array and checking the type of each object, for example: response[i] instanceof Error.
dynamicsWebApi.startBatch();

dynamicsWebApi.retrieveMultiple('accounts');
dynamicsWebApi.update('00000000-0000-0000-0000-000000000002', 'contacts', { firstname: "Test", lastname: "Batch!" });
dynamicsWebApi.retrieveMultiple('contacts');

//execute a batch request:
dynamicsWebApi.executeBatch()
    .then(function (responses) {
       //parse response
    }).catch(function (response) {
        //response is an array
        for (var i = 0; i < response.length; i++){
            if (response[i] instanceof Error){
                //error will be at the same index as the failed request in the batch
            }
            else{
                //response of a successful request
            }
        }
    });

v1.5.14

16 Nov 16:28

Choose a tag to compare

Fixes

  • error during parsing of a batch response that contains urls with alternate keys