![\"Automatically](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2025\/09\/How-to-Automatically-Detect-and-Remove-Unwanted-Solution-Components-in-Dynamics-365.png\")
<\/p>\n<\/p>\n
Imagine yourself managing a sprawling Dynamics 365 solution, bloated with thousands of components, including web resources, entities, and plugins, many of which are unused web resources with no dependencies. Cleaning them up via the Power Apps maker portal (https:\/\/make.powerapps.com\/<\/a>) means scrolling through endless lists and manually deleting each one, a tedious and error-prone task. One wrong move could break dependencies, crashing your solution. This common headache for Dynamics 365\/Dataverse developers and admins boils down to two challenges:<\/p>\n Here comes our tech-saviors, the powerful duo of RemoveSolutionComponentRequest <\/strong>and RetrieveDependenciesForDeleteRequest <\/strong>from Microsoft.Crm.Sdk.Messages<\/strong>, your cleanup superheroes.<\/p>\n These SDK classes work together to programmatically target and remove unreferenced components from an unmanaged solution, with dependency checks to ensure safety. In this blog, you\u2019ll learn how to streamline solution cleanup with key code snippets, components, and benefits for efficient maintenance.<\/p>\n Approach<\/strong><\/p>\n The aim is to replace manual UI deletions with an automated script that identifies solution components in SampleSolution (e.g., web resources with no dependencies<\/em>) and removes them safely.<\/p>\n The process uses a QueryExpression to target web resources (ComponentType=61<\/em>) and checks dependencies to ensure only idle components are deleted.<\/p>\n The steps include:<\/p>\n This approach eliminates manual effort, ensures safety, and scales for large solutions.<\/p>\n Step-by-Step Guide<\/strong><\/p>\n This guide provides a practical walkthrough to set up a console script that cleans up unreferenced web resources in Dynamics 365\/Dataverse. We\u2019ll focus on web resources with no dependencies, ensuring only those with no dependencies are removed. Set up an Azure AD app registration for authentication (ClientId, ClientSecret, org URL)<\/p>\n Step 1: Query Web Resources<\/strong><\/p>\n Query solutioncomponent for web resources (ComponentType=61<\/em>) in SampleSolution.<\/p>\n Step 2: Check Dependencies<\/strong><\/p>\n For each component, use RetrieveDependenciesForDeleteRequest <\/em>to confirm no dependencies exist.<\/p>\n Step 3: Remove Idle Components<\/strong> Key Components<\/strong><\/p>\n Output<\/strong><\/p>\n The script logs actions to debug_log.txt<\/strong> and the console, detailing processed and removed components.<\/p>\n For example, consider two web resources in SampleSolution: onLoadofAccount (attached to the Account form\u2019s onLoad event, dependent on the Account entity) and Test Account Script (an idle script with no dependencies). The script identifies Test Account Script as unreferenced and removes it, while skipping onLoadofAccount due to its dependency.<\/p>\n Before Cleanup:<\/em><\/strong> SampleSolution in make.powerapps.com, showing onLoadofAccount with its dependency and Test Account Script under Web Resources.<\/p>\n After Cleanup:<\/em><\/strong> SampleSolution with only onLoadofAccount remaining, as Test Account Script was removed.<\/p>\n Automating solution cleanup with RemoveSolutionComponentRequest <\/strong>and RetrieveDependenciesForDeleteRequest <\/strong>transforms a tedious and error-prone process into an efficient and safe workflow. By specifically targeting unreferenced web resources with a QueryExpression and ensuring dependency checks, this approach:<\/p>\n Give this approach a try in your Dynamics 365 solution and feel free to share your experience or insights in the comments!<\/p>\n","protected":false},"excerpt":{"rendered":" Imagine yourself managing a sprawling Dynamics 365 solution, bloated with thousands of components, including web resources, entities, and plugins, many of which are unused web resources with no dependencies. Cleaning them up via the Power Apps maker portal (https:\/\/make.powerapps.com\/) means scrolling through endless lists and manually deleting each one, a tedious and error-prone task. One\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,2361],"tags":[3225],"class_list":["post-42289","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-technical","tag-detect-and-remove-unwanted-solution-components-in-dynamics-365"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/42289","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=42289"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/42289\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=42289"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=42289"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=42289"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
string solutionUniqueName = \"SampleSolution\";\r\nint componentType = 61; \/\/ Web Resource\r\n\r\nQueryExpression query = new QueryExpression(\"solutioncomponent\")\r\n{\r\nColumnSet = new ColumnSet(\"objectid\", \"componenttype\"),\r\nCriteria = new FilterExpression\r\n{\r\nConditions =\r\n{\r\nnew ConditionExpression(\"solutionid\", ConditionOperator.Equal, GetSolutionId(service, solutionUniqueName)),\r\nnew ConditionExpression(\"componenttype\", ConditionOperator.Equal, componentType)\r\n}\r\n},\r\nLinkEntities =\r\n{\r\nnew LinkEntity\r\n{\r\nLinkFromEntityName = \"solutioncomponent\",\r\nLinkToEntityName = \"webresource\",\r\nLinkFromAttributeName = \"objectid\",\r\nLinkToAttributeName = \"webresourceid\",\r\nColumns = new ColumnSet(\"name\"),\r\nEntityAlias = \"wr\",\r\n}\r\n}\r\n};\r\n\r\n\u00a0\r\n\r\nvar results = service.RetrieveMultiple(query);\r\nLogMessage($\"Found {results.Entities.Count} components matching query.\");<\/pre>\nforeach (var component in results.Entities)\r\n{\r\nstring componentName = component.GetAttributeValue<AliasedValue>(\"wr.name\")?.Value?.ToString();\r\nif (componentName == null) continue;\r\n\r\nLogMessage($\"Processing component: {componentName} ({component.Id})\");\r\n\r\n\/\/ Check dependencies\r\nvar dependencyRequest = new RetrieveDependenciesForDeleteRequest\r\n{\r\nComponentType = componentType,\r\nObjectId = component.GetAttributeValue<Guid>(\"objectid\")\r\n};\r\nvar dependencyResponse = (RetrieveDependenciesForDeleteResponse)service.Execute(dependencyRequest);\r\nif (dependencyResponse.EntityCollection.Entities.Count == 0)\r\n{\r\nLogMessage($\"{componentName} has no dependencies. Attempting removal...\");\r\n\r\n}\r\n\r\nelse\r\n\r\n{\r\nLogMessage($\"Skipped {componentName}: Has {dependencyResponse.EntityCollection.Entities.Count} dependencies.\");\r\n}\r\n\r\n}<\/pre>\n
\nRemove components with no dependencies using RemoveSolutionComponentRequest<\/em>.<\/p>\nif (dependencyResponse.EntityCollection.Entities.Count == 0)\r\n{\r\n var removeRequest = new RemoveSolutionComponentRequest\r\n {\r\n ComponentId = component.GetAttributeValue(\"objectid\"),\r\n ComponentType = componentType,\r\n SolutionUniqueName = solutionUniqueName\r\n };\r\n try\r\n {\r\n service.Execute(removeRequest);\r\n LogMessage($\"Successfully removed: {componentName} ({component.Id})\");\r\n }\r\n catch (Exception ex)\r\n {\r\n LogMessage($\"Error removing {componentName}: {ex.Message}\");\r\n }\r\n}<\/pre>\n\n
\n
\n
\n
![\"Automatically](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2025\/09\/1Automatically-Detect-and-Remove-Unwanted-Solution-Components-in-Dynamics-365-1.png\")
<\/p>\n![\"Automatically](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2025\/09\/2Automatically-Detect-and-Remove-Unwanted-Solution-Components-in-Dynamics-365.png\")
<\/p>\n![\"Automatically](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2025\/09\/3Automatically-Detect-and-Remove-Unwanted-Solution-Components-in-Dynamics-365.png\")
<\/strong><\/p>\n![\"Automatically](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2025\/09\/4Automatically-Detect-and-Remove-Unwanted-Solution-Components-in-Dynamics-365.png\")
\nConclusion<\/strong><\/p>\n\n