Added Recommendation to README.md

Added recommendation to use @hso/d365-cli

Translation fallbackLng bugfix

When Translation.init used the fallbackLng 1033, it will not throw an error anymore.

NodeJs support

NodeJs support fixed after upgrading webpack version 3 to 4.

Fix broken tag 4.0.4

Tag 4.0.4 was broken by mistake. It was not using umd. Fixed!

NodeJs support

Check for window to support NodeJs

Internet Explorer 11 support

No need to use babel-polyfill anymore.
useBuiltIns is used to support IE11

Translation support for Unified Interface

In the Unified Interface the url for the Translation files were wrong.

Annotation.parseAnnotation regarding support (migration needed)

Annotation.parseAnnotation

Annotation.parseAnnotation supports regarding now.

Annotation.parseAnnotation(file, id, logicalName).then(function (annotation) {
    annotation.save().then(function () {});
});

Migration steps

Annotation.parseAnnotation(file, accountId) => Annotatoin.parseAnnotation(file, accountId, "account")

Babel-polyfill error fix (migration needed)

Babel-polyfill

Before this fix, crm-sdk used babel-polyfill, which will add polyfills on global context. When having multiple libraries using the babel-polyfill an error only one instance of babel-polyfill is allowed will occor. This is solved by implementing the babel-plugin-transform-runtime plugin.

Migration steps

As a result of removing the babel-polyfill the crm-sdk will not deliver the noBabelPolyfill versions of the distributions.

• CRMSDK.noBabelPolyfill.js => CRMSDK.js
• WebAPI.noBabelPolyfill.js => WebAPI.js

Filter ownerid field

Filtering ownerid implemented by rewriting to _ownerid_value.

    Entity.query('appointment', {
        ownerid: ... //failed before
    }).then(....)