Developers typically get the short end of the stick in lots of things, and consistent learning tools is one area I’d highlight, particularly in the Dynamics 365 space. Fortunately, this no longer appears to be the case, thanks to the release of exam MB-400.
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.
Custom pricing is an invaluable feature within Dynamics 365 Customer Engagement, that can be used to fine-tune your sales processes. If you're interested in finding out more about them, then my latest tutorial video is for you - find out more in this post!
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.
It seems to be non-stop changes and announcements when it comes to licensing for Dynamics 365 Customer Engagement at the moment. Now, as we move into September, we get yet another, which informs us of some potentially troublesome API limits, that will take effect from October onwards.
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.
The ability to consume Application Insights data from directly within Power BI is an excellent feature in what is already a pretty outstanding product. However, there will likely be some steps that you have to follow to ensure that your reporting solution is secured, using an appropriately privileged API key.
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...
The Dynamics 365 Customer Engagement/Common Data Service connector for Azure Data Factory can, in most cases, fit into your data integration needs. However, it is worth highlighting the two field types which are, specifically, not supported; namely, the Customer and Owner field types.