I’ve recently had a requirement to remove disabled Active Directory users from our SharePoint deployment so that organograms and the likes are correct. As part of this, I’ve been looking at the options available in SharePoint and stumbled upon a method that should automatically maintain our SharePoint deployment.
This is a rather long list of just about every single error that Dynamics 365 can generate which is useful when debugging errors using Dynamic’s built in trace logs. This is as much for my own use as others so use it how you will and the original list can be found at – https://msdn.microsoft.com/en-gb/library/gg328182(v=crm.8).aspx
There’s an awful lot of questions about this issue online with very few answers and it’s, unfortunately, something I came across earlier today when we realised that suddenly our support desk in CRM had stopped receiving any emails.
In this article, I’ll go through some things to check that fixed the issue for me and will hopefully help anybody else experiencing this.
I recently came across this issue on our internal SharePoint deployment and tried a few things to fix it without success. Initially, I thought it may be to do with the sheer quantity of Active Directory groups I was a member of, however after reducing the number of groups I was a part of there didn’t appear to be any change in the issue.
After looking around and attempting a few fixes I finally came across why the issue occurs and how to fix it. I’ll cover all of this in this article.
Although I created this some time ago in order to get an accurate count of important records in our system it’s taken me some time to tidy it up and get it ready for release to the public.
The project and all source code are available on GitHub, feel free to use it in any manner you see fit, however, I’d appreciate being credited and hearing about whatever you do with it.
The script below can be used in order to enable versioning in all SharePoint document libraries and also to set how many major versions to retain and how many minor versions to maintain.
it’s important to keep in mind when choosing how many minor versions to retain that the setting actually specifies how many ‘Major Versions’ drafts’ should be retained and not a hard limit on how many ‘draft versions’ will be kept.
I’ve seen quite a few people asking why the ‘First Response By’ and ‘Resolve By’ fields found on the cases CRM forms and within the Engagement Hub aren’t populated. I’ve seen people often assume this is a bug however that’s not the case.
Below I’ll go through a few reasons why these may not be getting filled in.