Changes in NAV 5 0 SP1

ø
Microsoft Dynamics™ NAV
Changes Made in Microsoft

Dynamics NAV 5.0 SP1 for
W1
This document describes the changes between Microsoft

Dynamics NAV 5.0 for W1 and Microsoft Dynamics NAV 5.0
SP1 for W1.
Date: March, 2008

Contents
Application Changes..................................................................3
General Ledger....................................................................................................3
Pre-Payment........................................................................................................7
Employee Portal................................................................................................12
Document Approval...........................................................................................12
Purchase............................................................................................................14
Sales and Marketing..........................................................................................25
Service Management.........................................................................................40
Jobs 44
Inventory...........................................................................................................48
Fixed Asset........................................................................................................54
Supply Planning.................................................................................................55
Item Tracking....................................................................................................57
Warehouse........................................................................................................58
Application.........................................................................................................60
Outlook Integration............................................................................................63
Integration.........................................................................................................65
Mobile................................................................................................................66
Manufacturing...................................................................................................67
Business Analytics Basic....................................................................................73
Development Environment and Database Changes....................74

SQL Server Option for Microsoft Dynamics NAV.................................................74
Platform.............................................................................................................75
Office Integration...............................................................................................83
Development Environment................................................................................83
Tools......................................................................................83
Navision ODBC Driver........................................................................................84
C/FRONT............................................................................................................84
CHANGES MADE IN MICROSOFT DYNAMICS™ NAV W1 5.0 SP1

Application Changes
General Ledger
A1) Error when inserting, renaming, and deleting Accounting Periods
Error
A run-time error occurred when the user modified, inserted, renamed, or deleted an Accounting
Period record in the Accounting Periods window.
This has been corrected

Codeunit 5810 Change Average Cost Setting
VSA reference: 8900879

KB article reference: 938366
A2) Adjust Exchange Rate with Start Date
Error
Adjust Exchange Rate batch job would not pick up Vendor Ledger Entries if you used the Start Date.

Report 595 Adjust Exchange Rates
A3) Inter Company deadlock
Error
When a transaction was sent twice it could result in a system error message, so instead, we have
inserted messages to inform the user what to do in those cases.

Report 511 Complete IC Inbox Action, Report 513 Move IC Trans. to Partner Comp
Clarify reference: SRZ070703000130

A4) Unrealized VAT was not Realized for applying entries
Error
Unrealized VAT was not realized when the applied entry for an application was posted with an
unrealized VAT and closed in the same application.
CHANGES MADE IN MICROSOFT DYNAMICS™ NAV 5.0 W1

Codeunit 12 Gen. Jnl.-Post Line
Clarify reference: 8997697

A5) Posting Group in Un-apply
Error
Un-apply used the Customer/Vendor posting group from the customer/vendor when posting to G/L.
This has been changed so that the posting group from the original application is used.

A6) Menu Suite had Points for Missing Reports
Error
Some reports were removed for 5.0 but their menu suite was not removed. These have now been
removed. The removed menus are ‘Delete Message Log Entries’ and ‘Delete Expired or rejected
Quotes’.

MenuSuite 10 MBS
A7) Error when Create Sales Lines from IC Transac. with Zero Qty
Error
The division by zero error occurred when the system created a sales order from an IC transaction
document if the Quantity field of the IC Inbox Sales Line table contained zero value.

Codeunit 427 ICInboxOutboxMgt

A8) Not possible create accounting period in a new company
Error
This is caused by the call from the Accounting Periods form (form 100) to the Inventory Period table
(table 5814) where the functions InvtPeriodClosed expected to find an entry from the Inventory Period
table.

Table 5814

A9) Intercompany Duplicate Postings
Error
When the user initiated an Intercompany transaction with a purchase or sales order, it resulted in
duplicate postings. If the transaction was initiated with a purchase order and both the purchase order
and the purchase invoice, which is returned by the partner, were posted, there would be duplicate
postings of the purchase invoice.
Therefore, some messages have been included to inform the user about when duplicate postings
might occur. These messages will appear both when the user is posting the original purchase order,
and when the user is trying to accept a purchase invoice in the inbox and a duplicate document
already exists. If the IC transaction is initiated with a sales order, both a purchase order and a
purchase invoice are sent to the partner. If both are posted, duplicate posting will occur. Some
messages will appear when the user is trying to post either the purchase order or purchase invoice to
inform the user of the risk of duplicate postings.

Codeunit 90 Purch.-Post, Table 418 IC Inbox Transaction, Table 426 IC Outbox Sales Header, Table
430 Handled IC Outbox Sales Header, Table 436 IC Inbox Purchase Header, Table 440 Handled IC
Inbox Purch. Header
A10) Blocking on Analysis View
Error
Unnecessary blocking on the Analysis View table occurred.

Cdeunit 410
Codeunit 7150
A11) Blank Statement Line No.
Error
The Statement Line No. field remained blank in bank account ledger entries, when doing bank
reconciliation.

Codeunit 370 Bank Acc. Reconciliation Post


A12) Error when making Order from Purch. Quote for Vendor with FCY
Error
An error prevented converting a purchase quote to an order if the quote was for a vendor with default
currency that was different from LCY.

Codeunit 96 Purch.-Quote to Order

A13) G/L Account Name added to G/L Entry
Feature
The description for the G/L Account No. is now available in the G/L Entry table and can be displayed
on the G/L Entries form by using Show Column.
This has been implemented
Table 17 - G/L Entry

Form 20 - G/L Entries
A14) Export Budget and Totaling Accounts
Error
When exporting a budget to Excel and using "Include Totaling Formulas" the account numbers of the
Totaling accounts was missing in Excel.

Report 82 Export Budget to Excel
Table 370 Excel Buffer

A15) Replace Entries in Budget Import with Dimensions
Error
When importing a budget from Excel and selecting Replace Entries, all entries with the same general
ledger account and on the same posting date were deleted. This has been changed to include
dimensions as well.

Report 81 Import Budget from Excel


A16) Not all XBRL labels were imported
Error
When importing XBRL files some labels were left out.

Codeunit 422 XBRL Import Taxonomy Spec. 2

A17) XBRL with long labels
Error
In some cases an XBRL document had a text that was longer than 1024 characters which is the
maximum that Microsoft Dynamics NAV can handle.

Codeunit 422 XBRL Import Taxonomy Spec. 2

KB article reference:
Pre-Payment
A18) Prepayment with Currency and VAT
Error
A consistency error occurred when you posted a prepayment invoice with currency and VAT.

Codeunit 442 Sales-Post Prepayments
Codeunit 444 Purchase-Post Prepayments
A19) Prepayment and Get Shipment
Error
When using Get Shipment on a prepayment order some amounts were transferred directly from the
order to the invoice, without the quantity being corrected. This could cause large orders with small
quantities to fail when the invoice was posted.

Table 37 Sales Line
Table 39 Purchase Line
Table 111 Sales Shipment Line
Table 121 Purch. Rcpt. Line

A20) Prepayment and Unrealized VAT
Error
When using unrealized VAT on Prepayment only and applying a prepayment credit memo to a
prepayment invoice, the unrealized VAT on the prepayment credit memo would not be reversed.

Table 382 CV Ledger Entry Buffer
A21) Prepayment posted as Unrealized VAT
Error
In order to run the invoicing of Prepayment Invoices with Unrealized VAT, even in scenarios with
normal VAT calculation for invoicing, we’ve added a setup checkmark box on the Prepayment
Unrealized VAT field on the General Ledger Setup form. When setting this checkmark to Yes the
normal Unrealized VAT functionality is used to post Prepayment VAT as Unrealized VAT, and the
normal Unrealized VAT posting Account is used (from the VAT Posting Setup). This means that you
should remember to set up the account when using this functionality. This also means that when
using both Unrealized VAT and Prepayment Unrealized VAT the posting will use the same account.

Table 98
Table 325
Form 118
Codeunit 12
Codeunit 442
Codeunit 444
A22) Over-subtracting Prepayment
Error
It was possible to reduce an invoice with a higher amount than invoiced in the prepayment invoice.

Table 37 Sales Line

A23) Not possible to delete prepayment invoice
Error
It was not possible to delete an invoice with prepayment.

Table 37 Sales Line, Table 39 Purchase Line

A24) Get shipment and prepayment caused an error
Error
An error occurred if you tried to make a get shipment on an order with prepayment.

Table 37 Sales Line, Table 39 Purchase Line, Table 111 Sales Shipment Line, Table 121 Purch.
Rcpt. Line, Codeunit 80 Sales-Post, Codeunit 90 Purch.-Post
A25) Wrong VAT when posting prepayment orders
Error
When a purchase/sales order with prepayment was posted in two steps (first receive then invoice/first
ship then invoice) no VAT for the prepayment was deducted on the G/L Entries.

Table 37 Sales Line, Table 39 Purchase Line

A26) Not possible to delete pre-payment order
Error
It was not possible to delete an order with prepayment that had been fully invoiced from an invoice
(with the function Get Shipment). Furthermore, the Status field on the Order header has been
changed so it set to ‘released’ as soon as any shipment takes place.

Codeunit 80 Sales-Post, Codeunit 90 Purch.-Post, Table 37 Sales Line, Table 39 Purchase Line

A27) Copy Document on Posted Invoice with Prepayment
Error
The last invoice line that was copied using the copy document functionality did not have the correct
dimensions when copying from a prepayment invoice, because the dimension was overwritten by the
dimension of the reverted prepayment invoice line.

Codeunit 6620 Copy Document Mgt.

A28) Dimensions on Reversal of Prepayment
Error
Dimensions were missing on the reversal line of prepayment invoices.

Codeunit 80 Sales-Post
Codeunit 90 Purch.-Post

A29) Global Dimensions on Prepayment Revert Line
Error
Global Dimensions was not filled on the line reverting Prepayment on a sales/purchase invoice.


A30) Export to Excel did not allow code of the form 000XXX
Error
The export to Excel functionality on analysis by dimensions, wrongly converted dimension codes of
the form 000123 to 123.

COD424

A31) Documents Approval Comments with long document numbers
Error
The document number parameter of the Set Filters function on forms 659, 660 and 661 only had 10
character spaces even though it could actually take 20 characters.
10

Form 659 Posted Approval Entries
Form 660 Approval Comments
Form 661 Posted Approval Comments
A32) Prepayment order lines with blank type
Error
It was not possible to have order lines with a blank Type field on prepayment orders.

Tabel 37 Sales Line
A33) Wrong information in the Prepmt. Amount Inv. Incl. VAT field
Error
The Prepmt. Amount Inv. Incl. VAT field was not updated when a pre-payment credit memo was
posted.

Codeunit 442 Sales-Post Prepayments,
Codeunit 444 Purchase-Post Prepayments

A34) Error with prepayment and posting in two steps
Error
Posting orders with prepayment, partial posting and posting in two steps (e.g. first Ship then Invoice)
did not work.

Codeunit 80 Sales-Post,
Codeunit 90 Purch.-Post,
Table 37 Sales Line,
11

A35) Purchase Prepayment % records without vendor
Error
The connected Purchase Prepayment % records were not deleted when deleting a vendor.

Table 23 Vendor
Employee Portal
A36) Sorting was not possible if sorting key was different
Error
When you created sorting for a key that was not on the primary key, the application did not respect
the sorting.

COD6813
Document Approval
A37) Document Approval and Zero Invoices
Error
The user would not be able to either post or approve when using Document Approval and making a
Zero invoice/order.

Codeunit 439 Approvals Management

A38) Document could not be approved after sending Approval Request
Error
When an approval request for a document was sent by the user who was defined as approver and
several approval templates were valid for this document, the status of an approval entry for the next
approver was not changed to Open. As the result, the next approver could not approve the entry.

12

Clarify Reference: SRQ070516600217
KB Reference: 939881
A39) Document Approval Entry for documents below limit
Error
When trying to approve a document below the customer credit limit the system didn't create the
needed approval entry and the document was still not approved after running the approval request.
Since the document wasn't approved it was impossible to post the document.


A40) Error occurred if user created purchase order from Blanket Purchase Order
Error
When user tried to create a purchase order from Released Blanket Purchase Order the error
message saying ‘Status must be open’ popped up.

Codeunit 97 Blanket Purch. Order to Order
A41) Document Approval and Credit Limit
Error
An error was telling the user that credit limit has to be set up on the customer when Credit limit was
set to 0 and when using document approval. This has been changed to handle credit limit = 0 as
unlimited credit.

Clarify reference: SRQ071015600274

A42) Approval Rejections and Cancellations sent too many e-mails
Error
Approval Rejections and Cancellations sent multiple e-mails containing the same message to the
same user. This has been reduced to one e-mail per user.

13

Codeunit 440 Approvals Mgt Notification

A43) Approval Entry with empty Approver ID
Error
In cases when the user used "Approval Type" Approver and "Limit Type" Credit Limit without having
an approver assigned, the system would generate an Approval Entry with Blank Approver.

A44) Multiple Approval entries for Additional Approvers
Error
When more than one template was used for a single document type and Additional Approvers was set
up on the first template, then the additional approvers received 2 Approval entries for the document.

A45) Document Approval and Invoice below credit limit
Error
The system told the user that no approver was found when document approval was set up to use
credit limit with additional approvers and a sales person generated a sales invoice that was below the
customer credit limit. This has been changed to automatically approve the invoice.


Purchase
A46) Ability to enter comments on purchase lines and to save comments to archived forms
Feature
Comments may be added for each line on all purchase documents and then moved to
posted/archived documents.
14

This has been implemented.
Table 39 - Purchase Line

Table 121 - Purch. Rcpt. Line
Table 123 - Purch. Inv. Line
Table 125 - Purch. Cr. Memo Line
Table 5109 - Purchase Header Archive
Table 5110 - Purchase Line Archive
Table 5125 - Purch. Comment Line Archive
Form 49 - Purchase Quote
Form 50 - Purchase Order
Form 51 - Purchase Invoice
Form 52 - Purchase Credit Memo
Form 54 - Purchase Order Subform
Form 55 - Purch. Invoice Subform
Form 97 - Purchase Quote Subform
Form 98 - Purch. Cr. Memo Subform
Form 136 - Posted Purchase Receipt
Form 137 - Posted Purchase Rcpt. Subform
Form 138 - Posted Purchase Invoice
Form 139 - Posted Purch. Invoice Subform
Form 140 - Posted Purchase Credit Memo
Form 141 - Posted Purch. Cr. Memo Subform
Form 509 - Blanket Purchase Order
Form 510 - Blanket Purchase Order Subform
Form 5164 - Purchase Quote Archive
Form 5167 - Purchase Order Archive
Form 5179 - Purch. Archived Comment Sheet
Form 6640 - Purchase Return Order
Form 6641 - Purchase Return Order Subform
Form 6650 - Posted Return Shipment
Form 6651 - Posted Return Shipment Subform
A47) Automatic archiving of Purchase Quotes and Purchase Orders
Feature
The user can define a setup option to automatically archive Purchase Quotes when they are turned
into Purchase Orders and archive Purchase Orders when they are fully received.
Table 312 – Purchases & Payables Setup

Table 5109 - Purchase Header Archive
Table 5110 - Purchase Line Archive
Form 460 – Purchases & Payables Setup
Form 7187 - Purch. Order Archived Subform
Codeunit 90 - Purch.-Post
Codeunit 96 - Purch.-Quote to Order
Codeunit 229 - Document-Print
Codeunit 5063 - ArchiveManagement
Menusuite 10 - MBS
15

A48) Return Orders enabled for archiving
Feature
Return Orders may now be manually archived the same way as other purchase documents. Note:
Return Orders are also included in the Automatic Archiving described in A43).
Form 6640 - Purchase Return Order

Form 6644 - Purchase Return Order Archive
Form 6645 - Purchase Return Order Archive Subform
Form 6646 - Purchase Return List Archive
Codeunit 5063 – ArchiveManagement
A49) Improved Balance drill-down from Vendor Card
Feature
The drill-down from the Vendor Card only shows the open ledger entries which support the balance.
Table 25 - Vendor Ledger Entry
A50) Ability to print archived documents
Feature
Archived quotes, orders, and return orders may be printed from the archive forms.
Table 77 - Report Selections

Form 6644 - Purchase Return Order Archive
Report 415 - Print Archived Purchase Quote
Report 416 - Print Archived Purchase Order
Report 417 - Print Archived Purchase Return Order
Codeunit 321 - Purch.HeaderArch-Printed
Codeunit 365 - Format Address
A51) Posting Date default options
Feature
The posting date on entry documents may be defaulted to a blank value depending on the Purchases
& Payables setup.
Table 38 - Purchase Header

Table 312 - Purchases & Payables Setup
Form 460 - Purchases & Payables Setup
16

A52) Quantity default options
Feature
The Quantity Remaining fields on purchase lines can be set to default to a blank value instead of
having to depend on the Purchases & Payables setup. This forces the user to decide how much
should be handled instead of accepting the full remaining quantity.
Table 39 - Purchase Line

Table 312 - Purchases & Payables Setup
Form 460 - Purchases & Payables Setup
Codeunit 90 - Purch-Post
A53) Navigation Panes added to documents
Feature
Navigation panes have been added to purchase documents similar to sales documents.
Table 23 - Vendor
Form 49 - Purchase Quote
Form 51 - Purchase Invoice
Form 54 - Purchase Order Subform
Form 55 - Purch. Invoice Subform
Form 7182 - Purchase Lines Subform
Form 7183 - Receipt Lines Subform
Form 7184 - Return Shipment Lines Subform
Form 7185 - Purch. Invoice Lines Subform
Form 7186 - Purch. Cr. Memo Lines Subform
Form 7187 - Purch. Order Archived Subform
Form 7189 - Get Purchase Line Disc.
Form 7190 - Get Purchase Price
Codeunit 7010 - Purch. Price Calc. Mgt.
Codeunit 7181 - Purchases Info-Pane Management
CodeUnit 7182 - Purch. History Copy Line Mgt.
A54) Purchase History from Vendor Card
Feature
The purchase history for a vendor may be invoked from the vendor card based on either the Pay-to or
Buy-from role for a vendor.
Form 26 - Vendor Card

Form 7181 - Vendor Purchase History
Codeunit 7181 - Purchases Info-Pane Management
17

A55) Posting Date available in Posted Lines
Feature
The Posting Date document is also posted to the Posted Line tables for purchase documents. This
allows for better detail reporting as well as the ability to view purchase history by date.

Table 6651 - Return shipment Line
Table 121 - Purch. Rcpt. Line
Codeunit 90 - Purch.-Post
Report 7181 - Update Posting Date in Docs is available for upgrade of existing documents.
A56) Purchase Quote number maintained in documents
Feature
The purchase quote number is maintained in all posted documents which started with a quote.

Table 122 - Purch. Inv. Header
Table 120 - Purch. Rcpt. Header
Form 136 – Posted Purchase Receipt
Form 138 - Posted Purchase Invoice
Codeunit 96 - Purch.-Quote to Order
A57) Applies-to Doc. Due Date added to Payment Journal
Feature
The payment journal now shows the due date for the document being paid on the form. The due date
is displayed from the Applies-to Doc. No/Type fields on the journal line.
Table 81 - Gen. Journal Line

Form 256 - Payment Journal
A58) External Document No. added to Payment Journal
Feature
The external document number is displayed on the Payment Journal form to display the Vendor
Invoice No that is entered in this field.
Form 256 - Payment Journal
18

A59) Printing Check with Altered Amount
Error
The check report recalculated the amount to pay even when the amount on a suggested vendor
payment line was altered by the user.

Report 1401 Check
A60) Unit of Measure in Requisition Line was not set correctly
Error
Manually entered lines in the requisition worksheet used the Base Unit of Measure if the location was
left blank although the Purchase Unit of Measure was different.

Table 246 Requisition Line
Clarify reference: SRZ071019000126-1

A61) Amount to Apply ignored date rules in application
Error
It was possible to set an application ID on records with illegal dates when using the Amount to Apply
field.

Form 232 Apply Customer Entries
Form 233 Apply Vendor Entries
A62) Dimensions weren't saved properly for Posted Purchase
Error
If a purchase order was created directly from a requisition worksheet using the Carry Out AM function,
and then posted, not all dimensions were saved properly in the G/L accounts.

Codeunit 333 Req. Wksh.-Make Order
19

A63) No Pay-to/Bill-to Contact No. on Posted Purch./Sales Docs.
Error
The Pay-to Contact No. and Bill-to Contact No. fields were missing on the posted purchase and sales
documents.
The Buy-from Contact No. field was missing in the Posted Purchase Receipt, Posted Purchase Credit
Memo and Posted Return Shipment windows. The Sell-to Contact No. field was not available in the
Posted Sales Shipment, Posted Sales Credit Memo and Posted Return Receipt windows.

Table 120 Purch. Rcpt. Header,
Table 124 Purch. Cr. Memo Hdr.,
Table 6650 Return Shipment Header,
Form 130 Posted Sales Shipment,
Form 134 Posted Sales Credit Memo,
Form 136 Posted Purchase Receipt,
Form 140 Posted Purchase Credit Memo,
Form 6650 Posted Return Shipment,
Form 6660 Posted Return Receipt
A64) Application was slow with large number ledger entries
Error
Application of Vendor or Customer ledger entries was slow when a customer or a vendor had a lot of
records in the ledger entries.

A65) Missing 0 VAT Entry after unapply
Error
When applying a payment to an invoice with payment discount and without VATm the system
generated a zero VAT amount. This entry was not counter posted when applying the payment.


20

A66) Date Check when applying from General Journal Line
Error
There was a check mark when applying directly from a General Journal Line on the Posting Date of
the applying entry versus the Posting Date of the applied entry/entries. This check mark was only
placed when the Document Type was Payment or Refund. This limitation has been removed.

A67) "Applies-to ID" on Reverted Entries
Error
When a Customer Ledger Entries or Vendor Ledger Entries were reverted the Applies-to ID field was
not cleared.

A68) Key for VAT Entries in Unapply
Error
The search for VAT Entries when unapplying did not use an optimal key.


A69) Document Date and late application
Error
General Ledger Entries that were generated late from a customer/vendor application was missing a
document date.

Codeunit 226 CustEntry-Apply Posted Entries
Codeunit 227 VendEntry-Apply Posted Entries

21

A70) Update Apply Form when Payment Discount is changed
Error
The Update Apply form is now updated when the user changes something in connection with
Payment discount.

A71) Reversal did not revert Payment Discount
Error
Reversal did not take all applications and un-applications of Payment Discount into consideration.

Table 179 Reversal Entry
Clarify reference:
A72) Apply Form miscalculated payment discount
Error
The discount on an invoice or credit memo was lost in cases where the payment corresponded
exactly to the due amount and the user was trying to close several entries in one batch.


A73) Payment Discount not Shown correctly from General Journal
Error
When opening the Apply window from a journal without filling the Amount field of the journal, the
Apply window did not show the payment discount.


22

A74) Amount to Apply from Apply to Document Number
Error
The Amount to Apply field on the Customer/Vendor Ledger Entries was not filled in when applying
from Apply to Document No. on a General Journal.

A75) Charge computation provided a rounding discrepancy
Error
When Charge (item) was posted a rounding problem occurred. The difference occurred in some
special cases if a foreign currency was used. This was a general problem in the posting codeunit.

A76) Incorrect calculation of the Expected Receipt Date
Error
The calculation of Expected Receipt Date was wrong if the Date Formula field contained a month.

A77) Dimensions on Printed Checks
Error
The system would try to insert two records with the same primary key in the Dimension table if default
dimensions existed on the used bank account, and the same dimension was specified on the first
payment line when printing a check.

Report 1401 Check

A78) Campaign No. not assigned to purchase documents
Error
The system design did not provide the user with the possibility to assign a campaign to a purchase
document. Posted purchase documents did not contain link to the campaign.
23

Table 120 Purch. Rcpt. Header,
Table 122 Purch. Inv. Header,
Table 124 Purch. Cr. Memo Hdr.,
Table 6650 Return Shipment Header,
Form 49 Purchase Quote,
Form 50 Purchase Order,
Form 51 Purchase Invoice,
Form 52 Purchase Credit Memo,
Form 509 Blanket Purchase Order,
Form 6640 Purchase Return Order
A79) Missing update of Vendor Item No.
Error
A validation on Cross Reference No., doesn't update the Vendor Item No. This could lead to
inconsistencies between the Vendor Item No. and the Cross Reference No.

Table 39
A80) Allowed to post Undo Receipt even though there wasn't enough quantity
Error
The system didn't check available quantity on stock properly and allowed to post Undo Receipt
although Bin didn't contain enough quantity to cover this demand.

Codeunit 7301 Whse. Jnl.-Register Line
A81) Multiple use of same shortcut
Error
In Purchase Quote, Order and Invoice the use of ALT+O and ALT+P was used multiple times.

Form 49 Purchase Quote
Form 50 Purchase Order
Form 51 Purchase Invoice
Form 54 Purchase Order Subform
Form 55 Purch. Invoice Subform
Form 97 Purchase Quote Subform
24

A82) Charge computation provided rounding discrepancy
Error
When Charge (item) was posted a rounding problem occurred. The difference occurred in cases
where the foreign currency was used. However, it was a general problem in posting codeunit.

Sales and Marketing
A83) Ability to enter comments on sales lines. In addition, ability to save comments to
archived forms
Feature
Comments may be added for each line on all sales documents and then moved to posted documents.
Both header and line comments are posted to non-editable forms.
Table 37 - Sales Line

Table 111 - Sales Shipment Line
Table 113 - Sales Invoice Line
Table 115 - Sales Cr.Memo Line
Table 5107 - Sales Header Archive
Table 5108 - Sales Line Archive
Table 5126 - Sales Comment Line Archive
Form 41 - Sales Quote
Form 42 - Sales Order
Form 43 - Sales Invoice
Form 44 - Sales Credit Memo
Form 46 - Sales Order Subform
Form 47 - Sales Invoice Subform
Form 95 - Sales Quotes Subform
Form 96 - Sales Cr. Memo Subform
Form 130 - Posted Sales Shipment
Form 131 - Posted Sales Shpt. Subform
Form 132 - Posted Sales Invoice
Form 133 - Posted Sales Invoice Subform
Form 134 - Posted Sales Credit Memo
Form 135 - Posted Sales Cr. Memo Subform
Form 507 - Blanket Sales Order
Form 508 - Blanket Sales Order Subform
Form 5159 - Sales Order Archive
Form 5162 - Sales Quote Archive
Form 5180 - Sales Archived Comment Sheet
Form 6630 - Sales Return Order
Form 6631 - Sales Return Order Subform
Form 6660 - Posted Return Receipt
Form 6661 - Posted Return Rcpt. Subform
Codeunit 80 - Sales-Post
Codeunit 86 - Sales-Quote to Order
25

A84) Automatic archiving of sales quotes and sales orders
Feature
The user can define a setup option to automatically archive sales quotes as they are turned into sales
orders and archive sales orders when they are fully shipped.
Table 311 - Sales & Receivables Setup

Table 5107 - Sales Header Archive
Table 5108 - Sales Line Archive
Form 459 - Sales & Receivables Setup
Form 7188 - Sales Order Archived Subform
Codeunit 229 - Document-Print
Menusuite 10 - MBS
A85) Return Orders enabled for archiving
Feature
Return Orders can now be manually archived in the same way as other sales documents. Note:
Return Orders are also included in the Automatic Archiving described in A75).
Form 6630 - Sales Return Order

Form 6627 - Sales Return Order Archive
Form 6628 - Sales Return Order Archive Subform
Form 6629 - Sales Return List Archive
A86) Improved Balance drill-down from Customer Card
Feature
The drill-down from the Customer Card only shows the open ledger entries which support the
balance.
Table 21 - Cust. Ledger Entry
26

A87) Ability to print archived documents
Feature
Archived quotes, orders and return orders may be printed from the Archive forms.
Table 77 - Report Selections

Form 6627 - Sales Return Order Archive
Report 215 - Print Archived Purchase Quote
Report 216 - Print Archived Purchase Order
Report 418 - Print Archived Sales Return Order
Codeunit 322 - SalesCount-PrintedArch
Codeunit 365 - Format Address
A88) Posting Date default options
Feature
The posting date on entry documents can be defaulted to a blank value depending on the Sales &
Receivables setup.
Table 36 - Sales Header

A89) Quantity default options
Feature
The Quantity Remaining fields on sales lines can be set to a blank value as default instead of the
quantity remaining depending on the Sales & Receivables setup. This forces the user to decide how
much should be handled instead of accepting the full remaining quantity.
Table 37 - Sales Line

A90) Sales History from Customer Card
Feature
The sales history for a customer may be invoked from the Customer Card based on either the Bill-to
or Sell-to role for a customer.
Form 21 - Customer Card

27

Form 7171 - Customer Sales History
Codeunit 7171 - Sales Info-Pane Management
A91) Posting Date available in Posted Lines
Feature
The Posting Date document is also posted to the Posted Line tables for sales documents. This allows
for better detail reporting as well as the ability to view sales history by date.
Table 113 - Sales Invoice Line

Table 111 - Sales Shipment Line
Table 115 - Sales Credit Memo Line
Table 6661 - Return Receipt Line
Report 7181 - Update Posting Date in Docs is available for upgrade of existing documents.
A92) Sales quote number maintained in documents
Feature
The sales quote number is maintained in all posted documents which started with a quote.
Table 36 - Sales Header

Table 112 - Sales Invoice Header
Table 110 - Sales Shipment Header
Form 42 - Sales Order
Form 132 - Posted Sales Invoice
Form 130 - Posted Sales Shipment
A93) Error when the Correspondence Type was chosen for interaction without attachment.
Error
A run-time error occurred when the user tried to define the Correspondence Type for an interaction
which was being created based on an interaction template without an attachment.

Table 5077 Segment Line
A94) Out of range Customer Ledger Entries printed in Aged Accounts Receivable report
Error
The Customer Ledger Entry that was posted after the date specified in the Aged As Of field on the
Request form was printed in the Aged Accounts Receivable report. This occurred when the Due Date
28

of the entry was later than the date specified in the Aged As Of field and the Due Date value was
chosen for the Aging By option on the Request form.

Report 120 Aged Accounts Receivable
Report 322 Aged Accounts Payable

A95) Wrong error message when posting a sales order
Error
When posting a sales order with a posting date that was out of range, a wrong error message
occurred.

Code 80
A96) Forms with many sub-forms are not correctly exported to Excel
Error
When a form had several sub-forms, this form was not correctly exported to Excel. This issue was
caused by a problem on the XSLT sheet. This has been corrected by creating different names on
worksheets.

NavisionFormToExcel.xslt
A97) Error when Name/Company Details Updated for a contact
Error
An error message stating that another user has modified the record was displayed when the user
updated the information in the Name Details or Company Details windows for a Contact Card.

Form 5050 Contact Card
A98) Last Issued Reminder Level of On Hold Customer Ledger Entries was modified
Error
The Create Reminders and Suggest Reminder Lines batch jobs could not create reminder lines based
on overdue Customer Ledger Entries which contained a value in the On Hold field.
29

Moreover, when the user issued a reminder, with lines related to on hold overdue Customer Ledger
Entries, the value of the Last Issued Reminder Level field of these entries was modified. The program
created reminder entries for all reminder lines, although reminder entries should not have been
created for on hold overdue Customer Ledger Entries.

Codeunit 392 Reminder-Make
Codeunit 393 Reminder-Issue

A99) Reminder Lines created for Customer Ledger Entries from Valid Reminder
Error
When the Suggest Reminder Lines (or the Create Reminders) batch job was run without the Only
Entries with the Overdue Amounts check box selected, the system inserted reminder lines for
Customer Ledger Entries which had been included in previous reminders that were valid at the
document date of a new reminder. As a result, these entries were repeatedly considered during the
interest calculation and influenced the reminder level in the header.

Codeunit 392 Reminder-Make

A100) Reminder Ending Text Lines were in Not Due Reminder Lines
Error
When the Update Reminder Text batch job was run on a reminder and the number of the reminder
ending text lines was not the same as in the original reminder, the reminder ending text lines were
placed between the reminder lines of the Not Due type.

Table 295 Reminder Header
A101) Charge Computation Provided a Rounding Discrepancy
Error
When Charge (item) was posted the rounding problem occurred. The difference occurred in some
special cases if a foreign currency was used. This was a general problem in the posting codeunit.

30

A102) Error occurred if Nonstock item was set for Quote without Customer No.
Error
If a sales quote was created without a Customer No. (or a Customer Template Code) and the
Nonstock item was selected, an error occurred which could not be corrected. The program deleted the
wrong sales line in Object Designer only.

Table 37 Sales Line

A103) Incorrect number of contacts on Customer Information side panel
Error
The system showed an incorrect number of contacts on the Customer Information side panel of the
sales order, sales invoice, and sales quote.

Codeunit 7171 Sales Info-Pane Management,
Table 36 Sales Header
A104) Salesperson Code on quote not updated if customer was created from quote
Error
If you created a customer from a sales quote based on a contact number and a customer template,
the salesperson code on the quote was not updated accordingly.

Table 5050 Contact

A105) No message and no price update when check price including VA
Error
When you changed the Prices incl. VAT field on the Sales Header, this was not confirmed, which was
caused by a wrong filter on the Sales Line.


31

A106) Rating not updated automatically if Contact Answer Profile was updated
Error
When the answers were updated in the Contact Answer Profile window, the contact’s rating was not
updated accordingly

Report 5199 Update Contact Classification

A107) All co-related contacts were used when segment was created
Error
When the user added contacts to a segment using filters on the Value Entry tab in the Add Contacts
report, the system included all contacts of the Person type related to the customer/vendor company,
not just the contact defined in the Sell-to Contact field of the posted sales/purchase document.

Report 5198 Add Contacts
A108) Sales Order cannot be released
Error
By mistake a blank was used instead of FIND ('-') which meant that the Sales Order could not be
released.

Codeunit 414

A109) Comments not saved to Created/Postponed Interaction
Error
Comments attached to an interaction using the Create Interaction wizard were not saved in the
database when the user finished/postponed the interaction.

Table 5077 Segment Line
Form 5077 Create Interaction

32

A110) The system failed to create a pick document
Error
Calculation of the Quantity Reserved was doubled when calculating the Quantity Available to pick.

CodeUnit 7332
A111) General Ledger Expense Account in Job Posting Setup
Error
The General Ledger Expense Account in Job Posting Setup was not allowed to be blank.

Codeunit 1001 Job Post-Line

A112) Code that is commented out should be removed
Error
Code that had been commented out due to a correction, had forgotten to be removed.

TAB37, TAB339
A113) Wrong Unit of Measure when restoring a Sales Order
Error
When restoring an order with a different Unit of Measure than the default, it was still restoring with the
default Unit of Measure.

Codeunit 5063
A114) Contract General Ledger Journal Lines in Job Journal
Error
The Job Planning line that was created from a Job Journal line using Contract and General Ledger
Account type had an incorrect "Gen. Prod. Posting Group".
33


A115) Rounding problem occurred if item was set with Item Charge
Error
Rounding problem occurred if items were set with serial numbers and item charge on the same
invoice. The total amount of value entries was higher than the original amount.

A116) Overdue Amounts (LCY) miscalculated
Error
When a Customer or a Vendor Ledger Entry had a due date on the same date as the work date, the
entry was not included in the Overdue Amounts (LCY) field on the Customer/Vendor Statistics.

Table 21 Cust. Ledger Entry
Table 25 Vendor Ledger Entry

A117) Wrong phone number on invoice
Error
One invoice could get the phone number of the responsibility center of the previous invoice when
multiple invoices were printed.

Report 204 Sales - Quote
Report 205 Order Confirmation
Report 206 Sales - Invoice
Report 208 Sales - Shipment
A118) Get Posted Document Line to Reverse failed
Error
The check mark on Apply-from Entry is now limited only to Reservation Entries with Item Tracking set
to None.
34

COD99000832
COD99000834

A119) County Code in Company Information generated an overflow error
Error
If the County Code field in the Company Information table was set to any value and Special Order
was used, the function Carry Out AM from the Requisition Worksheet generated the following error
message: "Overflow under type conversion of Text to Code...value: Northamptonshire".

Table 38 Purchase Header
A120) Attendees not saved for a New Meeting To-do On Finish
Error
The system did not save attendees that were specified using the Create To-do wizard window when
the user clicked Finish. Furthermore, the user did not receive a descriptive message during the
creation of a new To-do of type Meeting with invitations.

Table 5080 To-do,
Form 5097 Create To-do
A121) Run-Time error when create to-do from To-do Card
Error
The run-time error occurred when the user tried to create a to-do from the To-Do Card window.

FORM 5098 To-Do Card
A122) Error message not displayed in Attachment field of Create To-do
Error
An error message was not displayed when the user tried to assign an attachment to a To-do based on
interaction template without an attachment in the Attachment field of the Create To-do wizard.
35

Table 5080 To-do
A123) Copy Document function didn't maintain Reservation field on Sales
Error
Although the Reserve field on the Item card was set to Always, the Copy Document function did not
create a reservation for the new line.

Codeunit 6620 Copy Document Mgt.
A124) Error Message replaced by error box with Identification fields
Error
The function showed wrong error message.

A125) Payment Method and zero invoices
Error
The system failed when trying to post a zero invoice with Payment Method.


A126) The shipped and invoiced sales orders weren't able to delete
Error
If a sales order contained an item line and two assigned item (charge) lines, the report deleted the
charge lines only.

Report 299 Delete Invoiced Sales Orders
36

A127) The application closed down if Item Available by Variant form was closed
Error
When trying to close the Item Availability by Variant and Item Availability by Location forms the whole
application closed down with an error. These forms were open in the Order Planning form.

Form 492 Item Availability by Location
Form 5414 Item Availability by Variant
A128) Error occurred if Nonstock Item was set for sales quote without customer
Error
If a sales quote was created without a Customer No. (or Customer Template Code) and the Nonstock
Item was selected, the application ended up with an error which could not be corrected. The program
deleted the wrong sales line in the Object Designer only.

Table 37 Sales Line
A129) Error when changing the Quantity for a Charge on Sales Order
Error
Updates to Item Charges are now made after Credit Limit and Availability checks have been made.
UpdateItemChargeAssgnt = f(Quantity, Line Amount / Unit Cost) and therefore it is reasonable that it
is invoked after UpdateAmounts has completed.
So, all calls to UpdateItemChargeAssgnt are made at the end of UpdateAmounts.

TAB37,
TAB39

A130) Synchronization failed if language was other than English
Error
Synchronization with Outlook failed when the application language selected in Microsoft Dynamics
NAV was other than English.
37

Codeunit 5300 Outlook Synch. Setup Mgt.
Codeunit 5302 Outlook Synch. Type Conversion
Table 5303 Outlook Synch. Filter
A131) Redundant update of Outlook item
Error
Redundant update of Outlook item occurred when the user synchronized the modified Outlook item
with Microsoft Dynamics NAV.

MessageParser.cs
A132) Synchronization Scheme with incorrect attribute in localized version
Error
During the export of the synchronization scheme in a localized version of Microsoft Dynamics NAV,
the data from the Read-Only Status field of the Outlook Synchronization field table was exported
incorrectly. This led to failure of the synchronization process.

Codeunit 5306 Outlook Synch. Export Schema
A133) Synchronization failed when application server was run with localized fin.stx
Error
An error occurred when the application server was run with the OSYNCH parameter and the localized
fin.stx file, because the hardcoded field name prevented from initializing the variable correctly.

Codeunit 448 Job Queue Dispacher

A134) Incorrect data in Outlook Synchronization field in localized versions
Error
Incorrect data in the Default Value field of table 5304 in localized versions of Microsoft Dynamics NAV
made synchronization from Outlook to Microsoft Dynamics NAV fail.

Codeunit 5300 Outlook Synch. Setup Mgt.
38

A135) Menu suite Item linked to non-existing report 5192
Error
When the user clicked the Patch Exchange Reference menu item on the navigation pane, an error
message appeared stating that Report 5192 did not exist.

MenuSuite 10 MBS
A136) To-do was not created for an updated opportunity
Error
The system did not create a to-do after an opportunity was updated.

Table 5093 Opportunity Entry

A137) Opportunity values not recalculated after update on Opportunity Card
Error
When an opportunity for a contact was updated from the Opportunity Card window the Calculated
Current Value (LCY) and Completed % fields were not updated accordingly.

Table 5093 Opportunity Entry

A138) Unapply and Dimensions
Error
Dimensions for unapplied entries would in some case be incorrect due to wrong filtering in the
unapply functionality


39

A139) Archive option on Sales/Purchase reports
Error
If you had the Archive Document granule the Archive Document option was automatically set to YES
on the reports. You had to set Archive Quote and Orders to YES in Sales & Receivables and
Purchase & Payables to get the option automatically set to YES.

Report 204
Report 205
Report 404
Report 405
Service Management
A140) Dimensions are copied to Service Ledger Entry from Invoice Header
Error
When the user created an invoice for a service contract, dimensions of the new Service Ledger entry
were copied from the invoice header.

Codeunit 408 DimensionManagement,
Codeunit 5940 ServContractManagement

A141) Shipment is posted for a customer blocked to ship
Error
When the Shipment on Invoice check box was selected in the Service Management Setup window, a
shipment was posted for a customer during the service invoice posting, although the Blocked field
was set to Ship in the Customer Card window.

Codeunit 5988 Serv-Documents Mgt.
A142) Error when Repair Status was changed on Service Item Line
Error
An error message appeared when the user changed the value of the Fault Reason Code field on a
Service Item line and then attempted to change the repair status on the same line, without removing
focus from this line, while the Fault Reason Code field was set to mandatory in the Service
Management Setup window.
40

Table 5900 Service Header
Table 5901 Service Item Line
A143) Wrong value in Service Ledger Entry when posting Service Contract Credit Memo with
discount
Error
Incorrect values were assigned to the Amount (LCY), Discount Amount, Discount % and Unit Price
fields of the Service Ledger Entry created after posting a Service Credit Memo which contained a
discount and was related to a contract.

Codeunit 5912 ServLedgEntries-Post,
A144) Incorrect Dimensions in Combined Invoice for contracts
Error
When the user created a combined invoice for several contracts with the same Bill-to Customer using
the Create Contract Invoices batch job, header dimensions of the new invoice were copied from the
first contract and line dimensions were retrieved from the invoice header.


A145) Default Dimensions not deleted when Service Item is deleted
Error
After deleting a service item, the default dimensions related to this service item were not deleted from
the Default Dimensions table.

Table 5940 Service Item

A146) Call of CONFIRM Function after starting write transaction
Error
If the user did not reply to a confirmation message that appeared when deleting a customer with
associated service items and was prompted to delete the customer number for the associated service
41

items, the customer related tables Customer Ledger Entry, Service Ledger Entry and Warranty
Ledger Entry were locked for posting.

Table 18 Customer
A147) Couldn’t wend e-mail from Service Order if e-mail not Company’s
Error
It was not possible to send an e-mail message from the Service Quote/Order window to an e-mail
address that differed from the customer’s company e-mail address.

Codeunit 397 Mail
Codeunit 5064 E-Mail – Logging
Form 5148 Create Mail
Form 5900 Service Order
Form 5964 Service Quote
A148) E-mail/Phone fields not updated if contact changed on Service Order/Quote
Error
When the user modified the Contact No. field in the Service Order or Service Quote window, the E-
mail and Phone No. fields were not updated correspondingly.

Table 5900 Service Header
A149) Resource Ledger Entry not created when post consumption
Error
Resource Ledger Entry was not created after posting consumption for a service line of the Resource
type and if a job number was not assigned to this line. However, it was possible to post consumption
for service line of type Cost and G\L Account.

Table 5902 Service Line,
Codeunit 5819 Undo Service Consumption Line,
Codeunit 5987 Serv-Posting Journals Mgt.,
42

A150) No Service Item No. in Service Ledger Entry when posting Credit Memo
Error
When the user created a service credit memo that was not related to a service contract and assigned
a service item to a service line, this service item number was not transferred to the Service Ledger
Entry after posting.

Codeunit 5912 ServLedgEntries-Post

A151) Not sufficient permissions to post service lines
Error
The user could not post service lines with items containing item tracking information because of
insufficient permissions.

Codeunit 5985 Serv-Item Tracking Rsrv. Mgt.
A152) Credit Memo Lines could not be re-created after deletion
Error
When the user deleted a credit memo that was created from a service contract for a certain contract
line, it was not possible to re-create another credit memo from this contract line again.

Table 5964 Service Contract Line
Form 6052 Service Contract Subform
A153) Granule permission error when posting Service Order
Error
An error occurred during the service order posting when the program referred to Codeunit 6080
Service Price Management which was not covered by the license.


43

A154) Error when user viewed Item Shipment Line for posted invoice
Error
An error occurred when the user tried to view Item Shipment lines for a posted invoice. The error
occurred due to the fact that the Posted Service Invoice window contained incorrect reference to the
Posted Service Shipment Line List window.

Table 5991 Service Shipment Line
A155) Error in Dimension Values check when posting service line
Error
A service line posting failed because the program referred to an improper table to check the
dimension values.

Jobs
A156) Positive Job Ledger Entry when posting Purchase Credit Memo
Error
The system created positive entries in the Job Ledger Entry table when posting a purchase credit
memo.

Codeunit 1004 Job Transfer Line

A157) Error when posting G/L Account Purchase Invoice Line for Job with Dimensions
Error
When the user posted a purchase invoice with a line of the G/L Account type, and a job with the
assigned dimensions was specified for this line, the posting failed with an error. This took place since
the program tried to copy dimensions for this line from an incorrect table.

44

A158) Permission on Update Job Item Cost
Error
Granule 4510 did not allow Report 1095 Update Job Item Cost to update Job Ledger Entries.
Permissions have been added to the report to allow this modification.

Report 1095 Update Job Item Cost
A159) No Sales Invoices were created for Job Task
Error
The Job Create Sales Invoice report did not create an invoice for a job task if the previously
processed job task had not required invoice creation.

Codeunit 1002 Job Create-Invoice

A160) Document created by Copy Sales Document was linked to Job Planning Line
Error
Sales document lines could contain invalid job-related data when the Copy Sales Document batch job
was run while the check mark in the Recalculate Lines field was cleared. As a result, new sales lines
could be linked to a Job Planning Line.

Codeunit 6620 Job Copy Document Mgt.
A161) Account Type and Job No.
Error
It was not possible to use any other Account Type than G/L Account in a General Journal Line with a
Job. No set. This restriction had also been implemented for Balancing Account Type.

Table 81 Gen. Journal Line

45

A162) Invoice posting failed if Job Line Dimensions were identical
Error
When the user tried to post a purchase invoice that contained more than one line of type G/L Account
with job numbers assigned to these lines, the posting failed if there were identical line dimensions.


A163) Quantity on Job Planning Lines
Error
Posting an item on a credit memo and connecting the line to a job, caused the quantity on the
resulting Job Planning line to be wrong.


A164) Posting Groups on Job Planning Lines of Type Text
Error
Posting Groups were not reset on Job Planning Lines when changing type to Text. Furthermore, if a
line was added after a Text line then the Currency Date was blank resulting in a currency problem.

Table 1003 Job Planning Line
A165) Rounding of Currency Amounts in Job
Error
The rounding of foreign versus local currency in a job did not match the rounding conventions used by
the sales invoice.

Table 1003 Job Planning Line

46

A166) External Document Number on Job Ledger Entries
Error
The External Document Number was not transferred when posting a sales invoice that originated from
a Job Planning line.


A167) Global Dimensions was missing on Job Ledger Entries
Error
Job Ledger Entries Global Dimension field was not filled from the sales invoices that originated from
the planning line.

A168) Job No. was not transferred from invoices to G/L Entry
Error
Sales/Purchase Invoice/Credit Memo did not transfer Job No. to G/L Entries generated. This only
works for G/L Entries generated from lines. G/L entries that are connected to the Customer/Vendor
Ledger Entry will not have a Job No.


A169) Job No. on Gen. Journal Line
Error
For performance reasons we have added a check mark in the validation code of the Job No. form on
the Gen. Journal Line to exit the code if nothing has been changed.

Table 81 Gen. Journal Line
VSA reference:
47

A170) Job Task Dimension to General Ledger Entries
Feature
We have implemented the possibility to set up dimensions on Job Tasks and transfer these to WIP
Entries generated in the General Ledger.

Codeunit 408 DimensionManagement
Codeunit 1000 Job Calculate WIP
Form 1002 Job Task Lines
Form 1003 Job Task Card
Form 1004 Job Task List
Form 1005 Job Task Dimensions
Form 1008 Job WIP Entries
Form 1009 Job WIP G/L Entries
Table 1001 Job Task
Table 1002 Job Task Dimension
Table 1004 Job WIP Entry
Table 1005 Job WIP G/L Entry
Table 1018 Job WIP Buffer
Inventory
A171) Change Average Cost period generated error
Error
A limitation on a variable caused an overflow of errors.

Table 313 Inventory Setup

A172) Wrong applied quantity in Application Worksheet
Error
The following error message appeared: 'Shipped Qty. Not Returned is too low in Item Ledger Entry.'
Now there will be no error message but the application will be displayed in the Applied Entries
TableBox after the first attempt to apply.

COD22
COD6620
FOR521
FOR522
TAB339
48

A173) No message if system cannot create a purchase return line
Error
Missing error message if the system could not create a purchase return line when using Get Posted
Document Lines to reverse when getting the receipt lines.

COD22
COD6620
FOR521
FOR522
FOR5855
TAB339
A174) Wrong error message
Error
You get a wrong error message when a full quantity of a purchase invoice line could be applied to a
purchase return order several times.

COD22
COD6620
FOR521
FOR522
FOR5855
TAB339
A175) Wrong datatype
Error
Quantity@1003 : Integer; changed to Quantity@1003 : decimal;

TAB339
A176) FEFO method is not always working
Error
FEFO method didn’t always work. This depended on the setup done at location level, because a filter
was set without checking the conditions first.

Codeunit 7312 Create Pick
49

A177) Item Card costs were used when data was exported to Excel
Error
The system used the Standard Cost and Last Direct Cost field values from the Item Card when
exporting data to Excel, if the Use Stockkeeping Unit checkbox was selected on the request form of
the Inventory Cost and Price List report.

Report 716 Inventory Cost and Price List
A178) Wrong unit price on purchase lines when using foreign currency
Error
The unit price was wrongly calculated when using a foreign currency.

TAB39
A179) Wrong adjustment when invoicing occurred after a revaluation
Error
A partial revaluation affected inbound entries that were already shipped but not invoiced before the
revaluation took place. Partial revaluation should only affect inbound entries that are in the inventory
at the time of the revaluation.

COD5895
A180) Adjusted Unit Cost on Item Card not updated when Qty = 0
Error
Whenever inventory quantity goes to zero and adjustment is run, the Unit Cost on the Item Card and
SKU will now be updated with the last outbound entry. The criteria for selecting the last outbound
entry will largely be based on the valuation date.

COD5804
50

A181) On the Inventory - G/L Reconciliation form, the Calculate function generates error
message
Error
A limitation on a variable caused an overflow error.

Codeunit 5845 Get Inventory Report

A182) Error on SQL on RENAME
Error
Table Relation incomplete for Variant Code Field in table 5847 Average Cost Calc. Overview - Error
on SQL on RENAME.

Table 5847 Average Cost Calc. Overview
A183) Balancing Inventory Accrual Account (Interim)
Error
When the expected cost of a revaluation is invoiced it must not have a General Business Posting
Group.

Codeunit 22

A184) GetInvtSetup function in table 27 was global
Error
The GetInvtSetup function was called from wrong codeunits although it should have been used only in
the Item table.

Table 27 Item

Codeunit 5845 Get Inventory Report

51

A185) Order Tracking didn't work if Sales Order was created from Sales Quote
Error
When a sales order was created from either a sales quote or order planning and when using the
Tracking Only option in the Order Tracking Policy field, then Order Tracking didn’t work.

Codeunit 86 Sales-Quote to Order
A186) Field Name in Item Availability form was incorrect
Error
The Item Availability Line form didn't show the correct name.

Form 99000902 Item Availability Line List
A187) Endless loop when adjusting an Average Cost Item
Error
This is caused by transfer entries that repeatedly re-open the Period to Adjust due to the forwarding of
cost for the outbound transfer entry to its corresponding inbound transfer entry. If there is a rounding
value that keeps being shifted around, then an infinite loop occurs.

COD5895
A188) Item Tracing report - Overflow error occurred
Error
Overflow error occurred in the Item Tracing report if the description was longer than 50 characters.

Report 6520 Item Tracing Specification
52

A189) Missing validation when using the "Apply template" feature
Error
Error when using "Apply template" feature because the validation is skipped. The design is now
changed so that the validation is only skipped when a new company is been set up.

Codeunit 8611

A190) Calculate Inventory in the Physical Inventory and Blocked Item
Error
If an Item is blocked it wasn’t possible to run the Calculate Inventory report.

Report 790
A191) Item Charge Specification report didn't show right amount from Value Entry.
Error
The report showed Item Charge with an empty amount which was based on the Cost Amount (Actual)
field in the Value Entry table. But right field should have been "Sales Amount (Actual)".

Report 5806 Item Charges – Specification
A192) Wrong parameter was set in Item Charge Assignment
Error
Function CreateDocChargeAssgn used wrong parameter.

Codeunit 5805 Item Charge Assgnt. (Purch.)
Codeunit 5807 Item Charge Assgnt. (Sales)
53

A193) Item Cross Reference description disappears
Error
Descriptions specified for Item Cross Reference records were deleted every time a Vendor Catalog
was updated.

Codeunit 5702 Dist. Integration
Fixed Asset
A194) Warning when you reverse Fixed Assets Ledger Entries
Error
A warning has been introduced to use the Cancel Entries function instead of the Reverse
Transactions function when correcting incorrect Fixed Assets Ledger Entries.

FOR179
A195) Fixed Asset Depreciation
Feature
It is now possible for the user to use the calendar year of 365 days, where each month has the same
number of days as in the calendar. The only exception is February in leap years, which is 28 days and
not 29. Because of that, all years, also leap years, are considered to have 365 days.
This new feature, ’365-days depreciations’, cannot be used in combination with ’Custom 1
Depreciation’.

TAB5611 Depreciation Book
TAB5612 FA Depreciation Book
REP5607 Fixed Asset - Projected Value
COD5610 Calculate Depreciation
COD5611 Calculate Normal Depreciation
COD5612 Calculate Custom 1 Depr.
COD5616 Depreciation Calculation
COD5617 FA Date Calculation
COD5618 Table Depr. Calculation
COD5642 FA Reclass. Transfer Line
54

Supply Planning
A196) Running Regeneration Planning caused loss of existing reservation
Error
Regeneration Planning removed existing reservations if item used Make-to-Order policy.

Table 99000853 Inventory Profile
A197) Requisition worksheet calculated wrong quantity for reordering policy order
Error
The suggestion of purchase in the requisition/planning worksheet was wrong if two sales orders used
the same date and the quantity of one was reduced.

Codeunit 99000854 Inventory Profile Offsetting
A198) Order Planning didn't respect Demand Type of calculation
Error
Although users set the filter in the Order Planning form (Demand Type), the system created a
temporary table for all types of demand. This led to a performance issue.

Codeunit 5520 Get Unplanned Demand
Codeunit 5522 Order Planning Mgt.
A199) After planning the inventory level was below reorder point
Error
The planning engine didn't check inventory after planning. In some cases the total quantity was below
the reorder point.

55

A200) The Replan function changed finished Operations
Error
The Setup Time was allocated although operation was finished.

Report 99001026 Replan Production Order
A201) Overflow of errors displayed if we tried to reschedule Production Order Line
Error
An overflow of errors occurred when we tried to reschedule the production order line. This happened if
the combination Capacity UoM = Days, Send-Ahead Quantity field was used and direction was
Forward.

Codeunit 99000774 Calculate Routing Line
A202) Transfer posting was allowed even though there was no stock
Error
When a reclassification was made to the same location and variant, the outbound part of the transfer
tried to use the inbound part of the transfer as its source.
The correction ensures that the only application that can supply to an outbound Transfer Item Ledger
Entry must occur before the entry. This is done by comparing the entry numbers.

COD22
A203) Planning didn’t suggest lines for all SKU’s
Error
Requisition worksheet planned a new supply for the first location in the location list only.

56

Item Tracking
A204) Item Tracking availability information was incorrect
Error
Item tracking information was wrong when you tried to close the Item Tracking Lines form.

Codeunit 6501 Item Tracking Data Collection
A205) Microsoft Dynamics NAV didn't allow to choose serial number for Receipt of Transfer
Error
If item of transfer contained item tracking and quantity was shipped gradually the receipt could be
done only for the first quantity. The system didn't allow users to enter another Item Tracking number.

Codeunit 99000836 Transfer Line-Reserve
A206) Item tracking error when Order Tracking Policy was blank
Error
The program did not synchronize the item tracking for the shipment line with the item tracking for the
receipt line that is created when the order tracking is set.

Report 7391 Whse. Get Bin Content:
A207) Modifying quantity in Credit Memo caused error in posted document
Error
A Credit Memo could be posted with a quantity that differed from the quantity that was set for item
tracking. It led to problems in Value Entries.

Codeunit 99000834 Purch. Line-Reserve
A208) Overflow Error occurred when running Item Tracing
Error
Error was showed in the Item Tracing window, when using Tracing. The problem occurred because
the Description was created from more text strings.
57

Codeunit 6520 Item Tracing Mgt.
A209) Item Tracking Lines show excess quantities after posting
Error
The purchase order had the wrong Reservation Status assigned. This meant that the purchase order
was not recognized in the routines that handle these reservation entries after the posting of the
purchase order.

Codeunit 6500 Item Tracking Management
Codeunit 7324 Whse.-Activity-Post

A210) You couldn't state Item Tracking on Demand with Order-to-Order Binding
Error
For supplies that were linked to an original demand, the item tracking information that was created on
the supply side was not getting copied to the demand side. This resulted in a mismatch of the item
tracking information. This copying has now been implemented for Order-to-Order binding.

Codeunit 99000830 Create Reserv. Entry
Warehouse
A211) Inventory Pick was created although Shipping Advice was complete
Error
Inventory Pick was created from a sales order although one item wasn't on inventory and Shipping
Advice was set to Complete.

Codeunit 7322 Create Inventory Pick
58

A212) Calculate Inventory Adjustment doesn't respect different UoM
Error
In Calculate Warehouse Adjustment report, Unit of Measure is not taken into account while calculating
the quantities on the Adjustment Bin. In fact, only the Base Unit of Measure is used to create the item
journal lines. Thus the adjustment bin could not be cleared successfully if a unit of measure different
from the base unit of measure is used.

Report 7315 Calculate Whse. Adjustment
Table 83 Item Journal Line
A213) Couldn’t delete Warehouse Activity Lines in a SQL 5.0 database
Error
The system attempted to delete the line twice and ran on an error while doing so.

Table 5767 Warehouse Activity Line

A214) Posting a partial Sales Inventory Pick with item tracking
Error
When you post a partial Sales Inventory Pick with item tracking, the Quantity to Invoice (Base) field in
the Item Tracking line has an incorrect value. This is caused by an unneeded update on the
Reservations Entries when the pick is posted.

Code Unit 6500
Code Unit 7324

A215) Posting with same bin code on different locations is not working
Error
If the same bin number was used in two different locations, the locations were tested wrongly.

Table 83
59

A216) The Block Movement field could be set for a non WMS location
Error
No check present to establish the fact that the location uses Directed Put-away and Pick before
entering a Block Movement tag on a Bin.

TAB 7354 Bin
Application
A217) Menu button control was visible in strange position
Error
The menu button should have been hidden during resizing of the form.

Form 6510 Item Tracking Lines
A218) Wrong character filter
Error
A character filter for upper-case characters did not filter to get all characters.

Codeunit 400
VSA reference: SRZ07061500034
A219) Maxvalue of Profit % was too high
Error
Maxvalue of the Profit% field in these tables were out of proportion.

Table 27 Item
Table 99008505 Inbound Product Catalog Line
60

A220) Incorrect filter on DateTime field
Error
The reason for the different behavior of SQL Server and the Classic client is that the SQL database
doesn’t support 1 millisecond granularity for the date/time type.
To resolve this issue the MakeDateTimeFilter2() function in Codeunit 1 should be changed. We have
to change 235959.999 time to 235959.995 time.
Old code:
MakeDateTimeFilter2(VAR DateTimeFilterText : Text[250])
…
DateTimeFilterText := FORMAT(CREATEDATETIME(Date1,000000T)) + '..' +
FORMAT(CREATEDATETIME(Date1,235959.999T),0,1);
New code:
MakeDateTimeFilter2(VAR DateTimeFilterText : Text[250])
…
IF TempGLSetup.RECORDLEVELLOCKING THEN
FORMAT(CREATEDATETIME(Date1,235959.995T),0,1)
ELSE
FORMAT(CREATEDATETIME(Date1,235959.999T),0,1);

Codeunit 1

A221) Zero amount on check
Error
When you generate a Payment by Check through the Payment Journal and print it, then the amount
printed is zero and the line inserted to manage the check is zero as well.


A222) SQL Index removed
Error
SQL index removed on 72 tables to avoid extra overhead on the server central processing unit for
sorting.

TAB110
TAB111
61

TAB112
TAB113
TAB114
TAB115
TAB120
TAB121
TAB122
TAB123
TAB124
TAB125
TAB169
TAB203
TAB21
TAB246
TAB25
TAB254
TAB271
TAB272
TAB32
TAB337
TAB36
TAB37
TAB379
TAB38
TAB380
TAB39
Tab5405
TAB5406
TAB5407
Tab5409
Tab5410
Tab5414
Tab5415
Tab5416
TAB5741
TAB5745
TAB5747
TAB5765
TAB5766
TAB5767
TAB5772
TAB5773
TAB5802
TAB5832
TAB5900
TAB5901
TAB5964
TAB5965
TAB7310
TAB7311
TAB731
TAB7317
TAB7318
TAB7319
TAB7321
TAB7322
TAB7323
TAB7326
TAB7332
62

TAB7334
TAB7340
TAB7341
TAB7342
TAB7343
TAB81
TAB83
TAB99000829
TAB99000830
Outlook Integration
A223) No conflict in Outlook for deleted NAV contact after full synchronization
Error
A conflict was not processed in Outlook Add-In when a synchronized contact was deleted from the
Microsoft Dynamics NAV database and the subsequent Full Synchronization action was performed.

Microsoft.Dynamics.NAV.OLSync.NAVSyncAddIn.dll,
Microsoft.Navision.CFront.CFrontDotNet.dll
A224) Outlook Synchronization does not work
Error
Outlook Synchronization does not work after latest changes in C/FRONT. Synchronization just silently
stops.
Problem: AddIn makes sequential DBL_ConnectServerAndOpenDatabase()calls without

DBL_CloseDatabase(). This leads to TERMINATE inside cfrontsql.dll that correspond on latest
multithreading changes in C/FRONT. It is not documented that the client application can’t do this, but
this behavior seems to be logical.

Microsoft.Dynamics.NAV.OLSync.NAVSyncAddIn.dll
VSA reference:
A225) Runtime error if e-mail provider for Outlook is not Exchange
Error
When the user tried to send an e-mail from Microsoft Dynamics NAV, a run-time error occurred when
an e-mail transport provider in Outlook was other than Exchange.

OLHandler.dll
63

A226) E-Mail logging failed under application server
Error
It was not possible to either set up or to run the E-Mail Logging functionality under the application
server.

Codeunit 5064 E-Mail – Logging
Codeunit 5065 E-Mail Dispatcher
A227) Sales Order Confirmation title not present in Word document
Error
The style sheet for orders had an element referencing quotes.

SalesorderConfirmationToWord.xslt
A228) Fields not mapped to Outlook collection of categories
Error
Outlook Add-In did not map Microsoft Dynamics NAV fields to the Outlook collection of categories.

MapiHelper.dll, Microsoft.Dynamics.NAV.OLSync.NAVSyncAddIn.dll,
Microsoft.Navision.CFront.CFrontDotNet.dll
A229) Incorrect Memory Management of Outlook Add-In crashes Outlook
Error
Outlook crashed during synchronization because the memory that was allocated for the MAPI
structure that was populated with the meeting recipients, was released before the work with this
structure was finished.

MapiHelper.dll
64

A230) Synchronization error if two or more Windows Logins were used in Microsoft Dynamics
NAV
Error
If two or more Windows Logins had been created in Microsoft Dynamics NAV, the system could check
permissions for the wrong user when performing the synchronization. As a result, an error occurred.

Codeunit 418 Login Management,
Codeunit 449 Job Queue Start Codeunit
VSA Reference: 8855626

KB Article Reference: 936064
A231) Outlook synchronization failed with an error on Windows Vista
Error
When the user ran the Outlook synchronization on Microsoft Vista, a run-time error was raised and
the synchronization failed.

Codeunit 5306 Outlook Synch. Export Schema
HashCalculator.cs
Common.cs

Integration
A232) Misleading error messages from CGRequestClient
Error
When a user put the wrong schema name on the Commerce Gateway setup, or a partner wanted to
use the CGReqClient in a customize manner, the system did not give proper feedback in case of a not
well-formed schema.

CGReqClient40.dll
65

Mobile
A233) Mobile functionality in Microsoft Dynamics NAV
Feature
Microsoft Dynamics NAV 5.0 SP1 includes mobile functionality so mobile users can interact with
Microsoft Dynamics NAV using Microsoft Dynamics™ Mobile 2008 – Mobile Sales from a mobile
device.
Microsoft Dynamics Mobile 2008 provides customers with mobile access to the same line of business
applications that they rely upon in the office while away from the office. Microsoft Dynamics Mobile
2008 consists of a Mobile Sales application and Mobile Development Tools that includes Server
Components and Framework Components to enable customers and partners to create and run mobile
solutions.
Microsoft Dynamics NAV 5.0 SP1 contains the integration components for Mobile Sales and Mobile
Development Tools - Server Components to support the Mobile Sales scenario. For more information,
see the documentation (mobile.chm).
Note that to have full advantage of the functionality you also have to acquire Microsoft Dynamics
Mobile 2008.
This has been changed

Codeunit 1 ApplicationManagement
Codeunit 2 Company-Initialize
Form 42 Sales Order
Form 5086 Campaign Card
MenuSuite 10 MBS
Table 18 Customer
Table 27 Item
Table 5071 Campaign
Table 5080 To-do
Table 5199 Attendee
This has been added

Codeunit 8700 Mobile Document Dispatcher
Codeunit 8701 Mobile Document Management
Codeunit 8702 Mobile Queue Processor
Codeunit 8703 Mobile Document Handler
Codeunit 8704 Mobile XML DOM Management
Codeunit 8705 Mobile Permission Management
Codeunit 8725 Mobile Sales Document Handler
Codeunit 8726 Mobile Sales Management
Form 8700 Mobile Users
Form 8701 Mobile Groups
Form 8702 Mobile Group Users
Form 8703 Mobile Document Groups
Form 8704 Mobile Document Types
Form 8705 Mobile Document Queue List
Form 8706 Mobile Languages
Form 8707 Mobile Users Windows Login
Form 8708 Mobile Option Field Setup
66

Form 8709 Mobile Option Fld. Cptn. List
Form 8710 Mobile Document Schemas
Form 8711 Mobile Document Type Schemas
Form 8712 Mobile Schema Document Types
Form 8713 Mobile Field List
Form 8725 Mobile Sales Setup
Form 8726 Mobile Order Signature
Report 8700 Mobile Document Processor
Report 8701 Mobile Option Translation
Report 8725 Mobile Create Customer Price
Report 8726 Mobile Sync. To-do/Activity
Table 8700 Mobile User
Table 8701 Mobile Group
Table 8702 Mobile Group User
Table 8703 Mobile Document Group
Table 8704 Mobile Document Type
Table 8705 Mobile Document Queue
Table 8706 Mobile Language
Table 8707 Mobile User Windows Login
Table 8708 Mobile Option Field Setup
Table 8709 Mobile Option Field Caption
Table 8710 Mobile Document Schema
Table 8711 Mobile Document Type Schema
Table 8725 Mobile Sales Setup
Table 8726 Mobile Customer Price
Table 8727 Mobile Sales Activity
A234) Documentation for Mobile functionality in Microsoft Dynamics NAV
Feature
The functionality is described in a Help file, mobile.chm, which is available in English (US) only. The
mobile.chm file provides guidance for how to set up mobile functionality in Microsoft Dynamics NAV.
The mobile.chm file installs with the application help. The default location is C:\Program
Files\Microsoft Dynamics NAV5\CSIDE Client\ENU. Note that the Help is not F1 enabled, and that the
mobile.chm file is not part of the application Help.
Manufacturing
A235) Automatic Cost Adjustment is invoked by wrong criteria
Error
When the Inventory Posting routine uses the posting date of the Quantity Movement instead of using
the Valuation Date of the new entry that is being posted, Automatic Cost Adjustment is invoked by the
wrong criteria.
67

COD22.TXT
A236) Detailed Calc. report showed wrong value for item without BOM
Error
If an item didn't have the BOM defined, the Detailed Calculation report showed the previous value
although it should have been zero.

Report 99000756 Detailed Calculation
A237) Calculation of Low-Level Code was wrong
Error
The batches which calculated Low-Level Code of items differed from each other. None of them
worked properly if the BOM structure contained the item with Closed BOM.

Codeunit 99000793 Calculate Low-Level Code
Codeunit 99000853 Calc. Low-level code
A238) Compare List report didn't check dates of component
Error
The Compare List report also showed components which were not valid (they used Starting Date
and/or Ending Date).

Codeunit 99000771 BOM Matrix Management
A239) Due Date for Family on Production Order was changed when refreshing
Error
When refreshing a production order for a family, the due date was updated to reflect the inbound
warehouse handling time that was listed on the location card, but the ending date was not updated.

Table 5405 Production Order
Report 99001025 Refresh Production Order
68

A240) Some fields weren't refreshed if you used Copy Production Order Document
Error
When the user used the Copy Production Order Document function, some fields in the production
order line were not updated properly.

Report 99003802 Copy Production Order Document
A241) Overflow error displayed if we tried to reschedule Production Order line
Error
Overflow error showed up when we tried to reschedule a production order line. This happened if the
combination Capacity Unit of Measure = Days and Send-Ahead Quantity fields was used.

A242) Update Unit Cost Option checkbox didn't work
Error
There was a difference between the Update Unit Cost batch (the production order) and the Update
Unit Cost Option checkbox when the status of a production order was changed.

Codeunit 5407 Prod. Order Status Management
A243) The operation couldn't be changed if schedule was set manually
Error
In some cases the operations could not be scheduled manually.


69

A244) System error 2146823282 occurred when saving Production Schedule
Error
The application returned an error and closed the Production Schedule.

XMLPort 5506 Export Prod. Sched. Conflicts

A245) Production Schedule displayed error if Description of Routing contained characters not
allowed
Error
Description of Routing contained characters which were not allowed, such as &, < and >

XMLPort 5500 Export Production Schedule

A246) Bin Code Used Default Value instead of Value from POLine
Error
When user created output/consumption line manually then Bin Code was set to default Bin instead of
value from prod.order line/component.

A247) Output Line contained wrong dimensions
Error
If lines were added manually in an Output Journal for Production Orders which contained dimensions,
the dimensions were not be assigned correctly.

Codeunit 408 DimensionManagement

70

A248) No availability check in Production Journal if component appeared more than once
Error
If a production order contained more than one line and some components were used more than once,
the posting of consumption via Production Journal did not check availability of this item.

Codeunit 5510 Production Journal Mgt
A249) Posting a consumption for backward flushing didn't check availability
Error
Negative inventory occurred for backward flushed items when the same component was defined more
than once on a released production order. The system didn't check item availability.

Codeunit 22 Item Jnl.-Post Line
A250) Wrong Remaining Quantity when Post Consumption with different item tracking
Error
When posting consumption for a Production Order Component line where item tracking has been
specified for the component, an error occurred in the calculation of the new remaining quantity on the
component line.


A251) Error occurred if user ran statistics in production order with non item line
Error
The error 'Item No. xxx does not exist' appeared when user ran statistics on a production order with a
non Item line.

Codeunit 5836 Cost Calculation Management
71

A252) Allocated Time field in Production Order Capacity Need table wrong
Error
The Allocated Time field (Production Order Capacity Need table) was calculated incorrectly if routing
contained different Cap.Unit of Measure Code, although the value should have been stored in
minutes.

Codeunit 5407 Prod. Order Status Management
Codeunit 99000810 Calculate Planning Route Line
A253) A changed line in Order Planning wasn’t saved
Error
Changes which were made in the requisition line on the Order Planning form were not saved to the
table and disappeared.

Form 5522 Order Planning
A254) Inventory Pick couldn't be posted partially if component used item tracking and
reservation
Error
When a user partially posted an Inventory Pick for a production order component, which used item
tracking and reservation, the remaining quantity of the pick could not be posted.

A255) Wrong initial cost shares in the Standard Cost Worksheet
Error
Previously, when a user entered a new Standard Cost on the worksheet, the value was assumed to
be completely material. In the correction, the value of the new standard cost will be spread out to the
various cost shares using the same ratios as the original standard cost.

TAB5814
72

A256) Nos. Series didn't work properly if a new work center was created
Error
Some tables didn't use Nos. Series logic properly and didn't allow the user to create a new record.

Table 99000753 Work Center
Table 99000758 Machine Center
Table 99000763 Routing Header
Table 99000771 Production BOM Header
Table 99000779 Production BOM Version
Business Analytics Basic
A257) Business Analytics on named instance of SQL
Error
Business Analytics on named instance of SQL - only worked if the NAV database was on the default
instance.

Table700
A258) Configurator fails if illegal characters are used in names
Error
Analysis Services 2005 dimension names cannot contain characters that are illegal in Windows file
names. When analytical dimensions are created, a hidden intermediate dimension has to be created
that is named as a derivation of the fact table name, for example “LedgerEntryDimensionG/L Entry”
where “/” (slash) is the illegal character.
Resolution:
All Analysis Services 2005 dimension names are now checked for illegal characters and renamed
accordingly. Illegal characters are:? [ ] / \ = + < > : ;

Configurator.exe
73

Development Environment and Database Changes
SQL Server Option for Microsoft Dynamics NAV
P1) SIFT including Indexed Views
Feature
Microsoft Dynamics NAV now uses "Indexed Views" to maintain SIFT totals. Indexed views are a standard
SQL Server feature. An indexed view is similar to a normal SQL Server view except that the contents have
been materialized (computed and stored) to speed up the retrieval of data. For more information about
indexed views, see SQL Server Books Online.
Microsoft Dynamics NAV creates one indexed view for each SIFT key that is enabled. When you create a
SIFT key for a table, you must set the MaintainSIFTIndex property for that key to Yes to enable the SIFT
key and create the indexed view. Once SQL Server has created the indexed view, it maintains the contents
of the view whenever any changes are made to the base table. If you set the MaintainSIFTIndex property
for that key to No, SQL Server drops the indexed view and stops maintaining the totals.
The indexed view that is used for a SIFT key is always created at the most finely-grained level. Therefore, if
you create a SIFT key for AccountNo.,PostingDate, the database will store an aggregated value for each
account for each date. This means that in the worst case scenario, 365 records must be summed to
generate the total for each account for a year.
This feature has been implemented
P2) Bulk Insert
Feature
Microsoft Dynamics NAV automatically buffers inserts in order to send them to SQL Server in one go.
By using bulk inserts, Microsoft Dynamics NAV reduces the number of server calls thereby improving
performance.
It also improves scalability by delaying the actual insert until the last possible moment in the transaction.
This reduces the amount of time that tables are locked; especially tables that contain SIFT indexes.
Application developers who wish to write high performance code that uses this feature should understand
the following constraints outlined.
If you want to write code that uses the bulk insert functionality, you must be aware of the following
constraints:
Records are sent to SQL Server:
• When you call COMMIT to commit the transaction.

• When you call MODIFY or DELETE on the table.
• When you call any FIND or CALC methods on the table.
Records are not buffered if any of the following conditions are met:
• The application is using the return value from an INSERT call.

For example, "IF (GLEntry.INSERT) THEN"
• The table you are going to insert the records into contains BLOB fields.
74

• The table you are going to insert the records into contains Variant fields
• The table you are going to insert the records into contains RecordID fields.
• The table you are going to insert the records into contains fields with the
AutoIncrement property set to Yes.
Platform
3. Deletion of selected lines on form was impossible
Error
The issue is related to the fact that the form showed temporary records.
To fix this bug a call of the OnFindRecord trigger where the parameter equals “=” was introduced.
These changes extended the functionality and required changes in documentation. For example,
OnFindRecord couldn’t receive “=” as a parameter.

fin(sql).exe
4. Function names in C/FRONT import/export have been changed
Feature
Changes are:
- DBL_WriteObjects --> Should be now: DBL_ImportFOB

- DBL_ReadObjects --> Should be now: DBL_ExportFOB
- WriteObjects --> Should be now: ImportFOB
- ReadObjects --> Should be now: ExportFOB

cfront(sql).dll; cfront.net
5. Memory is leaking on COM callbacks
Error
For example, the AL_tagVariant has a destructor that cannot be derived from OM_NewDelete.
AL_tagVariant leaked because destructor wasn’t called.

fin(sql).exe; nas(sql).exe
75

6. Data does not restore into the Company Table
Error
Microsoft Dynamics NAV should not skip the data from the Company table when restoring.
The data from the restore resource that corresponds to the Company table should be added to the
database by the Modify function, such as the Company table, which is created in the beginning of the
restore process.

fin(sql).exe
7. Pictures shown upside down on reports
Error
Image scaling was changed to avoid rotation.

fin.exe, finsql.exe
8. Dataport property ReqFilterHeadingML is not imported
Error
Dataport property ReqFilterHeadingML was not imported after fixing NAV searches translations of the
MLReqFilterHeading option and imports them.

fin(sql).exe
9. Subform isn’t updated if the record on form changes
Error
The problem is that if a subform’s record depends on the value of the form’s record then the subform
isn’t updated if the form’s record changes its value.
In the proposed solution we check whether the version of the current form’s element had changed
after executing the OnValidate trigger. If it had changed, then we load the form’s current element. This
lead to the execution of the OnAfterGetRecord and OnAfterGetCurrRecord triggers.

fin(sql).exe
76

10. Dialog font corrupted in full screen text mode
Error
Dialogs font corrupted when the program started from the command prompt in the Full Screen Mode.
Font initialization in full screen text mode is now handled separately.

fin.exe, finsql.exe
11. About Box did not comply with LCA
Error
As requested by LCA, the order of the about box is now:
Product Name/version
Copyright notice
Licensee information
Warning

fin.exe, finsql.exe
12. CalcFields will fail if either too many filters or disabled
Error
1. The calculated SIFT key doesn’t necessarily contain all fields in the specified filter. In this
case we need to revert to getting the sum from the basetable.
2. The amount of calculated fields requested in CalcSums or CalcFields call can be greater than
the maximum number of SUM fields on a key. The internal structure used by the new SIFT sub-
system was not able to handle this situation so we got a buffer overrun. This has been corrected to
have a dynamically allocated buffer.

finsql.exe, ndbcs.dll
13. Copy and paste in Excel from matrix form
Error
The issue is related to the fact that the form shows temporary records.
To fix this bug a call of the OnFindRecord trigger where the parameter equals “=” was introduced.
These changes extended the functionality and required changes in documentation. For example,
OnFindRecord couldn’t receive “=” as parameter.

fin(sql).exe
77

14. Client will crash on certain stack overflows
Error
Stack overflow checking was changed.

fin.exe, finsql.exe
15. Right Cross References weren't created in 5.0 for Customer/Vendor
Error
If the Cross Reference Type was Customer/Vendor, then the record didn't contain the value in "Cross
Reference Type No." field. The record couldn’t be used later in Sales/Purchase.

Table 5717 Item Cross Reference
Clarify reference: 8903935
16. Microsoft Dynamics NAV crashes on exit
Error
Dummy functionality was removed from TempororyFileMap class.

17. Alternative startup screen was added for Entrepreneur
Feature
The Splash Screen was reintroduced. In order for it to appear, we needed the following line defined in
the stx:00200-00500-080-0: Yes

fin.exe, finsql.exe
18. COMMIT in a Single Instance Codeunit commits data that should not have been
committed
Error
If you have a Single Instance Codeunit which does a COMMIT while you run a report that updates
data, then the COMMIT function commits data while the report is printing even if the report later gets a
runtime error.
78

fin.exe, finsql.exe, nas.exe, nassql.exe

KB reference: 942215
19. Records will get cleared on every line in dataports
Error
The code cleared the record every time it completed an import, which made it impossible to reuse the
primary keys.

fin.exe, finsql.exe
20. GETVIEW will get an internal error when the length is too big
Error
GETVIEW command generates "Internal Error 1037 in Module 19" error when length exceeds 900
bytes. The error message was modified, so that it does not contain the Maximum size.

fin.exe, finsql.exe
21. A crash using recordRef + CalcField was corrected
Error
recordRef and Calcfield were corrected to prevent a reference to a NULL pointer, which was causing
the crash.

finsql.exe, nassql.exe
22. The Application Server crashed because of lack of resource
Error
Module - error message is displayed

fin.exe,
finsql.exe
nas.exe
nassql.exe
fin.etx
79

23. Permissions for the User Default Style Sheet table were not added
Error
We have to grant appropriate permissions for the User Default Style Sheet table.

NDBCS.DLL,
finsql.exe
24. Cannot rename a customer from blank
Error
We get this problem because it should not be allowed to create records with empty code fields if these
fields are referenced by some other fields in another table.
The problem has been fixed so that the program doesn’t allow renaming a field to a blank in the case
described above.

finsql.exe
Clarify Reference: SRZ071026000347

KB Article Reference: 945339 and 945340
25. Message ‘Record does not exist’ even when the record is there
Error
After implementing record links, the program deletes all record links if the record is deleted. The
problem is that the DeleteRecLinks function cleans all allowed errors. This problem has been fixed so
that the program now restores allowed errors after the record links are deleted in the DeleteRec
function.

fin(sql).exe
26. Multi Language Text constants have been increased
Error
The AttStr was virtually increased without changing the static size, in order not to "disturb" the rest of
the machinery. Dynamically allocated chunks of memory are re-used every time a new compilation is
done.
80

fin.exe, finsql.exe
27. BigText variables memory leaks
Error
After fix memory is cleaned when trigger is out of scope or CLEAR(Bigtext) is called.

28. COPSTREAM cannot be used on the same BLOB
Error
When in- and out-streams are connected to the same source we get an endless copying cycle. To
prevent this, check that Forbid Copying is added, so if the source is the same, the program terminates
this command.

fin(sql).exe, nas(sql).exe
29. The Application Server reported many messages when closing down
Error
The NAS was not exiting completely clean when it was stopping. This was due to a code change
made to try to resolve a small issue in 4.00 SP3 update 4. This fix was giving us problems, so it has
been reverted.

nas.exe, nassql.exe
30. NATHash.dll crashed when using GetNextStringPortion
Error
The problem was that the size of pTempBuffer variable will return size of pointer which is 2, but what
is intended is to put the size of the buffer. We have change the size of the initialization and the
copying of the pTempBuffer variable. An internal arithmetic buffer operation has been corrected.

NATHash.dll
81

31. Records are now cleared when importing via dataports
Error
The record is cleared out on every loop. However, the indexes are never cleaned out, as this can
introduce problems like in 25889.

fin.exe finsql.exe
32. GetRange usage with different Filter Groups
Error
C/SIDE GetRangeMax and GetRangeMin throw an exception when different Filter Groups are used.

modules\db\filter.cpp,
modules\dbcli\tables.cpp
fin.exe, finsql.exe, nas.exe, nassql.exe
33. Microsoft Dynamics NAV crashes after PC hibernation
Error
The program crashes when your PC wakes up from hibernation. The hibernation functionality is
turned off to avoid a crash. Then it will not reconnect to SQL Server. This will have to be done
manually.

fin.exe, finsql.exe
Clarify Reference: SRZ070719000095
34. Support for .dwg file type
Error
It was not possible to add the .dwg file type to the fin.stx file. We have now add .dwg to the fin.stx.

fin.stx
82

Office Integration
35. Child triggers execute when a parent table has got no record
Error
Child elements shouldn’t be serialized if the creation of a new element was unsuccessful.

fin.exe; finsql.exe;
Development Environment
36. Format example is wrong – C/SIDE online Help
Error
The FORMAT algorithm was changed for the Boolean type to match the C/SIDE online Help.

fin(sql).exe, nas(sql).exe
Tools
1. Decimal not used correctly in Office integration
Error
When evaluating decimal values, the value of the decimal separator changed according to the current
regional settings.

COD8611
2. Imported records not updated if assigned by number series
Error
The records imported to Microsoft Dynamics NAV from an Excel file were not updated with data from
a master template when the user clicked Apply Migration Data in the Migration Overview window, if
the primary key numbers for the imported records were automatically assigned by number series.

Form 8614 Migration Overview
83

Codeunit 8611 Migration Management

3. Job No. on Archive Order tables
Error
Job No. was not removed from archive sales/purchase headers

Codeunit 104045 Upgrade 5.00 Step 1

Navision ODBC Driver
37. DBQ "View File Directory" settings were added
Error
For the configuration dialog the DataBase Qualifier (DBQ) parameter was added to the ODBC data
source setup.

nodbccfg.cfg
C/FRONT
38. CFront.OCX data conversion error when assigning a BLOB
Error
1) Variant variable type was converted to the type that C/FRONT expects to receive.
2) DBL_Exit was corrected to succeed in cases where the database was not closed and there were
references to the database objects.

cfront.dll; cfrontsql.dll; cfront.ocx

84

Changes in NAV 5 0 SP1

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Changes in NAV 5 0 SP1

Încărcat de

Drepturi de autor:

Formate disponibile

ø

Microsoft Dynamics™ NAV

Changes Made in Microsoft

This document describes the changes between Microsoft

Date: March, 2008

Development Environment and Database Changes....................74

CHANGES MADE IN MICROSOFT DYNAMICS™ NAV W1 5.0 SP1

A1) Error when inserting, renaming, and deleting Accounting Periods

This has been corrected

VSA reference: 8900879

A2) Adjust Exchange Rate with Start Date

This has been corrected

VSA reference: 8992259

A3) Inter Company deadlock

This has been corrected

Clarify reference: SRZ070703000130

A4) Unrealized VAT was not Realized for applying entries

CHANGES MADE IN MICROSOFT DYNAMICS™ NAV 5.0 W1

Clarify reference: 8997697

A5) Posting Group in Un-apply

This has been corrected

VSA reference: 8979108

A6) Menu Suite had Points for Missing Reports

This has been corrected

VSA reference: 9006376

This has been corrected

Clarify reference: SRZ070507000246

A8) Not possible create accounting period in a new company

CHANGES MADE IN MICROSOFT DYNAMICS™ NAV W1 5.0 SP1

VSA reference: 8858416

A9) Intercompany Duplicate Postings

This has been corrected

Clarify reference: SRZ070212001944

A10) Blocking on Analysis View

This has been corrected

Clarify reference: SRZ070914000225

A11) Blank Statement Line No.

This has been corrected

Clarify reference: SRZ070402000428

CHANGES MADE IN MICROSOFT DYNAMICS™ NAV 5.0 W1

This has been corrected

VSA reference: 8912281

A13) G/L Account Name added to G/L Entry

This has been implemented

Table 17 - G/L Entry

A14) Export Budget and Totaling Accounts

This has been corrected

VSA reference: 8916132

A15) Replace Entries in Budget Import with Dimensions

This has been corrected

VSA reference: 9019456

CHANGES MADE IN MICROSOFT DYNAMICS™ NAV W1 5.0 SP1

This has been corrected

VSA reference: 8850088

A17) XBRL with long labels

This has been corrected

VSA reference: 8843249

A18) Prepayment with Currency and VAT

This has been corrected

A19) Prepayment and Get Shipment

This has been corrected

VSA reference: 9049990

CHANGES MADE IN MICROSOFT DYNAMICS™ NAV 5.0 W1