cancel
Showing results for 
Search instead for 
Did you mean: 

Consistent backend and plugin framework when working with charts

Author Name: Allan Varcoe

When data for a normal view is retrieved both the query and the result can be intercepted and modified by using the plugin framework. By registering a plugin on pre-retrievemultiple to modify the query - or on post-retrievemultiple to modify the resultset - we can provide additional and advanced filtering solutions, e.g. to enhance the security model or solve query issues that are not normally supported by Fetchxml.

However, data needed to render charts is not retrieved through the RetrieveMultiple request but through an undocumented internal message. This inhibits us to provide custom specific filtering or other functionality that was previously possible. Since it is not possible to disable charts for a specific entity, there is not available workaround.

Status: Under Review
Comments
Regular Visitor
Status changed to: Under Review
 
Regular Visitor
Same is true when working with FetchXML reports. In many integration scenarios you intercept RetrieveMultiple to populate or update fields on the fly, there is no workaround for this. Additionally, It's unfortunate that the ExecuteFetchXml method is still used internally when it has been deprecated.
Regular Visitor
Thank you for your feedback. This is a great suggestion, and we will consider this in our roadmap.
Regular Visitor
FYI - The same goes for fetch reports as well as the JavaScript REST endpoints (Jquery/JSON/Ajax). The fetch statements executed from the AdvancedFind and even Excel exports do utilize the Retrieve and RetrieveMultiple messages though.