From the Microsoft Dynamics 365 for Customer Engagement and CRM Blogs: Data Migration, Resource Scheduling, Static Marketing Lists, Email

This week on the Dynamics 365-CRM blog roundup:

  • Created on, created by, modified on and modified by – all you need to know to maintain history during data migration in Dynamics 365

  • Universal Resource Scheduling

  • How to build a segment off of a static marketing list

  • How to set default value of "allow other Dynamics 365 user to send email on your behalf" as "true" programmatically

Created on, created by, modified on and modified by – all you need to know to maintain history during data migration in Dynamics 365

On Debajit's Dynamics CRM Blog, Debajit Dutta stated during a data migration from one system to another there always seems to be a disagreement about maintaining the history of that data, specifically when it comes to four fields: Created on, created by, modified on, and modified by.

Dutta stated that any type of data operation should go through the CRM SDK, except for a couple scenarios. During a migration, Dutta told one customer that he would be maintaining the history of the four fields. The customer, however, took exception to that statement and said it was only possible to maintain the created on field but not the rest of the fields.

And without wasting much time in argument I referred this wonderful blog written by the wonderful Aileen Gusni on the same topic way back in 2014 and it still holds good today! 

Dutta explained how you can maintain the history of all four fields here.

Universal Resource Scheduling

On the Microsoft Dynamics CRM and Unified Service Desk blog, Neil Parkhurst stated that he typically used the schedule board with D365 Field Service or Project Service Automation to schedule work orders or project tasks.

But recently I've had a couple of requirements to schedule custom entities. This is possible using Universal Resource Scheduling (URS).

In his blog post, Parkhurst explained his initial experiments with URS, to help others who might want to use URS. The focus of his post is on how to create a custom entity that can be scheduled.

You can find out how here.