The following changes may require additional work as you upgrade to Microsoft Dynamics NAV 2013.

Excel Buffer Export/Import Supports Only OpenXML Spreadsheet Document Format

In Microsoft Dynamics NAV 2013, the import and export of Excel workbooks uses the OpenXML Spreadsheet document format. Other formats are not supported.

For more information, see Understanding the Open XML File Formats.

Key generation and storage for Payment Services for Microsoft Dynamics ERP

When you are performing an upgrade and try to set up Payment Services for Microsoft Dynamics ERP, you may see the following message:

This message is for C/AL programmers: A call to Microsoft.Dynamics.Nav.Encryption.RSAMachineKeyProvider.CreateKey failed with this message: Object already exists.

In Microsoft Dynamics NAV 2013, storage for encryption keys has moved from the MachineKeys folder to a file in the Microsoft Dynamics NAV installation. The key is required in order to decrypt data. If you lose the key, all encrypted data becomes unusable.

Microsoft Dynamics NAV Server can convert the MachineKeys to a file key if the key is granted full permission for the user account that is used for running the Microsoft Dynamics NAV Server. For more information, see How to: Change the Security Permissions for the MachineKeys Directory and Default permissions for the MachineKeys folders. The key is located in the following location:


Before you begin the upgrade process, you should save of copy of the old key. Store a copy of the new key after you complete the upgrade.

The recommended upgrade path varies depending on how you set up Payment Services for Microsoft Dynamics ERP in Microsoft Dynamics NAV 2009:

  • If you have set up Payment Services for Microsoft Dynamics ERP on Microsoft Dynamics NAV 2009 R2 for the RoleTailored client, make sure that the key noted earlier in this section has the required permission on Microsoft Dynamics NAV Server.
  • If you have set up Payment Services for Microsoft Dynamics ERP on Microsoft Dynamics NAV 2009 R2 for Microsoft Dynamics NAV Classic, copy the key from one of the client computers to the Microsoft Dynamics NAV Server computer and give the key file the required permissions.
    For more information, see DOL Encryption and Security Considerations for Online Services for Microsoft Dynamics ERP.

Change log support for sessions in multiple languages

Functionality in the change log has been modified in Microsoft Dynamics NAV 2013 to better support environments in multiple language environments. Among the changes, a field has been added to the Change Log Entry table. In addition, the Change Log Entries page now displays a different set of fields. There is no support for these changes in the Upgrade toolkit in order to avoid compromising any customization that you may have made to how the primary key in the change log is used. If your solution has a dependency on the Primary Key field in the Change Log Entry table, we recommend that you to consider the following when you upgrade to Microsoft Dynamics NAV 2013:

  • Before or after you upgrade, make a backup copy of the change log entries. Next, clean up the Change Log Entry table by deleting existing entries. For more information, see How to: Delete Change Log Entries. Continue with upgrade.
  • If you have a customization that uses change log functionality, you should consider updating the customization to use the new primary key field format.
  • If you are using the change log only in the context of Outlook synchronization, follow these steps.
    1. Complete a full synchronization for all clients that are using Outlook synchronization.
    2. Continue with upgrade.
    3. In the Outlook Synch. User Setup table, modify the value in the Last Synch. Time field for all records to a value that is later than the time of the upgrade.

Errors when Importing XMLports Created With Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013

Due to a change in the format of XMLports, some objects may not import.

For XMLports in TXT format, resolve this problem by removing the empty triggers before import.

For XMLports in FOB format, import into an older version of the Classic client, for example, the Microsoft Dynamics NAV 2009 R2 release without hotfixes applied, before you start the upgrade.

Specifically, the following actions fail:

  Copy Code

See Also