{"id":9809,"date":"2025-03-24T12:28:22","date_gmt":"2025-03-24T12:28:22","guid":{"rendered":"https:\/\/www.aegissofttech.com\/insights\/?p=9809"},"modified":"2025-09-24T11:22:46","modified_gmt":"2025-09-24T11:22:46","slug":"filter-sub-grid-rows-in-dynamics-365-ce-crm","status":"publish","type":"post","link":"https:\/\/www.aegissofttech.com\/insights\/filter-sub-grid-rows-in-dynamics-365-ce-crm\/","title":{"rendered":"How to Filter Sub-Grid Rows in Dynamics 365 CE (CRM) Using Fetch-XML & JavaScript?"},"content":{"rendered":"\n

INTRODUCTION<\/strong><\/h2>\n\n\n\n

Filtering sub-grids dynamically on model-driven forms is a common requirement in Dynamics 365 CRM implementations-especially when we want to present contextual data based on the record being viewed or edited. Out of the box, sub-grids offer limited flexibility for real-time filtering. However, by leveraging Fetch-XML and JavaScript, we can apply advanced filtering logic that adapts to business rules or user inputs on the fly. Such tailored solutions are often best implemented with the expertise of a Dynamics CRM Development Company<\/a>.<\/p>\n\n\n\n

In real-world CRM scenarios\u2014like sales forecasting, opportunity management, or customer service planning\u2014we often deal with interconnected tables and contextual views. Users expect the system to intelligently present related records without navigating away or manually filtering data. This is where programmatic control of sub-grid data becomes a game changer.<\/p>\n\n\n\n

This method helps ensure users are presented with the most relevant records based on their actions and selections, making the form behavior smarter and more efficient. Whether you’re customizing forms for Sales, Customer Service, or any other module, this approach gives us the precision and control needed for building intuitive and responsive UIs. By the end, you’ll have a clear understanding of how to implement custom filtering logic for sub-grids in your own Dynamics 365 CE environment.<\/p>\n\n\n\n

PRE-REQUISITES<\/em><\/strong>:<\/em><\/h3>\n\n\n\n
    \n
  1. A Dataverse\/Dynamics 365 CE (CRM) environment<\/li>\n\n\n\n
  2. System administrator \/ System Customizer role<\/li>\n\n\n\n
  3. (Optional) Access to XRM Toolbox for JavaScript web-resources<\/li>\n<\/ol>\n\n\n\n

    STEPS<\/em><\/strong><\/h3>\n\n\n\n

    1. In our Dataverse Search \/ D365 CE<\/a> (CRM) environment, there exists a custom table named Account Planning<\/em>. It has a lookup on it for Account<\/em>. Despite there not being any relationship between Account Planning <\/em>and Opportunity<\/em> tables, we go ahead and place one Sub-grid for Opportunities <\/em>on Account Planning<\/em> form (as shown in the screenshot below). We then SAVE the changes.<\/p>\n\n\n\n


    \"Dataverse
    <\/p>\n\n\n\n

    2. Next, we create one JavaScript web-resource and put the following JS code in it. We all know that there exists an Out-of-the-Box 1: N relationship between Accounts <\/em>and Opportunities. <\/em>In simpler words, one Account can have multiple Opportunities. We can see in the highlighted content \u2013 we are making a filtration in the Fetch-XML, instructing to pull only those active Opportunities that belong to the selected account.<\/p>\n\n\n\n

    IS.HPSAAccountPlanning.filterOpportunitiesSubgrid = function (formContext)\n{\n\tvar accountControl = formContext.getAttribute(\"infy_account\").getValue();\n\tif (accountControl)\n\t{\n\t\tvar accountId = accountControl[0].id;\n\t\tvar fetchXml = \"<fetch version='1.0' output-format='xml-platform' mapping='logical' distinct='false'>\" +\n\t\t\t\"<entity name='opportunity'>\" +\n\t\t\t\"<attribute name='name' \/>\" +\n\t\t\t\"<filter type='and'>\" +\n\t\t\t\"<condition attribute='parentaccountid' operator='eq' uitype='account' value='\" + accountId + \"' \/>\" +\n\t\t\t\"<\/filter>\" +\n\t\t\t\"<\/entity>\" +\n\t\t\t\"<\/fetch>\";\n\t\t\/\/ Set the fetchXml to the subgrid\n\t\tvar gridControl = formContext.getControl(\"subgrid_opportunities\");\n\t\tif (gridControl)\n\t\t{\n\t\t\tgridControl.setFilterXml(fetchXml);\n\t\t\tgridControl.refresh();\n\t\t}\n\t}\n}<\/code><\/pre>\n\n\n\n
    3. After Saving & Publishing the above JS web-resource, we add our function to the On Load <\/em>Handler Property of the Account Planning <\/em>form. Again, SAVE & PUBLISH.<\/p>\n\n\n\n
    \"Handler<\/figure>\n\n\n\n
    UNIT TESTITNG<\/em><\/strong><\/h3>\n\n\n\n