Changes Made in Navision Solutions 3.00

From Dynamics

Contents 1 Overview 2 Application Changes 2.1 General Changes 2.1.1 Features 2.1.2 Errors fixed 2.1.3 Issues 2.2 General Ledger 2.2.1 Features 2.2.2 Errors fixed 2.2.3 Issues 2.3 Fixed Assets 2.3.1 Features 2.3.2 Errors fixed 2.3.3 Issues 2.4 Bus. Interaction Mgt. 2.4.1 Features 2.4.2 Errors fixed 2.4.3 Issues 2.5 Sales & Receivables 2.5.1 Features 2.5.2 Errors fixed 2.5.3 Issues 2.6 Service Management 2.6.1 Features 2.6.2 Errors fixed 2.6.3 Issues 2.7 Purchases & Payables 2.7.1 Features 2.7.2 Errors fixed 2.7.3 Issues 2.8 Inventory 2.8.1 Features 2.8.2 Errors fixed 2.8.3 Issues 2.9 Warehouse Management 2.9.1 Features 2.9.2 Errors fixed 2.9.3 Issues 2.10 Manufacturing 2.10.1 Features 2.10.2 Errors fixed 2.10.3 Issues 2.11 Cap. Reqts. Planning 2.11.1 Features 2.11.2 Errors fixed 2.11.3 Issues 2.12 Resources 2.12.1 Features 2.12.2 Errors fixed 2.12.3 Issues 2.13 Jobs 2.13.1 Features 2.13.2 Errors fixed 2.13.3 Issues 2.14 Human Resources 2.14.1 Features 2.14.2 Errors fixed 2.14.3 Issues 3 Development Environment and Database Changes 3.1 Navision Server 3.1.1 Features 3.1.2 Errors fixed 3.1.3 Issues 3.2 SQL Server Option 3.2.1 Features 3.2.2 Issues 3.3 Development Environment 3.3.1 Features 3.3.2 Errors fixed 3.3.3 Issues 4 Tools 4.1 Navision Application Server 4.1.1 Features 4.1.2 Issues 4.2 C/ODBC 4.2.1 Features 4.2.2 Errors fixed 4.2.3 Issues 4.3 C/DART 4.3.1 Features 4.3.2 Errors fixed 4.3.3 Issues 4.4 C/FRONT 4.4.1 Features 4.4.2 Errors fixed 4.4.3 Issues 4.5 Communication Component and Bus Adapters 4.5.1 Features 4.5.2 Errors fixed 4.5.3 Issues 5 Documentation 5.1 Features 5.2 Issues

Overview

This document describes the changes between Navision Financials 2.60.E or Navision Manufacturing 2.60.E and Navision Solutions 3.00.

This document was originally written and published by Navision A/S and released 
as part of the Navision CD for that product. The original text has been preserved, 
and has only been edited for formatting. The original document can be found at the 
end of this document, under external links.

Application Changes

General Changes

Features

A1) Dimensions Functionality A new dimensions functionality has been implemented. The two old dimensions, Department and Project, have been replaced with an unlimited number of company-defined and company-named dimensions and dimension values. A range of new functionality supports dimensions:

• Analysis by dimensions, which allows you to manipulate data by dimensions.
• Hierarchical relationships within dimensions
• Business rules for dimension combinations, extended default possibilities and account prioritization
• Enhanced budgeting using dimensions

A2) Multiple Locations and Responsibility Centers Feature In order to handle and control inventory in multiple locations, a new feature has been created with the ability to tie a user or a location to a responsibility center. Stockkeeping unit (SKU) has been introduced as an additional layer to the item.

The location handles the physical placement and quantities of an item. The location object carries the ship-to and ship-from addresses and makes the relation to the SKU. A location can be a warehouse, service car, showroom, plant or area within a plant.

The responsibility center ties a document to an organizational unit. The responsibility center can carry dimensions to the sales, purchase, production and transfer documents.

In the replenishment process, the users can store information in the SKU on how to replenish at the different locations. The SKU carries all the replenishment parameters for a given combination of an item variant towards a location. A3) Costing Enhancement Feature Feature The costing functionality in Navision Financials did not meet all the requirements of distributors and manufacturers. In particular, the program needed to be improved in order to allow for:

• the addition of costs to the value of items.
• the accurate valuation of inventory, including.
• the detailed specification of costs.
• the transfer of inventory from one location to another, with the possibility for inclusion of transportation costs.
• the receipt of sales returns from customers, including the correct reversal of costs.
• the updating of costs at the time of receipt of items or change of legal title, so that inventory includes the items that are physically present at the location, as well as those that are owned by the company, they may have not arrived to or left the location.
• the updating of item value at the time of posting of costs in order to maintain an accurate cost history for each item.
• the maintenance of historical cost records in order to allow the computation of the value of inventory on any specific day.
• to provide better support for decision making.

Changes have been implemented in response to this issue. To create strong cost accounting functionality, our first step was to split item posting into item quantity posting and item value posting.

The Item Ledger Entry table (ILE) now contains only information about the quantity of items. Information about the value of items is now stored in a new table, the Value Entry table. This table is linked to the ILE and contains all monetary information about the items in the ILE, including costs, prices and discounts. The program can compute inventory value on any date in the past as well as on the current work date, in which case the valuation can include the expected value of items received.

You can set up the program so that expected costs are automatically posted to interim accounts when you post the receipt of items. When you post the invoice later on, the amount on the interim account is then balanced automatically to zero.

The ILE still registers the changes in quantity in your inventory, including positive and negative adjustments from a physical inventory. However, the Value Entry table now tracks the value of your inventory and contains all positive and negative value adjustments that are the result of quantity adjustments, discounts and exchange rate or rounding adjustments. Because of these and other adjustments, Navision Solutions 3.00 offers improvements in other areas as well:

• Better support of decision making
• Reconciliation of costs
• Reversing costs in connection with sales returns and returns to vendors
• Assignment of item charges to inventory value - or to customers or vendors for services relating to item sale or delivery
• Support for cost flow assumptions and valuation bases
• New principle for inventory valuation
• Adjustment of average cost

The cost accounting changes have not affected the following areas:

• It is still not possible to change costing methods for an item without emptying the inventory account.
• Customer entries or job entries (since the update of costs has only been done in inventory and manufacturing).
• Costs of handling or transportation of inventory within one location (for example, movement of goods from production area to inventory area).
• Adjustment of profits according to the item adjustment (for example, there is no adjustment of profit on the customer ledger entry when you adjust a cost value entry).
• Accurate posting of cost based on the date of the costs entered, and not the date of posting.

Errors fixed

A4) Customer/Vendor Statistics – Confusion about Which Fields are Including and Excluding VAT On the Customer Statistics and Vendor Statistics it has given some confusion about which fields are including VAT and which fields are excluding VAT.

In response to this issue, changes have been implemented. New Inv. Amount (LCY) field (including VAT) has been added and Pmt. Discount (LCY) field has been moved to the bottom on:

• Customer Statistics form (151)
• Vendor Statistics form (152)

The Amount (LCY) field has been changed to Sales (LCY) field (Still the amounts are excluding VAT) on:

• Sales Statistics form (160),
• Sales Order Statistics form (402),
• Sales Invoice Statistics form (397),
• Sales Credit Memo Statistics form (398)

The Amount (LCY) field has been changed to Purchase (LCY) field (Still the amounts are excluding VAT) on:

• Purchase Statistics form (161),
• Purchase Order Statistics form (403)
• Purchase Invoice Statistics form (400)
• Purchase Credit Memo Statistics form (401)

A5) Problem with Deleting Added Service Charge on Documents If a service charge was calculated to a document and then later on new lines or values were added to the document then the service charge was not recalculated.

This has been corrected.

• Codeunit 60
• Codeunit 70

A6) Incorrect Table Relations to Journal Batches: The Ledger Entries and Registers mentioned in Table 1 below have incorrect relations to the different Journal Batch tables (shown in Table 2 below)

Table 1
ID	Name	Field No	Field Name	Relation
17	G/L Entry	46	Journal Batch Name	Gen. Journal Batch
21	Cust. Ledger Entry	49	Journal Batch Name	Gen. Journal Batch
25	Vendor Ledger Entry	49	Journal Batch Name	"Gen. Journal Batch"
45	G/L Register	7	Journal Batch Name	"Gen. Journal Batch"
271	Bank Account Ledger Entry	49	Journal Batch Name	"Gen. Journal Batch"
5617	FA Register	7	Journal Batch Name	"Gen. Journal Batch"
5617	FA Register	7	FA Journal Batch	"FA Journal Batch"
32	Item Ledger Entry	45	Journal Batch Name	"Item Journal Batch"
46	Item Register	7	Journal Batch Name	"Item Journal Batch"
281	Phys. Inventory Ledger Entry	45	Journal Batch Name	"Item Journal Batch"
239	BOM Register	7	Journal Batch Name	"BOM Journal Batch"
203	Res. Ledger Entry	23	Journal Batch Name	"Res. Journal Batch"
240	Resource Register	7	Journal Batch Name	"Res. Journal Batch"
169	Job Ledger Entry	75	Journal Batch Name	"Job Journal Batch"
241	Job Register	7	Journal Batch Name	"Job Journal Batch"
5629	Ins. Coverage Ledger Entry	25	Journal Batch Name	"Insurance Journal Batch"
5636	Insurance Register	7	Journal Batch Name	"Insurance Journal Batch"

Table 2
ID	Name
232	Gen. Journal Batch
233	Item Journal Batch
234	BOM Journal Batch
236	Res. Journal Batch
237	Job Journal Batch
5620	FA Journal Batch
5634	Insurance Journal Batch

This has been corrected.

• G/L Entry table (17)
• Cust. Ledger Entry table (21)
• Vendor Ledger Entry table (25)
• Item Ledger Entry table (32)
• G/L Register table (45)
• Item Register table (46)
• Job Ledger Entry table (169)
• Res. Ledger Entry table (203)
• BOM Register table (239)
• Resource Register table (240)
• Job Register table (241)
• Bank Account Ledger Entry table (271)
• Phys. Inventory Ledger Entry table (281)
• FA Register table (5617)
• Ins. Coverage Ledger Entry table (5629)
• Insurance Register table (5636)

The property TableRelation is changed to <Undefined> on the fields in Table 1, and the property TestTableRelation is set to <Yes>.

A7) Vendor Posting on Sales Accounts and Customer Posting on Purchase Accounts: When posting a general journal line with Account Type = Vendor (Customer) and Bal. Gen. Posting Type = Sale (Purchase), there was an error indicating that the respective Customer (Vendor) does not exist.

Similarly, if posting a general journal line with Bal. Account Type = Vendor (Customer) and Gen. Posting Type = Sale (Purchase), there was an error indicating that the respective Customer (Vendor) does not exist

An error message should appear, but in general, the error message is not correct (Only if the there are customers and vendors with coinciding numbers the correct error message appears, say Customer 10000 and Vendor 10000 in the CRONUS Company).

This has been corrected.

• Gen. Jnl.-Check Line codeunit (11)
• Gen. Jnl.-Post Line codeunit (12)

The check for vendor posting on sales accounts and customer posting on purchase accounts is removed from Codeunit 12 and added to Codeunit 11. This implies that the global Boolean variables CustPosting, VendPosting, SalesPostingType, PurchPostingType and the function TestPostingTypes and any references to these variables and function are deleted from Codeunit 12.

A8) Problem with Positive and Negative Adjustments when making Application in Multi Currency When you made an application of an invoice in DEM with a payment in GBP, the system used the same account for the positive difference rounding as for the negative ones. Solved by implementing debit and credit accounts for Curr. Appln. Rounding in Customer and Vendor Posting Groups.

This has been corrected.

• Customer Posting Groups form (110)
• Vendor Posting Groups form (111)

A9) The System Changes the Amount on Posted Entries if You Get a Payment Discount The system changed the amount on posted entries if you got a payment discount or ran the adjust exchange rate batch job. That meant, that the system did not reflect the amounts that were actually paid by the customer.

This has been corrected Solved by implementing two new fields Original Amount and Original Amount (LCY). We have also implemented Detailed Customer Ledger Entries and Detailed Vendor Ledger Entries. This new functionality shows the changes made to Customer Ledger Entries and Vendor Ledger Entries.

A10) Problem when Applying a Payment with Customer or Vendor as Balance Account The content of the Balance fields on the bottom of the Apply Customer Entries form (232) was incorrect when you entered Customer No. as the Bal. Account No. on a payment. This was also a problem for Apply Vendor Entries form (233).

This has been corrected.

• Apply Customer Entries form (232)
• Apply Vendor Entries form (233)

A11) Performance Problem when Applying Vendor or Customer Ledger Entries When you scrolled through the entries on Apply Customer Entries form (232) and Apply Vendor Entries form (233), the screen blinked, because the form got updated a lot of times. The form does not update if you only have one currency within the filter on the form, but the forms still updates when there is more than one currency on the form (within the filter on the form).

This has been corrected

• Apply Vendor Entries form (233)
• Apply Customer Entries form (232)

A12) Appln. Rounding Incorrectly Shown in the Application Window When you have an invoice and post a payment in the same currency and the application rounding precision is set up, and the amount is within this application rounding precision, then the program considered the amount as a rounding instead as a balance. The amount now is now considered as a remaining amount and showed in the Balance field on Apply Customer Entries form (232) and Apply Vendor Entries form (233).

This has been corrected.

• Apply Vendor Entries form (233)
• Apply Customer Entries form (232)

A13) Inconsistency Error During Posting When using Additional-Reporting Currency and Sales Tax together, inconsistencies occurred during posting. In addition, when running VAT settlement (report 20), additional reporting currency was not updated on VAT entries.

This has been corrected.

• Codeunit 12

A14) Error When Checking Balance for Foreign Currency Amount in Recurring Journals The function for checking the balance for foreign currency amounts did not take recurring journals into consideration, which in practice makes it impossible to post a recurring journal in a foreign currency along with allocations.

This has been corrected.

• Codeunit 13

A15) Inconsistencies when Posting When posting with Additional-Reporting Currency set to EUR and Force Doc.Balance set to no. for "general" in the General Journal Templates, the systems did not check the General Journal lines properly.

This has been corrected.

• Codeunit 13

A16) Payment Discount Incorrectly Calculated Payment discount was incorrectly calculated when Additional-Reporting Currency had an amount rounding precision other than the LCY.

This has been corrected

• Codeunit 12

A17) Closing Date in Working Date. If the most recent date on a general ledger in the CRONUS company is a closing date, the system set the closing date as working date, although the user cannot specify a closing date as working date.

This has been corrected.

• ApplicationManagement codeunit (1)

A18) Problem with Undefined Posting Dates of Quotes. It is not possible to copy a sales quote or purchase quote with foreign currency into a sales order using the Copy Sales Document report (292) or Copy Purchase Document report (492), when the Include Header option is checked, due to undefined posting dates of quotes.

This has been corrected.

• Copy Sales Document report (292)
• Copy Purchase Document report (492)

A19) Sales Quotes and Purchase Quotes and Currency Exchange Rates. On the Sales Quote form (41) and Purchase Quote form (49) the assist button of the Currency Code field for a customer or vendor with Currency Code <> ' ' was not working. The error occurred, because the Change Exchange Rate window, which should open when the assist button is pressed, used the content of the Posting Date of the quote as a datefilter when finding an exchange rate for the currency. Since the Posting Date on a quote is undefined (OD), an exchange rates for the currency in question could not be found.

This has been corrected.

• Sales Quote form (41)
• Purchase Quote form (49)

A20) Apply Customer Entries/Apply Vendor Entries: Appln. Remaining Amount, Appln. Pmt. Disc. Possible and Missing Currency Exchange Rates: When Apply Customer Entries form (232) is opened or when the user scrolls up and down in the window, the form calculates the amounts Appln. Remaining Amount or Appln. Pmt. Disc. Possible. The Appln. Remaining Amount field shows the amount that remains to be applied to before the entry is totally applied to. The Appln. Pmt. Disc. Possible field shows the discount that the customer can obtain if the entry is applied to before the payment discount date. The amounts are shown in the currency represented by the code in the Appln. Currency field.

If there is not defined an exchange rate between the Appln. Currency (i.e. the Currency Code on the current ledger entry in the window) and every ledger entry displayed in the window the user would be prompted with an error message stating that there is no exchange rate defined. The same situation also applied for Apply Vendor Entries form (233).

This has been corrected.

• Apply Customer Entries form (232)
• Apply Vendor Entries form (233)
• Currency Exchange Rate table (330)

A21) Post Application of Customer and Vendor Ledger Entries: When posting an application, NF always informed that the application was successfully posted, even if no applying took place - due to the entries that were selected in the application (for example only invoices are selected in the application).

Furthermore, if no application takes place, the Applies-to ID of the current ledger entry was removed.

This has been corrected.

• CustEntry-Apply Posted Entries codeunit (226)
• VendEntry-Apply Posted Entries codeunit (227)

Issues

A22) Traceability in Customer and Vendor Ledger Being able to retrieve all legal documentation and to follow the documents as they are applied within the program is very important in some countries. To allow our customers to fulfill their legal requirements, we have redesigned the customer and vendor ledger entries. We have responded in particular to the following problems:

• It is not legal to change customer or vendor ledger entries in all countries.
• Exchange rate adjustments and payment discounts were not traceable in the program. You could not retrieve a customer’s or vendor’s balance on a historical date because exchange rate adjustments and payment discounts since then had perhaps altered the balance on the historical date.
• The customer and vendor ledger entries on any given date must reflect the entries in the general ledger and correspond to the amount on the invoice or payment documents. This was not the case in Navision Financials if payment discounts had been given or received.

In response to these issues, changes have been implemented. Besides the existing customer and vendor ledger entries, the program now has a new type of detailed subentries in tables named Detailed Customer Ledger Entry and Detailed Vendor Ledger Entry. The detailed ledger entries will store the actual amounts of an invoice or a payment, while the customer ledger entries will reflect the amounts as FlowFields. The new detailed ledger entries show exactly how changes in a customer or vendor ledger entry have occurred, and you can print the full details for historical balances on documents in the Balance at Date report.

A23) Rounding in Sales and Purchase Documents VAT (sales tax) was calculated on each line as unrounded amounts. The total VAT amount for several lines was correct (when rounded), and you did not have go back to the document to recalculate VAT when you were finished changing it. This functionality worked for most documents, but was not practical for partial invoices or invoice discounts, which had to be calculated on the total amounts. In these cases, VAT also had to be recalculated, since VAT is based on total amounts. In response to this issue, a change has been implemented. All amounts, except for quantity and unit price (or direct unit cost in purchase documents), are rounded to currency precision. The invoice discount amounts and VAT (sales tax) amounts on the sales or purchase lines are hidden.

A24) Manual VAT In most countries, companies are required by law to post the exact VAT amount that is specified on the invoice from the vendor. If the VAT calculated by the program differed VAT on the invoice, the user could not correct the VAT manually. In response to this issue, a change has been implemented. You can now change total VAT amounts in journals and on documents. The program checks for maximum allowed corrections and keeps a log of adjustments for the VAT authorities.

A25) Manual Entry of Invoice Discount The user is now being able to modify an invoice discount amount to match the amount on an external document. Changes to invoice discounts entered in the statistics window are distributed to the relevant lines.

A26) No Warning before Posting if the VAT Posting Setup Does Not Exist Code Unit 12 prevents an unknown VAT Posting Setup for being posted, but it would be more convenient if the user was prevented from making an entry with an unknown VAT Posting Setup. Solved by giving an error message if the VAT Posting Setup does not exist. On the Item card, it will not be possible to enter a non-existing VAT Prod. Posting Group, if the prices are incl. VAT and the Price/Profit Calculation is different from "no relations". In response to this issue, changes have been implemented.

• Sales Lines table (37)
• Purchase Lines table (39)
• Reminder Lines table (296)
• Finance Charge Memo lines table (303)
• Item Card form (30)

General Ledger

Features

Errors fixed

A27) VAT-VIES Declaration Tax Auth with Zero as Last Entry If the last VAT entry for a customer had zero in the Base field, then the customer was not printed on the VAT-VIES Declaration Tax Auth report (19). This has been corrected.

• VAT-VIES Declaration Tax Auth report (19)

A28) Missing Countries on the VAT VIES Declaration Tax Austria, Sweden and Finland were not on the report. This has been corrected.

• VAT-VIES Declaration Tax Auth report (19)

A29) Wrong Source Code on G/L Entries after Date Compress VAT Entries After date compressing VAT entries the related G/L entries had a wrong Source Code. This has been corrected. Solved by changing the Source Code from Compress Cust. Ledger to Compress VAT Entries.

• Date Compress VAT Entries report (95).

A30) Wrong Register Structure for Delete Empty G/L Registers The register structure for the report was not right. This has been corrected.

• Delete Empty G/L Registers report (99)

A31) Sales Tax with Currency Code Codeunit 398 assumed a currency rate in hundreds instead of a currency factor. This has been corrected.

• Codeunit 398

A32) Error-Text Alteration In the function UpdateAmountArray of Import Consolidation from File report (92) the following error-text

ERROR(
         'You cannot use more than %1 different posting dates with the ' +
         'Import Consolidation from DB batch job.',
         ARRAYLEN(DeletedDates));

was incorrect, since it related to Import Consolidation from DB instead of Import Consolidation from File This has been corrected.

• Import Consolidation from File report (92)

A33) Trial Balance/Budget and Negative Budgets: In Trial Balance/Budget report (9) the budget amounts were always shown as absolute amounts. But in the G/L Budget by Periods window the budget amounts were displayed with sign. When printing the report the amounts were shown without sign, which means that you could not figure out the sign of the budget. This has been corrected.

• Trial Balance/Budget report (9)

A34) Problem with Foreign Currency Balance Report (503) when You Apply Entries in Different Currencies If you applied entries in different currencies so no invoices in a specific currency were to be received anymore, the Foreign Currency Balance report (503) still showed that there was a balance for that currency. After we have implemented Detailed Customer Ledger Entries and Detailed Vendor Ledger Entries, this error is corrected. We have change the calculation, so the property CalcFormula is calculated on "Detailed Ledger Entry" in Currency table (4), Field No: 25 Customer Balance, 30 Vendor Balance, 34 Customer Balance (LCY) and 35 Vendor Balance (LCY). This has been corrected.

• Currency table (4)

A35) Close Income Statement Skips Entries The Close Income statement skipped some entries when it was closed using Global Dimension 2. This did not happen when it was closed using Global Dimension 1. This has been corrected.

• Report 94

A36) Wrong currency when printing a check and voiding it Vendor/Customer Ledger entries got the wrong currency if you changed the currency code in the process of printing a check and voiding it. This has been corrected.

• Codeunit 367

A37) Consolidations and Entering Closing Dates. When Importing Consolidation from DB it was not possible to enter closing date in the Starting Date or Ending Date controls of the request form or in the Business Units window, as suggested in the General Ledger Manual (e.g. in page 310). When Exporting Consolidation it was not possible to enter closing date in the Starting Date or Ending Date fields of the request form. When running the reports 14 Consolidation - Test Database, 16 G/L Consolidation Eliminations, 17 Consolidated Trial Balance and 18 Consolidated Trial Balance (4) it were not possible to enter closing date in the Starting Date or Ending Date fields of the request form. In these reports the property ClosingDates were set to <No> on both of the controls Starting Date and Ending Date. They should have been set to <Yes> This has been corrected.

• Consolidation - Test Database report (14)
• G/L Consolidation Eliminations report (16)
• Consolidated Trial Balance report (17)
• Consolidated Trial Balance report (18)
• Import Consolidation from DB report (90)
• Export Consolidation report (91)

A38) Consolidations with Closing Dates. When using closing dates as Starting Date or Ending Date in the Import Consolidation from DB batch job (90), Export Consolidation batch job (91) or Import Consolidation from File batch job (92) problems would occur with Copy Date checked. The reason for the problem were closing dates would be used in calculations either to check if period exceeded 500 days or to index arrays several places in the algorithm. This has been corrected.

• Import Consolidation from DB report (90)
• Export Consolidation report (91)
• Import Consolidation from File report (92)

Further, for Import Consolidation from DB report (90) new rules about consolidation date handling has been implemented, see below.

A243) Change in Consolidation Date Handling On the request form of Import Consolidation from DB batch job (90) and Consolidation - Test Database report (14) the fields Starting Date and Ending Date are used to specify the consolidation period. However, if the fields Starting Date and Ending Date of one or more Business Units are filled in then the consolidation period is actually defined by the fields Starting Date and Ending Date of the respective Business Units. But according to the online Help, the fields Starting Date and Ending Date of the Business Units should only be filled in when the consolidated company and the subsidiary companies (the companies specified by the business units) have different fiscal years. Hence, the online help description and the actual use of report 90 differ, which might be confusing. This has been corrected

• Import Consolidation from DB batch job (90)
• Consolidation - Test Database report (14)
• Business Units form (240)
• Business Unit table (220)

The management of the consolidation period is centered on the fields Starting Date and Ending Date of the request form. In order to run report 90 Import Consolidation from DB the consolidation period (the fields Starting Date and Ending Date on the request form) must be specified. If the Starting Date and the Ending Date of one or more business units are filled in, the Starting Date should be the first day of the business unit’s fiscal year and the Ending Date should be the last day of the business unit’s fiscal year. If this is not the case, an error message is issued.

If the Starting Date and the Ending Date of one or more business units are filled in, then the consolidation period specified by the Starting Date and Ending Date on the request form should be contained in the fiscal years of these business units. If this is not the case, the users are warned that consolidation period is not contained in the current fiscal years of the subsidiary companies and asked whether they want to proceed with the consolidation. If the users do not want to proceed, the batch job is aborted.

The consolidation period specified by the Starting Date and Ending Date of the request form should be contained in the current fiscal year of the consolidated company. If not, the users are informed/warned that consolidation period is not contained in the current fiscal years of the consolidated company and asked whether they want to proceed with the consolidation. If the users do not want to proceed, the batch job is aborted.

A39) Consolidating a Non-Closing Date Period Containing Closing Dates. When using the Import Consolidation from DB (Report 90) batch job or Export Consolidation (Report 91) batch job and the Starting Date and Ending Date are non-closing dates, the system checks if the company being consolidated contains a general ledger entry on a closing date in the consolidation period. If so, the system yielded an error. This has been corrected.

• Import Consolidation from DB report (90)
• Export Consolidation report ( 91)
• A new function CheckClosingPosting has been added to Import Consolidation from DB report (90)
• Export Consolidation report ( 91)

A40) Import Consolidation from DB and Import Consolidation from File Can Give Text-Overflow Using the Import Consolidation from DB (Report 90) batch job or Import Consolidation from File (Report 92) batch job could result in a text-overflow. The problem occurred when building General Journal Line descriptions. The description could contain one or more of the factors Last Balance Currency Factor, Balance Currency Factor and Income Currency Factor. These factors were not rounded, so they could contain up to 15 decimal places each. This could result in a description string longer than the maximum defined length of the field Description of the General Journal Line. This has been corrected.

• Import Consolidation from DB report (90)
• Export Consolidation report ( 91)

The factors Last Balance Currency Factor, Balance Currency Factor and Income Currency Factor are now rounded to 5 decimal places. Furthermore, the resulting description string is now never longer than the maximum defined length of the field Description of the General Journal Line.

A41) Foreign Currency Consolidation- Adjustment of Opening Entries of Balance Sheet Accounts: The Import Consolidation from DB (Report 90) and Import Consolidation from File (Report 92) did not handle the currency exchange update for balance sheet accounts properly.

If there is an exchange rate difference between the current consolidation and the last consolidation, the formula for adjusting the opening entries of balance accounts resulted in an incorrect adjustment of the opening entries of balance accounts.

This has been corrected.

• Import Consolidation from DB report (90)
• Import Consolidation from File report (92)

On the OnAfterGetRecord trigger of dataitem ConsolidGLAcc of Report 90 and on the OnAfterGetRecord trigger of dataitem G/L Account of Report 92, the formula for adjusting the opening entries of balance accounts

 GenJnlLine.Amount :=
	ROUND(
		(("Balance at Date" / "Business Unit"."Balance Currency Factor") -
		("Balance at Date" / "Business Unit"."Last Balance Currency Factor")));

has been replaced by the formula:

 GenJnlLine.Amount :=
	ROUND(
		"Balance at Date" *
		"Business Unit"."Last Balance Currency Factor" / "Business Unit"."Balance Currency Factor" 
 - "Balance at Date");

A42) Foreign Currency Consolidation- Zero Adjustment of Opening Entries of Balance Sheet Accounts: Exchange rate differences between the current consolidation and the last consolidation can result in zero amount journal lines. This zero amount adjustment journal line could not be posted. This has been corrected.

• Import Consolidation from DB report (90)
• Export Consolidation report (91)

The code handling the adjustment of the opening entries of balance accounts is modified, so General Journal Line is only posted if the adjustment amount is not zero.

A43) Receivables, Payables, and Bank Accounts Wrongly Added up in the Total-line. In Foreign Currency Balance report (503), for the columns Posted Value (LCY) and Current Value (LCY) the Total-line erroneously contained the sum of the absolute values of Receivables, Payables, and Bank Accounts for the selected Currencies instead of the sum of the values of Receivables, Payables, and Bank Accounts for the selected Currencies.

This has been corrected.

• Foreign Currency Balance report (503)

A44) Posting Payments Applied to Credit Memos and Warnings. When posting a payment on a customer with a credit memo applied so the amount is positive erroneously resulted in a warning stating ”Amount must be negative”. Similarly, posting a payment on a vendor with a credit memo applied so the amount is negative resulted in a warning stating: ”Amount must be positive”. This has been corrected.

• General Journal - Test report (2)

A45) Recurring Journal and Warnings. When using the recurring methods Balance or Reversing Balance in the Recurring Journals, you are not supposed to enter an Amount. But the General Journal - Test report (2) erroneously issued the warning ’Warning! Amount must be specified.’ This has been corrected.

• General Journal - Test report (2)
• Gen. Jnl.-Post Batch codeunit (13)

A46) Unit Amount Rounding Precision must be Specified. In Adjust Add. Reporting Currency batch job (86), the rounding functionality (using Unit Amount Rounding Precision and Amount Rounding Precision) did not test whether the field Unit Amount Rounding Precision of the Additional Reporting Currency is specified or not. This has been corrected.

• Adjust Add. Reporting Currency report (86)

A47) Wrong Field Used. In Adjust Add. Reporting Currency batch job (86), for DataItem Job Ledger Entry, the field Add.-Curr. Amount Recognized field was not calculated correct. The report used the Amt. to Recognize field as a base, where it should use the field Amt. Recognized. This has been corrected.

• Adjust Add. Reporting Currency report (86)

A48) Posting Zero-Amount General Journal Lines. In some situations it is necessary to be able to post zero-amount general journal lines that are not system created, for example, when posting a Recurring Journal Line with Allocations. A small amount allocated with a small percentage on one of the Allocation lines can be zero due to rounding. If this zero-amount recurring journal line has a blank general posting type, posting the recurring journal line yielded an error. The only way for the user to post the Recurring Journal, was to delete the Allocation line causing the problem This has been corrected.

• Gen. Journal Line table (81)
• Gen. Jnl.-Check Line codeunit (11)
• Gen. Jnl.-Post Line codeunit (12)
• Gen. Jnl.-Post Batch codeunit (13)
• CheckManagement codeunit (367)
• General Journal - Test report (2)
• Check report (1401)

A49) Division by Zero Error: When setting Amount (LCY) to 0 in a Gen. Journal Line with a non-fixed currency (i.e. the currency has exchange rates with Fixed Exchange Rate Amount <> Both) the system generates a system Division by Zero error instead of a controlled error message. This has been corrected.

• Gen. Journal Line table (81)

A50) Recurring Journal Produces Zero-amount G/L Entries: When posting a Recurring Journal Line with Recurring Method Balance or Reversing Balance, but with no Allocation lines attached to the journal line, it was possible to produce zero-amount G/L Entries, even if the balance of the G/L Account is non-zero. This has been corrected.

• Gen. Jnl.-Post Batch codeunit (13)
• General Journal - Test report (2)

A51) Recurring Methods Fixed and Reversing Fixed and Zero Amounts In Codeunit 13, the function CheckRecurringLine is missing a check regarding zero amounts and the recurring methods Fixed and Reversing Fixed. If one of these two recurring methods is used, and the Amount in the recurring journal line is zero the journal line could not be posted. The zero-amount problem was handled correctly in Codeunit 11, but actually, it should have been handled in function CheckRecurringLine in Codeunit 13, due to functional decomposition.

Changes have been implemented.

• Gen. Jnl.-Post Batch codeunit (13)

A52) Report 5 - Receivables-Payables: In the row ’after…’ at the end of the Receivables-Payables report (5) the amounts Cust. Balance Due (LCY), Vendor Balance Due (LCY) and Net Effect on Liquidity (LCY) were added up. This was incorrect. It should have shown the sum of amounts posted after the given period. This has been corrected

• Receivables-Payables report (5)

A53) Renaming Starting Date of Currency Exchange Rates: When renaming a Currency Exchange Rate line by renaming the Starting Date, the entire line except for the Starting Date became a copy of the line Currency Exchange Rate line with starting date closest to and earlier than the changed starting date, instead of just renaming the line and keeping the values. When inserting a new line the copy functionality must still work. This has been implemented.

• Currency Exchange Rate table (330)
• Currency Exchange Rates form (483)

A244) Direct Posting on Consolidation Accounts Report 92 Import Consolidation from File and Report 90 Import Consolidation from DB require that the G/L Accounts to be posted to as part of the consolidation should be Direct Posting accounts. Since it is the system that generates and posts Gen. Journal Lines, there is no reason for demanding the user to set Direct Posting on potentially all accounts in the consolidated company. This has been corrected.

• Import Consolidation from DB report (90)
• Import Consolidation from File report (92)

A245) Correction Made for Realizing VAT when Applying Entries Realized and Remaining Unrealized VAT were calculated incorrectly when focus was on an invoice entry, when applying posted entries.

This has been corrected.

A246) Set up Sales Tax and ACY could lead to Consistency Error when Posting Documents in ACY When you set up Sales Tax and Additional Reporting Currency, you could get a consistency error when posting documents in ACY.

This has been corrected.

Issues

A54) Test of VAT Registration Numbers The program did not automatically check the format of VAT registration numbers to ensure that numbers had the correct format. In response to this issue, a change has been implemented. We have included a user-defined VAT format check.

A55) VAT Entries and Sell-to/Buy-from No. If you posted an invoice in a general journal, and the program calculated VAT from a general journal line that did not have a customer or vendor as the account or balancing account, the program did not fill in the Sell-to/Buy-from No. field on the VAT entries. To print the VAT-VIES report, the user then had to fill in the Sell-to/Buy-from No. field manually. In response to this issue, a change has been implemented. You can now enter the sell-to/buy-from number manually in the journal and print the VAT-VIES report without having to specify the Sell-to Customer No. field manually. The sell-to/buy-from number is automatically inserted on the journal line during posting if the sell-to customer number is not already specified by the user.

A56) Optional VAT Calculation for Journals The user could not set up in the Gen. Journal Template and Gen. Journal Batch tables whether VAT should be calculated or not. In response to this issue, a change has been implemented. The Gen. Journal Batch now determines whether the fields Gen. Posting Type, Gen. Bus. Posting Group, Gen. Prod. Posting Group, VAT Bus. Posting Group and VAT Prod. Posting Group are copied from the account to the journal line or not.

A57) Improvements for VAT Statement The values concerning the VAT Entries should be saved when closing the window. The report should show the value zero as blank. The ColumnAmount field should change to default.

The Date Filter on the VAT Statement Line tab has been deleted and two new fields concerning statement period has been added on the Option tab.

In response to this issue, a change has been implemented.

• VAT Statement Preview form (474)
• VAT Statement Preview Lines form (475)
• VAT Statement report (12)

A58) Document Date Field Added to VAT Entry Table For doing the VAT Return it was suggested to put the Document Date field on the VAT Entry Table. In response to this issue, a change has been implemented.

• VAT Entry table (254)

A247) Correction Made for Calc. And Post VAT Settlement Corrections have been made for Calc. And Post VAT Settlement Account. For the Settlement account, it is now checked that it has no VAT posting attached.

Fixed Assets

Features

A59) Fixed Asset Can Be Sold From Sales Invoice A fixed asset can now be disposed of using a sales order and a sales invoice. The Type field now has a new option, Fixed Asset.

A60) Half-Year Convention Depreciation Method Has Been Implemented On the FA Depreciation Books form (5619), a new field (44), Use Half-Year Convention, has been implemented. If a check mark is placed in this field, the batch job Calculate Depreciation calculates six months of depreciation in the first fiscal year regardless of the value in the Depreciation Starting Date field.

A61) Changes to the FA Forms The fixed asset card and the FA depreciation books forms are now presented as main forms and subforms. We have added the Disposed field to the FA Depreciation Books subform (5666). The program enters a check mark in this field if the fixed asset has been disposed of. The subform also contains the FlowField field Book Value, which is set to zero if the fixed asset has been disposed of. In menu button Fixed Asset, you can open the ledger entries with table filter = Fixed Asset No. In menu button Depr. Book, you can open the ledger entries with table filter = Fixed Asset No. and Depr. Book Code.

A62) User Can Now Decide Whether Program Subtracts Purchase Line and Invoice Discount Amount from Fixed Asset Acquisition Cost We have added the Disc. in Purch. Inv. Excluded field to the depreciation book card, Form 5610. If you enter a check mark in this field on a purchase line of type Fixed Asset, you must enter a G/L Account No. in the Purch. FA Disc. Account field (5600) in the *General Posting Setup form (314) .

A63) New Disposal Accounts When You Sell a Fixed Asset Using Disposal Method Gross There are now disposal accounts for gain and loss when you sell a fixed asset and use the disposal method Gross, including fields for book value. The new fields are on the FA posting group card, Form 5613, on a new tab, ‘Gross Disposal’. The allocations of book value on disposal are split into one for gain and one for loss.

A64) FA Posting Group Totals Implemented in Various Reports FA posting group totals have been implemented on various reports. Changes have been implemented.

• Reports 5600, 5605, 5606, 5607, 5610, 5630.

A65) Improvements in Fixed Asset Statistics Form The Fixed Asset Statistics form has been redesigned. There is a new Boolean field, Disposed, which the program fills in if you have disposed of the asset, and a new Book Value field, which shows 0 if the fixed asset has been disposed of. If you still own the fixed asset, the Disposed field does not appear on the form. Changes have been implemented.

• Form 5602

A66) New Depreciation Method in Fixed Assets The program now offers, in Fixed Assets, the declining balance depreciation method combined with the custom 1 (Sonder-AfA) method. Changes have been implemented.

• Codeunit 5612

A67) Cancel FA Ledger Entries with New Posting Date In the FA Ledger Entries form (5604) you can transfer entries to a journal. In the journal, you can post the entries and transfer the entries to FA Error Ledger Entries. The journal lines get the same posting date as the ledger entries, but now it is possible for the user to enter a new posting date for the journal lines.

Errors fixed

A68) Access Key on Depreciation Table Card There was no access key on the menu button Depr. Table on the depreciation table card. This has been corrected.

• Form 5659.

A69) Users Could Only Key In G/L Account Numbers Set Up for Direct Posting In FA Tables In some fields in the FA Posting Group and FA Allocation tables, users could only key in G/L account numbers that had been set up for direct posting. This has been corrected.

• Fields in Table 5606: 23, 24, 25, 26, 27, 28, 29, 30
• Field in Table 5615: 4

A70) Automatic Updating to Next Number After Posting of Numeric Batch When you posted a numeric batch, the program did not automatically update the batch number with the next available number in the FA journal setup. This has been corrected.

• Table 5605, Codeunit 13, Codeunit 5633, Codeunit 5653

A71) Search Description for Fixed Asset in Account No. Field The user could not enter a search description for an asset in the Account No. field. This has been corrected

• Table 5600: The value Search Description in property AltSearchField has been implemented in field 1.

A72) LookUpFormID Property Shows Users The LookUpFormID property on the User ID field in the FA Journal Setup form did not show the users in the User ID form (59). This has been corrected.

• Form 5609

A73) Properties in Maintenance Registration Table Did Not Refer to a Form In the Maintenance Registration table, properties LookupFormID and DrillDownFormID referred to a form that did not exist. This has been corrected.

• In Table 5616, the properties are now set to <Undefined>.

A74) Blank Field after Dot in C/AL Statement in Main Asset Component Table In the Main Asset Component table, the C/AL statement FA.MODIFY had a blank field after the dot. This has been corrected.

• Table 5640.

A75) One More Place to Apply Change from Service Pack 2.60A In Service Pack 2.60A, except for one place in application area Fixed Assets, we changed FIND('><=') to FIND('-') in the check for the existence of records in a range. This change ensures better performance with the SQL Server. This has been corrected.

• Codeunit 5623.

A76) Missing Report for Fixed Asset Ledger Entries The Fixed Assed Document Nos. report did not exist for fixed asset ledger entries. This has been corrected.

• Report 5636

A77) Correction of Initialization Error in FA When you purchase or dispose of a fixed asset in the FA G/L Journal, the program sometimes created incorrect automatic entries. If the FA G/L Journal line had VAT, the program inserted incorrect values in the VAT Bus. Posting Group and VAT Prod. Posting Group fields. This has been corrected.

• Codeunit 5607

A78) Updating Problems in the Total Value Insured per FA Form (5622) Updating problems when the form was made smaller or bigger. This has been corrected

• By setting the property Editable = No. in Total Value Insured per FA form (5622) textbox 84.

A79) Ellipsis Needed on Menu Button "Posting" Menu Item Test Report in the FA Journal Batches Form (5633) This has been corrected.

A80) The Fixed Asset - Projected Value report didn’t show Ending Book Value. This has been corrected.

• Report 5607

Issues

Bus. Interaction Mgt.

Features

A81) The Old Contact Management Application Area Feature The old Contact Management application area has been changed and enhanced, and is now called Business Interaction Management. All objects from the 2.6 Contact Management application area have been changed or deleted and the original objects from the 2.6 Contact Management application area no longer exist. The entire Business Interaction Management application area has been created in a new number series.

An update toolkit is included, which will take care of converting all data from the old Contact Management to the new Business Interaction Management application area.

A82) Duplicate Checking Feature The duplicate checking facilities have been improved and now ensure consistent address books.

A83) Contact Management Feature This feature allows you to record basic information about contacts. It contains both the old Contact Management prospects and contacts in the same table. These are now all called contacts (which are companies and persons). The reason for merging this all in one table is to provide the user with an improved search function.

A84) Profiling Feature This feature allows you to enter a profile of your contacts to specify detailed information about them. You can enter all the characteristics that will help you improve your business relationships with your contacts. You can enter a profile on a person level as well as on a company level, based on your own criteria.

A85) Opportunity Management Feature This feature helps you to keep track of sales opportunities. Your salespeople have an overview of what’s in the pipeline and can plan ahead accordingly. Opportunity Management can also help you to section your sales process into different stages.

A86) Classification Management Feature This feature allows you to classify your contacts into different categories, and therefore tailor marketing messages to suit the individual needs of the customer. You can classify your customers based on criteria specified by you. For example, you may want to group contacts in terms of revenue. This information is crucial for campaign planning, for targeting your contacts more specifically and for streamlining your sales and marketing messages.

A87) Campaign Management /Segmenting Feature The campaign management feature, which helps you to create and keep track of campaigns, has now been improved with the inclusion of the segmentation feature. This feature lets you select the customers that you want to target your campaign at. You can also reuse existing segments. You can, for example, specify whether these segments are to be updated every time new information about a contact is entered, or you can ‘freeze’ the group for follow-up activities. You can also easily mail merge the identified segment with a Microsoft Word document.

A88) Task Management Feature This feature helps you to organize your campaign, marketing and sales tasks. If you are recorded in the program as, for example, a salesperson or a purchaser, you can create to-do lists for yourself. You can also assign tasks to other users or teams of users recorded in the program. This feature also allows you to create an activity that is composed of several to-dos.

A89) Document Management Feature This feature integrates Microsoft Word with Navision Solutions 3.00. It is easy to look up a contact and then launch Microsoft Word, using a given template. Basic information can be transferred from Navision Solutions 3.00 to the Microsoft Word document.

A90) Interaction Log Feature This feature allows you log all your interactions with a contact in the interaction log. Some entries may be logged automatically, others manually. Entries that are logged automatically may be business documents generated by Navision Solutions 3.00, like invoices and payment reminders. Entries that are logged manually could be Microsoft Word documents. The interaction log can also be used to record meetings and telephone conversations.

A91) Telephone Integration/TAPI Feature Navision Solutions 3.00 is integrated with Microsoft TAPI (Telephone Application Program Interface). By using TAPI compliant telecom devices, you can call a contact simply by clicking a button on the contact card.

A92) Integration with Other Application Areas Feature Integration to other application areas of Navision Solutions 3.00 has been improved. Activities that are done in other application areas will automatically be registered in the interaction log in the Business Interaction Management application area. If the user creates, for example, a sales reminder, sales quote or a service order for a customer, this interaction is automatically registered in the interaction log.

In this way, the interaction log will keep track of all interactions that you have had with a particular contact person.

A93) Word Integration, TAPI Integration and MAPI Integration Feature The Business Integration Management application area is closely integrated with Microsoft Word, MAPI and TAPI by using automation server technology. Most of the program logic is written in the C/AL, but for handling the user’s events in Microsoft Word, Navision Solutions 3.00 uses a new COM component: NSAppHandler.dll.

You can open a Microsoft Word document from a BLOB field in the Business Interaction Management application area, which automatically imports the document after it has been edited. It is also possible to store other types of documents in a BLOB field, but it is not possible to automatically import documents you have edited them.

The automatic mail merge to hard copy, e-mail or fax has been improved.

You can dial a phone number automatically from a contact card by using a TAPI device.

The MAPI integration is improved: The 255 character limit has been removed and Navision Solutions 3.00 does not stop with an error if the user presses ESC while composing a new message in Outlook or whatever mail program used.

A94) Wizards Feature To enhance user assistance, several wizards have been introduced in the Business Interaction Management application area. The wizards are to some extent just another way of collecting data from the user, but the complexity of this collection called for cards forms with a large amount of code and very poor usability. It was therefore agreed that wizards should be used instead.

A95) Use of a New C/Side Feature Feature In the segmentation functionality, we use a new C/Side feature: the GetSetView, for saving and retrieving criteria that have been defined.

Errors fixed

Issues

Sales & Receivables

Features

A96) Customer Returns Management Feature The new feature supports all standard activities for returning sales items. Customer returns management does not post to any of the Navision Solutions ledgers itself. Instead, it creates standard documents, such as sales orders and credit memos. These documents post to appropriate ledgers.

Various functions create replacements by creating sales orders, issuing customer credits, issuing call-tags and helping organize the return of a defective item to the vendor from whom it was originally purchased.

A97) Order Promising Feature This feature is a tool to calculate the availability of items based either on available-to-promise (ATP) or capable-to-promise (CTP). The feature calculates the delivery dates and shipment dates that meet confirmed delivery dates based on availability dates. These calculations are based on estimated outbound warehouse handling and shipping time. This could imply the issue of new replenishment orders. The lead time of the replenishment order is calculated, and the production of manufactured items is scheduled. If the Finite Loading granule is present, the load on the capacity constrained resources is taken into account. For manufactured items, the availability of the component is also taken into account. A multilevel check is made if the components are subassemblies.

Errors fixed

A98) Blanket Sales Order; Problems with VAT Specification for Two Orders When two different sales blanket orders was printed, the VAT Amounts in the VAT Specification for the last blanket sales order was not reset. This has been corrected.

• Blanket Sales Order report (210).

A99) Issuing Reminder/Finance Charge Memo and VAT: When a Reminder or a Finance Charge Memo is created the VAT Bus. Posting Group of the Reminder Header or Fin. Charge Memo Header is taken from the VAT Bus. Posting Group of the customer. The VAT Prod. Posting Group on the Reminder Lines or Fin. Charge Memo Lines is taken from the VAT Prod. Posting Group of the Interest Account of the Customer Posting Group of the customer. But when the Reminder or Fin. Charge Memo is issued and you have chosen to post the interest, the system creates a Gen. Journal Line were VAT Bus. Posting Group is taken from the Interest Account instead of from the VAT Bus. Posting Group of the customer

This leads to errors like: VAT Amount + VAT Base Amount must be Amount. This has been corrected.

• Reminder-Issue codeunit (393)
• FinChrgMemo-Issue codeunit (395)

A100) Reminders/Finance Charge Memos - Incorrect Rounding of Decimal Numbers: For Reminders, Issued Reminders, Finance Charge Memos and Issued Fin. Charge Memos the decimal numbers Original Amount, Remaining Amount and Amount where in certain situations not rounded according the currency of the document.

This happened in the case with two reminders where the number of the first reminder matches the document number of a reminder line on the second reminder. If the currencies on the reminders differs and the number of decimal places displayed for amounts in each currency also differs, then the decimal numbers Original Amount, Remaining Amount and Amount on the second reminder will be displayed according to the currency of the first reminder. This has been corrected.

• Reminder Line table (296)
• Issued Reminder Line table (298)
• Finance Charge Memo Line table (303)
• Issued Fin. Charge Memo Line table (305)

A101) Closed at Date were blank on some Closed Customer Entries Closed at Date were blank on customer entries if the amounts on two entries were the same and they both were closed at the same time. It was a problem for both payments and credit memos. We have implemented "Detailed Ledger Entries" for customer and vendor, where you can see "Detailed Ledger Entries" as "Sub"-entries to a Ledger Entry. The Detailed Ledger Entries have a entry for application, and the entry's posting date is the date that the entry is closed. This has been corrected

A102) "Unit Cost" not updated "Unit Cost" was not updated when currency rate was changed. This has been corrected.

• Table 36

A103) The Customer Statement Report and Customer Entries in Multiple Currencies The report did not work properly when customer entries were in multiple currencies. The report has been redesigned so the report only shows open entries. Sums are calculated with "Remaining Amount" instead of "Amount". This has been corrected.

• Report 116

New amount field "Original Amount"

A104) The Customer Detailed Aging report calculated sums incorrectly The report did not calculate the sums for Customer Ledger entries correctly because a filter was missing. This has been corrected

• Report 106

A105) Amounts in Different Currencies Wrongly added in the Total (LCY)-line. In Report 107 Customer- Order Summary, the Total (LCY)-line erroneously contained the sum of amounts in different currencies, when the Option Show Amounts in LCY is unchecked (ex. Amounts in USD and BEF were added with same weight, i.e. without being converted to LCY first). This has been corrected.

• Customer - Order Summary report (107)

A106) Ghost Records when Deleting Reminder Term/Reminder Level and Finance Charge Term: When deleting a Finance Charge Term, the Beginning Text and Ending Text lines and any additional fees in foreign currencies for the Finance Charge Term were not deleted.

Similarly, when deleting a Reminder Term, the underlying Reminder Levels were not deleted and any additional fees in foreign currencies for the Reminder Level were also not deleted. This has been corrected.

• Finance Charge Terms table (5)
• Reminder Terms table (292)
• Reminder Level table (293)

A107) Finance Charge Memos - Finance Charge Text substitution does not match the Online-help: For Finance Charge Memos, the Total Amount in the text: ‘Please pay the total of <Total Amount>’ was a total of Interest Amount, Additional Fee and VAT Amount of the Finance Charge Memo. The total Remaining Amount of the Finance Charge Memo was not included in the Total Amount, as it should. This has been corrected.

• Finance Charge Memo Header table (302)

A108) Reminder, Issued Reminder, Finance Charge Memo and Issued Fin. Charge Memo and Assist Edit button for the Currency Code: In the forms Reminder, Issued Reminder, Finance Charge Memo and form Issued Fin. Charge Memo there were no Assist Edit button on the Currency Code controls, and therefore you could not see the exchange rates. This has been corrected.

• Reminder form (434)
• Issued Reminder form (438)
• Finance Charge Memo form (446)
• Issued Finance Charge Memo form (450)

A109) Reminder Issue and Missing Permissions: Suppose you have created a reminder with the following settings: you want interests to be calculated and posted and the interest calculation should be based on all entries. Now a customer ledger entry (say, an invoice) on the reminder is paid and closed after the reminder was created. When you try to issue the reminder, you would get an error saying that you do not have permissions to modify entries in the Customer Ledger Entry table, because the Reminder Issue codeunit (393) had no permissions to the Customer Ledger Entries. This has been corrected.

• Reminder-Issue codeunit (393)

A110) Reminder/Issued Reminder Statistics and Customer Balance: On the Reminder Statistics form (437) and Issued Reminder Statistics form (441) the control Balance (LCY) on the Customer tab was always zero, even if the customer had a non-zero balance in LCY.

The reason was that it was the Balance of the customer that is calculated instead of the Balance(LCY). This has been corrected.

• Reminder Statistics form (437)
• Issued Reminder Statistics form (441)

A111) Finance Charge Memos and Reminders: Interest Calculation Method Average Daily Balance The formula for calculating the interest amount has been changed so the Document Date of the reminder and finance charge memo is taken into consideration when calculating interest on partial payments. If the date of payment is prior to the Document Date of the reminder and finance charge memo, the partial payments interest is calculated for the whole overdue period. If the Document Date of the reminder and finance charge memo is prior to the date of payment, the interest is calculated for the overdue period up to and including the Document Date. This has been corrected.

• Reminder Line table (296)
• Finance Charge Memo Line table (303)

A112) Update of the Sales Lines When items on sales lines were reserved automatically, the reserved quantity on the line was not updated until the curser was moved to the next line.

This has been corrected.

A113) Unit of Measure (UOM) and "Appl.- to Item Entry" Error If you have different UOMs (Units of Measure) for an item and you use the field Appl.-to Item Entry in sales line, the Unit Cost can be wrongly calculated. This has been corrected:

• Table 37

A114) Copy Document with Different Currency Codes Error If you copy a document with a currency code other than the one of the document you are copying to, you get an error if there is a G/L Account on the lines that you copy from. It is only possible to copy from lines that contain items. This has been corrected:

• Table 292

A115) Possible to Post an Order Even if the Item Number is Missing on Sales Order/Invoice Error It was possible to post an order when the Item Number was missing. This has been corrected

• Tables: 37, 39

A116) Pay-to or Bill-to was Missing on Post Code/City Error The Pay-to or Bill- to indication on control of Post Code/City was missing on the Purchases & Payables / Orders / Invoicing Tab. This issue also effected: Quotes, Invoices, Credit Memos, Posted Receipts, Posted Invoices, Posted Credit Memos. This has been corrected

• Forms: 49, 50, 51, 52, 136, 138, 140 and 509.
• Forms: 41, 42, 43, 44, 130, 132, 134 and 507.

A117) Missing Warning: “Vendor Invoice No. must be specified” on Test Report 202 Error We missed a check on the test report 202 to include checking for invoice when the field "Ext. Doc. No. Mandatory" is checked. This has been corrected

• Test report 202

A118) Ship Field on Sales Header Error This field should not be editable. This has been corrected

• Table 36_57.

A119) Posting Date Validation Code Problem in Sales Header Error If you pressed F2 on a sales invoice in the posting date field, and then pressed Enter, you would receive a message that you have changed the date and so on. This has been corrected

• Table 39

A120) Different Reaction in Sales and Purchase Area on Document Date Error You got a different reaction on the document date field in the Sales and Purchase area when you changed a posting date field. This could cause problems because the due date and the payment discount date are calculated from the document date. This has been corrected

A121) Error Message: “The Sales Line already exists” from Order Confirmation Error This message was triggered unnecessarily from Order Confirmation. This has been corrected

• Reports: 204, 210, 205 and 404, 410, 405.

A122) Drop Shipments: Wrong Update of Unit Cost and Unit Cost ($) Fields Error When a Drop Shipment Purchase Order was created from the Sales Order, the Unit Cost and Unit Cost ($) fields were not updated correctly (they were set to zero instead). This problem occurred in Codeunit 76. This has been corrected

• Codeunits: 76, 80

A123) Comment Line on Sales Order Error In some cases, the amounts were wrongly displayed and the decimals were not shown. This has been corrected

• Table: 98
• Reports: 202, 204, 205, 210 and 405, 402.

A124) Blanket Orders and Standard Text Codes Error It was not possible to make an order if the blanket order included a line with type = <blank> and the No. field had a value. This has been corrected

• Codeunits: 87, 97.

A125) Blanket Order and Copy Document Error

1. Make a blanket Sales Order and click Make Order.
2. Go to the Sales Order that was created and post it.
3. Make a new Sales Order, then click Functions, Copy Document, and select Posted Invoice and select the invoice that was posted in step 2. Copy with 'Include Header' clicked and 'Recalculate lines' unclicked.
4. Now post this new order and you will get the error message:' Quantity shipped in the associated Blanket Order must not be greater than .... etc.'.

This has been corrected

• Report: 292

A126) Combine Shipment and Reservation Error

1. Create a new sales order for Customer 10000, with one sales line: Item, 70000, Quantity := 10
2. Change the field Reserve := Reserve::Always or reserve items manually
3. Qty. to Ship := 3
4. Post the Shipment
5. Go to Periodic Activities, Combine Shipment and run it for Customer 10000.

The error message "Reserved Qty. (Base) must be reduced" seems wrong. This has been corrected:

• Codeunit: 64, 74, 80, 90,
• Reports: 295
• Tables: 37, 39

A127) Combine Shipment; Delete Ext. Texts Error

1. Create a sales order with one item and an extended text for this item.
2. Insert the ext. text for this item
3. Post only the shipment
4. Delete one line of this ext. text
5. Use the report "Combine Shipment" to post this shipment.

You would get an error such as: "Salesline doesn't exist...." This has been corrected

• Codeunit: 64

A128) Message Box Appears During Batch Posting of Sales Invoices/-Credit Memos Error These two reports provided an option for replacing Posting Date on each posted invoice/credit memo. If this option was active, a Message box appeared after posting of each posted invoice/credit memo. This has been corrected

• Reports: 297, 298

A129) Incorrect Overdue Warning for Foreign Currencies Error If you entered an amount in a Sales Journal in a foreign currency, the system would compare that amount to the Credit Limit in LCY, that is compare DKK10 against Pounds Sterling 10 , giving you an incorrect credit warning. This has been corrected

• Form: 343
• Table: 81

A130) Sales Order Header and Currency Code Error There were problems when refreshing the fields "Sell To Customer No." and "Bill To Customer No." This has been corrected

• Tables: 36 and 38

A131) Copy Document and Bill-to Customer No. Error If you copied a posted sales invoice to a sales order and did NOT recalculate lines but included a header, the Bill-to Customer No. was not inserted on the line. This has been corrected

• Tables: 111, 113, 115

A132) Drop Shipment Error If you had a purchase order with a drop shipment, you were unable to change the field "Pay-to Vendor No." in the Invoicing tab. This has been corrected

• Tables 38 and 36

A133) Missing Test on Whether the VAT Prod. Posting Group was Filled Out When Posting a Shipment Issue There should be a test on this when you only ship, such as when you invoice the sales line. This has been corrected

• Codeunit 80

A134) Error Message in Sales Quote, Blanket Order and Credit Memo Error

1. Go to Sales Quote and make a new sales quote
2. Fill in the Item No. and an Error Message pops up

You also get this error message when you try to make a Blanket Order and a Credit Memo. This has been corrected

A135) Credit Memo Copied from an Invoice with Cash Discount. Error When using a copy function on a credit memo to copy an invoice with a cash discount already granted, the resulting amount on the credit memo was the full amount from the original invoice, without the cash discount. This has been corrected:

• Reports: 492, 292

A136) Copy Documents can Copy to Itself but Gives Error Message Error It should not be possible to select the document to which you are copying. This is valid within both Sales & Receivables and Purchase & Payables This has been corrected:

• Reports: 292, 492

A137) Appl.-to Item Entry/ Lookup F6 Error If you wanted to balance a sales line with an Item No., for example, 70000 via Appl.-to Item Entry (and Serial No.) and you choose the item with F6 (Lookup), you would get all fields (in the sales line) filled automatically (e.g. Location Code and so on). If you did not use F6 but filled in the Serial No. (Appl.-to Item Entry) manually, nothing was automatically filled in. This has been corrected

• Table 37, 39

There is no difference between using F6 and doing the same manually.

A138) LookupFormID Wrong in Sales & Receivables Setup - Table 311 This has been corrected

• Table: 311

A139) Stockout Warning Problem Error While creating a sales order, when you changed the item No. from a previous line, you did not receive a proper stockout warning. This has been corrected

• Forms: 342

A140) Sales Document – Test Calling Wrong Function Error In W1 2.01, the function UpdateAmounts has been made global (Local = <No>). Unfortunately, this had a side effect on Report 202 (Sales Document - Test). The Function UpdateAmounts should have been called from report, which is a local function in the report instead of UpdateAmounts behind the table. This has been corrected

• Report: 202

Issues

A141) List from Item Card Issue When you selected Purchase-> Orders or Sales -> Orders from an item card, you got a list of order lines for the item. You could consider a line button to show main Order Document and Reservation Entries. This has been corrected

• Forms: 48, 56

Service Management

Features

A142) Service Management Functionality Feature The Service Management functionality is a completely new application area that we introduce in Navision Solutions 3.00. The application area targets service organizations that want to deliver superior customer service while staying profitable.

A143) Service Order Management Feature The Service Order Management functionality allows the user to create and keep track of service orders. This implies the following possibilities: preventive maintenance service generated from service obligations stated in a contract; quotations on a service, which when agreed on can be converted into a service order; and creation of service orders on a “once-off” basic.

A144) Service Item Management Feature Service Item Management allows a service organization to register basic information about the items, which are objects for service. This can be: contractual information, such as response time, contractual values, upcoming service; component management of items, which makes it possible to keep track of service items that consists of different parts (BOM structure). This enables the service organization to manage, for example, warranty issues separately on a component level.

A145) Service Contract Management Feature Service Contract Management enables service organization to set up, manage and monitor service related contractual engagements with their customers. All the conditions for the contract can be recorded, warranty, service level, spare parts, and so on. It is possible to set up service contract templates and groups, which allow service organizations to use and reuse standardized contractual information. The function also includes contract quote, which is useful when negotiating over a period of time. This allows you to save whatever you have in the contract quote on a specific time, and it lets you convert the quote into a contract when ready.

A146) Planning and Dispatching Feature The planning and dispatching features allow service organizations to schedule and allocate resources in an optimal way in order to meet customer expectations and obligations. The dispatching feature provides the user with the opportunity to schedule and allocate resources according to, for example, availability, skills and geographical proximity to the service site. Furthermore, the dispatching feature provides an overview of the overall service load level of the organization. Additionally, service tasks can be prioritized and escalated.

A147) Job Scheduling Feature Job scheduling enables service organizations to automate otherwise tedious and time consuming manual work, such as contract renewal and generation of preventive maintenance service orders.

A148) Integration with Navision Solutions Feature Service Management is tightly integrated to various application areas in Navision Solutions. This implies the following:

• It is possible to set up items so that a sale will automatically generate a service item.
• Purchase orders can be created directly from a service order and linked to this.
• The shipping of spare parts in relation to service, for example, is handled through the functionality in the distribution application area.
• The nonstock item is available from the service order, which allows you to choose nonstock items for the service order.
• The substitution function has been extended to include nonstock items as well.
• You can make reservations of spare parts for service orders and status tracking of spare parts that are manufactured are supported.
• Information on the resources in the Human Resources application area is used for resource planning and allocation.
• Service order history is logged through the Business Interaction Management application area.
• Service orders can be related to jobs in the Jobs application area for cost distributions purposes.

Errors fixed

Issues

Purchases & Payables

Features

A149) Improvement of the Requisition Worksheet The planning function, Reorder Inventory Items, on the requisition worksheet did not meet the demands for the new multilocation concept. The Requisition Worksheet planning functionality is now technically integrated with the Supply Planning functionality from the Manufacturing application area. The two functions are integrated, but there will still exist separate requisition worksheets and planning worksheets. The enhanced functionality is available with the existing Purchase Order Management granule.

Errors fixed

A150) Bank Account Currency Code and Vendor Ledger Entries: When running the Suggest Vendor Payments batch job (393) with Bal. Acc. Type = Bank Account and the bank in Bal. Account No. had a Currency Code <> ‘’, and this currency is different from the Vendor Ledger Entries to be paid, and error occurred. This has been corrected.

• Suggest Vendor Payments report (393)

A151) In the Apply Vendor Entries form (233) a variable was incorrectly defined (Decimal) In Apply Vendor Entries form (233) variable “I” in CalcApplnAmount were incorrectly defined (Decimal) than in Apply Customer Entries form (232) (Integer). This is corrected so variable “I” in CalcApplnAmount on Apply Vendor Entries form (233) is defined as Integer. This has been corrected

• Apply Vendor Entries form (233)

A152) Problems with Manual Checks and Document Numbers on Payment Journal Lines When running the Suggest Vendor Payments batch job (393) with the settings Summarize per Vendor unchecked, New Doc. No per Lin unchecked and Bank Payment Type = Manual Check journal lines with the same journal numbers were created. When the journal was posted an error message occurred, saying that Check XXX already existed for this Bank Account instead of an message saying that the combination Bank Payment Type = Manual Check, Summarize per Vendor and New Doc. No. per Line unchecked is not allowed. This has been corrected.

• Suggest Vendor Payments report (393)

A153) Blanket Orders Error When printing a Blanket Order, the No. field is always printed for the Vendor Item No. that was specified on the Ordering tab of the relevant Inventory item. The error is that when a Blanket Purchase Order is raised to a different Vendor, the Blanket Order still prints the same Vendor Item No. This has been corrected:

• Reports: 404, 410

A154) Inconsistency in the Type Field between Invoices and Posted Invoices. Error In 'Purchase Lines' (as part of Purchase Invoices), the field 'Type' allowed you to specify Account, Item or Fixed Asset. In 'Purchase Invoice Line' (as part of Posted Invoices), in the field 'Type', you could specify Account, Item, *Resource*, or Fixed Asset. This has been corrected

• Tables: 121, 123, 125

The Resource option has been removed, but the extra comma in the option string has been kept.

A155) Blanket Orders Missing in Extended Text Error Missing blanket order option for extended text. This has been corrected

• Table 279
• Form 386
• Codeunit 378

A156) Invoice a Blanket Sales Order Although you Haven't Shipped it Yet Error

1. Create a blanket sales order for any item with any quantity (e.g. 10)
2. Make an order from the blanket order in step 1)
3. Select the item in the order in step 2) that is a drop shipment
4. Create a purchase order and get the sales order (from step 2)
5. Receive the purchase order (important: do this in the purchase order window) --> the sales order will be received automatically
6. Invoice the sales order --> the sales order is completed and will be deleted automatically.

That's OK, but the blanket sales order does not work accordingly: Quantity Shipped = 0 and Quantity Invoiced = 10? This has been corrected

• Code unit: 90

A157) Invoice Discount on Purchase Documents Error In purchase documents, if you calculate invoice discounts and then you remove the flag "Allow Invoice Disc." from the line, the Unit Cost (LCY) is not recalculated. This has been corrected

• Table 39

A158) Property on "Reserved Qty. on Inventory" Field (no 101) in Item Table (no 27) Error Property: DecimalPlaces for Field 101 "Reserved Qty. on Inventory" is <Undefined> although Field 102 "Reserved Qty. on Purch. Orders" and Field 103 "Reserved Qty. on Sales Orders" are formatted as 0:5. The Invoice Credit Memo- Message needs to appear once per Batch Job whose Posting Date has been changed. This has been corrected:

• Reports: 296, 297, 298
• Codeunit: 80

A159) Post Purchase Batch and Document Date Change Error When you changed the Document Date as part of the Post Batch routine for Purchase Orders, the Due Date and the Payment Discount Date were not recalculated. This has been corrected:

• Codeunit 90

A160) Change of "Bill to Customer" in Sales Order Error If you choose a unit of measure in a sales line that was different from the base unit of measure in the item card and then changed the "Bill to Customer" in the sales header, the unit of measure was re-set back to base unit of measure on the item card. This has been corrected

• Tables: 36 and 38

A161) Two Intrastat Reports Must be Removed from Purchase Report List Error The placing of Intrastat reports in the Purchases & Payables application area was old – Intrastat reports are to be placed in G/L. This has been corrected

• Purchase and Payable report list.

A162) Make Orders: Two Variables have the Same Name. Error In Report 493 – the two variables for Make Orders were named equally. This has been corrected

• Report 493

A163) Purchase Line Gets Always Reserve = Always. Error If the selected item on a purchase line had the option Reserve = Optional, then the purchase line always got the option Reserve = Always, instead of retrieving the option from the purchase header. It works correctly for the sales documents. This has been corrected as for sales line.

A164) Different Currencies not Allowed in Get Receipt Error

1. Create a purchases order for vendor100000.
2. Receipt the order.
3. Go to purchases invoices.
4. In the header insert vendor 10000, and on the Foreign tab, insert the currency DEM.
5. Go to functions, Get Receipts and get the already created receipt. Press OK.
6. Post the invoice.

If you try to do the same in sales, the system gives you an error message, and doesn’t let you copy the shipment with a different currency code in the invoice header.

This does not happen in purchases.

The problem with this is that you will have wrongly calculated your Inventory costs.

Support note titles: “Oh no!!!!”; “Invoice and Receive in different currency”; “Invoice in other currency than shipment” This has been corrected

• Codeunit: 74

A165) Outstanding Quantity is not Maintained Correctly when Using Get Shipment Error All statistics based on the fields in invoices were wrong. The Reservation system allowed reservation on the line even if the quantity was already shipped. The Quantity related fields on the Shipment and Receipt Line tables were not properly maintained for the Reservation System, Combine Shipments, and Get Shipment/Receipt functionalities. This has been corrected

• Codeunits: 64, 74, 80, 90
• Reports: 295
• Tables: 37, 39

A166) Part Shipment with Different Location Codes Error When posting different shipments with different location codes on one line and trying to post one invoice for all the partial shipment on that line, you received an error message because different location codes were used on the shipment lines.

That was problematic because:

• You could not make combined shipments
• You could not use the batch posting function
• The customer received three invoices because we used three different location codes.
• The operator needed to post in the same sequence as the shipments were posted.

Why is there a TESTFIELD on the location code?

Steps to reproduce

1. Create an order for customer 10000 with item no. 70000 Quantity 100.
2. Post a shipment with quantity 50 on location code "BLUE"
3. Post a shipment with quantity 50 on location code "RED"
4. Try to post an invoice for both shipments with the quantity 100.
5. You get an error message, that the location code must be red.

This has been corrected

• We have removed the TESTFIELDS.

The concept is that the Location Code and Bin Code will follow the shipment (ILE) and that the Dimensions (not meaning Location and Bin) will follow the Invoice (Value Entry).

Location Code/Bin Code: The Location/Bin Code TESTFIELDS in COD80 and COD90 is removed and the consequences are handled in COD22. The Item Ledger Entry will be the "master". This means that whenever an Invoice is posted, the Value Entry will get the Location Code from the related Item Ledger Entry.

The consequence is that the Item Ledger Entry and the Posted Invoice Line might have different Location Codes. At some time in the future, the removal of the location code on the posted invoice line should be considered. Similarly, future consideration should be given to removing the location code on the posted invoice line, as this can be confusing.

Dimensions: The functionality that will create different dimensions on value entries belonging to the same Item Ledger entry has already been implemented in the costing functionality. This means that the TESTFIELD on the dimensions can be removed without problems. This change will make the dimensions at the time of invoice posting the dimensions that are used on the value entry.

The consequence is that the dimensions on the Item Ledger entry can be different from the dimensions on the value entries.

• Codeunits: 80, 90 and 22

A167) EXIT Command Used in Table 246 Error This is not according to standard. This has been corrected

• Table: 246

A168) Error in Request Form of Report 492 Error In the CASE statement on the request form of report 492, on the "OnOpenForm" trigger there were two statements to deal with "DocType::Quote". The second one was wrong.

Support Note reference: “Error in request form of report 492?” This has been corrected

• Report: 492

A169) Wrong Filter in Credit Memos Error When a certain filter (e.g. a "date filter") was added in form "Apply Vendor Entries" (under field "Applies-to Doc. No." On the Credit Memo Header, this filter was maintained when you went to another Credit Memo (from another Vendor/Customer). This has been corrected

• Tables: 36, 38

Issues

A170) Currency Code Added on Check Preview. When previewing a check, the amount in writing was without currency code. Changes have been implemented.

• Check report (1401)
• Check Preview form (404)

Inventory

Features

A171) Transfer Documents The transfer document keeps track of the items being shipped out of one location and received into another location. One transfer document only handles transferring from one location to another.

A172) Item Substitution This feature enables the user to link one item to another item (both interchangeable and not interchangeable). You can then offer the customer a substitute item in case the item that the customer requests is not available. You can offer customers items with similar characteristics but with different brands or prices.

A173) Item Cross References This feature allows the user to let the customer refer to his own item number or the vendor’s number instead of the program’s item number. The program can support any normal numbering system available.

A174) Nonstock Items This feature allows the user to create a catalog of items that are not in inventory. A vendor or manufacturer’s items can be included in the program as a nonstock item. When a nonstock item is processed, it is created as a unique inventory item. Special orders can be created for nonstock items from the requisition worksheet.

A175) Item Tracking The existing serial and lot numbering feature has been discontinued. The new feature is more flexible with the ability to choose tracking at various points in the process between purchase and sale. Serial numbers can be generated automatically. The feature supports the cost evaluation methods FIFO, LIFO and specific.

The feature is not entirely integrated with the reservation and tracking system, and it does not support hard reservation (the ability to reserve a specific serial numbers at sales order entry time).

Errors fixed

A176) Wrong Link on Item Price Change Table The field VAT Business Posting Group had a wrong table relation. This has been corrected.

• Item Price Change table (40).

A177) Report 790, Wrong Variable Used Error The DataItem-Variable was used instead of the variable: ItemNo for this "local" Trigger. This has been corrected

• Report: 790

A178) Report 798, Date Compression and Item Ledger Entries Error It could be a problem from the user to have the possibility of retaining Location, Bin or Variant on this report. The user may inadvertently remove Item Ledger entries.

Support note Title: Date compression and Item Ledger Entries This has been corrected

• Report: 798

A179) Error in Intrastat Declaration Error When using the decimal number in a quantity field, you obtained incorrect results when you retrieved the Intrastat entries report. This has been corrected

• Table: 263
• Report: 594

A180) Phys. Inventory Journal and Posting No. Series Error When using the No. Series in Phys. Inventory Journals, the Doc. No was OK. However, if also using the Posting No. Series, the Doc. No was still from the No. Series. The Posting No. Series name was not transferred to the Item Journal line. This has been corrected

• Report: 790

A181) Field Bill of Materials in Table 90, BOM Component Error The field Bill of Materials in table 90, BOM Component, was only updated in the trigger number OnValidate. If a Bill of Materials was added to an item that was already part of a Bill of Materials, then the corresponding field Bill of Materials in table 90 was not updated. A correction should implement a flowfield. This has been corrected

• Forms: 90

A182) Error in Report 713 when Deleting Customer Error The error " Cust.-No ... does not exist" occurred when deleting a customer and then running the report 713 Inventory Customer-Sales.

Support Note Title: “idem to this one.” This has been corrected

• Report: 713

A183) Allow Update of Invoice Disc. on the Purchase Line Error The field "Allow Invoice Disc." was not updated from the Item on the Purchase Line. This has been corrected

• Table 27

A184) Item.Net Change has Wrong AutoFormatType Error In table 27, the field 70 "Net Change" has AutoFormatType = 1. This property should only be set for amounts. The correct value is <0>

This has been corrected

• Table 27

A185) Error when Deleting Customer Error It is possible to delete a customer who has an outstanding order. This has been corrected

• Codes have been added on the OnDelete trigger.

A186) Error in Report 792... Error The Unit of Measure Code placed on the tab Item Price (as RequestFilterField) in report 792, is unusable. This has been corrected

• Report 792

Issues

Warehouse Management

Features

A187) Warehouse Management This feature covers the ability to handle the physical flow of items in the warehouse, from receiving items to picking and shipping to customer.

Receiving goods involves the accurate processing of receipts and the accurate maintenance of records, as well as activities and rapid access to material as soon as possible for sales order fulfillment (for example, cross-docking). The receiving process ends with a put-away into inventory.

Shipping goods consist of deciding which and how goods should be picked out of the inventory with the assign functionality; when goods should be shipped; how goods should be shipped; and who should ship the goods.

Errors fixed

Issues

Manufacturing

Features

A188) Multilocation Supply Planning To enable the use of distributed warehouses, the supply planning functionality has been enhanced. Now it is possible to specify separate planning parameters on the stockkeeping unit card for each combination of location and item variant. The planning functionality uses the parameters from the stockkeeping unit card if this exists for the specific combination of item number, location code and variant code. If it doesn’t exist, the program uses the parameters on the item card.

A189) Supply Planning with Transfer and Service Orders The supply planning functionality has been extended to take both transfer orders and service orders into account when planning the replenishment of items. Service orders contribute to the demand pattern, while transfer orders will be both a gross requirement and a scheduled receipt. In addition, Transfer is defined as a new option in the Requisition System field on the stockkeeping unit card. If this field is set to Transfer, the planning functions issue transfer orders to replenish this item.

A190) Supply Planning with Blanket Orders Sales blanket orders are now additions to the production forecasts in the planning algorithms.

Errors fixed

A191) Update of Unit Cost for a Production Order If the items produced on a production order were reserved for a sales order, the Update Unit Cost batch job did not update the unit cost on the sales line, even when there was a check mark in the Update Reservation field. This has been corrected.

• Update Prod. Order Cost codeunit (99000757)

A192) Unable to Create an Extra Key with an End-User License It was not possible to create a new key for the Finished Production Order table with an end-user license. Support base reference: ”An end user cannot create an extra key in T 99.000.815” This has been corrected.

• Change Status on Prod. Order codeunit (99000788)
• Finished Production Order table (99000815)

A193) Error with the Fnshd. Prod. Order Cost Dev. Report When the user ran the Fnshd. Prod. Order Cost Dev. Report, an error message appeared. Support base reference: ”Error when running report 99000792” This has been corrected.

• Fnshd. Prod. Order Cost Dev. report (99000792)

A194) The Direct Unit Cost on the Prod. Order Component Table The value of the Direct Unit Cost field on the Prod. Order Component Table was not calculated correctly but this caused no functional problems. Support base reference: ”Purpose of extra multiply with "Qty. per Unit of Measure" in table 5407 field 13 Unit of Measure Code.”

This has been corrected.

• Prod. Order Component table (5407)

A195) Replan in Multiple Levels When a production order was replanned in multiple levels, some of the component quantities were multiplied by two. Support base reference: ”2.6 - Replan - multiplication error”

This has been corrected.

Replan Production Order report (99001026)

A196) Using the Shortage List with Various Units of Measures If a Unit of Measure different from the Base Unit of Measure was used on a Production BOM, the Shortage List report would show incorrect quantities.

Support base reference: ”Consumption journal and Shortage list calculates wrong considering Unit of Measure”

This has been corrected.

• Prod. Order - Shortage List report (99000788)

A197) Incorrect Table Relation in the Fnshd Prod. Order Comp. Table In the Fnshd Prod. Order Comp. Table, the Variant Code field was defined with an incorrect table relation.

Support base reference: ”Wrong relation in table 99000819 Fin. Prod. Order Component Field Variant Code”

This has been corrected. Fnshd Prod. Order Comp. Table (99000819) A198) Incorrect definition of the User ID Field The User ID field was defined incorrectly for several tables.

Support base reference: ”User ID is too short”

This has been corrected.

• Work Center Ledger Entry table (99000755)
• Machine Center Ledger Entry table (99000759)
• Prod. Order Ledger Entry table (99000794)
• Fnshd Prod. Order Ledg. Entry table (99000817)

A199) Incorrect Quantities in the Where Used Function The Where Used function showed incorrect quantities needed in some cases.

Support base reference: ”The function "Where-used"does not work correct”

This has been corrected

• Where-Used Management codeunit (99000770)

A200) Incorrect Expected Quantities for Certain Product Structures In certain cases, the value of the Quantity per field in the Prod. Order Component table was incorrect.

Support base reference: ”Expected quantity incorrect for certain Product structure.”

This has been corrected.

• Create Prod. Order Lines codeunit (99000787)

A201) Formatting the Production Forecast Form When the user changed the column sizes in the Production Forecast form, it caused problems later on.

Support base reference: ”Production Forecast screen - format gets corrupted”

This has been corrected

• Production Forecast form (99000919)

A202) Simulated M-T-O Production Orders It was not possible to refresh a Simulated Production Order.

Support base reference: ”Simulated PO and M-T-O”

This has been corrected

• Create Reserv. Entry codeunit (99000830)

A203) Unit Conversion Error in the Planning Calculations If the Purchase Unit of Measure was different from the Base Unit of Measure, the MPS/MRP calculations resulted in an incorrect quantity.

Support base reference: ”Unit conversion error in MRP calculation”

This has been corrected.

• Inventory Profile Offsetting codeunit (99000854)

A204) Update Unit Cost and Reserved Items The Update Unit Cost batch job did not update the items that were reserved.

Support base reference: “Update unit cost doesn't update reservation”

This has been corrected.

• Update Prod. Order Cost codeunit (99000757)

A205) Variant Code on Reservation Entries Not Related to the Item Variant Table When an Item Variant was renamed, the Reservation Entries were not updated properly. A missing table relation on the Reservation Entry table caused this.

Support base reference: “Reservation + Bin and Variant code”

This has been corrected.

• Reservation Entry table (337)

A206) Unit Cost on the Production Order Line incorrect When an item was produced in another Unit of Measure than the Base Unit of Measure, the Unit Cost could be incorrect.

Support base reference: “Unit cost wrong in PO invoicing item ledger entry if unit conversion”

This has been corrected.

• Update Prod. Order Cost codeunit (99000757)

A207) Error in Standard Cost Calculation The Standard Cost calculation terminated with an error if a scrap percentage including decimals was used on the Prod. BOM Line.

Support base reference: “Standard cost calculation impossible with decimal scrap % on BOM”

This has been corrected.

• CalculationManagement codeunit (99000754)

A208) Average Cost Calculation In some cases, the calculation of the average cost led to an incorrect result. The problem happened when few invoiced units of an item were in inventory.

Support base reference: “Average cost in NManufacturing 2.60B”

This has been corrected.

• Item table (27)

A209) Detailed Calculation Report and Phantom BOMs The Detailed Calculation report could not handle Phantom BOMs. The cost of components in the Phantom BOM was not shown.

Support base reference: “Detailed calculation report does not show phantoms”

This has been corrected.

• Detailed Calculation report (99000756)

A210) Quantities of Components in an M-T-O Production Order In some cases when M-T-O production orders were used, the Quantity per field of the Prod. Order Components were calculated incorrectly.

Support base reference: “Bad posting consumption for item with M-T-O”

This has been corrected.

• Prod. Order Line table (5406)

A211) Planning Flexibility on Planning Lines The Planning Flexibility field at the Planning Lines was not transferred to the order when the Accept Action Messages batch job was executed.

Support base reference: “Question regarding option field "Planning Flexibility" on the planning worksheet line/ Production order line.”

This has been corrected.

• Carry Out Action codeunit (99000813)

A212) Deletion of Project or M-T-O Production Orders When Project or M-T-O Production Orders were deleted, the components, routings and capacity need for subsequent production order lines were not deleted, as they should have been.

Support base reference: “Deleting Project Orders”

This has been corrected.

• Prod. Order Line table (5406)

A213) Reorder Point and Items at Inventory In some situations, the planning calculation could ignore items at inventory when the quantity was evaluated against the Reorder Point.

Support base reference: “Item Ledger Entry being ignored, when comparing to Reorder Point...?”

This has been corrected.

• Inventory Profile Offsetting codeunit (99000854)

A214) Deleting Production Forecasts When Production Forecasts are set to zero, it is done by creating a record with a negative quantity. Unfortunately, the planning calculations just checked whether a record existed. For that reason, it could happen that forecasts entered by an error and deleted again could cause an item to be regarded as an MPS item.

Support base reference: “Productions-forecasts mps/planning error”

This has been corrected.

A215) Inventory Column in the Item Availability by Locations Form The Inventory column in the Item Availability by Locations form was calculated incorrectly.

Support base reference: “Item Availability by Location - Form 515”

This has been corrected.

• Item Avail. by Location Lines form (515)

A236) The Planning Calculation Ignores Items at Inventory In some situations, the planning calculation ignored items at inventory when the quantity was evaluated against the Reorder Point.

Support Base reference: “Item Ledger Entry being ignored, when comparing to Reorder Point...?” This has been corrected

• Inventory Profile Offsetting codeunit (99000854)

A237) The Rolled-Up Cost Shares Report The values in the Rolled-Up Cost Shares report were not correct when components with Qty. Per different from 1 were used.

Support Base reference: “Rolled Up Cost Shares report not calculating correctly”. This has been corrected.

• Rolled-up Cost Shares report (99000754)

A238) Incorrect Order Tracking Entries When the Order Tracking Policy was set to Tracking Only, it could cause problems to change the item number at order lines.

Support Base reference: “Incorrect Reservation Entries”. This has been corrected. Sales Line-Reserve codeunit (99000832) Req. Line-Reserve codeunit (99000833) Purch. Line-Reserve codeunit (99000834) Item Jnl. Line-Reserve codeunit (99000835) Prod. Order Line-Reserve codeunit (99000837) Prod. Order Comp.-Reserve codeunit (99000838) Plng. Component-Reserve codeunit (99000840) Item Ledger Entry-Reserve codeunit (99000841) Reservation Management codeunit (99000845) A239) Non-default Unit of Measure and Production Orders If a Production Order was created from a Sales Line with a Unit of Measure different from the default Unit of Measure, it was not possible to change the status of the Production Order.

Support Base reference: “Unit of measure conversion problem - sales order to production order”. This has been corrected.

• Create Prod. Order Lines codeunit (99000787)
• Create Prod. Order from Sale codeunit (99000792)
• Calculate Planning Line codeunit (99000809)
• Create Reserv. Entry codeunit (99000830)
• Sales Line-Reserve codeunit (99000832)
• Req. Line-Reserve codeunit (99000833)
• Purch. Line-Reserve codeunit (99000834)
• Item Jnl. Line-Reserve codeunit (99000835)
• Transfer Line-Reserve codeunit (99000836)
• Prod. Order Line-Reserve codeunit (99000837)
• Prod. Order Comp.-Reserve codeunit (99000838)
• Plng. Component-Reserve codeunit (99000840)
• Service Invoice Line-Reserve codeunit (99000842)
• Reservation Management codeunit (99000845)
• AvailabilityManagement codeunit (99000889)

A240) Text Overflow When the Status of a Production Order was Changed If the Description, Search Description or Description 2 fields on a Production Order contained more than 30 characters, an error occurred when the status of the Production Order was changed to Finished.

Support Base reference: “Text overflow when changing status from released to finish on a PO”. This has been corrected.

• Finished Production Order table (99000815)
• Finished Prod. Order Line table (99000818)

Issues

A216) Performance of the Replan Batch Job The performance of the Replan batch job could be improved significantly.

Support base reference: “Function Replan and performance”

In response to this issue, a change has been implemented.

• Reservation Management codeunit (99000845)

Cap. Reqts. Planning

Features

A217) Finite Loading The finite loading feature enables more realistic planning for capacity constrained resources. It is now possible to specify those resources (work centers or machine centers). Afterwards, the scheduling algorithms will make sure that the allocated load at the specified capacities does not exceed a specified limit.

Errors fixed

A218) Update of the Production Order Line The update of the production order line was not correct when a routing that had only one operation was modified.

Support base reference: “Not correct updating of PO lines when changing Prod. Order Routing line.” This has been corrected.

• Prod. Order Routing Line table (99000792)

A219) Incorrect Scheduling of Production Orders When a two-shift calendar was used for a machine or work center, it sometimes caused some problems in scheduling algorithms for production orders.

Support base reference: “PO back scheduling wrong when using 2 shifts MC calendar” This has been corrected.

• Calculate Routing Line codeunit (99000774)

A220) Rescheduling an Operation on a Production Order When an operation on a production order was rescheduled, the workload on already finished operations could be recreated.

Support base reference: “Not correct handling of previous workload when rescheduling a next operation.” This has been corrected.

• Prod. Order Routing Line table (99000792)
• Check Prod. Order Route codeunit (99000772)
• Calculate Prod. Order codeunit (99000773)
• Calculate Routing Line codeunit (99000774)

A221) Sorting of Entries in the Prod. Order Capacity Need Form The entries in the Prod. Order Capacity Need form were not sorted in a proper sequence. This has been corrected.

• Prod. Order Capacity Need table (99000793)
• Work Center Load Lines form (99000888)

A222) Lot Size on Routing Line Ignored When you specify a Lot Size on a routing line, the specified run time is the expected time used for a quantity equal to the lot size. When the program automatically flushed, this Lot Size was ignored. Support base reference: “Lot Size field on Routing Line is ignored during Auto Flushing.” This has been corrected.

• Change Status on Prod. Order codeunit (99000788)

A223) Absence Registered on Machine Centers Using a Consolidated Calendar Was Ignored When you used a consolidated calendar for a work center, the program ignored the absence that you registered on the related machine centers.

“Consolidated calendar” This has been corrected.

• Calculate Work Center Calendar report (99001046)

A224) The Calculate Subcontracts Batch Job Used the Incorrect Description When you ran the Calculate Subcontracts batch job, the Description field from the item card was used instead of the description field from the operation on the current routing.

Support base reference: “Subcontracting Worksheet- Description” This has been corrected.

• Calculate Subcontracts report (99001015)

A225) Using the Same Routing on Several Production Order Lines When you used the same routing on several Production Order lines, some problems would occur.

Support base reference: “Error in function "Make order from MRP"” This has been corrected.

A226) Using a Concurrent Capacity Greater Than the Capacity of the related Work or Machine Center It was not possible to use a routing line with the concurrent capacity set to a value greater than the capacity of the related work or machine center. In addition, it seemed that it was not possible to use a capacity of less than 1 (one) for a work or machine center. This has been corrected.

• Calculate Routing Line codeunit (99000774)

A227) The Table Relation Property for the Field Routing No. For certain tables, the table relation property was left blank for the field Routing No. This caused problems later on, when routing was renamed.

Support base reference: “Tablerelation property on routing No. missing”

This has been corrected.

• Prod. Order Routing Line table (99000792)
• Prod. Order Capacity Need table (99000793)
• Fnshd Prod. Order Rtng Line table (99000816)

A228) Problem With Existing G/L Entry In some cases, when using automatic flush of capacity, problems with existing G/L Entries could occur.

Support base reference: “G/L Entry Entry No. 'XXXX' already exists for RELEASE 260B”

This has been corrected.

• Output Jnl.-Post Line codeunit (99000781)

A229) Subcontracted work shown in the availability forms When Subcontracted Work was issued, the quantity was added to the available quantity.

Support base reference: “Scheduled Receipt in Item Availability and Subcontract Purchase order”

This has been corrected.

• Calculate Subcontracts report (99001015)

A230) Subcontracting Cost Calculation Based on Units When the Capacity Cost for a Subcontracted Work Center was based on Units, the Expected Subcontracting Cost on the Production Order Statistics was incorrect.

Support base reference: “Prod.order subcontracting cost not calculated correctly when based on units”

This has been corrected.

A231) Using Unit of Measure on an M-T-O Production Order When a Unit of Measure smaller than the Base Unit of Measure was used for a component on an M-T-O Production Order, it was not possible to refresh the Production Order.

Support base reference: “Reserved Quantity and MTO order”

This has been corrected.

• Create Prod. Order Lines codeunit (99000787)

A232) Expected Capacity Cost for Production Orders When output was posted to a Production Order, the expected capacity cost in the Production Order Statistics was changed.

Support base reference: “Expected capacity cost in PO statistics is deleted”

This has been corrected.

• Output Jnl.-Post Line codeunit (99000781)

A241) Subcontracted Purchase Orders with Location When subcontracted Purchase Orders were made with a Location code from the Subcontracting Worksheet, the resulting Item Ledger Entry got the Location code from the Purchase Order Header and not the one from the Purchase Order Line.

Support Base reference: “Error with Purchases Order when we make Order from a Subcontracting Worksheet.”. This has been corrected.

• AddOnIntegrManagement codeunit (5403)

A242) Subcontracting Cost on Production Order Statistics When subcontracted work was based on “Units” instead of “Time”, the Subcontracting Cost at the Production Order Statistic Window was calculated incorrectly.

Support Base reference: “Prod.order subcontracting cost not calculated correctly when based on units”. This has been corrected.

• Calculate Routing Line codeunit (99000774)
• Calculate Planning Route Line codeunit (99000810)

Issues

A233) Date-Time Field on Production Orders In general, the implementation of the Capacity Requirements Planning algorithms was more complex than needed because of the separation of the date and time fields. New Date-Time fields have now been added to the relevant tables in the Capacity Requirements Planning area. These fields enable the use of simpler algorithms in the scheduling of production orders.

In response to this issue, a change has been implemented.

Resources

Features

Errors fixed

Issues

Jobs

Features

Errors fixed

A234) Additional Reporting Currency and Additional Currency Total Cost and Add.-Currency Total Price on the Job Ledger Entries: If you are posting a purchase order linked to a job (or a sales invoice linked to a job) and you are not using an Additional Reporting Currency, then the fields Additional Currency Total Cost and Add.-Currency Total Price on the resulting Job Ledger Entry would be incorrect. The fields Additional Currency Total Cost and Add.-Currency Total Price should be zero but are not. If you are using an Additional reporting Currency, then if you are posting a purchase order linked to a job on a vendor with a currency code equal to the Additional Reporting Currency or a sales invoice linked to a job on a customer with a currency code equal to the Additional Reporting Currency, then the fields Additional Currency Total Cost and Add.-Currency Total Price on the resulting Job Ledger Entry would be incorrect. The fields Additional Currency Total Cost and Add.-Currency Total Price contain zero values were it should have had a value different from zero. This has been corrected.

• Job Jnl.-Post Line codeunit (202)

A235) Prices in Connection with Jobs Error If a job No. was inserted in a sales line the prices were re-calculated but the fields “Amount” and “Amount incl. VAT” were not.

Support notes reference: Support base reference: “Invoicing a Job”, “Prices in connections with jobs” This has been corrected

Issues

Human Resources

Features

Errors fixed

Issues

Development Environment and Database Changes

Navision Server

Features

P1) Navision Server Snap-in for Microsoft Management Console Feature A snap-in for MS Management Console is provided to control Navision Servers installed on Windows NT or Windows 2000.

Errors fixed

Issues

SQL Server Option

Features

P2) Support for MultiLanguage and Data Retrieval from External Tools Feature When creating/altering a database with the option ‘Maintain SQL views’ checked, SQL Server will create and maintain a view for each language ID that is added to, deleted from or changed in a table in Navision Solutions. For further description, please refer to the relevant documentation.

P3) Workaround for Problems with Retrieving Data from SQL Server Tables containing certain characters Feature Retrieving data from SQL Server tables where an identifier contains a period (.), single quote ('), or double quote (") from 3rd party products is often very difficult if not impossible. With the release of Navision Solutions 3.00 the above-mentioned characters will be replaced on the SQL Server with an underscore (_) for database names, company names, table names and column names according to the following rules:

Character Database Name Company Name Table Name Column Name . (period) Not allowed Replaced with _ (underscore) Replaced with _ (underscore) Allowed ' (single quote) Allowed Replaced with _ (underscore) Replaced with _ (underscore) Replaced with _ (underscore) " (double quote) Changed to _ (underscore) Replaced with _ (underscore) Replaced with _ (underscore) Not allowed.

From within the Navision Solutions Client the company, table and column names will be presented as usual.

Existing identifier names will be converted the first time a Navision Solutions 3.00 client connects to the database.

As periods in database names are no longer allowed, a Navision Solutions 3.00 client will refuse to connect to a database with a period in the database name. Existing databases with a period in the database name should be converted manually. In order to rename a database from ‘OldName’ to ‘NewName’, execute the following SQL statements in Query Analyzer: set quoted_identifier on use master exec sp_dboption 'OldName', 'single user', 'TRUE' sp_renamedb 'OldName', 'NewName' exec sp_dboption 'NewName', 'single user', 'FALSE'

Please remember to update other SQL scripts using the renamed database.

P4) Record Level Security Feature Record Level Security is a feature whereby you can limit the access users have to the information that is stored in the tables and ensure that they gain access to specific records in the tables only. You can read more about Record Level Security in the Installation and System Management: SQL Server Option manual.

P5) SQL Server 2000 Support Feature Support for the use of a SQL Server 2000 was introduced with Navision Financials 2.60.C. With the release of Navision Solutions 3.00, you can take further advantage of features of the SQL Server 2000. You can read more about using SQL Server 2000 in the Installation and System Management: SQL Server Option manual.

P6) Enhanced Linked Server Support Feature With this release, it is possible to insert and modify data in a linked server on a SQL Server. You can read more about using linked servers in the Application Designer’s Guide.

P7) Getting Table Information for Linked Tables Ignored Feature Getting the record count for a linked table could take a significant amount of time when viewing the table information. To avoid this, all linked tables are being ignored when getting table information.

P67) Client Monitor has been Enhanced and is also Available for the SQL Server Option Feature The Client Monitor has been enabled for the SQL Server option, containing ‘SQL Statement’, ‘Reads’ (logical) and ‘Server Time’ parameters. An ‘Elapsed Time’ parameter has been added for both server options which is the total round-trip time for the command. Additional Date and Time fields, containing a stamp of the time at which the client issues commands, have been added for both server options. The ‘Physical Reads’ event in the Navision Server version has been renamed to ‘Reads’, but still denotes physical reads (for the SQL Server option they are logical reads). The ‘CPU Time’ event has been renamed to ‘Server Time’ but remains CPU time for both versions. All other parameters are unchanged but may differ slightly in their availability between the two server versions. Errors fixed

P8) Improper Error Message in Case of Key Violation when Using Non-clustered Index Error In case of a key violation the error message depended on the type of index. When using clustered index a proper error message was displayed, but when using non-clustered index an encapsulated SQL Server error message was displayed. Link to Support database: Support base reference: “Error with INSERT when the clustered index is removed”

This has been changed to make both error messages look like the one used for clustered indexes.

P9) Changing Password Impossible when Using Database Login and Connected to MS SQL 2000 Error When using the MS SQL Server option and database login to connect to a MS SQL Server Option database on SQL Server 2000, the user was not allowed to change password from the Navision Financials Client.

This has been corrected

P10) Security Leak with the Role ‘Security’ Error A user assigned the roles ‘Security’ and ‘All’ was able to grant himself access to the role ‘Super’. Link to Support database: Support base reference: “Serious security bug in SQL Option”

This has been corrected for the MS SQL Server Option

P11) Error when Changing Read Permission Error When changing Read permissions for a user the error message ‘Error 0 in module 0’ was raised under special circumstances. Link to Support database: Support base reference: “Error 0 in module 0”

This has been corrected.

P12) Object Designer not Updated when Linking to Existing Objects Error When a new table description is created that will link to an existing SQL Server object, and the dialog prompting to link was OK'd, the object designer did not refresh as it would have with a new ordinary table. This has been corrected

P13) Data type ‘DateFormula’ Couldn’t be Used with the MS SQL Server Option Error It was impossible to create and save a table containing a field of the type dateformula. Link to Support database: Support base reference: “SQL and Dateformula”

This has been corrected

P14) Flowfield Summing Error in Special Situations Error In the following situations, SIFT sums calculated using the SQL Server SIFT implementation would fail: • The last field in the aggregate key (the combination of secondary and primary key fields) was of type Date • A (flow) filter was applied to the date field. The filter should specify a date range that didn’t match whole months • The MaintainSIFTindex key property was set to Yes (default) In those cases, the sums returned by the server would be wrong. The error was introduced in NF2.60.D This has been corrected Link to Support database: Support base reference: ” SIFT sums calculated using the SQL Server SIFT implementation will fail”

P15) OnDelete Trigger Variables didn't Reset Filters for SQL Server Option Error OnDelete triggers called repeatedly from a DELETEALL didn't reset their filters between calls. So filters set from deleting the first entry, was still active when DELETEALL called the trigger the second time (for the second record to be deleted - if any). This has been corrected This now works for SQL Server Option as for Navision Server. Support base link: Support base reference: ”Major critical BUG”

Issues

P16) Strange Behavior with Linked Tables when Date/Time Formats didn’t Match Issue When linking a Navision table to a SQL Server view containing date/time fields with data being invalid seen from a Navision point of view, could lead to undesired behavior when running the Navision table.

The functionality is changed to check for correct format when reading a date/time field. If the format is not correct, an error message is displayed.

Development Environment

Features

P17) Hyperlinks in Navision Solutions Feature The Navision Solutions client now supports hyperlinks to forms and reports. This is reflected in the File and Edit menu, where entries are changed. It is now only possible to send e-mail when there is something to attach to the e-mail. Hyperlinks are also accessible from C/AL through new functions and triggers on forms and reports. Together with hyperlinks, the following new C/AL functions are added: • form.URL, report.URL • form.OBJECTID, report.OBJECTID • table.SETVIEW, table.GETVIEW • table.SETPOSITION, table.GETPOSITION • CONTEXTURL For more details, see the online Help (C/SIDE Reference Guide) and the Manual Introduction.

P18) Dynamic Captions Feature To handle the configuration of field captions for dimensions, the concept of a dynamic caption or, more precisely, label classes are introduced. This new feature allows the user to centrally configure the caption of a field or control without having to modify code. The following components are new: • The property “CaptionClass” • form.UPDATECONTROLS For more details, see the online Help (C/SIDE Reference Guide).

P19) New Data Types Feature The following data types have been added to the C/SIDE development environment: • Variant • InStream • OutStream For more details, see the online Help (C/SIDE Reference Guide) and the Application Designer’s Guide.

P20) New Function for Navision Application Server Feature Together with Navision Application Server, the system.GUIALLOWED function has been added to the development environment. For more details, see the online Help (C/SIDE Reference Guide) and the Application Designer’s Guide.

P21) Enhancements to the Automation Controller Issue The Automation Controller has been improved with the following: • The Automation Controller now supports events, a new property WithEvents secure backward compatibility. • The new function IsClear checks whether or not an automation object has been added. • Functionality allowing parsing properties on automation objects by reference has been added. For more details, see the online Help (C/SIDE Reference Guide) and the Application Designer’s Guide.

P22) Enhanced Functionality for Codeunits Feature The codeunit objects have been enhanced with two new features: • Single Instance Property • Codeunits as Objects For more details, see the online Help (C/SIDE Reference Guide) and the Application Designer’s Guide.

P23) Rec.CURRENTKEY now Returns Field Caption Issue In previous versions, the function rec.CURRENTKEY returned a string that contained the field names of the current key. In a Multilanguage solution, this is not acceptable. The user wants the field captions in their own language. Rec.CURRENTKEY now returns a string that contains field captions, instead of field names.

P24) Max String Length has been Increased Issue The maximum string length has been increased from 260 to 1024 characters.

P25) Multilanguage enabling Multilanguage in Navision Solutions provides functionality that can handle different languages within the same application. This means that users can choose among several languages when working in the application, independent of their geographical location. To find out more about the Multilanguage-enabling functionality, look in the document “ML Product Specification.doc” in the Multilanguage folder on the localization CD.

Errors fixed

P26) DataFormula and Lower Case Letters Error It was not possible to enter a DateFormula in lower case letters. This has been corrected.

P27) Internal Error 6 in Module 6 Error Some bitmaps in reports that had defect bitmap headers could invoke an "Internal Error 6 in Module 6" when used in reports. This has been corrected.

P28) Navision Financials Crash in Report Designer Error The problem was that the program did not clear the field menu selection. This has been corrected.

P29) Internal Error 4 in Module 42 with 2.60 cu 90 Error The status bar had problems showing long strings. This has been corrected.

P30) Internal Error 1262 in Module 19 Error There was a problem when the user opened a database with more companies than the user’s license allowed. The program would display an internal error 19-1262. This has been corrected.

P31) Dataports and Filename Error In some cases when using assist edit on filenames, an Internal Error 408 in Module 77 could occur. In Navision Solutions 3.00 (NS W1 3.00), a new informative message will be shown when the assist edit option cannot be used. This has been corrected. The text for Internal Error 408 in Module 77 has been added to reflect, "The data type must be text."

P32) Navision Financials Crashed when Using the Toolbar Buttons Error When you used the toolbar buttons and got an error, Navision Financials would crash when you clicked OK in the error dialog box. This has been corrected.

P33) Navision Financials Crashed when Trying to Contact a File it Could not Connect to Error When you tried to open an empty file, Navision Financials would crash. This has been corrected. When trying to flush a file that does not exist, no action is taken.

P34) Navision Financials did not Support Automation Servers with High Version Numbers Error If the version of an automation server was above 9.0, Navision Financials could not see the automation server in the Automation Server List This has been corrected. Navision Solutions now converts the version number from hex. string to dec. string before converting to long data type.

P35) The Function FORM.RUN Didn't Work as Intended, if Rec.Field was Empty. Error There was an assumption in the code that Rec.Field should be present when it was not empty. This is not the case when you have just added a new record, so the assumption was changed to, if a new record has just been created, then Rec.Field might be empty. This has been corrected.

P36) Internal Error 21 in Module 35 when Integrating with Outlook Error It is stated in the COM documentation that a COM object might provide a NULL pointer in the BSTR variable if it contains an empty string. This was not being checked before in the Automation code, but the problem has been solved. Outlook provides (correctly) a NULL BSTR when it cannot provide an ID (when it is not running). This has been corrected.

P37) Internal Error 2 in Module 48 Error Max size for entries in zup file was increased in Navision Financials 2.60. The increase was not big enough - in certain situations we could exceed the buffer size and get the internal error. This has been corrected. • Buffer size increased. • Entries too large for the zup files are ignored in release versions of C/SIDE, because end users cannot do anything about them.

P38) Error 1355 in Module 19 and Roles Error While navigating in the Role window, it was possible to provoke 'Error 1355 in Module 19'. Link to Support database: Support base reference: “Error 1355 in Modul 19 and Roles”

P43) Long Text Strings in URLs and Captions Error When using long text strings when creating URLs, in form captions or in reports you got an Internal Error 5 in module 9, followed by an application crash. This has been corrected Very long URLs are truncated and will not be allowed (an error occurs if you try to use them). Very long captions in forms and reports are truncated when saving the object. Internal reference ID: D8FE68AA60D5563E41256A01003FB567

P44) Client Crash if a Form Control had a Table Relation Containing a Filter Error If a form control had a source expression that was not a record variable and a table relation with a filter was defined for the control, the client program could crash when doing lookup. This has been corrected The program will issue an error message when the filter is executed. Internal reference ID: C444BEFBF926DC9441256974003D91E7

P45) New Records Would be Deleted if Escaping from Lookup Forms Error If you were entering e.g. a sales order line and made a lookup on the Reserved quantity field, the line would be cleared when you escaped the lookup form.

This has been corrected This bug was introduced in the NS3.00, beta 1 release and has now been removed. Internal reference ID: FA963DD449C9B17041256982002FD61C

P46) AutoFormat Problem with Tables Error C/SIDE had a problem with the AutoFormatType and AutoFormatExpr on tables. If both properties were not set, C/SIDE would disregard the property setting and use the default formatting properties instead. In text boxes on forms, it is possible to set only one of the autoformat properties. This has been corrected C/SIDE has been changed so AutoFormat works the same way on tables and on text boxes - now only one of the AutoFormat properties has to be set. Internal reference ID: 1E56FF636EEBDD2541256975004BD686 AEF8091A6414B8EDC1256641003E34CB

P47) Entering a Date Formula has to be in Capital Letters Error It was not possible to enter date formulas in lower case letters. This has been corrected It's now possible to use lower case when entering date formulas for the data type DateFormula. Internal reference ID: 01B4CB25D39CFEEAC12569DF0037C0DA

P48) FIN.EXE Parameter database=part1+part2+part3... didn’t Work Error When starting the Fin.exe program from the command line specifying a database that used multiple files, you got an error message stating that the “database=...” parameter contained a “character that may not be used”. This has been corrected Internal reference ID: C6435B37BC07BBDF412569420027DEE5

P49) Primary Key Violations after Rollback in OnInsert or OnModify Triggers Error If an insert or modify statement had failed, subsequent inserts could fail with error messages like: “The Sales Header already exists”. This has been corrected The behavior of the OnInsert and OnModify triggers on tables has been changed. Now, if an error occurs while the trigger is executing, changes to fields in the record done while executing the trigger are discarded. This was done to handle a number of problems relating to the numbering system. Internal reference ID: 0BCF9546BBBE7CAB412567F5003939C8

P50) Error 101 in Module 60 Error If a user chose lookup and while the lookup window was open, the record he was trying to lookup data for was deleted, an error occurred. First C/SIDE correctly displayed an error message but then an Internal Error appeared. This has been corrected Internal reference ID: 31AF068487F625474125687400514147

P51) Crash Related to the Use of Toolbar buttons Error If an error was generated during use of a toolbar button Navision Financials would crash when the Ok button on the error dialog box was pressed. This has been corrected Internal reference ID: EC0469E88B8F22A8412568000055E4FD 709BDF6DFD28CB98C12567300050EDA4 8A06DADF9AA2797841256943005DCF9A 5C872EECDDFCAA81412567A2003C025D 9044F3F653530C92412567E50046EF15 99FC5D3B2144A981412567ED00314E3D D6F6B9D384ECA8D1412567FB002D8525 B2A6C58D38EBA52041256970003A9033

P52) Page Setup Makes Navision Financials Crash Error If the File|Page Setup menu was selected without having a printer installed the Navision Financials client would crash. This has been corrected You will now get a message saying that you have to install a printer followed by a small guide describing how to install a printer. Internal reference ID: 298882077C51DB96412569310038830B

P53) Files Remains Locked after a Failed File Copy Operation Error When FILECOPY failed, it left the source file locked. This has been corrected Now it should not lock the source file even when FILECOPY fails, since the target file is opened first. Internal reference ID: 409D569AB80AC287412567BE00308483

P54) INT Datatype and Automation Error Variants were not changing datatypes to assume the data type expected by an automation server. As an example, if you had an Automation that was expecting a VT_BSTR and you passed a Variant that contained a numeric value (integer), the passing value was not correct (since the conversion didn't take place). This has been corrected Now Variants coerce (when possible) to the target data type. Internal reference ID: 08C17B4D5BACC62C4125698C003EB5EA

P55) NS 3.0 close with an error. Error When a codeunit was run in the context of a form, and the codeunit terminated with an error, it would leave behind an invalid reference to the codeunit causing the application to crash if the codeunit was executed again without the form having been closed in the meantime. This has been corrected Internal reference ID: 7191A616FCB99C3B41256997003DC05E

P56) Open Company Form Error when Working with Maximized Windows in SQL Option Error If the main form had been maximized on FinSQL, the Open Company form wouldn’t display the next time. This has been corrected Internal reference ID: 75255B5575EF2147412568F500302234

P57) Incorrect Conversion of Extended Characters in "Waiting to hibernate" Message Error Extended characters were not converted correctly in the “Waiting to hibernate” message being displayed if Navision Financials was busy when a Windows 2000 machines was put into standby mode. This has been corrected Internal reference ID: 7564A9448B2AFFD34125699300510EC7

P58) Error Saving FOB Files Error It was not possible to export a fob or txt file to a directory which had a subdirectory ending with .fob / .txt. This has been corrected Internal reference ID: B1CA36BDB8130139C1256635004AA71F

P59) Program Crash if the TableNo Property of a Codeunit was Empty In the object designer, when creating a codeunit and leaving the TableNo field empty, Navision Financials would crash. This has been corrected Internal reference ID: 99C7179A95FD4ED34125699F003BD3F2

P60) Exception Information not Shown Correctly when the bstrSource was not Present Error When an exception was issued from an automation server that contained the bstrDescription only and not the bstrSource, Navision Financials was reporting an error 10 in module 45. This has been corrected This has been changed and now the bstrDescription is shown together with the Automation server name as the Source. Internal reference ID: 9A46007AF74ADC214125697E003B67CA

P61) Cannot Export an Object to a Text File with the Same Name as an Existing FOB File Error When exporting xxx.txt to a directory where there was a file called xxx.fob, NS came up with an error message that the file xxx.fob already existed. This has been corrected Internal reference ID: 3A1019F5B0A8A4E1412568870037BFF3

P62) Navision Financials Didn’t Create a New Default Path if it Didn't Already Exist Error Changing the default path to a folder that did not exist and then reopening the main menu would cause Navision Financials to crash. This has been corrected Internal reference ID: 0D9B3AA04BAB389E4125689A0028554C

P63) Internal Error if Using Dialog Windows with More than 200 Characters Error Displaying more than 200 characters in a dialog window would cause an internal error 4 in module 42. This has been corrected It is now possible to have more that 200 characters in dialog text fields. Internal reference ID: 5E67CBE0AFFFCCAFC125693100173A97

P64) Wrong Caption on Menu Separator Error When inserting a menu separator on a menu button, C/SIDE would create an empty caption. This would show up when exporting texts for translation. This has been corrected The problem has now been fixed, but existing object with empty menu item captions remains unchanged. Internal reference ID: 9BE82EAFBB9E747D412569DC006FD5F8

P68) ConstValues of Text Constants Should be Accessible from the Symbol Menu Error It was only possible to see the names of the text constants in the Symbol menu; it should have been the ConstValues of the text constants that you should have seen. This has been corrected Internal reference ID: 4E10C28845BA79C141256A1F002024A6

P69) Internal Error 46 in Module 70 Error Translate/Import accepted only 256 characters. If you got strings longer than 256 characters, you would get the internal error 46 in module 70 and your Translate/Import would stop.

This has been corrected It is now possible to Translate/Import up to 999 characters. Internal reference ID: 174827D3AD958E1941256A03004D34C0

P70) AutoFormatExpr doesn't Work with Default Values Anymore Error AutoFormat problem with tables C/SIDE had a problem with the AutoFormatType and AutoFormatExpr on tables. If both properties were not set, C/SIDE would disregard the property setting and use the default formatting properties instead. This was different from how textboxes on forms worked, where it was possible to set only one property. This has been corrected C/SIDE has been changed so that AutoFormat works the same way on tables and on textboxes - now only one of the AutoFormat properties has to be set. Internal reference ID: 1E56FF636EEBDD2541256975004BD686

P71) C/SIDE Got Slower and Slower Each Time the Company was Opened Error When opening a company a number of times (e.g. by pressing Ctrl+o), the processing time for opening the company would double for each opening. This has been corrected Internal reference ID: 71632BCB190F5DB941256A1D0044A64F

P72) Length of Text Constants were not Checked. Error There was no check on the size when entering a Text Constant. This has been corrected A check is now added and the max size of a Text Constant is 1024 characters. Internal reference ID: 47A12A46A683D4C641256A26003B61A5

P73) Errors in the New Stream Functionality Error There was a problem when writing binary data through streams. If you requested to write a size different from the datatype, an error was displayed even if a return value was used. An example would be:

 Written:= OutStream.Write(Binary, Size); // An error was displayed when Size <> 'Binary size'
                                          // even though Written is present.

This has been corrected An error is displayed (correctly) only when the return value is not present. Internal reference ID: CBD4D43C42EF0FCB41256A3F002E75DF

P74) Error when Resizing Forms that Contained a Checkbox with a Label Error There was a problem in resizing a form if it contained a checkbox and a label with HorzGlue=Right. This has been corrected Internal reference ID: 3F273DD9FFAF5DED412569DE0042474F

P75) When Using a Char in a Variant Parameter it did not Get Passed on to the Server Error It was not possible to use char (VT_I1) as a parameter in an Automation or Event. This has been corrected VT_I1 is now supported when used in combination with a Variant datatype or "returned" to an AL Char datatype. Internal reference 596FDCD48E78AAA8C125661E004A35E6

P76) Error in CONVERTSTR( Str128+Str128, 'abcde', 'ABCDE') Error There was an error when using CONVERTSTR with strings longer than 255 characters with source and target in the same variable space (for instance, both variables in Globals). This has been corrected This has been solved and now the limit is in the size of the target string. Internal reference ID: FE8E1B020EF19B8C41256961005A4377

P77) Too Many Parameters in Events Error It was possible to use parameter number 40 in an event. This parameter was declared as "???????". This has been corrected Now e vents act according to the documentation where it is stated that only the first 39 parameters can be used. Internal reference ID: 94EF51B2576BF181412569A7002C3268

P78) Error in DATE2VARIANT Error DATE2VARIANT did not work correctly when using TODAY as the date parameter. This was an issue in NS3.00, Beta2. This has been corrected This problem has been fixed and now it should be possible to use TODAY as the date parameter in DATE2VARIANT. Internal reference ID: 8E54EC2C5ACC555341256A15005867AE

P79) TRANSACTIONTYPE and ACTION were Missing Error TRANSACTIONTYPE and ACTION were missing on the Symbol menu. This has been corrected Internal reference ID: F0F6400AF6A41EEB41256A22004A8511

P80) It was not Possible to Handle Strings Larger than 10K Error If you fired an event with a parameter ByRef Variant (VAR x : Text[1024]) containing a string bigger than approx. 10K, the program would crash. This has been corrected This does not happen anymore. Still, you can't use strings bigger than 1024 when the parameter is ByVal or 4100 when ByRef. Internal reference ID: 80CB493EB597821B41256A1F004439A3

P81) A Form "Hung" After an Error Message Error Escaping certain status forms that had a cancel button caused NS to be locked, i.e. not respond to any actions with anything except a 'ping'. This has been corrected Internal reference ID: 55911218705E7DBEC1256A07004A9EEA

P82) Navision Financials Crashed when Registering Custom Controls Error If you tried to register a control, Tools->Custom Controls->Control->Browse and you selected a control that wouldn’t register (ex. c:\winnt\system32\3DViewer.dll), Navision Financials would crash. This has been corrected Internal reference ID: EBB290B164E6E327412569DD003656E1

Issues

P39) New Data Type: DateFormula In response to the Multilanguage enabling, the DateFormula has been changed. The DateFormula is now a Data Type.

P40) New Product Name Issue The product name has been changed from Navision Financials to Navision Solutions.

P41) Online Help (C/SIDE Reference Guide) Changed from WinHelp to HTML Help Issue The format of the online Help has been changed. Navision Solutions 3.0 uses HTML Help, which has caused the Help menu entries to be rearranged.

P42) OCX and AUTOMATION Entries in the Symbol Menu Issue There are no generic OCX/Automation functions in C/SIDE. In response to this issue, a change has been made. A filter has been implemented in order to remove any data types that do not provide any static functions (OCX, Automation and Streams).

P65) Changes in Event with Datatype VT_Dispatch Issue Concerning Event Triggers: Receiving data from an Automation was not always handled right. This was very much depending on the data types received and the conversion between COM types and AL-types. Now this data conversion is handled more smoothly. First data is only converted when (and if) needed. If conversion is never needed, meaning that the data is not used inside the event trigger, the data will never be check for legal data type or legal range.

Second, during the old conversion data was squeezed into the allowed range for the destination AL-type, if possible. This was done without any warning. Now data will never be changed to enable conversions. If incoming data cannot be converted to the needed type without any loss of information an error will popup on the screen and the event trigger will terminate. The same is valid for data send back to the Automation via a call by ref. parameter.

Internal reference ID: 1A5C02FE9F65AB3D412569F20047ACB8

P66) Change in File Export Dialogs Issue The behavior of file export dialogs has been changed. Previously, file export dialogs like the Export Object dialog in the Object Designer would display a standard Windows FileSave dialog regardless of the file format (*.txt or *.fob) chosen in a previous dialog. Now, the file extension selected in the “Save as type” field of the Windows FileSave dialog controls the type of file (binary .fob or text .txt). Consequently, it is no longer possible to save a file as type 'All Files (*.*)'. This is in line with general Windows behavior, where the file extension designates the type of the file and the name (possibly including .'s (periods) and other special characters) is used for general identification. This change goes for all file save dialogs in the application. Internal reference ID: E474D038019444F74125688700364D3E

Tools

Navision Application Server

Features

T1) Navision Application Server Feature The middle-tier server, Navision Application Server, is essentially a Navision Solutions client with no GUI (graphical user interface). Navision Application Server uses a variety of the features found in the Navision Solutions client, where the GUI parts of the functionality are stripped out. Navision Application Server is limited to execute codeunits and tables. For more information, see the Installation & System Management: Navision Application Server.

T2) Navision Application Server Manager Feature This is a Microsoft Management Console Snap-in for managing and configuring Navision Application Servers on the network. For more information, see the Installation & System Management: Navision Application Server. Errors fixed

Issues

C/ODBC

Features

Errors fixed

Issues

C/DART

Features

Errors fixed

Issues

C/FRONT

Features

Errors fixed

Issues

T3) The C/FRONT Sample Spreadsheet was Supported by Navision Server Only Issue Previous versions of the C/FRONT sample spreadsheet (cfront.xls) only supported the use of Navision Server.

This has been changed, to make the supplied spreadsheet compatible with both Navision Server and MS SQL Server Option databases.

Communication Component and Bus Adapters

Features

T4) Communication Component and Bus Adapters Feature The Communication Component (NSComCom2) and the Bus Adapters (Message Queue and Named Pipe) allows communication between Navision products and other entities (other Navision products included). It is possible to send and receive information in the form of messages, synchronously and asynchronously. Both bus adapters can coexist in a single communication component and use, as their names imply, Message Queues or Named Pipes. For more information, see the Development Guide for Communication Components online Help project.

Errors fixed

Issues

Documentation

Features

D1) Communication Component Reference Guide Feature This reference guide describes the communication component for Navision Solutions, which handles the exchange of data streams between Navision Application Server and a bus adapter.

D2) Installation & System Management: Navision Application Server Feature This manual describes how to set up and manage Navision Application Server.

D3) No Service Management Manual Feature According to the overall Capri documentation concept, there is no manual for the Service Management functionality. The instructions are created as tasks in the online Help.

D4) Installation and System Management: Navision Server Feature The manual has been updated and all known errors have been corrected.

• “Financials” has been replaced by “Solutions”.
• All references to Win 95 have been removed.
• New preface has been added.
• New templates have been applied.

D5) Installation and System Management: Microsoft SQL Server Option Feature The manual has been updated and all known errors have been corrected.

• “Financials” has been replaced by “Solutions”.
• All references to Win 95 have been removed.
• Description of record level security has been added.
• Description of the change password functionality has been added.
• New preface has been added.
• New templates have been applied.

D6) C/ODBC Guide Feature This guide has been superficially updated.

• All references to Win 95 have been removed.
• New preface has been added.
• New templates have been applied.

D7) C/FRONT Reference Guide Feature This guide has been updated.

• “Financials” has been replaced by “Solutions”.
• All references to Win 95 have been removed.
• Description of DBL_UseCodeUnitsPermissions has been added.
• New preface has been added.
• New templates have been applied.

D8) C/FRONT Online Help Feature This has been converted to HTML Help.

• It has been updated.
• A number of samples have been added
• Description of UseCodeUnitsPermissions has been added.

D12) Company Notes Feature The Company Notes feature enables super-users to write notes for online Help topics. By attaching hints and instructions directly to a Help topic, super-users only need to communicate the information once. If a note is created for a form's help topic, any user who presses the form's Help button will see the note at the top of the Help topic. The note will appear on a light yellow background - resembling a stick-it note. The notes are stored separately so Help topics are not modified when notes are added. This means that the notes are maintained when upgrading to later versions of the online Help. Read more about this feature in the online Help topic "Company Notes" which can be found directly from the Navision Solutions Help welcome page. Errors fixed

Issues

D9) Application Designer’s Guide Issue The Application Designer’s Guide has been updated with descriptions of the new features mentioned in the “Development Environment and Database Changes” section of this document.

D10) Online help – C/SIDE Reference Guide Issue The C/SIDE Reference Guide has been converted to HTML Help and updated with descriptions of the new features mentioned in the “Development Environment and Database Changes” section of this document.

D11) Online Help for Navision Manufacturing Feature The online help from Navision Manufacturing has been converted to HTML help and integrated with the rest.