CRM Software Logo

Microsoft Dynamics 365 & Dynamics CRM experts provide reviews and opinions to aid professionals with the Dynamics 365 selection process.

 
 
Rob Triggs, CRM Dynamics Ltd.

Are You Getting the Following Subgrid Errors after Applying Microsoft Dynamics CRM 2016 Rollup 1.0 (or CRM2015 Online Update 1)?

Email | Print

 Are you seeing the following errors after you updated your Microsoft Dynamics CRM 2016 or 2015?

  • SetParameter is undefined
  • Cannot read property 'SetParameter' of undefined at FilterCasesSubgrid
  • Error: Unable to get property '$Y_3' of undefined or null reference
  • Unable to get property 'SetParameter' of undefined or null reference
  • Unable to get property setparameter of undefined or null reference

Microsoft has deprecated support for XML customization of subgrids in CRM2015 and CRM2016. Starting with CRM2016 Rollup 1.0 and CRM2015 Online update 1 You can no longer apply custom FetchXml to a subgrid using Javascript. As stated on the Microsoft website, “directly accessing the Document Object Model (DOM) of any Microsoft Dynamics CRM application pages is not supported.”

Where does this occur? If you have subgrids in CRM2015 or CRM2016 (on premise, or Microsoft cloud (CRM Online) where you have inserted XML code for filtering, the latest rollup removes support for processing these tags.

CRMD has a fully supported solution that can resolve the above issue – for more information please contact [email protected] or visit our web site at www.crmdynamics.com to chat with a live agent.

subgridsolutioninfographic

by CRM Dyamics, Ltd.

Comments are closed.

 

 
 
Show Buttons
Hide Buttons