Monday, October 15, 2018
In part 1 of this post I demonstrated building and using a service which receives a FetchXML query and returns Dynamics 365 data to any Portal page in an asynchronous manner as a JSON object. This service is similar to the SDK’s RetrieveMultiple message.
In this part 2, I’ll demonstrate a different service, which like the SDK Retrieve message, receives a record type, record id (GUID) and columns set to return the required data as a JSON object.
This is useful when you already have a specific Dynamics 365 record id at hand and you want to retrieve additional data for...
Friday, October 12, 2018
Leveraging Colin Vermander brilliant article on using Liquid Templates to return JSON, I would like to demonstrate creating and using a ‘service’ to asynchronously retrieve Dynamics 365 data into any portal page.
Why is this useful?
Liquid Templates tags are rendered on server side before a response is returned to the browser, so FetchXML tag will return a static result once the page is returned.
But what about responding dynamically to client side events such as option selection, button click or expending an element to view more details?
Sending the page to the server again is no longer an option if you want...
Friday, January 8, 2016
Although the Audit History entity is somewhat degenerated, records for this entity can be extracted via multiple API mechanisms in both Online and on-premise scenarios: Organization Service query (QueryExpression, QueryByAttribute, LINQ, FetchXML) OrganizationData Service query The Audit History entity lacks a FilteredView element and therefore can not be retrieved from the Database in a supported manner. Also, version 2016 new Web API does not expose the Audit entity and can not be used for that purpose. In this post I will demonstrate using some of the API mechanisms to extract Audit History records. Note that...