In this blog we discuss the benefits of using the Microsoft Dynamics 365 Marketing Module!
In this post, we'll go a bit beyond basic CRM how-to's. We're going to cover a quick and painless resolution to the unique column names error on import of a managed solution into CRM 2011 using the OrgDbOrgSettings Tool.
Here is the error message from the Excel import log:
“Column names in each table must be unique. Column name ‘new_ordernumber' in table 'new_orderlistBase' is specified more than once.”
The cause of this issue is that the PhysicalName property for the field is not the same in the two managed solutions. The field in question was likely removed from the form and recreated with the same name but not the same case. This difference is enough to cause the import to fail.
To resolve the issue, we can make use of Microsoft’s supported OrgDbOrgSettings Tool.
To use this tool you will need:
To use the tool:
1. Download and install the OrgDbOrgSettings Tool. I recommend not burying this in your C: drive because you will need to access it through command line in a few moments.
Documentation for Microsoft’s OrgDbOrgSettingsTool can be found here.
2. Modify the tool’s configuration file to target your CRM.
a. Open your CRM and navigate to Settings > Customizations > Developer Resources and take note of your discovery service url. This value will need to match the tool’s configuration url.
b. Open the tool’s configuration file and modify the following urls to match your CRM settings
c. Modify the user name to match the system administrator’s login. You will need the password at runtime.
d. Modify the deployment type. ‘Online’ works for online as well as hosted deployments.
e. Save and close the configuration file
3. Open the command console and navigate to the OrgDbOrgSettingsTool directory where you installed the tool.
4. Enter the following command. Make sure the org name matches your CRM org name.
5. Press enter and enter the password for the user previously defined in the configuration. Press enter again and wait. After a few moments a message should appear and notify you of the result from the tool. Here is a successful update of the CRM setting:
After performing this update the managed solution was able to import without issue. The Microsoft team has verified that his setting is safe to leave toggled, so unless your organization has reason to change it back you can move on. Don’t forget to document this change in your change logs to avoid future headaches!
The OrgDbOrgSettingsTool can modify other settings as well. Typing the following command will show a list of all settings available to the tool as well as their current values within the org:
Dynamics CRM import errors like this one can be difficult to diagnose, but through careful utilization of supported tools you can resolve these issues quickly and painlessly.