In a January post I discussed some of the new Dynamics 365 Portal features that were expected as part of the April ’19 release. The exciting news is that these features are now available, so we can take a closer look.
It seems to be happening more and more these days that we are being asked to assist organizations that have launched a Dynamics 365 Portal but they are unhappy with the performance. If you find yourself dealing with a portal that is slower than you think it should be, this post should give you an idea of where to start looking.
I’ve been spending a lot of time on Dynamics 365 Portal performance recently, and I was able to dig a bit into a topic that I thought was worth sharing: the output caching of the header and footer templates. If that doesn’t catch your attention, how about the fact that it involves donuts?
I spent last week in Amsterdam attending both eXtreme365 and the User Group Summit, and was lucky enough to get to present three sessions on Dynamics 365 Portal topics. At each one of these sessions, one of the areas that generates the most interest is when I discuss the idea of a Companion App. Companion Apps are a technique you can use to leverage server-side code in your Portal implementation, and since it’s a topic I haven’t really covered on my blog, I thought it was about time.
