Last week in Atlanta, Georgia, Microsoft hosted the new yearly Business Applications Summit which brings together the Microsoft product teams across Dynamics, PowerApps, Flow, PowerBI and Project Services to delivery to both partners and customers the latest news. This years event also coincided with the announcement of the release plan for release wave 2 (October 2019) so there was a lot of news out of the event and great content for presenters to deliver at the conference. KPMG Adoxio was in attendance and thought these were some of the big highlights of the event.
This information alert is to advise of the pending release of VeloCITY 365 Version 2.3. This product release is designed to be compatible with the new Microsoft Unified Interface. This release will be generally available for deployment to your non-production environment as of Friday, June 14, 2019. Please contact Support to coordinate/schedule deployment.
3 weeks ago I had the good fortune to attend the Dynamics 365 Saturday event in Toronto, Canada, and it got me thinking about what a great space Dynamics and the Power Platform is to be in and what a fantastic community surrounds it. I myself have only recently begun to become involved with the Microsoft Community - despite having been involved in the development of the Portals Product from back in the Adxstudio days.
In December of 2017, I wrote an article about a script that could be used to enhance the Dynamics 365 web templates’ ACE editor by increasing its coding area and providing the capability to customize its color theme. Dynamics 365 now has a new liquid editor that comes with portals v9 solutions as explained in this article by Colin Vermander. The new editor is the Microsoft Monaco Editor, which is the editor used in Visual Studio code.
In my post about the Create Portal Content Wizard, I talked about how easy it is to add content to the portal using point-and-click configuration, and demonstrated that the Wizard creates a whole lot of records in the background for you so that you don’t have to. It’s like magic! It certainly does beat having to spend the time configuring Entity Forms, Lists, Permissions, and web pages all from scratch. However, the Wizard also has its limitations. There are several scenarios that it simply can’t manage, including some fairly basic ones. The Wizard can also leave you with a fair bit of manual work or cleanup to do, depending on what you’re building.
In order to better understand the Wizard, I figure now’s the time to spell out exactly what records actually get created by the wizard. To do this, we’ll go through the different options for configuring a list (we care mostly about displaying organization entities, so that’s the focus of this article) and then see exactly what configurations are created with each and what changes occur with the different settings. If you aren’t familiar with the Wizard, I explain the steps for using it here. Read that first, then come back – this article is more of a deep dive.
Recently I participated in a group discussion with Colin Vermander about what it takes to have a successful implementation of Dynamics 365 Portals. Among many other factors that I’m sure we’ll discuss in the future, one that struck me is how to build the perfect Portals Implementation team
I thought it would be fun to take a look at the skillsets that are needed to build that team, and the roles associated with those skillsets. Now let’s make the distinction clear before we get started that many of these roles overlap, and the people who fill these roles simply need to have the skillsets required. Very often, one person might fill multiple roles on a smaller project. For example, the Business Analyst and Functional Consultant might be the same person. Conversely, on large implementations with tight deadlines, you might have a very large team with multiple workstreams. Each workstream might have a team of BAs, its own dedicated functional, solution architect, and development team. The golden rule at the end of the day is to ensure that the project is not understaffed, and that each of the below skillsets is taken into consideration when building your team.
Also note, that this article tries to be methodology-agnostic as much as possible. Some roles might only apply to certain methodologies – for example if you are using scrum you’ll need a scrum master, etc. Alright, without further adieu, let’s get down to it.
Ever tinkered with something you wished you hadn’t? Ever wished for an ‘Undo Customizations’ button in Dynamics 365?
There isn’t one… yet. But until there is, here’s how you can remove unmanaged customizations from a managed component (including a native system component).
Logic apps by default have data retention of 90 days. The cost of Data retention can grow exponentially if not managed properly. Unless needed for business requirements to keep the run history of your logic apps I would suggest the settings of Data retention to 7 days the lowest setting available. As of March 13th 2019 the data retention setting can only be configured from Azure after you have enabled and/or deployed the logic apps.
This information alert is to advise of the pending release of Velocity365 Version 2.2. This product release contains numerous product enhancements as well as UI improvements and bug fixes. This release will be generally available for deployment to your non-production environment as of Friday March 15, 2019.
Some applications for Dynamics 365, such as Field Service, Portals, and Unified Service Desk store their configuration data as records in Dynamics 365 – alongside your business data.
Microsoft’s Configuration Migration tool allows you to easily move configuration data between Dynamics 365 environments. One limitation of the export function, though, is the inability to separate configuration records from business records of the same type.