NAV 2013: Saving Time being online .. release notes

Microsoft Dynamics NAV Documentation

Release Notes for Microsoft Dynamics NAV 2013

September 2012

This document describes how to install Microsoft Dynamics NAV 2013 and describes known issues that may affect your experience using the product.

Installing Microsoft Dynamics NAV 2013

Use the Microsoft Dynamics NAV 2013 Setup program to install Microsoft Dynamics NAV 2013 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.

Known Issues

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

Missing the correct caption for some promoted actions on configured profiles

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.

Queries return DateTime values when they should return Date values

Description: When you run a query from the Microsoft Dynamics NAV Development Environment, fields of type Date are returning DateTime values. This does not happen when executing the query and looping through the result set from C/AL code.

Microsoft Office Outlook add-in not working with Office 2007

Description: The Microsoft Office Outlook Add-in does not load when it is installed for Microsoft Office 2007.

Workaround: Follow these steps:

  1. Copy this file.
    C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Office.dll

    To this location.

    C:\Program Files (x86)\Microsoft Office\Office12\
  2. Copy this file.
    C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Microsoft.Office.Interop.Outlook.dll

    To this location.

    C:\Program Files (x86)\Microsoft Office\Office12\
Excel add-in not working with Office 2007

Description: When you install Microsoft Dynamics NAV 2013, you can install the Microsoft Office Excel Add-in. However, if you install on a computer where Microsoft Office 2007 is already installed, it may not always work correctly. For example, if you try to send a customer list to Excel, Excel will start, but the list will not contain any content.

Workaround: Uninstall the Microsoft Office Excel Add-in using Microsoft Dynamics NAV 2013 Setup. Then when you choose the Send to Microsoft Excel action, the list is sent to Excel. For more information, see the System Requirements for Microsoft Dynamics NAV 2013.

Mail merge not working with Office 2007

Description: Mail merge does not work on a computer that has Office 2007 installed and you may receive the following error message:

"This message is for C/AL programmers: Cannot create an instance of the following .Net Framework object: Assembly ‚Microsoft.Office.Interop.Word, Version=14.0.0.0,Culture=Neutral,PublicKeyToken=71e9bce111e9429c‘."

Workaround: Follow these steps:

  1. Install the Trial version of Office 2010 Professional

    For more information, see http://office.microsoft.com/en-us/try.
  2. Copy the Microsoft.Office.Interop.Word.dll file from C:\Windows\assembly\GAC_MSIL\Microsoft.Office. Interop.Word\14.0.0.0__71e9bce111e9429c to C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\Add-ins\Office.
  3. Open Object Designer in the Microsoft Dynamics NAV Development Environment, and compile codeunit 50504, WordManagement.
Codeunit 5054 does not compile on a computer that has Office 2007 installed

Description: Codeunit 5054 will not compile on a computer that has Office 2007 installed. This is because of a reference to Word.Interop.dll for Word 2007. The compilation of code unit 5054 fails with the following error message:

"Could not load type ‚Microsoft.Office.Interop.Word.ApplicationClass.’Microsoft.Office.Interop.Word, Version=14.0.0.0,Culture=Neutral,PublicKeyToken=71e9bce111e9429c‘."

Workaround: The workaround is the same as for the previous issue.

Not possible to record print interaction of invoices when printing from preview mode

Description: It is not possible to record print interaction of invoices when printing from Preview mode. In order to record the interaction of printing invoices you must send them directly to the printer.

The interactions can be logged when the report is directly sent to printer, but not when printing from preview mode. Therefore to avoid errors (such as issuing and printing invoices multiple times) in sensitive reports such as Sales invoices, the Print option is disabled in the Preview page. But it is possible to print from Preview in Report 206 (Sales Invoice). Therefore it is possible to print invoices without recording them.

Workaround: To avoid printing from the Preview page, use the CurrReport.PREVIEW property before data items are processed (for example, OnInitReport, OnPreReport, OnOpenReport).

Importing queries into the development environment fails when the language is not English

Description: When using a language other than English in the Microsoft Dynamics NAV Development Environment, designing or importing query objects can fail. The problem is that the options for DataItemLinkType are localized.

Workaround: In the development environment, change the language to English before importing or designing query objects. Another workaround is to reference the option by number instead of by name.

Expired user counts against license

Description: The administrator can specify an Expiry Date when a user is created. After the expiration date, the user can no longer log on, but is still counted against license limits.

Workaround: Edit the User card and change the State field for the user to Disabled.

Report initialization overrides the values set through code on variables for the report instance

Description: When running a report, the user sets a variable on the Request Page to a value, for example, a Boolean variable is set to TRUE. When the report is called through code, and the code sets the variable to its default value, in this example, FALSE, before REPORT.RUN is called, when the report is run, then the value is overridden by the saved value and reset incorrectly to TRUE. This behavior can occur with any variable that is displayed on a page.

Adding a primary key when the record size is close to the limit prevents the table from being compiled

Description: The maximum record size in Microsoft Dynamics NAV 2013 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.

Posting and printing in background times out and leaves background sessions

Description: A sales or purchase document is posted and printed in the background but there is no printout. The corresponding Job Queue entry remains, with Status set to In Progress, but then changes to Error after two hours with the following error message:

"The job has timed out."

The corresponding background session appears to have stopped responding on the Microsoft Dynamics NAV Server instance. This problem occurs when Post & Print with Job Queue is enabled in the Sales & Receivables Setup or Purchases & Payables Setup page, and documents have been sent to a printer that displays a pop-up window. The printing is controlled by the Microsoft Dynamics NAV Server process, but the end user never sees the pop-up window. Printers might display pop-up windows to requests credentials, or to show a notification for low paper or ink.

Workaround: To clean up the unresponsive background sessions, restart the Microsoft Dynamics NAV Server instance.

The unresponsive background sessions will not affect your ability to use background posting, nor will they count against the number of licensed users. These sessions should only have a negligible effect on performance. In general, it is advised that you avoid printers that display any blocking windows.

Posting in background fails on confirmation dialog boxes

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.

It is not possible to order actions in system groups in the Home tab

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.

Removing a promoted action in the Home tab and re-adding it in the same session will cause duplication of the action

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.

Manually install .NET Framework 3.5 SP1 and 4.5 before you install Microsoft Dynamics NAV Server on Server Core for Windows Server 2008 R2

Description: Server Core for Windows Server 2008 R2 is a minimal server installation option. If you run Microsoft Dynamics NAV 2013 Setup to install Microsoft Dynamics NAV Server on a computer that is running Server Core for Windows Server 2008 R2 without first installing both .NET Framework 3.5 SP1 and .NET Framework 4.5, the installation fails.

Microsoft Dynamics NAV Server cannot start with the CRONUS International Ltd. demonstration database on a localized operating system

Description: When you install the CRONUS International Ltd. demonstration database 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.

SQL replication in Microsoft Dynamics NAV 2013 does not work as it did in Microsoft Dynamics NAV 2009

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, when multiple Microsoft Dynamics NAV Server instances are running, the cache is only cleared when 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 know about 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.

Fixed asset is added two times to cash flow forecast

Description: If an open sales order contains a fixed asset and the disposal information also lists the same fixed asset, then both sources are included in the cash flow forecast.

Workaround: There are multiple workarounds:

  • Use a sales invoice to sell fixed assets.
  • Verify that the sales order is invoiced before the cash flow forecast is updated.
  • After the line has been suggested in the worksheet, delete it manually before updating the worksheet.
Incorrect cash discount amount is displayed when it is calculated based on a cash flow payment term

Description: A cash discount amount that is calculated based on a cash flow payment term is incorrect if the invoice has been partially paid. This issue exists both for payables and receivables.

RapidStart Services: Configuration worksheet export to Excel does not work on the Microsoft Dynamics NAV Web client

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.

RapidStart Services: Binary type not supported

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.

RapidStart Services: Error when exporting data to Excel

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.

Deleted or Promoted Actions

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

Version

Page

Action

Target

Resolution

DACH

9020 – Small Business Owner RC

Action10

Sales Order (42)

Delete the action or delete and move the duplicate action from the "New Document" group.

DACH

9020 – Small Business Owner RC

Action3

Purchase Order (50)

Delete the action or delete and move the duplicate action from the "New Document" group.

ES

43 – Sales Invoice

Action63

No target

Delete the action.

ES

44 – Sales Credit Memo

Action114

No target

Delete the action.

ES

507 – Blanket Sales Order

Action67

No target

Delete the action.

ES

509 – Blanket Purchase Order

Action69

No target

Delete the action.

ES

51 – Purchase Invoice

Action61

No target

Delete the action.

ES

52 – Purchase Credit Memo

Action53

No target

Delete the action.

ES

6630 – Sales Return Order

Action55

No target

Delete the action.

ES

6640 – Purchase Return Order

Action53

No target

Delete the action.

IN

132 – Posted Sales Invoice

Action58

No target

Delete the action.

IN

5743 – Posted Transfer Shipment

Action51

No target

Delete the action.

IT

9004 – Bookkeeper Role Center

Action8

Sales Invoice (43)

Replace caption with "Sales Invoice".

IT

9004 – Bookkeeper Role Center

Action556

Purchase Invoice (51)

Replace caption with "Purchase Invoice".

NA

16 – Chart of Accounts

Action1900670506

Detail Trial Balance (4)

Replace caption with "Detail Trial Balance"

NA

21 – Customer Card

Action190068113206

No target

Delete the action.

NA

27 – Vendor List

Action1905766406

Vendor List (27)

Payments on Hold (319)

NA

27 – Vendor List

Action1905685906

No target

Delete the action.

NA

370 – Bank Account Card

Action53

Bank Account Statement List (389)

Replace the caption with "Bank Account Statement List".

NA

371 – Bank Account List

Action7

Bank Account Statement List (389)

Replace the caption with "Bank Account Statement List"

NA

434 – Reminder

Action1906359306

Customer – Trial Balance (129)

Replace the icon with "Customer – Trial Balance"

NA

9004 – Bookkeeper Role Center

Action8

Sales Invoice (43)

Delete the action or delete and move the duplicate action from the "New Document" group.

NA

9004 – Bookkeeper Role Center

Action556

Purchase Invoice (51)

Delete the action or delete and move the duplicate action from the "New Document" group.

NA

9020 – Small Business Owner RC

Action10

Sales Order (42)

Delete the action or delete and move the duplicate action from the "New Document" group.

NA

9020 – Small Business Owner RC

Action3

Purchase Order (50

Delete the action or delete and move the duplicate action from the "New Document" group.

NL

9004 – Bookkeeper Role Center

Action8

Sales Invoice (43)

Replace the caption with "Sales Invoice".

NL

9004 – Bookkeeper Role Center

Action556

Purchase Invoice (51)

Replace the caption with "Purchase Invoice".


Kommentar hinterlassen

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.

*

code