Use the Microsoft Dynamics NAV 2013 R2 Setup program to install Microsoft Dynamics NAV 2013 R2 on a computer where no Microsoft Dynamics NAV software is already installed or where all previous Microsoft Dynamics NAV software has been uninstalled. For more information, see Deployment in the MSDN library for Microsoft Dynamics NAV 2013 R2.

The following issues may affect your experience using Microsoft Dynamics NAV 2013 R2.

1. Installation: Repair option in Microsoft Dynamics NAV Setup removes all web server instances except the default instance
   
   
2. Upgrade: Some reports fail with an exception after the upgrade to SQL Server Report Viewer 2012
   
   
3. Excel integration: Users cannot add new sheets to the Excel workbook after sending data to Excel
   
   
4. Excel integration: Limitations for installing the Microsoft Office Excel add-in
   
   
5. Excel integration: The Microsoft Office Excel add-in does not uninstall when disabled
   
   
6. Excel integration: The Microsoft Excel add-in prompts the user to log in each time
   
   
7. Excel integration: Users cannot embed Excel worksheets in Word when the Microsoft Excel add-in is installed
   
   
8. Excel integration: Unhandled exception when the user sends data to Excel in an Office 365 configuration
   
   
9. Outlook integration: Error when viewing mail based on interaction log entries
   
   
10. Office integration: Not all scenarios are supported when sending Office documents from the Microsoft Dynamics NAV Web client
    
    
11. Office integration: Not all scenarios are supported when sending Office documents to Office 365
    
    
12. Office integration: Microsoft Dynamics NAV may close unexpectedly when a user tries to access Office products
    
    
13. SharePoint: Integration with SharePoint optimized for SharePoint Online
    
    
14. SharePoint: Browser compatibility considerations when you embed the Microsoft Dynamics NAV Web client in apps for SharePoint
    
    
15. Microsoft Dynamics NAV Web client: Pages containing more than one control add-in
    
    
16. Microsoft Dynamics NAV Web client: Browser crashes while modal dialog is open preventing the user to login again
    
    
17. RapidStart Services: Configuration worksheet export to Excel does not work on the Microsoft Dynamics NAV Web client
    
    
18. RapidStart Services: Binary type not supported
    
    
19. RapidStart Services: Error when exporting data to Excel
    
    
20. RapidStart Services: New companies initialize with the profile for RapidStart Services
    
    
21. RapidStart Services: Cannot import more than 65536 rows from Microsoft Excel
    
    
22. Deployment: Microsoft Dynamics NAV Server cannot start on a localized operating system
    
    
23. Development: "The specified service can’t be reached” error when compiling table objects in Microsoft Dynamics NAV Development Environment
    
    
24. Development: Adding a primary key when the record size is close to the limit prevents the table from being compiled
    
    
25. Development: Changes to linked tables are not visible in Microsoft Dynamics NAV because data is cached
    
    
26. Development: Posting in background fails on confirmation dialog boxes
    
    
27. Development: It is not possible to order actions in system groups in the Home tab
    
    
28. Development: Removing a promoted action in the Home tab and re-adding it in the same session will cause duplication of the action
    
    
29. Development: Changes in Help - Walkthrough: Creating and Using a Client Control Add-in and Manifest Overview are updated on MSDN
    
    
30. Development: TRANSFERFIELDS function does not copy uninitialized fields
    
    
31. Development: GETURL function does not return correct URLs for company names that contain special characters
    
    
32. Development: Paging does not work for OData URLs where company name is a parameter
    
    
33. Development: Error starting debugger when Microsoft Dynamics NAV 2013 R2 and Microsoft Dynamics NAV 2013 are installed on the same computer
    
    
34. Administration: SQL replication in Microsoft Dynamics NAV 2013 R2 does not work as it did in Microsoft Dynamics NAV 2009
    
    
35. Administration: Changes to Microsoft Dynamics NAV 2013 R2 Administration Shell cmldets
    
    
36. Administration: Export-NAVApplication cmdlet does work on databases that have more than one filegroup
    
    
37. Administration: Microsoft Dynamics NAV 2013 Server Administration tool does not work in a side-by-side installation with Microsoft Dynamics NAV 2013 R2
    
    
38. Help: Translated help content for user setup and configuration not fully updated
    
    
39. Help: Translated help content for Cash Management not fully updated
    
    
40. Translation: Missing the correct caption for some promoted actions on configured profiles
    
    
41. Italy: SEPA Direct Debit mandate ID is not retrieved when generating collection entries
    
    
42. Microsoft Dynamics C5 2014: On first sign-on, the welcome video may cause a busy state and script error
    
    
43. Microsoft Dynamics C5 2014: Videos may be blocked on https protocol in Internet Explorer by “Only Secure Content Is Displayed” message
    
    
44. Microsoft Dynamics C5 2014: Error in Bank Export/Import Setup table when applying the small-business RapidStart package
    
    
45. Microsoft Dynamics C5 2014: Online Map setup not included in the small-business RapidStart package
    
    
46. Microsoft Dynamics C5 2014: CASH Payment Method setup not complete in the small-business RapidStart package
    
    
47. Microsoft Dynamics C5 2014: Cash Flow setup is not complete in the small-business RapidStart package
    
    
48. Deleted or Promoted Actions
    
    

Description: You can use Microsoft Dynamics NAV Setup to install the Microsoft Dynamics NAV Web Server components. Setup installs a default web server instance on IIS for the Microsoft Dynamics NAV Web client. After the initial installation, you can add and configure additional web server instances by using the cmdlets that are provided in the Microsoft Dynamics NAV Administration Shell. Afterward, if you run the Repair option in Microsoft Dynamics NAV Setup, then Setup re-creates the initial default environment, which includes a default web server instance, and removes any web server instances that have been added.

Workaround: To ensure that you can easily re-create the web server instances after you run the Repair option, we recommend that you create Windows PowerShell scripts that add and configure the web server instances.

Description: After the upgrade to SQL Server Report Viewer 2012 you may find that some reports fail in print layout and saving as PDF with the following exception:

An error occurred during local report processing.

(Processing): ScalableList: Index 5 outside the allowed range(0::4)

Workaround: We are aware of this issue and are in process of fixing this bug with the SQL Server team.

Description: If you send data to Microsoft Excel from Microsoft Dynamics NAV, such as the customer list, and you then want to add a worksheet to the workbook, you see the following error: That command cannot be used on multiple selections..

Workaround: Save the workbook and close Microsoft Excel. When you open the workbook again, you can insert new sheets.

Description: In Microsoft Dynamics NAV 2013 R2, you must choose to install the Microsoft Office Excel add-in because it is not installed automatically when you install the Microsoft Dynamics NAV Windows client. The installer for the Microsoft Office Excel add-in has the following limitations:

• When you install the Microsoft Dynamics NAV Windows client, choose to also add the Microsoft Office Excel add-in.
  
  
• If you install the Microsoft Dynamics NAV Windows client using the ClickOnce deployment technology, the Microsoft Office Excel add-in cannot be part of the installation configuration.
  
  
• The Microsoft Office Excel add-in will not work in a side-by-side installation with previous versions of Microsoft Dynamics NAV. You must uninstall the Microsoft Office Excel add-in from Microsoft Dynamics NAV 2013 before you install the Microsoft Office Excel add-in from Microsoft Dynamics NAV 2013 R2.
  
  

Description: If you disable the Microsoft Excel add-in from Excel, and you then uninstall the component, the uninstallation is not complete. As a result, you may not be able to send data to Excel from Microsoft Dynamics NAV.

Workaround: In the registry, under HKEY_CURRENT_USER/Software/Microsoft/Office/Excel/addins, delete the following registry setting: Microsoft.Dynamics.NAV.ExcelAddIn.

Description: In deployments with the credential type set to UserName or NAVUsernamePassword, the user is asked to log in to Microsoft Dynamics NAV each time they send data to Excel and they have the Microsoft Excel add-in installed.

Workaround: For users who have the Microsoft Excel add-in, use the Windows credential type.

Description: If the user has installed the Microsoft Excel add-in, then they cannot embed Microsoft Excel worksheets in Microsoft Word documents. Microsoft Word displays error messages that prevent the user from successfully saving or closing the Word document.

Description: You can configure Microsoft Dynamics NAV to store documents on SharePoint Online using an Office 365 account. If you have configured your online document storage to use the users' personal sites, users may encounter errors until they have logged into their personal site at least once through the Office 365 portal.

Workaround: The user must log in to their My Personal Site at least once through the Office 365 portal.

Description: An error may appear when you want to view a logged email in the Interaction Log Entries window. The error occurs when Microsoft Dynamics NAV attempts to open the corresponding email in Microsoft Outlook.

Workaround: Make sure that you are not running either Microsoft Dynamics NAV or Outlook as administrator. Otherwise, close all instances of Outlook, and then, in the Interaction Log Entries window, choose Show again.

Description: With Microsoft Dynamics NAV 2013 R2, you can save and open Office documents from the Microsoft Dynamics NAV Web client. However, not all scenarios for interaction with Microsoft Office products are enabled for the Microsoft Dynamics NAV Web client. The following table describes the scenarios that are supported for the Microsoft Dynamics NAV Web client and the Microsoft Dynamics NAV Windows client.

Description: With Microsoft Dynamics NAV 2013 R2, you can save and open documents based on your Office 365 account. However, not all scenarios for interaction with Microsoft Office products are enabled for Office 365 in Microsoft Dynamics NAV. When you configure Microsoft Dynamics NAV for use with Office 365, certain scenarios still require installed versions of Office to work. The following table describes which version of Office is required for different activities in Microsoft Dynamics NAV.

Description: Users can access office products in different ways, including Office on Demand, which streams a full-featured version of Office to the user's computer. In those scenarios where Office is not installed on the user's computer when the user sends data to Excel, for example, Microsoft Dynamics NAV may close unexpectedly.

Workaround: Users who expect to use Office products with Microsoft Dynamics NAV must install the relevant office products, for example by downloading Office from an Office 365 subscription.

Description: You can configure Microsoft Dynamics NAV to store documents on SharePoint Online using an Office 365 account. The scenario for saving documents to SharePoint on-premises has not been prioritized in the current version of Microsoft Dynamics NAV.

Workaround: If you want to use SharePoint, configure an Office 365 account and use SharePoint Online.

Description: If you create an app for SharePoint where you embed pages from the Microsoft Dynamics NAV Web client, users may see an error such as "Internet Explorer has modified this page to help prevent cross-site scripting.". This occurs if the URL that you have specified for accessing the Microsoft Dynamics NAV Web client from SharePoint includes the {StandardTokens} parameter.

Workaround: When you design your app for SharePoint, when you specify URLs for opening pages in the Microsoft Dynamics NAV Web client, specify the SPHostUrl={HostUrl} parameter instead of {StandardTokens} in the query string.

For the latest version of the best practices for creating apps for SharePoint that access the Microsoft Dynamics NAV Web client, see Best Practices for Creating Apps for SharePoint in the MSDN Library.

Description: Pages that contain more than one control add-in, can potentially hang and appear frozen when opened. This is likely to occur when control add-ins do callbacks.

Workaround: Refresh the browser using F5.

Description: If the browser has crashed while a modal dialog is open, the user might get the following error message when trying to log on again:

There is a dialog box open in another Microsoft Dynamics NAV browser window. You must close that dialog box before other operations can continue.

Workaround: To be able to log on again, the user will have to wait for the client session to timeout.

Description: When a user tries to export a table from the configuration worksheet into Excel using the Microsoft Dynamics NAV Web client, an error message appears stating that .NET interoperability components are not supported by the Microsoft Dynamics NAV Web client.

Workaround: Use the Microsoft Dynamics NAV Windows client to import and export with Excel.

Description: If you add a table to the Configuration Worksheet that contains a field of the Binary data type, you may receive the following error message: "The type Binary is not supported." You may be unable to use navigation pane links or a ribbon action to reopen the worksheet. Other links, including those to tables listed in the worksheet, also become inoperable.

Workaround: Before adding a table to the Configuration Worksheet, check to see whether it contains fields of the Binary type, and modify the table before you continue with the addition.

Description: When exporting tables from the Configuration Worksheet or Configuration Package to Excel, you may receive the following error message:

“Old format or invalid type library."

If the client computer runs an English version of Excel and the locale for the current user is configured for a language other than English, Excel will try to locate the language pack for the configured language. If the language pack is not found, the error is returned.

Workaround: This is a known Excel issue. For more information about resolving this issue, see http://support.microsoft.com/kb/320369.

Description: When a new company is created using the Microsoft Dynamics NAV 2013 R2 Administration Shell, the profile for RapidStart Services is set as the default. This makes it easier to start configuring the new company. The default RoleCenter field is a cross-company setting. Accordingly, all users where you have not specified a profile in the User Personalization Card will be assigned the profile that is specified as the default.

Workaround: Assign the relevant profiles to users if you do not want them to be assigned the default RoleCenter. Also, a user who sees the RoleCenter for RapidStart Services can choose the Complete Setup action on the Home tab, and then choose the profile that they want to use as the default the next time they start the client.

Description: Due to a limitation in Microsoft Excel, RapidStart Services cannot import more than 65536 rows from Excel into Microsoft Dynamics NAV. If the number of rows in Excel is higher, not all rows are imported, and no error or warning is shown.

Workaround: Make sure that each Excel document does not contain more than 65536 rows.

Description: When you install Microsoft Dynamics NAV Server on a computer that has a localized version of Windows, the Microsoft Dynamics NAV Server instance may not start if the instance is running with the credentials of the built-in NETWORK SERVICE account, and the computer is not joined to a domain. The problem does not occur if Windows has been localized using a Windows Multilingual User Interface (MUI) pack.

Workaround: You can either join the computer to a domain or use a different account to run the Microsoft Dynamics NAV Server instance. The account must have the "Log on as a Service" property.

Description: When you try to compile a table object that you have modified in the Microsoft Dynamics NAV Development Environment, you might receive the following error: The specified [service instance] can’t be reached, where [service instance] is the name of the Microsoft Dynamics NAV Server instance.

The error occurs because the development environment is attempting to validate the metadata changes in the table by using Microsoft Dynamics NAV Server, but the development environment does not have sufficient privileges to connect to Microsoft Dynamics NAV Server and execute the validation.

Workaround: The development environment and Microsoft Dynamics NAV Server must be running on the same computer. When you start the development environment, you must run it as an administrator. To run the development environment as an administrator, right-click the Microsoft Dynamics NAV Development Environment icon, and then choose Run as Administrator.

Description: The maximum record size in Microsoft Dynamics NAV 2013 R2 is 8000 bytes. Adding a primary key to a table when the record size limit is close to this limit will prevent the table from compiling.

Description: Microsoft Dynamics NAV caches data from linked tables. But if the data in a linked table is modified by an external product, the changes do not appear in the Microsoft Dynamics NAV Windows client or Microsoft Dynamics NAV Web client because of the cache. If the changes are made in Microsoft Dynamics NAV, the changes do appear.

Workaround: If you know that data has been changed externally, refresh the Microsoft Dynamics NAV window.

Description: With background posting, a sales or purchase document may not post with the following error message:

"Microsoft Dynamics NAV Server attempted to issue a client callback to show a confirmation dialog box."

This error occurs because in posting routines, when confirmation dialog boxes are displayed, background posting fails.

Workaround: The text of the confirmation dialog box is appended to the posting error. Use this information to correct the issue and then re-post. If this does not correct the problem, temporarily disable background posting in the Sales & Receivables Setup or Purchases & Payables Setup page, and then try to re-post. If your organization relies on these confirmation dialog boxes, consider disabling background posting.

Description: In the Microsoft Dynamics NAV Windows client, you cannot order actions in system groups in the Home tab.

Workaround: Remove all actions from the group, apply changes, and then add the actions again. This will ensure that metadata is created for all actions and that they can be sorted as you want.

Description: In the Microsoft Dynamics NAV Windows client, removing a promoted action in the Home tab, and then re-adding it in the same session will cause duplication of the action.

Workaround: Remove the action, apply changes, add the action again, and then apply changes. Or, remove the action, add it again in same session, and then apply changes. Remove duplicate instances and apply changes.

The Walkthrough: Creating and Using a Client Control Add-in and the Manifest Overview topics have been updated on MSDN to reflect an important design change. Please check http://go.microsoft.com/fwlink/?LinkId=321643.

Description: The TRANSFERFIELDS function copies field values from a record (source) to matching fields in another record (target), as specified by the FromRecord and Record parameters. If a field in the source record has not been initialized with a value, then no value is copied and the matching field in the target record keeps its current value. This behavior is different than in Microsoft Dynamics NAV 2009 which copied the default value of uninitialized fields in the source record to the target record.

Workaround: Assign a value to uninitialized fields in the source record.

Description: If the company name contains special characters, such as the forward slash (/) in the Cronus Danmark A/S company name, the GETURL function will generate a URL where the company name is not encoded correctly. You can see the incorrectly formatted URL in the Web Services page.

An upcoming hotfix for Microsoft Dynamics NAV 2013 R2 will resolve this issue.

Workaround: Encode the company name correctly when you call the web service.

Description: In Microsoft Dynamics NAV 2013 R2, you can specify an OData URL where the company name is passed as a query string parameter, such as http:// ServerAddress/OData/ServiceName?company='CompanyName'. However, since the link for retrieving the next page of data does not contain the company parameter, users see an error message when they try to navigate to the next page of data. The error message states that the default company has not been specified.

An upcoming hotfix for Microsoft Dynamics NAV 2013 R2 will resolve this issue.

Workaround: Use the default OData URL syntax where the company name is based on the default company, such as http://ServerAddress/OData/Company('CompanyName')/ ServiceName.

Description: When you try start debugger from the Microsoft Dynamics NAV Development Environment, you get the following error:

Microsoft.Dynamics.Nav.Client has stopped working.

This error indicates that the Microsoft Dynamics NAV Windows client cannot start. The error can occur when the version of development environment is different than the version of the Microsoft Dynamics NAV Windows client that debugger is starting. You can verify the versions by comparing the Application Version for the Microsoft Dynamics NAV Windows client that is shown in details section of the error dialog box with the version of the development environment.

Workaround: By default, the development environment starts the version of Microsoft Dynamics NAV Windows client that was last installed. Microsoft Dynamics NAV Windows client that is used by debugger is determined by the path that is specified by a protocol handler in the following registry key on the computer running the development environment:

HKEY_CLASSES_ROOT\DYNAMICSNAV\Shell\Open\Command

To work around this issue, before you start debugger, change the data value of the registry key entry to the path of the Microsoft Dynamics NAV Windows client that you want to use for debugging. For example, to start the Microsoft Dynamics NAV 2013 R2 version of the Microsoft Dynamics NAV Windows client, set the value to C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe -protocolhandler "%1".

Description: In Microsoft Dynamics NAV 2009, SQL replication was supported and it was possible to have one Microsoft Dynamics NAV Server instance connecting to a database that allows reading and writing (the Publisher database) and another Microsoft Dynamics NAV Server instance connected to another database that only allows reading (the Subscriber database). This worked because the cache on the Microsoft Dynamics NAV Server computer was cleared every minute. In Microsoft Dynamics NAV 2013 R2, when multiple Microsoft Dynamics NAV Server instances are running, the cache is only cleared when it is necessary. When one instance writes to a table in the database, all other instances connected to that database clear their caches for that record within 30 seconds. Since the SQL replication is one-way, instances connected to the Subscriber database would never find the other instances connected to the Publisher database. Even though the content of the Subscriber database is changing, Microsoft Dynamics NAV Server instances connected to it do not expect the change, because there are no explicit writes. Without cache synchronization, the data for instances connecting to the Subscriber may be outdated.

Description: The following table includes changes that have been made to Microsoft Dynamics NAV 2013 R2 Administration Shell cmldets. These changes improve the usability of the cmdlets when piping data from one cmdlet to another cmdlet.

In Microsoft Dynamics NAV 2013, these cmdlets returned a System.Data.Dataset object as output. With Microsoft Dynamics NAV 2013 R2, the cmdlets return the rows in the dataset one by one. In general, this means that any code that enumerates the cmdlet output no longer needs to enumerate the output.Rows property. You can now enumerate the output directly. This change is illustrated in the following code examples:

Description: The Export-NAVApplication cmdlet extracts the application tables from an existing Microsoft Dynamics NAV database and stores them to a separate application database. When you run the Export-NAVApplication cmdlet, if the source database (which is specified by the DatabaseName parameter) has more than one filegroup, then you will get the following error:

"Export-NAVApplication : The '[DestinationDatabase]'database that is specified in the ApplicationDatabaseName, contains NAV application tables."

The error occurs because the application tables in the source database are stored in the filegroup that is called Data Filegroup 1 and the cmdlet attempts to copy the tables to the same filegroup in the destination database. However, the destination database that is created only includes the PRIMARY filegroup. For example, this is the case when the database has been created from the Microsoft Dynamics NAV Development Environment. As a result, the application tables fail to be migrated into the destination database because the filegroup that they reside in does not exist.

Whether for upgrade purposes or multitenancy, to create an application database from an existing Microsoft Dynamics NAV database that has more than one filegroup, you can perform one the following workarounds.

Workaround 1: With this workaround, you use a backup of the Microsoft Dynamics NAV database.

1. Create a backup of the Microsoft Dynamics NAV database from which you want to export the application tables.
   
   
2. Mount the original database as an application on the Microsoft Dynamics NAV Server instance.
   
   

   Note
   The mounted application database will contain tables related to the tenant. However, this is not an issue because the entire database will be regarded as an application and the tenant tables will be ignored.

3. Restore the database backup that you created, and then mount the restored database as a tenant on the Microsoft Dynamics NAV Server instance.
   
   

   Note
   The mounted database will contain tables related to the application. However, this is not an issue because the entire database will be regarded as a tenant database and the application tables will be ignored.

Workaround 2: With this workaround, you create a new database in SQL Server.

1. In the SQL Server, manually create a new empty database that has the same filegroup structure as the Microsoft Dynamics NAV database from which you want to export application tables. The filegroup that is in addition to the PRIMARY filegroup must have the name Data Filegroup 1.
   
   
2. Run the Export-NAVApplication cmdlet and use the new database as the destination database for the application.
   
   

Description: If Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 are installed on the same computer, then the Microsoft Dynamics NAV 2013 Server Administration tool will not work. When you try to run the Microsoft Dynamics NAV 2013 Server Administration tool, you will receive the following error:

MMC has detected an error in a snap-in and will unload it.

Description: Some of the Help content for setting up users in Microsoft Dynamics NAV 2013 R2 has been updated in the English version but is not fully updated in the translated versions, such as German, Danish, Dutch, Spanish, and so on. As a result, users who read the translated versions of Help will see that the content does not fully match the product. This includes information RapidStart Services.

Workaround: Read the content about user setup and configuration in English only. This is available in the Help that is accessed from the Microsoft Dynamics NAV Development Environment, and it is available from the Microsoft Dynamics NAV Help Server if you change the language to en.

Description: Some help topics for new Cash Management features are not translated. As a result, users who read the translated versions of Help will see that the content does not fully match the product. The help topics in question are for fields or tables that mainly target super users.

Workaround: Read the non-translated content in English.

Description: Profiles on local versions contain promoted actions with labels such as "Action 12345". This occurs because of the difference between the profile for the W1 version of Microsoft Dynamics NAV and the local profile. The pages in local versions can contain actions that have been deleted or promoted to another group. The instances are identified in the Deleted or Promoted Actions section, later in this document, with information about how resolve the differences.

Description: When creating SEPA Direct Debit collections entries for a sales invoice that was posted with a SEPA Direct Debit mandate ID, the Mandate ID field in the Direct Debit Collect. Entries window is not filled.

Workaround: Manually fill the Mandate ID field for each direct debit collection entry.

Microsoft Dynamics C5 2014 is only intended for the Danish version of Microsoft Dynamics NAV and requires a special small-business license.

Description: A welcome video starts automatically when you sign on to Microsoft Dynamics C5 2014 for the first time. In some browsers, the video may cause a busy state and script error due to a race condition between the welcome video and the chart on the Small Business Role Center. To proceed, the user must refresh the browser or restart the client.

Workaround: Implement the following fix in page 1390, Mini Generic Chart:

1. Define a global boolean variable called ChartVisible with the IncludeInDataset property set to TRUE.
   
   
2. On the OnOpenPage trigger, create the following two local variables.
   
   

   Name	DataType	SubType
   MiniGettingStartedMgt	Codeunit	Mini Getting Started Mgt.
   FileManagement	Codeunit	File Management

3. Insert the following code on the OnOpenPage trigger: ChartVisible := NOT (MiniGettingStartedMgt.ShouldWelcomeVideoBePlayed AND FileManagement.IsWebClient);
   
   
4. Create a new group containing BusinessChart. Set the Visible property of the group to ChartVisible.
   
   

This fix means that the chart on the Small Business Role Center does not initialize on first sign-on. This prevents the race-condition issue.

Microsoft Dynamics C5 2014 is only intended for the Danish version of Microsoft Dynamics NAV and requires a special small-business license.

Description: If the product is hosted on a secure site using the https protocol, which is the default IE security configuration, then the two videos on the Small Business Role Center may be blocked with the following message in Internet Explorer: “Only Secure Content Is Displayed".

Workaround: In codeunit 1321, Mini Getting Started Mgt., in the PlayWelcomeVideo and PlaySettingUpYOurSystemVideo functions, change http to https in the hyperlinks.

Microsoft Dynamics C5 2014 is only intended for the Danish version of Microsoft Dynamics NAV and requires a special small-business license.

Description: The Bank Export/Import Setup table (1200) causes an error when you apply the small-business RapidStart package.

Workaround: Open the RapidStart package and select the line for table 1200. On the Lines FastTab, choose Functions and then select Apply Data.

Microsoft Dynamics C5 2014 is only intended for the Danish version of Microsoft Dynamics NAV and requires a special small-business license.

Description: After creating a Microsoft Dynamics C5 2014 solution with the small-business RapidStart package, the Online Map Setup window is empty. This means that users see “Cannot Display this Page” in their browser when they choose the Online Map field.

Workaround: Open the Online Map Setup window once to automatically insert default values: On the Small Business Role Center, on the Setup tab, choose Setup, and then select Company Information. In the Company Information window, on the Home tab, in the Regional Settings group, choose Online Map Setup.

Microsoft Dynamics C5 2014 is only intended for the Danish version of Microsoft Dynamics NAV and requires a special small-business license.

Description: After creating a Microsoft Dynamics C5 2014 solution with the small-business RapidStart package, the CASH payment method is set up. However, the Bal. Account No. field in the Payment Methods window is not filled. This means that a sales invoice with the CASH payment method does not change to Paid status when it is posted.

Workaround: Manually fill the Balance Account No. field as follows: On the Small Business Role Center, on the Setup tab, choose Setup, and then select Sales & Receivables Setup. In the Sales & Receivables Setup window, on the Home tab, in the Payments group, choose Payment Methods. On the line for the CASH payment method, choose the Bal. Account No. field and then select an appropriate balancing account for cash payments.

Microsoft Dynamics C5 2014 is only intended for the Danish version of Microsoft Dynamics NAV and requires a special small-business license.

Description: After creating a Microsoft Dynamics C5 2014 solution with the small Business RapidStart package, the following setup is missing before the user can perform cash flow analysis:

• No accounts exist in the Chart of Cash Flow Accounts window
  
  
• The Cash Flow Setup window is not accessible.
  
  
• The Cash Flow Worksheet window is not accessible.
  
  

Workaround: Manually set up the missing Cash Flow functionality. On the Small Business Role Center, choose the Setting Up Your System tile to launch a video that goes through all required setup work.

The following table shows pages in the local version of Microsoft Dynamics NAV 2013 R2, which contain actions that have been deleted or promoted to another group, with a recommendation for a possible resolution.