When someone first gets started with the Portal capabilities for Dynamics 365, one thing I’ve noticed that can be a bit overwhelming is how many different places you can put a piece of HTML, JavaScript, Liquid, etc to achieve the same result. In this series of posts, I describe some of the options, and provide some our best practices.
In my fourth and final post in the series on how you can add an integration with SharePoint to the Employee Self-Service Portal in Dynamics 365 without using server-side code, I’ll show you how you can add the ability to upload a file from the Portal directly into SharePoint.
In my third post in the series on how you can add an integration with SharePoint to the Employee Self-Service Portal in Dynamics 365 without using server-side code, I’ll dive into using the SharePoint REST API to display documents in a folder related to a record in Dynamics 365.
In my second post in the series on how you can add an integration with SharePoint to the Employee Self-Service Portal in Dynamics 365 without using server-side code, I’ll describe how we go about getting the SharePoint folder location for the current Case on the Edit Case page.
In this series I’m going to step through how you can add an integration with SharePoint to the Employee Self-Service Portal in Dynamics 365 without using server-side code. While the recent news that the October ’18 release of the Portal capabilities for Dynamics 365 with include out-of-the-box SharePoint integration may make this series obsolete in a hurry, I’m sharing it as it might inspire other solutions that can leverage the same techniques.
Microsoft decided to make the October ’18 release notes available while I was on vacation (it’s like they didn’t even consider my schedule!), so I’m a bit late on this, but here are my thoughts on what to expect in the fall when it comes to the Portal capabilities for Dynamics 365.
When using the Microsoft-provided PowerShell scrips to assist with an upgrade from Portals v7 to v8, there are a few known issues that could still leave your data in an undesirable state. We’ve released an XrmToolBox plugin to help address a couple of those items.
One of the big things we’ve talked about during the transition from Adxstudio Portals v7 to the Portal Capabilities for Dynamics 365 v8 is losing the ability to include server-side code in your website project. There are ways around this limitation – typically we recommend using a Dynamics 365 Portals Companion App. However, there is another technique, which we’ve always considered a bit of a hack, but not only does it work, Microsoft is using the technique in their own Portals. So if they can do it, why not us?
We have an Adxstduio Portals v7 site that’s been causing us grief recently by getting stuck in an error state. The error state is easily resolved by clearing the cache, but this solution required manual intervention. Since the site is currently being upgraded to v8, we didn’t want to invest too much into finding the root cause – it was easier to just kill the cache when the site went down. But what was even easier was using Microsoft Flow and Uptime Robot to do the job for us.
And now for something completely different! While I normally talk about Dynamics 365 Portals, we’ve had a few requests recently around SharePoint and Dynamics 365 integration, specifically around uploading documents to SharePoint via a custom interface. I initially thought that it would be a topic well covered on the Dynamics blogosphere but, to my surprise, I couldn’t find a lot out there. So I spent some time figuring it out, and thought I’d share my findings.
