Adoxio's Technical Director of Services Delivery, Colin Vermander will be speaking at eXtreme365 (formerly eXtremeCRM) on March 13-17, 2017, in Lisbon.

The purpose of the eXtreme365 conference is to help the Microsoft Dynamics 365 (CRM) community more effectively grow their business by selling, deploying and extending the Microsoft Dynamics 365 solution. eXtreme365 is dedicated to providing insight to the Microsoft Dynamics 365 future vision and strategy and encourages sharing of knowledge among the Microsoft Dynamics 365 community.  eXtreme supports critical connections with Microsoft, ISVs and partners – all with a goal of helping the community learn, grow and work more productively together.

Colin will be speaking at two sessions: Extend Dynamics 365 Portals with Custom Code, and Everything you need to know - Dynamics 365 Portals Implementations.

We hope to see you in Lisbon!  If you would like to pre-schedule a meeting with Colin while in Lisbon, please feel free to contact us.

A number of the Dynamics 365 application services; Field Service, Project Service and portals, all became generally available this week following the release of Dynamics 365 earlier this month. These all offer a number of improvements and new features from their previous iterations under Dynamics CRM. Previously called CRM portals, now Dynamics 365 portals, has received some significant updates, even some functionality that starts to bring the 3 application services together with Project and Field Service functionality now in some portals. Let’s take a look at some of the largest changes in this release:

I received this very generic looking message (below) when trying to run a Dynamics CRM portal. After a little experimenting I found the problem to be that my credentials pointed to a user that had not yet been added to the target CRM organization (but did exist in Active Directory).

Yet another reminder to check the basics when faced with strange errors.

The interesting thing here is that the error message I received might lead you to believe that tracing needs to be enabled for your portal (in order to gather more error details). However, this error is actually being delivered from the Dynamics CRM server, and is not reflective of the tracing settings for your portal.

If you are operating Dynamics CRM on premise, and would like it to include these additional exceptional details with its faults (so you can possibly see the reason behind the fault), instructions on how to do so can be found here.

Here’s my original error message:

As can be expected from Microsoft, having now officially launched CRM Portals for Dynamics CRM Online, they've published new documentation and support materials. Here are some of the notable new materials which we've seen so far.