Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
One thing I often notice when reviewing deployments of Microsoft CRM is that the tables used to store records regarding workflow and async processes can get very large; specifically the AsyncOperationBase and WorkflowLogBase tables. By default, the records in these tables are stored indefinitely, when in fact after a point in the time business value of the information may not justify the extra space in the database. If a lot of workflow is being used in the deployment, these tables can grow quickly and can sometimes cause performance issues. There is some information available in KB articles on how a couple of registry keys can change the way these records are handled. The video below shows how these keys affect the records and how this has changed a bit in CRM 2011. Links to the KB articles explained in the video are also below. Whether or not these records are stored or removed will need to be a decision made for each deployment individually as each customer has different business rules. However in most cases, at some point it will make sense to remove some of these records.
Business Applications communities