Top 10 Data Migration Traps

While planing for the data migration item for one of my project, found this great article by Bruce Buxton which explains top 10 data migration traps. It was good to know as prevention is always better than cure 🙂

http://www.xrmconsultancy.com/2013/10/top-10-data-migration-traps/

Advertisements

DID YOU KNOW? You can update owner and status with a single Update request in CRM 2015 with Update 1

Before CRM 2015 Update 1 release, specialized messages were required to update certain entity attribute values. These were AssignRequest to change owner of a record, SetStateRequest to change status of a record, SetParentSystemUserRequest, etc. In this release, UpdateRequest can now be used to set these attributes.

Thus with Update 1 release following specialized message will be deprecated.

  1. AssignRequest
  2. SetStateRequest
  3. SetParentSystemUserRequest
  4. SetParentTeamRequest
  5. SetParentBusinessUnitRequest
  6. SetBusinessUnitRequest
  7. SetBusinessEquipmentRequest
  8. SetBusinessSystemUserRequest

These specialized messages will continue to work with the 2011 endpoint. However, the recommendation is to use the UpdateRequest or Update method when possible to set these attributes. The Update message simplifies the SDK API and makes it easier to code standard data integration tools used with Dynamics CRM. In addition, it is easier to code and register a plug-in to execute for a single Update message instead of multiple specialized messages. The AttributeMetadata.IsValidForUpdate property for the above listed attributes has been changed to true in this release to enable this capability.

For plug-ins, when update requests are processed that include both owner fields plus other standard fields for business owned entities, plug-ins registered for the Update message in pipeline stage 20 and/or stage 40 execute once for all non-owner fields, and then once for the owner fields.

For workflows, when update requests are processed that include both owner fields plus other standard fields, workflows registered for the Update message execute once for all non-owner fields, and then once for the owner fields. Workflows registered for the Assign message by users continue to be triggered by updates to owner fields. When update requests are processed that include both state/status fields plus other standard fields, workflows registered for the Update message execute once for all non-state/status fields, and then once for the state/status fields. Workflows registered for the Change Status step continue to be triggered by updates to state/status fields.

Invoice and Invoice Line data import in Dynamics CRM

Recently I found that many people have issues importing old Invoices either from legacy system into Dynamics CRM. This is manly in scenarios where Products are not maintained in CRM. In this case import of Invoice Line throws error as the data import template for Invoice line do not have relationship with Invoice. Below are the steps that can be followed to fix the issue.

Invoice lines is a relationship between invoice and products. Thus if you need to add invoice lines, you need to add products using the “Product.xml” template file. But in our case as we don’t maintain Products in CRM, while importing Invoice lines, add invoice number of imported invoices in CRM in a separate column and select the Product as write-in in import file.

For importing Invoice lines, you need to download the “Invoice Product.xml” template file.

All the mentioned templates can be downloaded from “templates for Data Import” in Data Management section in Settings.

  1. Export Invoice Product.xml
  2. Add Invoice Line data in the xml with below values.
    1. Set “Select Product” column value to “Write In”.
    2. Add a new column “Invoice ID” and set the value to Invoice ID field of respective Invoice.
  3. Save and import the file.

4. Import the above xml file.

5. During Import wizard, on Review Mapping Summary Page, click on Edit.

6. In Map Fields, for Invoice ID row click on the look up reference and select “Invoice ID” field and click Ok.

7. Click Next and progress with the import process.

Probably issue with many users follow is at step 7. Invoice ID field is by default map to Invoice name and Invoice GUID field.

Hope this helps!

Microsoft Dynamics CRM Online 2015 Update 1 (7.1.0) Product Documentation is Available!

***[Referencing to Microsoft Dynamics CRM Team Blog]

Check out the new documentation for Microsoft Dynamics CRM Online 2015 Update 1 (7.1.0).

What’s new in this update

Everything you need to learn about – and prepare for – the new features is on these pages:

Information for IT pros, administrators, implementers, and customizers

For CRM administrators and customizers, this update includes:

Information for developers

For developers this update includes:

All new code samples for this update are available on MSDN Developer code samples:

We are in the process of migrating our codes samples out of the downloadable SDK package and make them available online so that they can be discovered more easily.

Finally, please visit the new responsive Microsoft Dynamics CRM Developer center at http://crmdevelopercenter.com/. Be sure to try the new search, which is filtered to return only MSDN library content from the Microsoft CRM SDK

Information for end-users

www.CRMhelpandtraining.com

For end-users, this update includes new topics and updates to the Training & Adoption Kit.

  • New Mobile User’s Guide –  Find out how to install the new phone app, work offline, and manage your leads through the sales process

  • Updated Training & Adoption Kit! The popular, easy-to-customize PowerPoint source files are right here – all ready for you to use for your own training, presentations, and webinars.

Enjoy the new features!

We hope this new content gets you going on all the new features of this online update.

As always, you can find your way to all documentation by visiting the central portal for all the CRM content sites: the CRM Help Center.

Let us know in the blog comments what you think of the new content – of if there’s something else you need. Give feedback to the Documentation Team at any time.

http://blogs.msdn.com/b/crm/archive/2015/05/01/product-documentation-for-microsoft-dynamics-crm-online-2015-update-1-7-1-0-is-available.aspx

 

White Paper: Microsoft Dynamics CRM Online patterns & principles for solution builders

In the world of Microsoft Dynamics CRM, the shift to the cloud is well underway. Microsoft Dynamics CRM Online is growing by leaps and bounds, including sales to massive customers with huge user counts.

You may believe that the difference between building a solution for an on-premises and an online deployment consists of a few technical details, like the requirement to use FetchXML for reports in online deployments, or the requirement to sandbox plugins. But in reality, the differences are much deeper than that. To truly build a high-quality solution for Microsoft Dynamics CRM Online, you need to do more than simply build the on-premises way and then check a few extra boxes.

The Microsoft Dynamics CRM Online patterns & principles for solution builders whitepaper describes the new mindset required to successfully design solutions for online deployment. Check it out at the following location!

Download: Patterns and Principles for CRM Online Solution Builders.pdf

View the original article here.

New naming conventions for Microsoft Dynamics CRM updates

From Microsoft Dynamics CRM End User Team:

We’re changing the way we name product updates to make things simpler and to unify our approach for Microsoft Dynamics CRM Online and Microsoft Dynamics CRM (on-premises).

Finding and understanding version numbers

To understand the new naming conventions, let’s first take a look at version numbers in CRM.

To find your version number, in the upper-right corner of the web client, choose the Settings icon, and then choose About. You’ll see the following screen:

The first three numbers of the 7-digit version number tell you most everything you need to know about which version you’re working with, whether you’re using CRM Online or CRM (on-premises):

So what’s changed?

Three things have changed in regard to naming conventions:

  • CRM Online. Product names for minor releases of CRM Online will now include the year as part of the name. For example, the spring release of CRM Online for 2015 is CRM Online 2015 Update 1. If there’s an incremental update that applies to the minor release, it will be appended to the name. For example, the first incremental update to the spring 2015 release would be called CRM Online 2015 Update 1.1.
  • CRM (on-premises). In the past, incremental updates for the on-premises version of Microsoft Dynamics CRM were called “Update Rollups”. In the future, Update Rollups will just be called “Updates” and will be associated with the third digit of the version number. For example, the first incremental update for version 7.0 is CRM 2015 Update 0.1. The complete version number in this case is 7.0.1.xxxx, which indicates that the update applies to the major 7.0 release, not a spring release. There will not be a spring 2015 release for the on-premises version, but if there’s a minor fall release, it would be called CRM 2015 Update 2, and any subsequent incremental updates would be appended to that number.
  • CRM for phones. The new phone app introduced with CRM Online 2015 Update 1 will be called CRM for phones. The CRM phone app for CRM 2013 and CRM 2015 will now be called CRM for phones express.

Product names, versions, releases, and code names

The following table shows CRM Online product names with their associated version numbers and code names.

Product Name

Version
Descriptor

Version
Number

Release or
Update

Code
Name

Microsoft Dynamics CRM Online Fall ’13 6.0.0 Major release “Orion”
Fall ’13 6.0.1 Incremental update None
Fall ’13 6.0.2 Incremental update None
Spring ’14 6.1.0 Minor release “Leo”
2015 Update 7.0.0 Major release “Vega”
2015 Update 1 7.1.0 Minor release “Carina”

The following table shows CRM (on-premises) product names with their associated version numbers and code names.

Product Name

Version
Descriptor

Version
Number

Release or
Update

Code
Name

Microsoft Dynamics CRM 2013 6.0.0 Major release “Orion”
2013 UR1 6.0.1 Incremental update None
2013 UR2 6.0.2 Incremental update None
2013 SP1 6.1.0 Minor release “Leo”
2015 7.0.0 Major release “Vega”
2015 Update 0.1 7.0.1 Incremental update None

We hope this blog demystifies naming conventions for CRM going forward!