I’ve been asked a few times recently about my recommendations for customers who aren’t using Dynamics 365 Online but still want portal functionality. In this post I’ll present some options and provide my two cents.
The April ’19 Release Notes we’re published on Monday – at over 300 pages, there is a lot to digest! In this post I’ll discuss highlights related to the Dynamics 365 Portal product, including CDS starter portal, maintenance mode, PowerBI enhancements, and more!
A question that pop ups from time to time is the difference between restarting a Microsoft Dynamics 365 Portal, and resetting it. The concern is typically around losing any of the customizations or configurations you’ve performed if you do either of those two things. Let’s look at the difference between these two options.
As a follow-up to last week’s post on conditional action buttons, I wanted to dive a bit deeper into a very cool, but completely undocumented feature that exists in the Dynamics 365 Portal product: the Filter Criteria for action buttons.
A question was asked on the Microsoft Dynamics 365 Community forums about how to hide or show a workflow action button based on the current user’s role, and since there are a few different ways to do this, I thought it was worthy of a blog post.
2018 was a busy year for the Dynamics 365 Portal product! From the end-of-life of Adxstudio v7 to the release of new features like SharePoint and PowerBI integrations, I’ll cover the most exciting developments throughout the year.
During last week’s eXtreme365 event in Austin, Texas, I was lucky enough to co-present a session with Nikita Polyakov (a Senior R&D Solution Architect at Microsoft, with a focus on Dynamics 365 Portal implementations). One of the tips he mentioned during the session was about using Liquid to decide which Entity Form to display on a page – it’s a very cool technique that seems to be underused. Then, a question showed up on the Dynamics 365 Community forums where that technique could be used to solve the problem. So I figured I’d write a quick blog post to get the word out on using Liquid to determine which Entity Form to display on a page.
My latest article for MSDynamicsWorld.com was published today. It talks about the October ’18 release of the Dynamics 365 Portal product, which includes SharePoint and PowerBI integration, as well as some of the other exciting things to look forward to in future releases, including availability within CDS environments, client-side SDK and sandbox licenses.
In my previous blog post, I talked about looking at the page-specific attributes like Copy, Summary, Custom JavaScript and Custom CSS when you’re searching for where the code is being saved. In this post, I touch on a few other places, such as Entity Forms, Entity Lists, Web Files and Content Snippets.
In my previous blog post, I talked about the overall page structure for a Dynamics 365 Portals page, and the main elements included in the rendered page, including the Header, Footer, and the Page Content. In this post, I get into the details about where code might be within the Page Content.
