Microsoft recently added functionality for one-click document generation to Dynamics 365. Although this is great functionality, it is a bit limited with regard to where it can save the generated document. Out of the box, we can add the SetWordTemplate action to a workflow, but that generates the document and saves it as an attachment to an annotation. What if you want to save it in SharePoint? We can accomplish this with a custom plugin.
The Incoming Email feature of SharePoint works great when all of your services are on-premises, but what do you do if you are using Exchange Online (or are looking to migrate to Exchange Online) and SharePoint on-premises? As it turns out, there’s a little bit of additional configuration, but it’s very easy to do! In this post, I will walk you through the settings you need to configure to get Incoming Email working in a hybrid environment.
The Secure Store Service in SharePoint 2010 is a really convenient way of storing credentials for external applications. However, what do you do if you set up a credential in the service, but forgot to record the password? No worries…with a little PowerShell script we can retrieve all username/password combos from the service.
A common complaint from SharePoint 2007 was that pages would become slow over time. This was usually due to users closing web parts instead of deleting them from the page. Even though Microsoft fixed this problem in SharePoint 2010, some people might like to find closed web parts and delete them. The other day I came across a post by Phil Wicklund, and although the script is functional as-is, I decided to expand on it.
A common complaint I hear about custom InfoPath forms on lists and libraries is that you can’t print them. If you try and use the print button through the browser, you will likely end up printing the entire page. If you take a screenshot, you might not capture the entire form.