Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
WebResourceBase, altogether with RibbonClientMetadata are used to render the apps on browsers. The issue with these tables is that it will contain data from regular applications (Sales team Member, Service Hub, Sales Hub) as well as from your custom apps (either Canvas or modelDriven). They will also include images/translation files (resx files)/Scripts. It will also contain references to the files included on your solutions.
One common issue is that files that are added in a solution (let's say v1.0) might not be in use and on another iteration (v1.1) and as a result, those files are not included anymore. As a consequence, the WebResource file is left Orphan within your environment, occupying some storage.
Finally, another common issue is related to the number of records on the table. According to the documentation on https://docs.microsoft.com/en-us/power-platform/admin/capacity-storage#do-indexes-affect-database-storage-usage, records on table will require indexes. Some of the indexes are controlled directly by admins (Including fields into queries, or querying the table). Other indexes are generated automatically based on the usage, in order to improve performance.
Best advice would be to open a request with Microsoft Support to understand which of these (if any) is affecting the size on your environment and check if there's any possible action.
Business Applications communities