Time flies and suddenly 2018 will be there, when the next Summit EMEA will take place in Dublin from 24th to the 26th of April.
During the Summit EMEA, multiple users groups will participate in the conference and offer several events including presentations, essential peer-to-peer knowledge exchanges, product insight forums, and networking opportunities.
My main focus will be on the D365UG|CRMUG user group . This week we have had our first committee meeting to discuss the agenda structure and how the sessions are going to be organised, very exciting… 🙂
If you would like to be a speaker, watch this space because there will be a call for papers very soon.
I’ll keep on posting any news.
During the last few months I have been doing some work around Dynamics 365 (CRM) and dotmailer. This article focuses on the integration between both platforms and how the new Organization Insights has proven to be very useful to understand the behavior of the Dynamics API and how it is consumed by other applications.
Looking at the Organization Insights dashboard, we noticed there was a big number of API calls happening every day between 08:00 and 09:00 in the morning.
Looking at the Most Used API chart, the “Crm Field” entity was the most utilised. This entity is part of the dotmailer solution. Basically it allows you to define what Dynamics 365 (CRM) attributes could be used by a dotmailer communication for a particular Email Account.
After several conversations with the dotmailer and Microsoft engineers, we were able to confirm those API calls were coming from this particular integration. The figures should respond to this formula:
Total number of API calls from DotMailer to Dynamics 365 to synchronise CrmMetadata = [Number of Email Accounts] * [Number of CRM Fields per Email Account] * 6
The number 6 is the number of calls per Crm Field and Email Account:
- 2 API calls are made to connect to Dynamics
- 2 API calls are made to retrieve time stamps of when the data was last sync’d
- 1 API call to get all the CRMMetadata
- 1 API call to save changes to Dynamics
Looking at the dotmailer synchronisation settings, you can specify when this process starts and how frequently runs for a particular Email Account:
The CrmMetadata type is the one defining the synchronisation related to the Crm Field entity. Based on our current configuration, the process would run “Once a day” with “No Restriction (24 hours…)”.
Our first approach was to change this setting to a less busy time, when the application was rarely used by the business users or other integrations (e.g. 02:00 am). Unfortunately, there is a bug in the dotmailer integration which reverts the setting to 08:00 am after it runs the first time.
I have raised this bug with the dotmailer team in the following post:
I would appreciate if you vote it up 😉
Few years ago, I started a project in Codeplex called “Dynamics CRM Custom Emails“, which allows you to send emails from a Microsoft Dynamics 365 / CRM process (e.g. workflow, action) based on an Email Template. Additionally, these emails can contain dynamic values for any entity (out-of-the-box or custom) and any type of attribute (e.g. lookup, option set, currency, etc).
Apart from just migrating the project from one place to the other, I have also updated it to the latest Dynamics 365 version.
There are some open issues in Codeplex that I would like to review, so I will try to do it before Codeplex closes and reflect them in the new Github project. I would like to thank you those guys who have collaborated and provide their feedback.
For those who has never seen this project, I would like to show you a quick example with some screenshots.
Let’s say we had the following Email Template:
We could then produce an email like this:
These would be done by a Dynamics workflow like this one:
This workflow will use the custom workflow activity provided by this solution. You can then specify the corresponding context parameters:
You will find more documentation in the Github project site:
This week we were trying to install Visual Studio 2017 (15.3.2) but we were getting the following error:
Package ‘Microsoft.VisualStudio.Debugger.JustInTime,version=15.0.26621.2’ failed to install
Other Visual Studio components depend on this package:
- .NET desktop development
- .NET desktop development tools
- Windows Workflow Foundation
Since the Windows Workflow Foundation module couldn’t be installed, I couldn’t open workflow libraries to develop Custom Workflow Activities for Dynamics 365.
The solution was as simple as updating the System Variable __PSLockDownPolicy value to 1:
This is related to the PowerShell Constrained Language Mode, see the following article for more details:
Basically the Visual Studio installer was trying to run a command that was not allowed based on the PowerShell Constrained Language policy.
***Thanks to my colleague Emir for his help 😉
Looking at forums, there were other suggestions like stopping the anti-virus or run the following command:
Unblock-File -path “C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.Debugger.JustInTime,version=15.0.26621.2\RegisterJustInTimeDebugger.ps1”
The following discussions were talking about the same:
This month my Microsoft MVP award has been renewed! So, definitely, a very positive month 🙂
During more than 6 years, I have enjoyed participating and collaborating with different community initiatives around Dynamics CRM and Microsoft technologies.
With Dynamics 365, there are plenty of things to do this year, so let’s carry on enjoying!
Last week I was running a new Dynamics 365 trial (v 188.8.131.529) and I wanted to use the Voice of the Customer module.
Based on the previous versions of this solution (v.8.x.x.x), I followed the same steps that I used to: Office 365 => Dynamics 365 Admin Portal => INSTANCES => Solutions, see below screenshot:
However, when I tried to install it from this Solutions section, the installation process just failed once and again.
After a quick call with Microsoft Support, they told me the new installation process at the APPLICATIONS tab, see below screenshot:
Once you are there, just click on MANAGE and follow the next few steps choosing your corresponding instance (whose version needs to be >=8.2). Then you can track again the installation process in the Solutions section:
Hope this saves you some time 😉
This article describes how to create a simple Dynamics 365 (CRM) web resource that would allow us to display images based on a dynamics URL. This URL would be stored in an entity attribute and the name of the attribute would passed as a parameter to the web resource.
Preparing the demo for EMEA Summit 2017, I needed to display some logos and organisations images (covers) in the Account entity.
Let me show you a picture and you will immediately get what I mean:
In our demo, we used the account entity to track the different NGOs / charities that would be part of the end solution. Each charity would have their own different logo and image cover that would be, later on, displayed in the PowerApp we also prepared.
Those images would be defined based on the following account attributes:
Solution: A simple web resource that would allow us to specify the attribute name with the URL as a parameter.
Below you can see the form definition, which got 2 web resources to host those previous images:
If we now look at the properties of each web resource, we would see they are using the same HTML web resource behind the scene, but the parameter we are passing is different. The parameter is actually the attribute name to feed the image:
And the other one:
If you want to see the code of that HTML web resource, have a look at my GitHub link.
Hope you find it useful 🙂
This year I’ll be presenting at the CRMUG Summit EMEA 2017 celebrated in Amsterdam. The idea started last year when I was speaking with my Microsoft AX MVP colleague Antonio @_Gilabert_ at the MVP Summit.
With Dynamics 365, CRM and AX are closer than ever, so we thought that it would be great to have a presentation together and share our experience and view with the community.
We would like to do a functional and practical session where we will show how both platforms can be integrated, in the new Dynamics 365 world, to deliver a real business scenario. Our challenge is to use the new Microsoft Flow and Common Data Service for the integration. At the moment, they are still very new and many capabilities are very limited.
Although we are still working in the demo, we are also preparing a PowerApp to improve the user experience and present how they can be useful alongside Dynamics 365 for Sales and Operations.
I would also like to say thank you to Hugo de Jesús, who is helping us a lot to prepare the presentation.
You can find more information about the schedule in this link.
We hope you enjoy the event, and of course, our session! 🙂