Releases: AleksandrRogov/DynamicsWebApi
Releases · AleksandrRogov/DynamicsWebApi
v1.5.2
v1.5.1
v1.5.0
v1.4.7
Fixed:
- npm update; added
.npmignorefile
Other minor changes.
v1.4.6
Changes:
- Added functionality to work with Global Option Sets
v1.4.5
v1.4.4
v1.4.3
Changes:
- Added Entity Metadata helper functions:
createEntity,updateEntity,retrieveEntity,retrieveEntities. - Added Attribute Metadata helper functions:
createAttribute,updateAttribute,retrieveAttribute,retrieveAttributes. - Additional request properties related to Entity and Attribute Metadata queries:
navigationPropertyKey,metadataAttributeType.
Next release will include helper functions to work with Relationship and Global Options Sets Metadata.
v1.4.2
This release contains multiple fixes and enhancements. At this moment, I am working on adding functions to help developers to work with Entity Metadata.
Changes:
- Parse aliases into a JavaScript object. This enhancement is related to the following ticket: #23.
Starting from this version you can access aliased parameters in the following way:
var fetchXml = "<fetch version='1.0' distinct='false'>" +
" <entity name='contact'>" +
" <attribute name='fullname' />" +
" <attribute name='contactid' />" +
" <link-entity name='systemuser' from='systemuserid' to='owninguser' visible='false' link-type='outer' alias='owner'>" +
" <attribute name='fullname' />" +
" </link-entity>" +
" </entity>" +
"</fetch>";
dynamicsWebApi.fetch('contacts', fetchXml).then(function (response) {
var ownerFullname = response.value[0].owner.fullname;
//instead of: response.value[0].owner_x002e_fullname;
})
.catch(function (error) {
//...
});- Enhancements related to Entity Metadata requests. Next release will contain functions that will help developers to use DynamicsWebApi to query metadata.
Fixes:
- Special symbols in the filter query parameter. Related to #22.
- Other fixes.
Thank you for all your support! It means a lot to me.
v1.4.1
Changes:
- Added:
createRequestfunction for create request with additional parameters. - GUID brackets will be removed from the filter if they exist, for instance:
accountid eq {00000000-0000-0000-0000-000000000001}will be replaced withaccountid eq 00000000-0000-0000-0000-000000000001. It does not apply if the right side of the condition is a string, for example:sometextfield eq "{00000000-0000-0000-0000-000000000001}"will remain the same.