Canvas Power App development can be a little challenging, particularly if you are coming from a Dynamics CRM / 365 background. Understanding, for example, how to work with option sets within is not immediately clear. Fortunately, once you understand what’s involved, it’s easy to start doing some amazing things…
Dynamics 365 and Power Platform developers should always use Business Rules over JavaScript / TypeScript form functions. Full stop. However, there are situations where the native capabilities within Business Rules are not up to scratch, such as when you start working with multi-select option set fields…
Application users within Dynamics 365 / the Common Data Service arguably provide a far superior option when compared to traditional service accounts with a user name and password. In today's post, we'll dive and find out more about them.
OAuth authentication, especially involving the Common Data Service or Dynamics 365, is a subject you may not grasp fully the first time around. The technical setup required can be tricky to understand or even implement at all, meaning you find yourself dealing with error codes such as AADSTS65001.
The wave 2 release for Dynamics 365 Sales brings to the table a lot of cool new functionality, especially in the areas of Artificial Intelligence (AI). The Business Card Scanner feature, enabling you to quickly scan and save business cards as a new Lead or Contact read, is the cornerstone of this and requires a little bit of thinking about from a deployment perspective.
Project Service Automation (PSA) can be a beast when first approached. The application contains a breadth of functionality which is not always properly documented and can be challenging to figure out. To find proof of this assertion, we only need to look at how price list mark-ups and discounts operate.
When starting with Power Bi Desktop in conjunction with Dynamics 365 Customer Engagement, you are presented with several routes to bring your data into the application. In this week’s blog post, I take a detailed look at four of these avenues, outlining the benefits of each one.
Longstanding Dynamics 365 Customer Engagement professionals will be well versed in the capability to auto-create new entities and fields, based on a data import file. This functionality has been exposed fully within the Common Data Service as well, which naturally means the same kind of issues can crop up.
Having the ability to straightforwardly obtain a records Globally Unique Identifier after programmatically creating it within Dynamics 365 Customer Engagement can help significantly with data integration requirements. This is a relatively easy task when working with the Web API using JScript but less so if C# is your language of choice...