Skip to content

Commit 16144ae

Browse files
v2.0.0 release
1 parent 09eef06 commit 16144ae

File tree

8 files changed

+18
-13
lines changed

8 files changed

+18
-13
lines changed

.github/README.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ As well as Microsoft Dynamics 365 CE (online), Microsoft Dynamics 365 CE (on-pre
1212

1313
### **This documentation is for version 2.x. If you are working with version 1.x, please check [this instead](https://github.com/AleksandrRogov/DynamicsWebApi/tree/v1).**
1414

15+
If you want to upgrade from v1 - v2 breaking changes are [here](/.github/BREAKING_CHANGES_V2.md). List of new features in v2 is [here](/.github/NEW_IN_V2.md).
16+
1517
Please check [DynamicsWebApi Wiki](../../../wiki/) where you will find documentation to DynamicsWebApi API and more.
1618

1719
Browser-compiled script and type definitions can be found in a [dist](/dist/) folder.
@@ -28,6 +30,7 @@ Browser-compiled script and type definitions can be found in a [dist](/dist/) fo
2830
- **Node.js and a Browser** support.
2931
- **Proxy Configuration** support.
3032

33+
3134
## Terminology
3235

3336
Check out [Dataverse Terminology](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/understand-terminology). Microsoft has done some changes in the namings of the objects and components of D365 and since DynamicsWebApi has been developing for many years there may be _conflicting_ naming, such as: `createEntity` - which _right now_ means "Create a Table Definition". Dataverse SDK terminology is what the library has been based on. I have no plans on changing that (except in documentation), mainly because Microsoft may change the namings again in the future which will lead to naming issues ...again.
@@ -1166,7 +1169,7 @@ dynamicsWebApi.create({
11661169
inChangeSet: false //<--- do not include in a change set
11671170
});
11681171

1169-
//this is a workaround a D365 bug (checked on July 16, 2023)
1172+
//this is a workaround to a D365 bug (checked on July 16, 2023)
11701173
dynamicsWebApi.retrieveMutliple({
11711174
collection: "contacts",
11721175
top: 1,
@@ -1975,24 +1978,26 @@ The `csdlDocument` will be the type of `string`. DynamicsWebApi does not parse t
19751978
19761979
## Formatted Values and Lookup Columns
19771980
1978-
Starting from version 1.3.0 it became easier to access formatted values for properties and lookup data in response objects.
1981+
With DynamicsWebApi it is easier (less code) to access formatted values for the columns as well as the lookup data in response objects.
19791982
DynamicsWebApi automatically creates aliases for each property that contains a formatted value or lookup data.
19801983
For example:
19811984
19821985
```ts
1983-
//before v.1.3.0 a formatted value for account.donotpostalmail field could be accessed as following:
1986+
//DynamicsWebApi supports an access to formatted values in both ways
1987+
1988+
//normally you would access a formatted value for account.donotpostalmail field could as following:
19841989
let doNotPostEmailFormatted = response['[email protected]'];
19851990

1986-
//starting with v.1.3.0 it can be simplified
1991+
//with DynamicsWebApi it can be access like this:
19871992
doNotPostEmailFormatted = response.donotpostalmail_Formatted;
19881993

19891994
//same for lookup data
1990-
//before v.1.3.0
1995+
//normally
19911996
let customerName = response['[email protected]'];
19921997
let customerEntityLogicalName = response['[email protected]'];
19931998
let customerNavigationProperty = response['_customerid_value@Microsoft.Dynamics.CRM.associatednavigationproperty'];
19941999

1995-
//starting with v.1.3.0
2000+
//with DynamicsWebApi
19962001
customerName = response._customerid_value_Formatted;
19972002
customerEntityLogicalName = response._customerid_value_LogicalName;
19982003
customerNavigationProperty = response._customerid_value_NavigationProperty;

dist/browser/esm/dynamics-web-api.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

dist/cjs/dynamics-web-api.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

dist/dynamics-web-api.d.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
/*! dynamics-web-api v2.0.0-beta.4 (c) 2023 Aleksandr Rogov */
1+
/*! dynamics-web-api v2.0.0 (c) 2023 Aleksandr Rogov */
22
/// <reference types="node" />
33
/**
44
* Microsoft Dynamics CRM Web API helper library written in JavaScript.

dist/dynamics-web-api.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

dist/dynamics-web-api.min.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

dist/esm/dynamics-web-api.mjs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
/*! dynamics-web-api v2.0.0-beta.4 (c) 2023 Aleksandr Rogov */
1+
/*! dynamics-web-api v2.0.0 (c) 2023 Aleksandr Rogov */
22
var __defProp = Object.defineProperty;
33
var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
44
var __getOwnPropNames = Object.getOwnPropertyNames;

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "dynamics-web-api",
3-
"version": "2.0.0-beta.4",
3+
"version": "2.0.0",
44
"description": "DynamicsWebApi is a Microsoft Dynamics CRM Web API helper library",
55
"keywords": [
66
"d365",

0 commit comments

Comments
 (0)