Ana səhifə

2011 User's Guide Copyright


Yüklə 3.76 Mb.
səhifə177/177
tarix18.07.2016
ölçüsü3.76 Mb.
1   ...   169   170   171   172   173   174   175   176   177

Delete a system chart


Can I do this task?

This task requires the System Administrator or System Customizer security role or equivalent permissions. More information about specific permissions and performing this task while offline: Chart Permissions

You cannot delete a system chart if the chart is used in a dashboard.


  1. In the Navigation Pane, click Settings.

  2. Under Customization, click Customizations.

  3. In the Customization area, click Customize the System.

  4. Under Components, expand Entities.

  5. Expand the name of the entity that has the chart that you want to delete, and then click Charts.

  6. In the list of charts, select the chart that you want to delete. Then, on the Actions toolbar, click the Delete button .

  7. In the Confirm Deletion dialog box, click OK.



Export a system chart


Can I do this task?

This task requires the System Administrator or System Customizer security role or equivalent permissions. More information about specific permissions and performing this task while offline: Chart Permissions

You cannot create complex visualizations such as multi-series charts or comparison charts by using the Microsoft Dynamics CRM Web application. To create complex charts, export the chart, edit the chart definition file, and then import it back into Microsoft Dynamics CRM.


  1. In the Navigation Pane, click Settings.

  2. Under Customization, click Customizations.

  3. In the Customization area, click Customize the System.

  4. Expand the name of the entity that has the chart that you want to export, and then click Charts.

  5. Select the chart that you want to export and on the Actions toolbar, click Actions, and then click Export Chart.

  6. To open the exported chart definition file, click Open.

- OR -

To save the file, click Save.


Import system charts


Can I do this task?

This task requires the System Administrator or System Customizer security role or equivalent permissions. More information about specific permissions and performing this task while offline: Chart Permissions

You cannot create complex visualizations such as multi-series charts or comparison charts by using the Microsoft Dynamics CRM Web application. To create complex charts, export the chart, edit the chart definition file, and then import it back into Microsoft Dynamics CRM.


  1. In the Navigation Pane, click Settings.

  2. Under Customization, click Customizations.

  3. In the Customization area, click Customize the System.

  4. Under Components, expand Entities.

  5. Expand the name of the entity to which you want to import the chart, and then click Charts.

  6. On the Actions toolbar, click Actions, and then click Import Chart.

  7. On the Import Chart dialog box, click Browse to select the definition file of the chart that you want to import, and then click OK.

Note

When you import the definition file, Microsoft Dynamics CRM checks the chart definition file for the chart ID, chart name, and the file name in the same order.

If a chart with the same ID already exists in Microsoft Dynamics CRM, you are given the option either to replace the existing chart with a file or to save the chart that you are importing with a new name. If an ID is not specified in the chart definition file, Microsoft Dynamics CRM checks to see if a chart with the same name already exists. If a chart exists with the same name, you are given the option either to replace the existing chart or to save the chart that you are importing with a new name. If both ID and name are not specified, Microsoft Dynamics CRM checks to see if there is a chart with the name same as the file name. If a chart exists with the same name, you are given the option either to replace the existing chart or to save the chart that you are importing with a new name.

If there are two or more existing charts with the same name, you can only import a chart with a new name.


Reference

Troubleshooting


Because there are so many details required to map data from a source system to Microsoft Dynamics CRM, migration typically requires several passes before you get all your data to migrate without errors. The basic troubleshooting process is to use test files, and when a record fails to migrate, review the errors, fix them, and then try again.

Preparing a Test Migration

The following topics provide troubleshooting help for specific steps of the data migration process.


  • Troubleshooting Configuring and Starting Data Migration Manager (on page 619)

  • Troubleshooting Importing a Data Map (on page 623)

  • Troubleshooting Bulk Deletion (on page 624)

  • File Errors - Wizard Page (see "File Upload Errors" on page 620)

  • Conversion Errors - Wizard Page

  • Data Upload Errors - Wizard Page (on page 620)

  • Turning on Trace (on page 621)

Copyright

Troubleshooting Configuring and Starting Data Migration Manager


This topic includes information about:

  • Requirements for running and starting Data Migration Manager

  • More information about configuration wizard pages

  • Specific error messages

Requirements for Running and Starting Data Migration Manager

  • You must have the Microsoft Dynamics CRM security role to use Data Migration Manager.

  • Only the user who installed Data Migration Manager can configure and use it.

  • Data Migration Manager can only work with one Microsoft Dynamics CRM server.

To work around this, if you need to migrate data to another instance of Microsoft Dynamics CRM, you must uninstall and reinstall Data Migration Manager.

Any data maps that you have created for migrations will be deleted when you uninstall and reinstall. If you need to use an existing data map with the other server, be sure to export the data map prior to uninstalling Data Migration Manager.



  • If you choose an existing SQL Server during setup, it must be in the same domain as the computer running Data Migration Manager.

  • You must be able to browse to Microsoft Dynamics CRM from this computer to configure and use Data Migration Manager.

  • Data Migration Manager is designed for use with Windows default themes. If you are using a different theme and text is not visible, switch to the default theme while you run Data Migration Manager.

More Information About Configuration Wizard Pages

Specify SQL Server Page

If you are using a computer running Microsoft SQL Server rather than Microsoft SQL Server Express, by default the configuration wizard will attempt to connect to the default instance on your server. If you prefer to use a different instance, specify the server name in the format SQL_server\instance.

Connect to Microsoft Dynamics CRM Page

Type the same address that you type in the box in Microsoft Internet Explorer when you want to open Microsoft Dynamics CRM.

Specific Error Messages

The request could not be completed because the server is busy. Try again later.

Microsoft Dynamics CRM cannot complete your request because the servers are busy serving requests from users in your organization. If this problem continues, contact Microsoft Dynamics CRM support.

Copyright


File Upload Errors


A file upload error can occur if there is an error in any individual ,csv, .xml or .txt file, or if there is an error in one of the files in the .zip file. In either case, Import Data wizard does not allow you to continue until the erroneous file is fixed or is removed from the .zip file being imported.

Common Errors and How to Fix Them

Related Topics


Troubleshooting 619



Data Upload Errors - Wizard Page


The Data Upload Errors page is shown only if there are errors uploading the data to the Microsoft Dynamics CRM server. This page displays the first 50 errors found. To view additional errors and additional details for each error, click Export.

For a quick overview of which records failed and why, click Details.



Choice

Action

Implications

If you want to continue with your import, even though you have some errors:

Click Export Errors, and export errors from each entity with failures to a new file so that you can return later to clean up the data, and then click Next.

Only records without errors will actually import.

This option is useful if you want to save any mappings you have done with the wizard. Since mappings aren't saved until import is completed, it makes sense to complete the import, and then delete all data that was imported. Then you can clean up any errors and repeat the import.



If you're using an existing data map and want to cancel this import and fix errors:

Click Export Errors, and export errors from each record type with failures to a new file so that you can return later to clean up the data, and then click Close.

Any mappings you have done will be lost.

Common Errors and How to Fix Them

Related Topics


Troubleshooting 619



Turning on Trace


You can turn on tracing for detailed migration logging. Trace files for large migrations are large, so after you are done troubleshooting, either turn off trace, or remove any unneeded trace log files. After you have done one of these, close or stop Data Migration Manager, Data Migration Manager Hoster, and Async service. Restart these before the next migration.

By default, data migration logging is turned off. Logging functionality is maintained in the following registry entries in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Data Migration Wizard key.



Key

Default Value

Comments

TraceEnabled

dword:00000000

00000001 turns logging on, 00000000 turns logging off.

TraceDirectory

empty

Path of local directory where log files are created. By default, for Microsoft® Windows Server® 2003 and Windows XP the log files are saved to: C:\Documents and Settings\logon_name\Application Data\Microsoft\MSCRM\Traces

For Windows Vista® the log files are saved to: C:\Users\logon_name\Application Data\Microsoft\MSCRM\Traces



TraceCategories

*:Verbose




TraceSchedule

Daily




TraceRefresh

dword:00000001




To turn on trace on the Microsoft Dynamics CRM server, in the registry, in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM, change the value of TraceEnabled to 1, and the value of TraceRefresh to to a number between 1 and 99. This value is the number of minutes that will pass before the trace settings are reloaded from the registry.

Copyright


Related Topics


Troubleshooting 619



Common Error Messages


Troubleshooting information

Errors are found at several stages of the migration process:



  • Validating Files.

File Errors - Wizard Page (see "File Upload Errors" on page 620)

  • Converting Data.

Conversion Errors - Wizard Page

  • Uploading Data.

Data Upload Errors - Wizard Page (on page 620)

Note

To view the error details later, click Export Errors, and save the data to your computer. There is no way to retrieve error information later if you don't use Export Errors.

There are several common reasons a record might not migrate:


  • A record that does not have an owner who is a valid Microsoft Dynamics CRM user will not migrate.

  • There is missing or incorrect data in an attribute used to create a relationship to another record type.

  • If an incident record references a contract record of a contract with a Contract End Date or Billing End Date attribute value less than the current date, the incident record will not be migrated. To work around this, you could change the value in Contract End Date and Billing End Date during the migration, and after data migration is complete, change the values in Microsoft Dynamics CRM.

Copyright

Related Topics


Troubleshooting 619



Conversion Errors - Wizard Page


The Conversion Errors page is shown only when errors are found converting the data to Microsoft Dynamics CRM format. This page displays the first 50 errors found. To view additional errors and additional details for each error, click Export.

For a quick overview of which records failed and why, click Details.



Choice

Action

Implications

If you want to continue with your import, even though you have some errors:

Click Export Errors, and export errors from each entity with failures to a new file so that you can return later to clean up the data, and then click Next.

Only records without errors will actually import.

This option is useful if you want to save any mappings you have done with the wizard. Since mappings aren't saved until import is completed, it makes sense to complete the import, and then delete all data that was imported. Then you can clean up any errors and repeat the import.



If you're using an existing data map, and want to cancel this import and fix errors:

Click Export Errors, and export errors from each record type with failures to a new file so that you can return later to clean up the data, and then click Close.

Any mappings you have done will be lost.

Common Errors and How to Fix Them

Related Topics


Troubleshooting 619



Troubleshooting Importing a Data Map


Start from a simple data map that only maps the source files to target entities, and then import it. If it works, add attribute mappings a few at a time. Import the data map frequently as you go, so that it is easy to isolate any problems found in the section you just added. Remember to change the name of your data map each time you import it, or delete previous attempts before importing.

When the Import Data Wizard tries to import a data map, it checks first to make sure the schema is valid. All schema errors result in the following error message:

The following mistakes in your file will generate this error message:


  • Unclosed XML elements.

To troubleshoot, open your data map in an XML editor. This will help you see any elements that are not closed properly.

  • Element names with errors.

Compare each element name to the name in the data map schema. Element names are case-sensitive.

Data Map Schema Reference



  • Missing required elements.

Compare each element to the data map schema. Make sure you include all child elements for each element.

Data Map Schema Reference



Specific Error Messages

After the schema is validated, specific messages are displayed.

At the time of import, if a map with same name exists, the Import Data Wizard prompts you to save the map with a different name.

If you have a value that is too long in a parameter such as SourceName, Name, or SourceEntityName, you will receive this error. The log file will show a "Generic SQL error." To work around this problem, shorten parameter names in the data map to 160 or fewer characters.

Double-check each target attribute and make sure you are using the name of the attribute, rather than the display name.

The file specifies a list value that does not exist in Microsoft Dynamics CRM.

For mappings in the PicklistMap element, list values must be integers, not the strings used in Microsoft Dynamics CRM. The list values must be valid integers: do not enter commas in numbers.

To look up the integer for each list value displayed in Microsoft Dynamics CRM:



  1. Go to the Customization area of Microsoft Dynamics CRM.

  2. Double-click Customize the System, double-click the record type, and then click Attributes.

  3. Double-click the drop-down list attribute.

  4. For each list value you are mapping to, select the list value and then click Edit.

The Value listed in the Modify List Value dialog box is the value you should put in the TargetValue element.

Troubleshooting Bulk Deletion


Specific Error Messages

Copyright



1   ...   169   170   171   172   173   174   175   176   177


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət