Thoughts on Summit EMEA 2018 in Dublin
As I sit in the Dublin airport awaiting my flight back to Canada, I thought I’d jot down a few notes on the week that was D365UG/CRMUG Summit EMEA 2018.
As I sit in the Dublin airport awaiting my flight back to Canada, I thought I’d jot down a few notes on the week that was D365UG/CRMUG Summit EMEA 2018.
Last month Microsoft unveiled the Spring Release 2018 of Dynamics 365. While there were a lot of interesting items in the announcement (Marketing, Embedded Intelligence, PowerBI Insights apps), the one that I’m most excited about is the latest release of Common Data Service (CDS), version 2.0. In this post I’ll provide my thoughts on this latest update, as well as what it might mean for the Portal capabilities of Dynamics 365.
Dates, times, time zones, daylight savings time, and anything related to those concepts is an area that has always been a huge pain in the you-know-where for developers. There are so many rules and variables that it’s hard to be confident that your solution is handling all cases perfectly. Thankfully frameworks like .NET remove a lot of the guesswork, but you still have to be careful. In this post, I’ll investigate how Dynamics 365 and Portals handle dates and times.
In order to confirm that much of the functionality in Dynamics 365 Portals works with virtual entities, I needed to have data sources with some pretty specific fields. Rather than hunting for an existing service to meet all of my requirements, I was able to quickly setup a fake OData service hosted in Azure Web Apps that I could use as my Dynamics 365 Virtual Entity Data Source.
So far in this series I’ve provided an intro on virtual entities and a deeper dive into virtual entities and relationships. In this post, I’m finally going to talk about how they work with Microsoft Dynamics 365 Portals.
In my first post in this series I discussed how virtual entities and the link-entity node in FetchXML don’t mix well. In this post I’m diving a little bit more into virtual entities and how they can be related with other virtual entities, as well as non-virtual entities.
One of the great new features available in Dynamics 365 v9 is Virtual Entities, which allow you to represent data from external system as entities without copying or synchronizing data, and often times without any custom code. In this series of posts, I’ll dive into this new feature, with a focus on what it means for Dynamics 365 Portals, and how we can leverage them to create no-code integrations between your Dynamics 365 Portal and other systems.
My latest article for MSDyanmicsWorld.com was released last week. It talks about the latest release of Dynamics 365 Portals, as well as the release of documentation for the migration from Adxstudio Portals v7 to the Microsoft-hosted v8.
If you’ve done any work with Dynamics 365 Portals, you’ve probably run into the dreaded “We’re sorry but something went wrong” white screen of death. In this post I’ll share the tricks I’ve used to get more details about the error without contacting Microsoft support.
Since we were so close, we decided to finish off adding support for the entire Online Management API to our XrmToolBox Plugin. We’ve actually released two versions recently: one with the new features, and then another one fixing a bug we had introduced with the new features.