• Building the Perfect Portal Team

    This post was originally posted on Robert Bailey's personal Blog. Please Support him by viewing the original post here. For more great content, also follow him on LinkedIn and Twitter.

    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.

    Continue reading...


    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).

    Continue reading...

  • Save Cost on Logic App Data Retention

    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.

    Continue reading...

  • VELOCITY 365 v2.2


    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. 

    Continue reading...

  • Isolate Your Configuration Data Before Import Using PowerShell

    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.

    Continue reading...

  • Dynamics 365 Power Platform April 2019 Release

    The April 19 release of the Power Platform marks a major change in Microsoft’s delivery of updates to customers. With the changes in the updates from last October and the forced upgrade to version 9.x, the platform now will only maintain 1 version and has removed the Customer Driven Update Process. The April 19 release marks the first major release without a customer able to schedule it but the new process ensures everyone is on the latest version and adheres to a consistent update schedule. 

    Continue reading...

  • “Under Maintenance” pages for Dynamics 365 portals

    It’s common that a single feature update in your portal means modification to multiple components – which can’t be deployed one at a time. Even after proper rehearsal – deploying these changes to a live production environment can be risky business. Any mistakes or delays in your deployment are immediately visible to users.

    In these cases it may be decided that the best course of action is to take your portal down and replace it temporarily with a maintenance notice page – informing your users that updates are in progress and the portal will be back up momentarily.

    This approach may not be suitable for all situations. Please refer to the Further Consideration section for more details.

    An official “maintenance mode” feature is planned for the April 2019 release of Portals. This feature offers the benefits described in this blog post – and also addresses the concerns described below regarding search engine optimization. This blog post offers an interim solution.

    Continue reading...

  • Basic Portal Entity Permissions and the Create Content Wizard

    In the last article I wrote on this subject, we talked a bit about the Create Portal Content wizard. In that article, we walked through creating a list of leads that displays on the portal. Anyone can access the list, and it’s read-only. So where can we go from here?

    Continue reading...

  • Hey Siri, close the service request in CRM

    I was doing some testing for my previous blog where I needed to repititively change the status of service request to Resolved, which will send a message to the citizen. I was thinking what if there is a way through which I am able to change something in the D365 very easily. What if I ask the bot to do it for me ?

    Continue reading...

  • Adding Content Faster and Easier with the New Portal Management Centre

    There’s been lots of talk about the new portal management capabilities in the latest release of Dynamics 365 and portals. Managing content and adding web pages in portals has up until now been most easily done using the front-side editor when it comes to standard content; meanwhile adding views or forms for other non-portal entities has always been a manual process involving creating entity forms and entity lists on the CRM backend. Indeed, the pain and confusion involved with the process of doing so has been a big blocker in terms of adoption of the Portals as a turn-key solution.

    Continue reading...