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.
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?
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.
The June 2018 release of the Portal Capabilities for Dynamics 365 has a new major version number (v9). Also, in case you missed it (like I did), Microsoft announced in March that a few features are being deprecated.
In a January blog post on upgrading to the xRM Portals Community Edition, I promised to look into automatic cache invalidation. It only took a few months, but I’m finally delivering on that promise.
Dates, times, time zones, daylight savings time, and anything related to those concepts is an area that has always been a huge pain in the you-know-where for developers. There are so many rules and variables that it’s hard to be confident that your solution is handling all cases perfectly. Thankfully frameworks like .NET remove a lot of the guesswork, but you still have to be careful. In this post, I’ll investigate how Dynamics 365 and Portals handle dates and times.
Having gone through the entire process of upgrading a customer from Adxstudio v7 to xRM Portals Community Edition, I’d like to share what I’ve learned so that it might make your upgrade process a smoother experience.
