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 🙂
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.
- Export Invoice Product.xml
Add Invoice Line data in the xml with below values.
- Set “Select Product” column value to “Write In”.
- Add a new column “Invoice ID” and set the value to Invoice ID field of respective Invoice.
- 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!
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!
View the original article here.
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:
Product names, versions, releases, and code names
The following table shows CRM Online product names with their associated version numbers and code names.
The following table shows CRM (on-premises) product names with their associated version numbers and code names.
We hope this blog demystifies naming conventions for CRM going forward!