Creating scheduled workflows has always been a challenge in Dynamics
CRM 365. The community and ISVs have offered several original options, but there is not yet an official out-of-the-box option. This article brings another alternative to the table using Microsoft Flows.
A scheduled workflow is the one that runs at a certain arranged time and it may recur to run again after a period of time. If you want to understand more about this challenge and how our CRM community has resolved it so far, have a look at the following articles:
Microsoft Flow offers the option to create Recurrence jobs. This can be used to schedule and trigger actions in Dynamics 365, like retrieve, create or update records (see available actions). So, using this functionality you already have a good alternative to create your own scheduled workflows without development effort. You can see some examples in the following article as well as in these Dynamics 365 Flow templates.
The other alternative would be a mix solution where a recurrence Microsoft flow creates a custom Dynamics 365 “Scheduled Job” record and this triggers the corresponding Dynamics 365 workflow. The “Scheduled Job” entity would have attributes like “Process Name”, “Run as” (e.g. system user name), “Query scope” (e.g. FetchXML or view name), …, to specify what and how to run the workflow. This option would require additional development, either a plugin or a custom workflow activity to call on demand the given process, but it would also allow you to reuse the logic and capabilities you already have within Dynamics 365.
Hope you find this article useful. Looking forward to hearing your feedback.
The new Dynamics home page gives you an easy start point to join the user experience of our CRM and ERP users:
There we can find the different functional applications, from Sales to Operations:
Everything has got the same look & feel:
A key part of Dynamics 365 is the aim of joining different apps in a single ecosystem, there is where we find a seamless integration with AppSource:
We can also feel the “Mobile First, Cloud First” strategy on the mobile apps coming with Dynamics 365:
The integration with Outlook carries on improving, providing more contextual information on our emails:
The Intelligence is another fundamental part of Dynamics 365, which covers several areas:
The Relationship Insights is definitely one of the most AI interesting points, where we will be able to get a better view of our customers. For instance, Exchange emails from Office 365 would be joined with the Dynamics 365 emails and we would be able to understand how our relationships are doing:
We will be able to see who has opened our emails and interact with them in a simple view:
As part of the analytics improvements, we have also got the just announced Customer Insights, which brings the ability to create great single customer views:
Have you seen that message before on your Microsoft Dynamics CRM organisation?
You may have if you have tried to activate more than 10 business processes at the same time for the same entity.
This is a limitation by design which is well-known and described on the Microsoft technical documentation, have a look at the following article.
This limitation can be changed using the organisation property Organization.MaximumActiveBusinessProcessFlowsAllowedPerEntity. The easiest way to to change this attribute is using the following tool: Dynamics CRM Organization Settings Editor (OrgDBOrgSettings)
And now, you may be thinking: “why on earth would you do that??”
If your CRM deployment is heavily used, some core entities (e.g. Case, Opportunity) may be used intensively on different processes across an organisation.
Note: the current CRM version I’m using is: (220.127.116.119) (DB 18.104.22.1689)
Microsoft Dynamics CRM 2016 Update 1 brings Email Signatures as an out of the box functionality. They can be used on Users or Queues (based on Teams).
Create a new email and you will see a new icon on the email designer to insert signatures:
To create more signatures, go to Personal Settings or, as an admin, Administration => Templates section.
Administration => Templates:
Notice Email Signatures is a new entity and it is part of the security roles. So, for instance, if the Customer Service Team requires to use Email Signatures, they should have access to the Email Signature Entity. See below an example security role:
Note: My current on-line build version is : 22.214.171.1242 – DB 126.96.36.1999
You can find more information in the following Microsoft CRM article:
Probably many customers and partners have already asked you this question: where is our data? You can give them more details and a quick picture using the next Microsoft site:
You can already try the new Voice of the Customer (VoC) functionality in Dynamics CRM Online (only Online for now). Initially it was only available in US deployments (https://orgname.crm.dynamics.com) but this week has been released in EMEA datacenters as well (https://orgname.crm4.dynamics.com).
VoC allows you to design and publish surveys using Dynamics CRM. You can then share these surveys with your customers and gather their feedback efficiently within CRM.
The current CRM version I’m looking at is 188.8.131.52:
And the solution package is 8.1.344.1:
You can find more documentation in the next link:
We noticed incoming emails stopped getting in and we saw a 401 Authentication Error in the CRM Email Router server logs. Nothing has changed in the system account used for this Forwarded Mailbox and the password is still valid.
Deployment: CRM Online + CRM Email Router + Exchange Online
CRM Email Router Configuration: Forward mailbox is used for incoming emails.
After a few tests using the next utilities (very useful!):
We noticed that system account cannot access its own mailbox. Very weird, like if you don’t have access to your own home suddenly.
Finally, we just had to force an update on this system account to make it work again using the next PowerShell command:
set-msoluser -blockcredential $true -userprincipalname [userAccountName]
set-msoluser -blockcredential $false -userprincipalname [userAccountName]
It looks like the system account was desynchronised between our internal AD and Microsoft Online AD, causing this issue.
The xRMVirtual session on Tuesday September 1 had to be cancelled last minute because of technical and audio difficulties and we couldn’t share our experience on previous events such as Convergence, CRMUG and eXtreme CRM.
However, you can still find some of the tricks I was about to share in the next link How to get the most out of Convergence in Barcelona and you can find the deck here:
If you need to give the ability for a Dynamics CRM user to Import Data, you can just create a security role with access to the next entities:
- Data Import
- Data Map
- Import Source File
Note: I have notice you will need, at least, Delete right – user level on the Data Import entity (it doesn’t make sense if you just want to allow the import, but this is what I found; it could be a bug). Otherwise the IMPORT DATA button won’t appear. See the same in the next screenshot:
See below an screenshot with the configuration described above.
Have you seen the latest CRM Developer Center? It is a great place for developers getting started with Dynamics CRM. The search has been customised and improved to find content only related to CRM, see below an example.
Also there are many resources for those interested on Mobile development, have a look at Mobile SDK.
Notice how “entity” brings results only relevant about Dynamics CRM (e.g. rather than Entity Framework)