I’ve recently started to write for a new blog called ‘Sysadmin Central’ which will contain articles about various subjects I find particularly interesting. I plan to keep this one running as long as possible and hope to add more to it as I cover more elements of either SharePoint or CRM.
But for now, please check out my new blog, I’ll be covering a few topics over the coming weeks such as properly removing Panda antivirus, getting a Raspberry PI to run at 4k, various PowerShell scripts and study notes around the latest Azure exams.
This is going to be a rather complex technical article covering how to create the custom workflow step required to email all individual users in a team. This is useful for support desks or situations where you can’t or don’t want to directly email the team.
I’ll try my best to simplify this topic enough so that an individual with little to no prior experience should be able to follow it, however, if you just need to implement the functionality quickly and don’t mind paying for it I believe there are some companies or solutions online which may do this.
I recently had a requirement to move all the contents of a document library to another library and anybody that has had the displeasure of having to move files in SharePoint knows what a pain that can be.
To make matters worse, due to the specific setup I was dealing with the ‘Content & Structure’ tool was a non-option as it wasn’t functioning correctly and there were a large number of nested folders in the source library. Luckily this gave me the chance to use one of my favourite power tools – PowerShell.
This article contains a script which will copy all contents of a single library to another library, by using the built-in MoveTo command where possible so no data is lost or by copying if the source and target libraries are in different site collections.
Today’s just a very short article that will hopefully serve as a reminder to myself and a help to others searching for how to resolve the ‘Invalid XML’ error that is generated by C# plugins and the likes utilising FetchXML for querying CRM data.
By this point, I think it’s rather evident that Microsoft has little inclination to improve the experience of trying to create an email in CRM, time and again I’ve witnessed users struggling to create a basic email with some simple formatting because the built-in tools just don’t quite cut it.
To improve this situation, let’s add TinyMCE support to our email form in CRM which will allow our users to add some proper formatting and some extra goodies such as tables and source code without issue.
We recently updated our SharePoint instance with the latest update and realised that suddenly all of our workflows were starting to throw a ‘Failed to Start’ status, which upon further investigation, it was found that we were seeing the following error in the SharePoint ULS Logs –
Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file.