You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/README.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,8 @@ As well as Microsoft Dynamics 365 CE (online), Microsoft Dynamics 365 CE (on-pre
12
12
13
13
### **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).**
14
14
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
+
15
17
Please check [DynamicsWebApi Wiki](../../../wiki/) where you will find documentation to DynamicsWebApi API and more.
16
18
17
19
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
28
30
-**Node.js and a Browser** support.
29
31
-**Proxy Configuration** support.
30
32
33
+
31
34
## Terminology
32
35
33
36
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({
1166
1169
inChangeSet: false//<--- do not include in a change set
1167
1170
});
1168
1171
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)
1170
1173
dynamicsWebApi.retrieveMutliple({
1171
1174
collection: "contacts",
1172
1175
top: 1,
@@ -1975,24 +1978,26 @@ The `csdlDocument` will be the type of `string`. DynamicsWebApi does not parse t
1975
1978
1976
1979
## Formatted Values and Lookup Columns
1977
1980
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.
1979
1982
DynamicsWebApi automatically creates aliases for each property that contains a formatted value or lookup data.
1980
1983
For example:
1981
1984
1982
1985
```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:
0 commit comments