You are currently browsing the tag archive for the ‘Dynamics 365’ tag.

Ok, we all know by now, with Dynamics 365 CE we have portal capabilities. It’s a configurable portal driven by the config and data in your CRM. But that’s where I’ll stop. The CRM Portal architecture is very much coupled to your CRM, and it doesn’t qualify for our Decoupled Architecture topic.

Instead, in this post I want to focus on the large majority of enterprises. They already have a portal, most likely a CMS driving their current site, Read the rest of this entry »

Advertisements

We’ve all seen the scenario, something happens in Dynamics, and a user must be notified. We’ve done it so far using emails, the brave ones have even done it with SMS by integrating with Twilio. SMS is not a protocol that confirms the receipt of the message (just FYI), and typically not under the umbrella of a Messaging Team to manage. But what if there was another way?

Welcome to Skype for Business notifications. Yes, we can send a message on Skype to a user when something of importance happens in Dynamics.

For this scenario I’m going to do a no-code approach, using Flow. We’ll discuss the challenges further down, but for now, let’s see how easy it is.
Read the rest of this entry »

I would argue that in today’s world, it is almost impossible for one person to know in detail all aspects of a platform. Take Dynamics 365 for example. With the merger of multiple platforms under one generic marketing name, now we have specialists in Customer Engagement, F&O, Talent, etc. Take it one step lower, inside Customer Engagement, and with Field Service and PSA, you need to catch-up on new concepts, business models, etc. And then there’s always been the xRM part, which is all about the client’s business need outside of the scope of typical standard modules. But that’s not all.

The platform, as we knew it, is growing at an exponential rate. Where does that take us?
Read the rest of this entry »

All robust platform can have a daunting data structure. With some, and in certain situations, you might not directly care about the intricacies. But if you are looking to create reports and visualization, identifying the complexities around data structure becomes quite important.

When working in Power BI, and connecting to Dynamics 365 Customer Engagement, the first step is to identify the entities and relationships that will help you to create relevant dashboards.

You could just ask a Dynamics developer to walk you through it, but that’s not always an option.

Back with older versions of Dynamics CRM, the SDK used to include these complex and large ERD diagrams. They were hard to read, and too stuffed of information. I remember spending time cleaning them up and removing non-relevant entities and relationship so I can present a small portion in documentation.

But fast forward to today. As a Power BI resource that is just starting to look at leveraging data from Dynamics 365, you can start first by looking at the entities. You can find a listing of the entities in the SDK (available for 8.2 at this time).
Read the rest of this entry »

UPDATE: The issue has been resolved. If you still encounter issues, open a support ticket.  

Message:
OData: The feed’s metadata document appears to be invalid. Table: Subject.

 

If you’ve been working with Power BI and pulling data from Dynamics 365, you might have encountered an issue with the OData connection. This applies when connecting to Dynamics 365 either using Power BI, Excel, or even when using the Power BI content packs for Sales Analytics and Customer Service Analytics. You will either get the following error when using Power BI or Excel:

image

Or you will see in your logs on Power BI:

image

This is a relatively recent occurrence (first I’ve encountered it was on Feb. 07, 2018), and it does not affect all environments. It’s been identified as a known issue and logged on the Power BI support site at

https://powerbi.microsoft.com/en-us/support/

image

Waiting for the next update on a resolution.

One common question when embracing Cloud is the ability to have a hybrid scenario. And with Dynamics 365, the question translates into “Is there a hybrid deployment model?”

The short and dry answer is NO. But, there are some aspects to consider that can make it an overall hybrid solution.

Let’s first look at the supported deployment models for Customer Engagement. Read the rest of this entry »

We’ve all done it in the past, where we started tinkering with the navigation, filtering entities based on permissions, removing entire areas from the navigation, and tinkering with user roles and hiding aspects of the platform.

Well, welcome to a new world of apps. What started with mobile, where “there’s an app for that”, now find it’s home in Dynamics 365 CE also. Microsoft gave us the tone, with the Sales and Customer Service apps, and gave us the tools to roam free.

We can now use the very visual App Designer to create our own very specialized apps. And the beauty, it follows the same configurable model as any other configuration on the platform.

NOTE that, while you have the ability to configure new apps in both a solution file or directly in the core solution, you should really try to stick with using solutions.

Read the rest of this entry »

With all the focus on the Dynamics 365 Customer Engagement naming, the split into Dynamics 365 for Sales and Dynamics 365 for Customer Service, with or without Marketing, and all the licensing implications and additional functional packages, this is a question that came out of the blue and caught me a little off-guard. While I’m still working on a few on-premise instances, all the licensing discussions lately have been around the online model. As such, maybe I haven’t paid enough attention to versioning for on premise, my bad.

Read the rest of this entry »

As we’ve seen in the previous articles on How to work with Power BI in Dynamics 365 for Sales and Service as well as How to work with Power BI in Dynamics 365 for Sales and Service–Part 2, we can leverage the existing content packs to simplify our data presentation for the Sales and Service modules in Dynamics 365. And that works fine if your requirements conform to what’s already built in those content packs. But most of the time that’s not necessarily the case.

Let’s have a look at how you can work with Dynamics 365 Customer Engagement data in Power BI from scratch. We’re going to be doing this from Power BI desktop. If you don’t have it installed on your machine, grab it from the Microsoft Store or from here.
Read the rest of this entry »

As we’ve seen in the previous post, getting content from Dynamics 365 for Sales or Service into Power BI is a relatively easy task when leveraging the Content Packs created by the great guys at the Power BI team.

Now, with the content packs in place, let’s go back to our Dynamics 365 instance and bring the data with a nice lipstick on.

First off, you must enable Power BI visualizations.

Go to Settings > Administration. Here open System Settings and on the Reporting tab, enable Power BI visuals.

image
Read the rest of this entry »

Seems like this is a topic of interest. My previous post HERE is still one of the most popular posts, even though it was published way back in April 2014. As such, and since I was recently putting together a small POC that involved this functionality, I decided to revisit this topic.

As I was saying, recently I had the opportunity to look at an asset management solution that integrates assets from Esri with other sources for enhanced data, as well as Customer Service and Field Service. Lots of integration work, as well as some interesting challenges along the way.

It is unfortunate that Esri decided a while back to pull support for their Dynamics CRM solution. Now we can only integrate to bring data into Dynamics 365. Even the support for the old 2015 version has been retired at the beginning of June 2017. It’s even more interesting, since they seem to support SharePoint, but I digress.

The part I want to focus on, and to come back to why I mentioned the original article, is simple. It deals with leveraging Google Maps to locate assets on a visual map.

Through integration, I can get my needed details on asset type, description and location in the form of Latitude and Longitude. This being a physical asset, like a tree, bench, bus stop, or any other type of urban furniture, an address does not apply and the coordinates are tracking the exact location of the item. IoT provides additional data points on the assets, depending on the asset, but that will be a different topic one day.

So, on my asset record, I am tracking the Latitude and Longitude data fields in two fields named asm_latitude and asm_longitude. Similarly to the approach described in the referenced article, I’m using a HTML web resource to present the location.

The Google API has evolved, and you will find references stating that as of v3 a key is not required anymore. While technically that is correct, pay close attention to the licensing model. This is an asset tracking application, and, as described HERE in the Pricing and Plans section, a Premium Plan is required for Asset Tracking Use Case. Obviously, contact sales for a price. And HERE is the description on the usage limits.

But, back to the record form, the format I chose for this POC is quite simplistic. See the screenshot below.

image

The displayed map is nothing more that a Web Resource of type Webpage (HTML).

The code to make it render, based on the Latitude and Longitude coordinates in the asset form is below (remember, this goes in the web resource, in the Source of the page).

NOTE: I’m not showing any kind of error handling for simplicity. Build your own error handling to make sure no unexpected behavior is impacting the user experience.

<html><head>
<meta name="viewport" content="initial-scale=1.0, user-scalable=no">
<meta charset="utf-8">
<style>
#map {
    height: 100%;
    margin: 0;
    padding: 0;
}
</style>
<meta charset="utf-8"></head>
<body style="word-wrap: break-word;">

var point_lat = window.parent.Xrm.Page.getAttribute(“asm_latitude”).getValue();
var point_lng = window.parent.Xrm.Page.getAttribute(“asm_longitude”).getValue();

function initMap() {
    var point_location = new google.maps.LatLng(point_lat, point_lng);
   
    var map = new google.maps.Map(document.getElementById(‘map’), {
        zoom: 15,
        center: point_location
    });
   
    var marker = new google.maps.Marker({
        position: point_location,
        map: map
    });
}

https://maps.googleapis.com/maps/api/js?key=font

</body></html>

Replace the YOUR_KEY_HERE with an API key. You can obtain one from HERE.

There’s three main pieces to this code. First off, the style in the header sets-up the page format to extend all the way. You could tinker with this, but it’s best to just maximize it.

The second part is the div with an id of map. This is our anchor point on the page, and the script is looking for this.

And lastly, the script. I’m reading the values from the Latitude and Longitude fields on the form using windows.parent to reference the record form rather than the web resource the script is running in. The rest is straight out of Google’s API documentation. Strongly recommend you browse through that for more examples, as well as the description of zoom values available (cool to know).

Wham, bam, 5 minutes jam, happy demo!

With the current and future business evolution models, globalization and ease of reach into new markets, and the increased ability of companies to reach to existing and new customers, a robust CRM system is at the core of most organizations. If it’s not, well, it should be.

Microsoft, as one of the big players in this area, recognizes the importance of a robust CRM solution, and makes great efforts to provide increased value to customers with each platform update.

Recently we’ve seen the next step in this evolution, with the launch of Dynamics 365. In this release, Microsoft positions its Dynamics platform as more than just another CRM. We’ve seen the recognition of Project Service Automation and Field Service as two of the core offerings part of the already robust package. We are also seeing an evolution and expansion into ERP, with the addition of Operations and/or Financials depending on the organization type, scale and needs.

Furthermore, licensing has been adjusted to match an a-la-carte menu, with options to pick and choose only the components needed for your business. This is an option not readily available on some other platforms, and a distinguishing value proposition.

In addition, bundle pricing provides great value, as well as promotional upgrade offerings for customers on older versions or on-premise deployments provide additional value. For public pricing consult your license provider or see the following site:

https://www.microsoft.com/en-us/dynamics365/pricing

Do not forget that additional discounts are available for certain types of organizations, as described here:

https://www.microsoft.com/en-us/Licensing/licensing-programs/licensing-for-industries.aspx

The Dynamics 365 licensing guide is available in PDF format here:

Enterprise Edition Licensing Guide

Business Edition Licensing Guide

Let’s not forget the tight integration with other existing services, including Office 365 and Azure. The sky’s the limit.

What an amazing time to be part of this evolution!

Microsoft Business Solutions MVP

Check out my course [Video]

Configuring and Extending Dynamics 365 Customer Engagement

Configuring and Extending Dynamics 365 Customer Engagement

Check out my course [Video]

Getting Started with Dynamics 365 Customer Engagement

Reviewed Book

Implementing Microsoft Dynamics 365 for Finance and Operations

Implementing Microsoft Dynamics 365 for Finance and Operations

Reviewed Book

Microsoft Dynamics 365 Extensions Cookbook

Microsoft Dynamics 365 Extensions Cookbook

Check out my Book

Microsoft Dynamics CRM 2016 Customization - Second Edition

Microsoft Dynamics CRM 2016 Customization - Second Edition

Check out my Book

Microsoft Dynamics CRM Customization Essentials

Microsoft Dynamics CRM Customization Essentials

Check out my Book

Microsoft Dynamics CRM 2011 Scripting Cookbook

Microsoft Dynamics CRM 2011 Scripting Cookbook

Reviewed Book

Microsoft Dynamics CRM 2011: Dashboards Cookbook

Microsoft Dynamics CRM 2011: Dashboards Cookbook

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 514 other followers

Follow Dynamics 365 Wizardry on WordPress.com