158

Suggested by Kevin Hendricks Needs Votes 

Hello All, As you probably know adding a Custom Fetch into an Editable Grid is not supported by CDS / Dynamics 365. In the old interface this functionality was available only through an unsupported implementation as seen below. var gridControl = formContext.getControl(GRID_NAME); var subGrid = window.parent.document.getElementById(GRID_NAME); var rowCount = gridControl !== null ? gridControl.getGrid().getTotalRecordCount() : 0; if (subGrid !== null) { if (gridControl === null) { setTimeout(function () { //Repeat call initial function for delayed loading of the grid }, 1000); return; } if (subGrid == null || gridControl == null || rowCount == null) { Xrm.Utility.alertDialog("Grid not found"); return; } subGrid["control"].SetParameter("fetchXml", fetchXML); subGrid["control"].SetParameter("effectiveFetchXml", fetchXML); subGrid["control"].SetParameter("fetchXmlForFilters", fetchXML); //subGrid["control"].SetParameter("layoutXml", LayoutXml); subGrid["control"].Refresh(); } In the new interface the above solution does not work (which is to be expected as it is unsupported). There is a way to set it in JavaScript but the Grid does not support it and hence will ignore it, as seen below. var gridControl = formContext.getControl(GRID_NAME); gridControl.setFilterXml(fetchXML); gridControl.refresh(); The official statement that it is currently unsupported can be found here: https://github.com/MicrosoftDocs/dynamics-365-customer-engagement/issues/719 I would like to propose adding the ability the insert a Custom Fetch into the Editable Grid from the SDK as seen in my last example.
Comments (17)
  • feature very needed from years!
  • It's kind of ridiculous that this can't be done. Please add this functionality.
  • This functionality is critical to provide the option to customize views of data. Without this functionality that was possible in the classic CRM interface, the UCI is a step backwards.
  • Why not read only grids as well? I have needed this so many times...
  • Instead of FilterXml it should fetchXml for the Grids itself , because multiple linked queried sub-grids are being requested and everytime we are having them turned down just because the product is not supporting yet :(
  • we need it
  • we need it, the workarounds are too expensive

  • We need it

  • We need it

  • We need this feature