A week is a small space of time in the Dynamics 365 Customer Engagement world at the moment, as we ramp up to the October release and the many changes this brings to the table. This week, some interesting developments occurred concerning CSP licensing for the product.
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.
Obscure error messages can be the bane of an IT professionals life, often hampering or even preventing outright any successful resolution of issues. An example of this happened to me recently, during what appeared to be a run-of-the-mill Azure SQL automated deployment.
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.
Project Service Automation provides a cornucopia of desirable functionality for organisations wishing to integrate their sales and project management processes tightly. Be careful, though when implementing this app when using custom calculations within Dynamics 365 Customer Engagement, as you may encounter a few issues…
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.
Dealing with “Your Azure credentials have not been set up or have expired” Error Message in a Azure Template Visual Studio Project
Keeping things simple is an idea I like to promote at all times, particularly in the world of IT. Adopting this mantra can lead to fewer headaches and, as a recent example involving Azure Template deployments within Visual Studio demonstrates, a much faster resolution to your particular problem.
Migrating across from Microsoft Flow to Azure Logic Apps is ridiculously easy. However, there are some critical feature differences that you must make yourself aware of. One difference relates to how triggers actions work, particularly in tandem with an Azure template.
Dealing with “SQL Bulk Copy failed due to received an invalid column length from the bcp client” Errors in Azure Data Factory
When you are amid a pesky IT issue, it can be difficult determining whether the problem is down to a bug/system fault or human error. Like this recent example involving Azure Data Factory illustrates, it is generally best to assume the latter, to avoid any prolonged difficulty.
Resolving “No IP address is available to hand out to the dial-in client.” VPN Errors (Windows Server Routing and Remote Access)
Sometimes in IT, you can hit a brick wall when working with something outside of your comfort zone. When this occurs within a personal testing environment, then it also means that resolving errors, such as IP address assignment for the Windows Server Routing and Remote Access service, can be somewhat challenging…