Changes Made in Microsoft Business … Page 1 of 246 2003-05-26 Changes Made in Microsoft Business Solutions–Navision W1 3.70 This document describes the changes between Microsoft

ChangesInNAV3.70.doc Page 1 of 246 2003-05-26

Changes Made in Microsoft Business Solutions–Navision W1 3.70 This document describes the changes between Microsoft Navision Attain W1 3.60 and Microsoft Business Solutions–Navision W1 3.70. Changes made between Microsoft Business Solutions–Navision W1 3.70 (RTL) and Microsoft Business Solutions–Navision W1 3.70 are in [ ].

Table of Contents

1 General Changes ............................................................................................................... 2 1.1 Product Name Change and Branding Update ............................................................ 2

2 Application Changes .......................................................................................................... 3 2.1 General Changes ........................................................................................................ 3 2.2 General Ledger ......................................................................................................... 10 2.3 Fixed Assets.............................................................................................................. 36 2.4 Sales & Receivables ................................................................................................. 37 2.5 Marketing and Sales ................................................................................................. 59 2.6 Service Management ................................................................................................ 84 2.7 Purchases & Payables ............................................................................................ 102 2.8 Inventory.................................................................................................................. 113 2.9 Warehouse Management........................................................................................ 141 2.10 Manufacturing...................................................................................................... 155 2.11 Cap. Reqts. Planning........................................................................................... 176 2.12 Resources ........................................................................................................... 178 2.13 Jobs ..................................................................................................................... 181 2.14 Human Resources............................................................................................... 186 2.15 Commerce Portal................................................................................................. 187 2.16 Commerce Gateway............................................................................................ 206

3 Development Environment and Database Changes...................................................... 218 3.1 Microsoft Business Solutions–Navision Database Server ...................................... 218 3.2 Microsoft SQL Server Option for Microsoft Business Solutions–Navision.............. 220 3.3 Development Environment...................................................................................... 229 3.4 User Portal .............................................................................................................. 237 3.5 Microsoft Business Solutions–Navision Application Server.................................... 238

4 Installation ...................................................................................................................... 239 4.1 Installation Program ................................................................................................ 239

5 Tools............................................................................................................................... 240 5.1 Debugger................................................................................................................. 240 5.2 Upgrade Toolkit ....................................................................................................... 242

6 Documentation ............................................................................................................... 243 6.1 Online Help.............................................................................................................. 243


1 General Changes

1.1 Product Name Change and Branding Update

Following the Microsoft acquisition of Navision a/s, the Navision Attain product has changed name to Microsoft Business Solutions–Navision. All other products in connection to Microsoft Business Solutions–Navision have also been changed according to the new naming guidelines:

Old Definition New Definition

Navision Attain Application Server Microsoft Business Solutions–Navision Application Server

Navision Attain Database Server Microsoft Business Solutions–Navision Database Server

Navision Attain Debugger Microsoft Business Solutions–Navision Debugger

Navision OnTarget Modeler Microsoft Business Solutions Partner Methodology Modeler Tool

Navision Attain Microsoft Business Solutions–Navision

Navision Web Shop Microsoft Business Solutions–Navision Webshop

Microsoft SQL Server Option for Navision Attain

Microsoft SQL Server Option for Microsoft Business Solutions–Navision

Navision Academy Not to be used anymore

Navision Attain Developers Toolkit Microsoft Business Solutions–Navision Developer’s Toolkit

Navision Attain Tools CD Microsoft Business Solutions–Navision Tools CD

Navision Attain Commerce Portal Microsoft Business Solutions–Navision Commerce Portal

Navision Attain Commerce Gateway Microsoft Business Solutions–Navision Commerce Gateway

Navision Attain User Portal Microsoft Business Solutions–Navision User Portal

In the Customer Relationship Management functionality names have been changed further:

Old Definition New Definition

CRM - Marketing & Sales Microsoft Business Solutions–Navision Relationship Management

CRM - Service & Support Microsoft Business Solutions–Navision Service Management

For more detailed information, please see the naming guidelines on the marketing web. Following the acquisition and the new branding of Microsoft Business Solutions the colors used in the application have been changed to all blue shades instead of light blue and red. These changes have been implemented.


2 Application Changes

2.1 General Changes

Features

A1) Anti-Piracy

Feature

The About Box window now contains a link to the Anti-Piracy Web page.

This feature has been implemented.

Service System reference: HQ-513-956-UFTP

A2) Demo Tool for Creating Manufacturing Data

Feature

When running the demo tool with a check mark in the manufacturing field, the tool would not create demo data without user intervention.

This has been corrected.

Codeunit 90000792 create Prod.Order from Sale //Demotool Codeunit 119076 Make Mfg. Order from Sales //Demotool Internal Workbase reference: BED998489F92916E4125697B003398D5

A3) Only Show Licensed Application Areas in Main Menu

Feature

The main menu’s left hand command buttons (used for choosing application areas) are modified so that only buttons for application areas that the customer has actually bought licenses for are shown. This feature can be selected (turned off) in the General Ledger Setup, so the customer actually can choose to see all application areas.



A4) Disable Un-Accessible Main Menu Function Buttons

Feature

The application area menu windows are changed so that function buttons that the user does not have permission for are disabled. This can be turned off in the General Ledger Setup (the setup field is shared with the feature described above).


A5) “Wizard” to Iterate Through All Setups in Setup Checklist

Feature

We have created a “wizard” that helps the user to run through all setup tables sequentially and to let the user set the status from the wizard.


Errors fixed

A6) The Fields Department Code and Project Code Have Been Renamed

Error

The fields Department Code and Project Code have been removed from table 99008504 Inbound Product Catalog Hdr. because they didn't map to a data instance when importing a Product Catalogue. These changes implied changes in several forms and codeunits, which referred to those fields. The encoding/decoding of XML documents (made in codeunits 99008517-XML Document-Create and 99008518 - XML Document-Transform) reflect these changes, so the labels used now are: Shortcut_Dimension_1_Code Shortcut_Dimension_2_Code Biztalk Document Specifications and Mappings also use these tag names now. The fields Department Code and Project Code have been replaced by Shortcut Dimension Code 1 and Shortcut Dimension Code 2 in the following tables: Table 99008500 Inbound Sales Document Header Table 99008501 Inbound Sales Document Line Table 99008502 Inbound Purch. Document Header Table 99008503 Inbound Purchase Document Line Table 99008506 Outbound Sales Document Header Table 99008507 Outbound Sales Document Line Table 99008508 Outbound Purch. Document Hdr. Table 99008509 Outbound Purch. Document Line.



Service System reference: HQ-511-729-CRKX

A7) Creating Meeting To-do for Meeting Organizer without Outlook Integration Setup Requires Attachment

Error

If you did create a to-do meeting on behalf of another sales person, who were not setup to synchronize, you would be asked to make an attachment to the meeting invitation when pressing Finish button, because the program acts as if the meeting was never meant to be synchronized, which is the correct behavior. This is corrected so that you get the error message when pressing Next button on second step of to-do wizard where meeting organizer is selected.


Form 5097 Create To-do

Service System reference: HQ-651-775-ZNMH

A8) Several Access Request Windows Appear When Changing Outlook Items for Another User

Error

If you create or change a to-do in Navision for another sales person, who in Outlook actually has not given you permission to modify his/hers Outlook items, you will, when synchronizing with Outlook get a warning on this not once but several times. This has been changed so you will get the warning only once.


Table 5050 Contact Table 5080 To-do Table 5199 Attendee Table 5119 Outlook Integration Log Codeunit 5072 Outlook Application Management Codeunit 5074 Buffered Synchronization Form 5000 Relationship Management Menu Service System reference: HQ-822-667-SGUZ

A9) Archived Documents Without Lines Cannot Be Accessed

Error

When creating a purchase order header without adding lines, archiving the purchase order and then delete it, you would experience that the archived order no longer is available if you try to open it from the Purchase List Archive. The problem has been solved by linking the field Document No. in table 5110 to the field No. in the table Purchase Header Archive.



Table 5110 Purchase Line Archive Service System reference: DE-295-353-XAKM

A10) Error Message If You Try to Print the Report Opportunity - Detail

Error

If you print the report Opportunity - Detail, you could get the following error message: You cannot base a date calculation on an undefined date. This has now been corrected.


Report 5068 Opportunity – Details

Service System reference: DE-751-344-UE8S

A11) Creating To-Dos for Other Salespeople Causes the Disruption of Data

Error

If you create a to-do, meeting with more attendees in Navision for another salesperson (with the other salesperson as organizer), you would experience that the meeting was corrupted in the synchronizing process with Outlook. Attendee would be missing in the corresponding Outlook meeting, attendee to-dos would be deleted in Navision etc. This is fixed by changing the procedures of the events activated from Outlook in the synchronization process.


Codeunit 5072 Outlook Application Management Codeunit 5073 To-do Handler Table 5080 To-do

Service System reference: HQ-684-947-ZNDE

A12) Printing from Carry Out Action Message Request Form in Planning Worksheet Did Not Work

Error

The select option of "Firm Planned & Print" or "Create purch. orders and print" in the carry out action message request form did not work. Two new printing functions have been added and called.


CodeUnit 333 Req. Wksh.-Make Order CodeUnit 99000813 Carry Out Action Service System reference: US-135-997-VQFP


A13) Permissions for Table 6550 Were Missing from Various Objects.

Error

Missing permission to table 6509 Whse. Item Entry Relation and not table 6507 Item Entry Relation. Permission Insert to codeunit 5760 -> TableData 6509=I has been added. User will have to set the permissions for table 6550 and 6509.


Table 5767 Warehouse Activity Line Form 6550 Whse. Item Tracking Lines Report 7305 Whse.-Source - Create Document Codeunit 5763 Whse.-Post Shipment Codeunit 6500 Item Tracking Management Codeunit 7307 Whse.-Activity-Register Codeunit 7312 Create Pick Codeunit 5760 Whse.-Post Receipt Service System reference: NL-108-730-LFLP

A14) Length of Routing Version Code

Error

It was possible to define a number series for the routing version code with more than 10 characters. This caused problems when used later on.


Table 99000786 Routing Version Service System reference: DE-865-159-79GW

A15) Multilanguage Enabling of Customized Calendars

Error

The source code of the customized calendar functionality was not multilanguage enabled.


Codeunit 7600 Calendar Management Service System reference: ES-642-920-AC2W

A16) Incorrect Use of SETFILTER on the Balance(LCY) Field on the Customer Card Form (21)

Error

On the customer and vendor card and on the statistics forms SETFILTER was used incorrectly, as special characters as & and | would be interpreted as filter commandos.


Form 21 Customer Card


Form 26 Vendor Card Form 151 Customer Statistics Form 152 Vendor Statistics Service System reference: US-705-773-LRQA

A17) SETFILTER Used Instead of SETRANGE

Error

In several objects, SETFILTER was used where SETRANGE would have been sufficient.


Form 30 Item Card Form 31 Item List Report 813 Inventory Picking List Report 5706 Create Stockkeeping Unit Report 5753 Get Source Documents Report 99000788 Prod. Order - Shortage List Codeunit 99000845 Reservation Management

Service System reference: HQ-453-83-ALNJ

A18) Table 8 Language

Error

In the German version, if you printed sales invoice, every English customer would get

invoices in German. This has been corrected so that all language codes have been inserted,

and US customers/vendors will get ENU as their language code.


Codeunit 101004 Create Currency

Codeunit 101008 Create Language

Service System reference: INT-239-730-3UWM

A19) Renaming of Sell-to/Buy-from No. to Bill-to/Pay-to No.

Error

The “Sell-to/Buy-from No.” field has been renamed to the “Bill-to/Pay-to No.” field because they get their value from the Bill-to Customer No./ Pay-to Vendor No. fields.


Table 81Gen. Journal Line Table 254 VAT Entry Table 382 CV Ledger Entry Buffer Form 39 General Journal Form 253 Sales Journal Form 254 Purchase Journal Form 283 Recurring General Journal Form 315 VAT Entries


Report 13 VAT Register Report 19 VAT- VIES Declaration Tax Auth Report 20 Calc. and Post VAT Settlement Report 24 Sales Taxes Collected Report 31 VAT Exceptions Report 88 VAT- VIES Declaration Disk Report 95 Date Compress VAT Entries Codeunit 12 Gen. Jnl.-Post Line Codeunit 13 Gen. Jnl.-Post Batch Code 80 Sales-Post Code 90 Purch.-Post Code 338 VAT Entry - Edit Internal Workbase reference: 0F5BB1FE29EE16FDC1256C440042B518

A20) [Validation Code on Post Code Fields could Trigger a RunModal Error in the Demotool

Error

The Demotool could not handle several City names to the same Post Code, because the validation code on the Post Code fields would trigger a RunModal error.


Codeunit 101014 Create Location Codeunit 101018 Create Customer Codeunit 101023 Create Vendor Codeunit 101079 Create Company Information Codeunit 101156 Create Resource Codeunit 101222 Create Ship-to Address Codeunit 101224 Create Order Address Codeunit 101225 Create Post Code Codeunit 101270 Create Bank Account Codeunit 101287 Create C/V Bank Account Codeunit 101550 Create Contact 5050 Codeunit 101551 Create Contact Alt. Addr. 5051 Codeunit 101600 Create Employee 5200 Codeunit 101607 Create Union 5209 Codeunit 101616 Create Alt. Address 5201 Codeunit 102212 Create Com. Portal Contacts Codeunit 102225 Create Templ. Contacts Codeunit 118020 Create Responsibility Center Service System reference: HQ-636-195-DET8]


2.2 General Ledger

Features

A21) Payment Tolerance

Feature

We have redesigned the Payment Tolerance and Payment Discount Tolerance functionality based on channel feedback received after the W1 3.60 release.

• The program now allocates payment tolerance amounts across all documents in a multiple document application.

• You can also specify whether tolerance will be automatically allowed or whether the user will decide on a case-by-case basis.

• A new feature has been added that allows you to close an outstanding invoice with a payment amount that is slightly larger than what is owed.


A22) Allowing Multiple City Names for the Same Post Code

Feature

The primary key on the Post Codes table has been changed from Code to both Code and City so that it is now possible to use the same post code for more than one city or vice versa. This feature allows the user to, for example, enter the post code in two different languages: "1000 Bruxelles 1" and "1000 Brussels 1". When the user selects a post code that has more than one city name, a window will appear so that the user can select the appropriate city. The feature does not affect the countries that don't need this feature; for them, Post Codes/Cities works in the old way. Service System reference: HQ-707-527-CRRR

Changed/new Objects

Table 14 Location Table 18 Customer Table 23 Vendor Table 36 Sales Header Table 38 Purchase Header Table 79 Company Information Table 110 Sales Shipment Header Table 112 Sales Invoice Header Table 114 Sales Cr.Memo Header Table 120 Purch. Rcpt.


This feature has been implemented

Errors fixed

A23) Length of field Name in table Responsibility Center Should Be 50 Instead of 30

Error

The length of field Name in table Responsibility Center was 30. This was inconsistent with field Name 2 in the same table, with the information in the on-line help about this field, and with the Name and Name2 fields in the Company Information table.


Table 5714 Responsibility Center Service System reference: DE-500-781-2EPM

A24) Wrong Value in Field "Rem. Amount to Assign" in Item Charge Assignment

Error

When using a local currency with rounding precision 1 and assigning an item charge on purchase and sales orders with another currency and another rounding precision, a remainder amount in field "Rem. Amount to Assign "could not be assigned in the item charge assignment form. This resulted in an inconsistency in the G/L entries.

This has been corrected

Table 5805 Item Charge Assignment (Purch) Table 5809 Item Charge Assignment (Sales) Service System reference: HU-750-10-4F9Z

A25) G/L Entry External Document No. Field Not Populating for Inventory Postings

Error

External Document No. were not filled in for G/L Entries when Inventory postings were made per Ledger Entry.


Codeunit 5802 Inventory Posting To G/L Service System reference: GB-411-964-AMTL


A26) Missing Purchase Amounts on Value Entries in 3.60

Error

There were missing purchase amounts on value entries in 3.60 that were available before 3.60 for statistical purposes. New fields have been added on the Value Entry table to record purchase amounts. Upgrade to 3.70 also ensures that these fields are updated accordingly.


Codeunit 22 Item Jnl.-Post Line Report 798 Date Compress Item Ledger Table 382 CV Ledger Entry Buffer Table 32 Item Ledger Entry Service System reference: ES-619-723-GEB9

A27) Adjust Cost field on the ILE entries and Applied Entries When Using Average Costing

Error

Independent from the costing method, the adjusted cost of a negative entry should always be calculated using the adjusted cost of the positive entry if a fixed application is posted. This wasn't true for items with Costing Method Average, when a Sales with a fixed application was posted. The adjusted cost of sales of items with costing method Average was always calculated using the average cost, no matter, whether the sales was fixed applied to a positive entry.


Table 339 Item Application Entry Table 5802 Value Entry Service System reference: AU-312-772-F9LY

A28) Problem with Listseparator and Export Budget Formula

Error

When exporting a budget to Excel with option Include Totaling Formulas activated, you would get an error if your system was not set up with listseparator ";".


Table 370 Excel Buffer Report 82 Export Budget to Excel Service System reference: HQ-742-504-CP98


A29) The Change Global Dimensions Report (83) Could Fail When Using Account Type Default Dimensions

Error

The Change Global Dimensions Report (83) Could Fail When Using Account Type Default Dimensions.


Report 83 Change Global Dimensions Service System reference: HQ-746-691-VKAH

A30) Update of Analysis View Failed When No. of Entries Were More Than 2.100.000

Error

When updating Analysis View, a calculation overflow error would come up if there were more than 2,100,000 entries.


Codeunit 410 Update Analysis View Service System reference: NL-377-458-RDA7

A31) Balance Due Was Calculated Incorrect in the Customer - Summary Aging Simp.

Error

Balance Due was calculated incorrect in the Customer - Summary Aging Simp. report (109). This error occurred because the Balance Due fields on several tables could not be shown historically due to the datefilter definition on the flowfields.


Table 4 Currency Table 18 Customer Table 23 Vendor Table 98 General Ledger Setup Table 379 Detailed Cust. Ledg. Entry Table 380 Detailed Vendor Ledg. Entry Table383 Detailed CV Ledg. Entry Buffer Report 105 Customer - Summary Aging Report 106 Customer Detailed Aging Report 109 Customer - Summary Aging Simp. Report 305 Vendor - Summary Aging Service System reference: SE-604-692-FJ2W


A32) Error Export Budget to Excel

Error

When exporting a budget with the option Include Totaling Formulas activated, and the Language selected in the application (e.g.Spanish) was not the same as in MS Office (e.g.English), the process did not work right.


Table 370 Excel Buffer Report 82 Export Budget to Excel Service System reference: ES-36-615-QJQW

A33) Total Type Dimensions Not Picked Up by Account Scheduler

Error

The totaling filters in the Dimension 1-4 Totaling fields have until now only been treated as filters on dimensions on which postings can be made. This has been extended, so if the dimensions within the filter all are of type Total or End-Total, the program will use their Totaling values instead. In short; this means that the user can now specify totaling dimensions in the dimension totaling fields.


Codeunit 8 AccSchedManagement Form 490 Acc. Schedule Overview Service System reference: GB-659-759-HEZD

A34) Incorrect Decimal Places in Table 263 Field 15 Quantity

Error

The number of decimals for two fields (15 : Qyantity & 22: Total weight) in Table 263 was 0:5 which did not match Intrastat demands.


Table 263 Intrastat Jnl. Line Service System reference: DE-389-890-HKVQ

A35) Problem with Listseperator and Export Budget Formula

Error

When exporting a budget to Excel with the option Include Totaling Formulas activated, you would get an error if your system was not set up with listseperator ";".


Table 370 Excel Buffer Report 82 Export Budget to Excel


Service System reference: HQ-742-504-CP98

A36) Incorrect Decimal Places in Table 263 Field 15 Quantity

Error

The number of decimals for two fields (15 : Quantity & 22: Total weight) in Table 263 was 0:5 which did not match Intrastat demands.


Table 263 Intrastat Jnl. Line Service System reference: DE-389-890-HKVQ

A37) Gap in the Detailed Ledger Entry No. after Running the Adjust Exchange Rates Batch Job

Error

After running the Adjust Exchange Rates batch job, the program skipped a number in the entry no. series for the detailed ledger entries.


Report 595 Adjust Exchange Rates Service System reference: DE-647-111-ECGP

A38) Pmt. Discount Date and Payment Terms Code in General Journals

Error

If you selected a vendor in the General Journal Line with a payment terms code or a payment discount date and you deleted the vendor, the payment discount date and payment terms code were not deleted.


Table 81 Gen. Journal Line Internal Workbase reference: 7894AD408D11A5B0412568A1003A545A

A39) Incorrect Value When Using Lookup for the Taxonomy Name Field on the XBRL Taxonomy Line Form

Error

In the Taxonomy Name field, when you clicked the lookup button, the wrong taxonomy name was highlighted on the XBRL Taxonomy Line form (583).


Form 583 XBRL Taxonomy Lines


Internal Workbase reference: 11156CF4F84F7B92C1256BCA00349C99

A40) The Change Log Setup (Table) List Form Did Not Show Table Caption

Error

The Change Log Setup (Table) List form (593) showed the table name instead of the table caption.


Form 593 Change Log Setup (Table) List Internal Workbase reference: 1016F60984F69571C1256C16005291D5

A41) Change Log Setup and Language

Error

The option string for the Log Insertion, Log Modification and Log Deletion fields was not multi-language enabled in the Change Log Setup (Table) List form 593.


Form 593 Change Log Setup (Table) List Service System reference: DE-748-419-SCFY

A42) Problem with Unrealized VAT

Error

When you posted a purchase invoice for the first time, with two items which had different VAT Prod. Posting Group for example: VAT 25 and VAT10 and then later you applied a partial payment which covered the full VAT amount to the invoice, the unrealized VAT was not adjusted correctly. Not all VAT entries were posted from the unrealized VAT account to the realized VAT account.


Codeunit 12 Gen. Jnl.-Post Line Internal Workbase reference: E0C313EF1E98D265C125670F00543BF7

A43) Incorrect VAT Calculation in Connection with Unrealized VAT

Error

When you applied a credit memo to an invoice, and later paid the invoice, the unrealized VAT account was not adjusted correctly because the program ignored the VAT of the credit memo.


Codeunit 12.Gen. Jnl.-Post Line


Service System reference: DE-281-147-AD6Y

A44) Close Income Statement Did Not Work for Consolidated Companies.

Error

If you consolidated two companies into a third consolidated company, and then ran the Close Income Statement batch job in the consolidated company with a checkmark in "Close By Business Unit" field, the program did not give separate closing entries for each business unit. This error also occurred when you selected the “Close By Dimensions” field.


Report 94 Close Income Statement Table 386 Entry No. Amount Buffer Service System reference: US-466-768-4NC7

A45) Australian Taxonomy Could Not Be Imported

Error

Due to various differences in the format of the XML files compared to the previously known taxonomies from other countries, the Australian taxonomy could not be imported. The error has been corrected, but there are still errors in the Australian documents, and you cannot import these without first correcting the XML-documents.


Codeunit 422 XBRL Import Taxonomy Spec. 2 Internal Workbase reference: 07C6E1BC82AD8FCBC1256C2B0031AE20

A46) Transfer to General Journal Function in Bank Account Reconciliation

Error

The Transfer to General Journal batch job did not use the General Journal Batch's number series in the general journal line that was created, if the batch job had a number series assigned to it.


Report 1497 Trans. Bank Rec. to Gen. Jnl. Internal Workbase reference: 4EC980FC2A295E3C412568F70045F56E

A47) Missing a Source Code After Using the Transfer to General Journal Function

Error

The source code was missing when you used the Transfer to General Journal batch job and posted the transferred entries from the general journal.



Table 242 Source Code Setup Form 279 Source Code Setup Report 1497 Trans. Bank Rec. to Gen. Jnl. Codeunit 2 Company-Initialize Internal Workbase reference: 8AF082FD727C1E74C1256ACA002C14F4

A48) Intrastat - Transaction Nature Codes

Error

The standard transaction nature codes in Cronus International Ltd. and in the Navision General Ledger manual were out of date.


Codeunit 101258 Service System reference: GB-238-73-GLA6

A49) Consistency in the Field Names in the Change Log Entry

Error

In the Change Log Entry table (405) the “Primary Key Field List” field has been renamed to “Primary Key” fields, and the “Primary Key Field 1/2/3 Caption” field has been renamed to “Primary Key Field 1/2/3 Name” field.


Table 405 Change Log Entry Form 595 Change Log Entries Report 509 Change Log Entries Codeunit 423 Change Log Management Service System reference: DE-875-782-FKU8

A50) Incorrect Test in the General Journal - Test Report (2)

Error

The General Journal - Test report (2) did not show a warning when some entries had the same document number as the external document number.


Report 2 General Journal - Test Internal Workbase reference: 63B895D37FA283CAC125671D003106EF


A51) Missing Log in Edit-Codeunits

Error

Codeunit 218, 338, and 391did not have the logging feature that was implemented on the Customer/Vendor Ledger Entry –Edit codeunits.


Codeunit 218 Job Entry -Edit Codeunit 338 VAT Entry -Edit Codeunit 391 Shipment Header - Edit Internal Workbase reference: 7711F68D88422ACCC1256C410042B9B9

A52) VAT-VIES Reports (19 and 88) Created Totals Based on the Sell to/Buy from No.

Error

In the VAT-VIES reports (19 and 88), the program summarized the VAT entries based on the contents of the Sell to/Buy from No. field. As a result there was more than one line with the same VAT registration number in the report if there was more than one customer with the same VAT registration number. According to the guidelines set up by the authorities there must only be one line per receiving 'VAT reg. number.' in the list sent to the authorities. A warning message in reports 19 and 88 has been changed from "Sell to/buy from No. was not filled in for all VAT entries..." to "VAT Registration No. was not filled in for all VAT entries..."


Table 254 VAT Entry Codeunit 12 Gen. Jnl.-Post Line Codeunit 367 CheckManagement Form 315 VAT Entries Report 19 VAT- VIES Declaration Tax Auth Report 88 VAT- VIES Declaration Disk Internal Workbase reference: 29B73B07FE7B502B412569EE00303912

A53) Change Log and Rename

Error

If a user changed the item number after changing the contents of the Item Description field without first closing the Item Card window, the description was not logged, only the contents of the No. and Last Date Modified fields were logged.


Codeunit 1 ApplicationManagement Codeunit 423 Change Log Management Service System reference: DK-333-771-3CCU


A54) Intrastat and VAT Country Code

Error

On the sales document header, the program did not update the VAT country code when you changed the ship-to country code and/or the sell-to country code.


Table 36 Sales Header Table 38 Purchase Header Service System reference: SE-502-407-9LY6

A55) VAT% was Incorrect Initialized in VAT Posting Setup

Error

In the VAT Posting Setup table (325), when validating a VAT Identifier (e.g. VAT25) by pressing F2 & <Return>, VAT% was changed to 0.


Table 325 VAT Posting Setup Service System reference: BE-491-123-PGFG

A56) Budget on an End-Total Account

Error

If you set up a totaling account without an interval (1110 | 1140) for an end-total account and there was no budget entry for these accounts, you would get the following error message: “The filter 1110|1140 should specify an interval when you click the AssistButton…”.


Form 120 G/L Budget Entries Service System reference: NL-679-788-DGB7

A57) Renaming of Recurring Journal Batch Name

Error

When you renamed a journal batch or template name, the dimensions in the journal lines were maintained but the dimensions in the Journal Line Dimension table were blank.


Table 356 Journal Line Dimension Service System reference: SG-590-272-Y6FE


A58) General Journal – Test Report (2)

Error

If you created two general journal lines which balanced individually and all had blank as the document type and same document number, but one had "G/L" in the Account Type field and “Purchase” in the Gen. Posting Type field and the other had "Customer" in the Account Type field, the General Journal-Test report would display the following warning: "Customer and Gen. Posting Type Purchase are not allowed.", but you could still post the lines.


Report 2 General Journal - Test Service System reference: DK-285-390-MEL3

A59) The Adjust Exchange Rates Batch Job Returned an Error and Then Stopped

Error

You could not run the Adjust Exchange Rates batch job if "Dimension Code Mandatory" was assigned to a G/L Account. This has been corrected so that the program copies the dimensions from the bank account's default dimensions, each customer/vendor ledger entry's dimensions respectively for the normal adjustments, and from the G/L account’s default dimensions that corrections are posted to for the adjustments of additional reporting currency.


Table 331 Adjust Exchange Rate Buffer Report 595 Adjust Exchange Rates Service System reference: LT-179-465-4G6G

A60) Only English Languages Were Supported in Analysis Views Export to Excel Function

Error

In the CreateFile function in codeunit 424, there was a CALCDATE Function with a calculation formula of '1W', which it made impossible to export analysis views in non-English languages.


Codeunit 424 Export Analysis View Service System reference: DK-84-428-TBNU

A61) Not Possible to Select Dimension when "Automatic" Posting

Error

When you inserted a correction entry for additional reporting currency rounding, the program did not check the dimension value posting.



Codeunit 12 Gen. Jnl.-Post Line Service System reference: DE-141-338-TGWQ

A62) Copying Global Dimension to Non-Global Dimensions

Error

When you copied dimension values from a global to a non-global dimension, the program doubled the dimension values when looking up into the dimension values for the global dimension on general journal line.


Table 349 Dimension Value Service System reference: US-274-741-CJQ4

A63) Minor Inconsistency in Report 2

Error

The text constants (Text059,Text060) in Report 2 have been changed from: Customer and Gen. Posting Type Purchase are not allowed. Vendor and Gen. Posting Type Sale are not allowed. to:

The combination of Customer and Gen. Posting Type Purchase is not allowed.

The combination of Vendor and Gen. Posting Type Sale is not allowed.


Report 2 General Journal - Test Internal Workbase reference: 431E8D445FE3F648C12567370015DEAD

A64) Incorrect No. Series When Reversing in a Recurring Journal

Error

When you posted a recurring journal with a posting date just before a date with a new Posting No. Series and you used the Recurring Method RF/ RV/ RB, the posted entry did not contain the right document number from the new Posting No. Series.


Codeunit 13 Gen. Jnl.-Post Batch Codeunit 396 NoSeriesManagement Internal Workbase reference: 8BC9570C9536B8584125685D003A2C79


A65) XBRL Labels with Multiple Languages

Error

Because XBRL/Denmark allowed an arc to point to several destination labels that had different language codes, Codeunit 422 has been changed to support XBRL Labels with multiple languages.


Codeunit 422 XBRL Import Taxonomy Spec. 2 Internal Workbase reference: 27FAD4EF50338EDFC1256C610028E0B

A66) Code Mandatory and Automatic Posting

Error

It was not possible to run the Calc. and Post VAT Settlement report if you had set up Account Type default dimension for an G/L account with the dimension value=Code Mandatory. This error has been corrected by using default dimensions from G/L Account in VAT Settlement.


Report 20 Calc. and Post VAT Settlement Internal Workbase reference: 280BAA3B3DA2DC6841256AB2002DEE99

A67) G/L Balance Trendscape - Date Range Filter Did Not Function

Error

If you set the time interval to "day" on the G/L Balance form, after you entered a date filter which contained more than one day, the filter changed to the last date in the date range and you would only see the balance for one day. The same problem also occurred on the G/L Balance/Budget form.


Form 414 G/L Balance Form 422 G/L Balance/ Budget Service System reference: US-148-402-RRWE

A68) Error When Posting Manual Checks

Error

If you created a payment journal with two lines: the first had "Computer check" and the second line had "Manual Check" in the Bank Payment Type field, and you then posted the journal, you would get the following message: "Cheque Ledger Entry 'entry 1' already exists".


Codeunit 12 Gen. Jnl.-Post Line Internal Workbase reference: 2A6D6A460452A235C12567350042BFD1


A69) Using Dimensions in Combination with VAT Settlements

Error

It was not possible to post VAT settlements including dimensions. This has been changed so that the posted entries will get the default dimensions from the G/L accounts that they are posted to. This was also a problem for the Adjust Exchange Rates report (595), which:

• used the default from the bank accounts for adjusting bank accounts,

• used the posted dimensions on customer/vendor ledger entries for adjusting the ledger entries and

• used the default from the G/L accounts for adjustments of additional reporting currency.


Report 20 Calc. and Post VAT Settlement Report 595 Adjust Exchange Rates Service System reference: NL-638-700-CCNE

A70) Update Problem of the Account Name Field in General Posting Setup

Error

On the General Posting Setup form (314) the account name in the Account Name field was not updated correctly when you moved the cursor from one column to another. This was because of the UpdateGLAccName("..") function. Sales Pmt. Disc. Credit Acc. Sales Pmt. Tol. Debit Acc. Sales Pmt. Tol. Credit Acc. Purchase Pmt. Disc. Credit Acc. Purchase Pmt. Tol. Debit Acc. Purchase Pmt. Tol. Credit Acc.


Form 314 General Posting Setup Service System reference: NL-472-153-TF6E

A71) Account Schedule Report

Error

On Report 25, you could not get a lookup list by pressing F6 on the Department or Project Filter line. The reason was that you could not make a table relation, because dimension 1 was determined by whether the account schedule was based on analysis views or on G/L entries. This has been corrected by a redesign, so now Report 25 does not have the Account Schedule Name tab and the Account Schedule Line tab, but only the request form. The request form has been extended with all the filter fields. Form 490 has a new tab "Dimension Filters" with the Dimension Filter field, and a Print menu item has been added under the Functions button.



Report 25 Account Schedule Form 104 Account Schedule Form 490 Acc. Schedule Overview Service System reference: US-788-168-BLPE

A72) Database Test Gave Error Due to the Selected Dimensions Table

Error

When you ran the Database Test report with the option "Test field relationship between tables" you got an error when there were values in the Selected Dimensions table (369). This has been corrected by removing the table relation because it is not used and this is simpler than changing the table definition, online Help and upgrade tool.


Table 369 Selected Dimensions Service System reference: FI-56-635-CK4F

A73) The Totaling Field had Different Lengths in Tables: 15, 85, 349, 367 and 376

Error

The Totaling field in Tables 15, 85, 349, 367 and 376 had different lengths and this could cause text overflow errors.


Table 85 Acc. Schedule Line Table 349 Dimension Value Table 367 Dimension Code Buffer Service System reference: DE-695-199-GH8R

A74) Intrastat and Costing Method Standard

Error

If you purchased some items from an EU vendor, then sold all these items (and thereby empty the inventory) to an EU customer, and used the Get Entries function in the Intrastat Journal window, you would get a total amount 0 on the purchase. This was because the Intrastat Journal table used the contents of the Average Cost field on the item card when calculating the amount on the lines, and the Average Cost field contained 0 after the item was sold out.


Report 594 Get Item Ledger Entries Service System reference: NL-509-797-QCFX


A75) Change Variable Length in Report 31

Error

In Report 31, the variable length of "MinVATDiffText" needed to be changed from 50 to 250 because of localization problems.


Report 31 VAT Exceptions Service System reference: DK-190-381-RCG3

A76) Problems Running the Calculate Inventory Report

Error

If you had two companies in the database, one with Dimensions and another without, and you first ran the Calculate Inventory report (790) with dimensions selected in the company with dimensions and you then tried to run the same report for the company without dimensions, you would not be able to do so and you could not change the chosen dimensions of the other company either.


Table 368 Dimension Selection Buffer Report 82 Export Budget to Excel Report 94 Close Income Statement Report 97 Date Compr. G/L Budget Entries Report 98 Date Compress General Ledger Report 198 Date Compress Customer Ledger Report 398 Date Compress Vendor Ledger Report 790 Calculate Inventory Report 798 Date Compress Item Ledger Report 1198 Date Compress Resource Ledger Report 1298 Date Compress Job Ledger Report 5696 Date Compress FA Ledger Report 5697 Date Compress Insurance Ledger Report 5698 Date Compress Maint. Ledger Service System reference: DK-389-305-UG5G

A77) Calculation on Analysis Views Were Incorrect When Name Contained Filter Signs

Error

If the code of an analysis view contained filter signs errors would occur in the calculation of the analysis views. This was because of the following lines in codeunit 8, the CalcGLAcc function:

WITH AnalysisViewEntry DO BEGIN SETFILTER("Analysis View Code",AccSchedName."Analysis View Name");

IF GLAcc.Totaling = '' THEN

SETRANGE("G/L Account No.",GLAcc."No.")

SETFILTER has now been replaced with SETRANGE.



Codeunit 8 AccSchedManagement Service System reference: DK-647-235-TFQ5

A78) No. Series with Starting No. and with Leading Zeros

Error

The starting number of the number series could not have zero as a leading number because the program automatically deleted the leading zeros.


Codeunit 396 NoSeriesManagement Service System reference: DK-165-335-KCVA

A79) The Report List Translations Form Did Not Show Report Name in the Caption Bar

Error

The Report List Translations form (572) did not show the report number/name in the caption bar.


Form 572 Report List Translations Internal Workbase reference: 7BF8E65B34798707C1256C3F0024C2A7

A80) Test Report and Deleted No. Series

Error

If you deleted a number series for journals for example GJNL-SALES, and then created a journal line, and previewed the Test report without specifying any filters, you would get the following error message: “No. Series Code 'GJNL-Sales' does not exist”.


Report 2 General Journal - Test Service System reference: DE-84-973-TGQP

A81) VAT Difference Was Not the Same for Man. VAT on Documents with Prices Incl. VAT and Journals

Error

In Attain 3.60 we had changed the documents so the VAT base was updated when you changed the VAT amount in the Prices Incl. VAT field on the Statistic form. However the VAT Difference field on the Statistics form and the posted entries were not updated in the same way as when you posted from a journal.



Table 81 Gen. Journal Line Internal Workbase reference: 3D635B66D20E3A3DC1256BEC0041FEB9

A82) G/L Account Budget Filter Did Not Work As Expected

Error

The system did not transfer the filter set up on the Chart of Accounts form to the G/L Account Balance/Budget form.


Form 16 Chart of Accounts Form 113 Budget Service System reference: DK-641-957-3EU2

A83) Character Length Error in the Totaling Field

Error

In the Chart of Accounts table, the length of the Totaling field was 250 characters, but the field could only lookup G/L accounts when it's length was less than 20 characters. When you did the lookup and selected more than one account, only one account was included in the Totaling field.


Form 16 Chart of Accounts Service System reference: MY-162-61-6CPQ

A84) Bank Account Reconciliation

Error

In Form 381 Apply Bank Acc. Ledger Entries, the Open field and the two Global Dimension fields were editable. The user should not be able to edit these fields.


Form 381 Apply Bank Acc. Ledger Entries Service System reference: GB-128-636-GJT8

A85) Field Namespace in Table 400 Was Not Used

Error

In Table 400, the Namespace field had never been used and had never been shown on any form. So it has been removed from the table.



Table 400 XBRL Linkbase Internal Workbase reference: 68F87B7F76928AE9C1256BB5002E04B2

A86) Incorrect Caption in the XBRL Comment Lines Form

Error

If you clicked the Information/Notes menu item on form 585, the caption of the window only showed "XBRL Comment Lines" which did not reflect the menu choice.


Form 585 XBRL Comment Lines Internal Workbase reference: 72815CDF088ACD9EC1256BD1003C2F7A

A87) Change Log Setup List Report

Error

In the Change Log Setup List (508) and Change Log Entries (509) reports, the AssistButton on the Table No. field did not work.


Table 405 Change log Entries Table 403 Change Log Setup (Table) Service System reference: ES-42-179-YKZR

A88) Budget Filter on Analysis By Dimensions

Error

If you entered a value in the Budget Filter field in the Analysis by Dimensions window or in the G/L Balance by Dimension window, you would get the following error message: "Budget name does not exist".


Form 408 G/L Balance by Dimension Form 554 Analysis by Dimensions Internal Workbase reference: 7DD8108120AAF559C1256C4D003ACC90

A89) Dimension Management Codeunit

Error

The TempDimBuf2 variable was not RESET on exit from the SaveTempDim() function with the result that the GetJnlLineDefaultDim() function only found the last saved record in TempDimBuf2 variable.



Codeunit 408 DimensionManagement Service System reference: AU-357-346-J679

A90) InitValue = 1 for Amount Rounding Precision and Unit Amount Rounding Precision

Error

In Table 98, the Amount Rounding Precision field had InitValue=1, and the Unit Amount Rounding Precision field had InitValue =1. They have been changed to: Field 73 Amount Rounding Precision, InitValue = 0,01 Field 74 Unit Amount Rounding Precision, InitValue = 0,00001


Table 98 General Ledger Setup Service System reference: SE-504-941-LJKM

A91) Analysis View Entry Table

Error

If a company had an analysis view that was updated when you posted and a user tried to post a warehouse shipment while another user updated the analysis view at the same time, the first user would get the following error message: "Another user has modified...", and another error message "You cannot ship more than zero units" when they reposted the Shipment. This has been corrected so that the COMMITs which keep the G/L Entry table locked during posting have been removed.


Codeunit 410 Update Analysis View Service System reference: GB-584-330-SGC6

A92) Missing CaptionClass in General Ledger Setup

Error

In the General Ledger Setup table (98), the CaptionClass property of the Global Dimension 1 Filter and the Global Dimension 2 Filter fields were missing.


Table 98 General Ledger Setup Service System reference: DE-477-640-695K


A93) Intrastat in Combination with Drop Shipment

Error

When you ran report 594 to get item ledger entries in the Intrastat Journal, the goods shipped as drop shipment were not included.


Report 594 Get Item Ledger Entries Service System reference: DE-517-443-FK42

A94) Additional Reporting Currency Adjustments Was Not Automatically Reflected in Analysis View

Error

When you adjusted exchange rates including the additional reporting currency, the adjustments were not automatically reflected in analysis views that had a check mark in the Update on Posting field. You had to manually update the view, or the view would get updated the next time you made a posting.


Codeunit 367 CheckManagement Service System reference: GB-403-875-MLPA

A95) Overflow in Analysis by Dimension - Export to Excel

Error

When you exported the analysis view to Excel with G/L Account Filter/ Date Filter/ Budget Filter/ Dimension Filter fields that contained more than 30 characters, you would get an overflow error message.


Codeunit 424 Export Analysis View Service System reference: ES-511-515-KLMH

A96) Key Groups

Error

The key groups used in table 32, 379, 380, 383 and 5407 did not match the key groups defined in the Database Key Groups table.


Tables 32 Item Ledger Entry Table 379 Detailed Cust. Ledg. Entry Table 380 Detailed Vendor Ledg. Entry Table 383 Detailed CV Ledg. Entry Buffer Table 5407 Prod. Order Component


Service System reference: DE-55-532-TB94

A97) Delete Empty G/L Registers

Error

When you ran the Delete Empty G/L Registers report (99) to delete empty G/L registers, the program did not check the FA Ledger Entry table and the Maintenance Ledger Entry table before deleting of a G/L register entry. Therefore a G/L register entry would be deleted even though it had an FA ledger entry or Maintenance ledger entry attached.


Report 99 Delete Empty G/L Registers Internal Workbase reference: E69E95FA68A3E98FC1256C010036D228

A98) Document Dimension without Document

Error

If you created an order with a standard text code, and then changed a document dimension, the dimension on the lines with blank numbers was updated incorrectly.


Table 357 Document Dimensions Codeunit 378 Transfer Extended Text Service System reference: DE-949-516-8KVW

A99) Error When Posting General Journal

Error

An error message showed up when you posted to the general journal. This error was caused by removal of the COMMITs from the Update Analysis Views codeunit (410) in connection with another error. Therefore a COMMIT has been added to the Gen. Jnl.-Post Batch codeunit (13).


Codeunit 13 Gen. Jnl.-Post Batch Internal Workbase reference: 6027DE91BCA6B658C1256C7700378E5F

A100) Export to Excel File

Error

When you exported an account schedule to Excel, the following error message would appear: “Type conversion error text to text”. This was because the Cell Value local variable should be 250 instead of 50 in the Entercell function in the Export Acc. Sched to Excel report (29).



Report 29 Export Acc. Sched to Excel Internal Workbase reference: FBCBB7FC94437130C1256B490034C2AE

A101) Modification Not Shown on the Sales Reports-Print Form

Error

When you modified the Text field in the Sales Reports-Modify form, the modification was not shown on the Sales Reports-Print form.


Table 243 Report List Service System reference: DE-594-73-MKAY

A102) Dimensions Deleted in Posting Codeunits

Error

When you used the RUN() function instead of the RunWithCheck()/RunWithoutCheck() function the program deleted the TempJnlLineDim records resulting in inconsistent dimension posting.


Codeunit 22 Item Jnl.-Post Line Codeunit 32 BOM Jnl.-Post Line Codeunit 202 Job Jnl.-Post Line Codeunit 212 Res. Jnl.-Post Line Codeunit 5652 Insurance Jnl.-Post Line Service System reference: AU-26-97-PV2C

A103) Void Check in Payment Journal Where Account Type Was G/L Account

Error

If you opened the Intrastat Journal Templates window without entering a name in the Batch Template field, you would get a very long and unusual error message.


Form 327Intrastat Jnl. Batches Service System reference: GB-638-887-4LBC


Issues

A104) Adding IBAN, SWIFT Code and Industrial Classification Fields to Forms

Issue

An Industrial Classification field has been added to the Company Information table (79). Futher more an IBAN and SWIF Code field has been added to the Company Information table (79), Bank Account table (270), Customer Bank Account table (287) and the Vendor Bank Account table (288).

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

Table 79 Company Information Table 270 Bank Account Table 287 Customer Bank Account Table 288 Vendor Bank Account Form 1 Company Information Form 370 Bank Account Card Form 371 Bank Account List Form 423 Customer Bank Account Card Form 424 Customer Bank Account List Form 425 Vendor Bank Account Card Form 426 Vendor Bank Account List Service System reference: HQ-558-357-EJHK

A105) Prevent the Deletion of G/L Posting Accounts

Issue

The G/L Account Deletion functionality has been extended. You can now set up a date that restricts the deletion of G/L accounts before this date. If the account has any entries posted after the specified date, you will not be able to delete the G/L account. When using this feature, you can specify that the program must check whether or not the G/L account is used in posting groups or other setup tables before allowing the G/L account to be deleted. If you do so, and if a G/L account is used in posting groups or other setup tables, a window will appear showing where the G/L account is used. This extended functionality can be used for specifying that financial data should be kept for, say, 5 years. This feature can also be used to get an overview of the posting groups or other setup tables in which a G/L account is used.


Table 98 General Ledger Setup Table 180 G/L Account Where-Used Form 16 Chart of Accounts Form 17 G/L Account Card Form 18 G/L Account List Form 99 G/L Account Where-Used List Form 118 General Ledger Setup Codeunit 100 Calc. G/L Acc. Where-Used Codeunit 361 MoveEntries Service System reference: HQ-643-233-PHJ6


A106) Allowing Multiple City Names for the Same Post Code

Issue

The primary key on the Post Codes table has been changed from Code to both Code and City so that it is now possible to use the same post code for more than one city or vice versa. This feature allows the user to, for example, enter the post code in two different languages: "1000 Bruxelles 1" and "1000 Brussels 1". When the user selects a post code that has more than one city name, a window will appear so that the user can select the appropriate city. The feature does not affect the countries that don’t need this feature; for them, Post Codes/Cities works in the old way.


Table 14 Location Table 18 Customer Table 23 Vendor Table 36 Sales Header Table 38 Purchase Header Table 79 Company Information Table 110 Sales Shipment Header Table 112 Sales Invoice Header Table 114 Sales Cr.Memo Header Table 120 Purch. Rcpt. Header Table 122 Purch. Inv. Header Table 124 Purch. Cr. Memo Hdr. Table 156 Resource Table 222 Ship-to Address Table 224 Order Address Table 225 Post Code Table 270 Bank Account Table 287 Customer Bank Account Table 288 Vendor Bank Account Table 295 Reminder Header Table 297 Issued Reminder Header Table 302 Finance Charge Memo Header Table 304 Issued Fin. Charge Memo Header Table 5050 Contact Table 5051 Contact Alt. Address Table 5107 Sales Header Archive Table 5109 Purchase Header Archive Table 5200 Employee Table 5201 Alternative Address Table 5209 Union Table 5714 Responsibility Center Table 5740 Transfer Header Table 5744 Transfer Shipment Header Table 5746 Transfer Receipt Header Table 5900 Service Header Table 5930 Posted Service Header Table 5970 Filed Service Contract Header Table 6650 Return Shipment Header Table 6660 Return Receipt Header Table 99000754 Work Center Table 99000758 Machine Center Service System reference: HQ-707-527-CRRR


A107) Using Dimensions in Combination with e.g. VAT Settlements

Issue

It was not possible to post VAT Settlements including Dimensions.


Report 20 Calc. and Post VAT Settlement Report 595 Adjust Exchange Rates Service System reference: NL-638-700-CCNE

2.3 Fixed Assets

Errors fixed

A108) VAT Was Incorrectly Calculated When Copied to Fixed Asset G/L Journal

Error

If a fixed asset entry with a FA posting type, Acquisition Cost, Disposal or Maintenance was copied to Fixed Asset G/L journal (with a check mark in the batch field ‘Copy VAT Setup to Jnl.Lines’) then VAT was calculated incorrectly. Fixed asset entries were copied to the Fixed Asset G/L Journal in these fixed asset functions: Reclassify entries, Index entries, Copy entries and Cancel entries.


Table 81 Gen. Journal Line Service System reference: NO-750-995-KGEJ

A109) Use of FA Posting Type in Purchase Invoice Did Not Refresh VAT Product Posting Group

Error

The system did not calculate the VAT % correctly for fixed assets on purchase invoice lines. If the user changed the FA Posting Type from Acquisition Cost to Maintenance, and the Acquisition Cost and Maintenance had different VAT % the lines would not be updated. If the user entered a depreciation book code different from the default depreciation book code then the system created an error.


Table 37 Sales Line Table 39 Purchase Line Service System reference: AU-988-760-W8SJ Service System reference: ES-494-680-HE7L


A110) Multilanguage Error in the FA Posting Group - Net Change Report

Error

The filter of the FA Posting Group - Net Change report (5611) was not translated when you changed the application language code.


Report 5611 FA Posting Group - Net Change Internal Workbase reference: F18736D7A89AA245C1256C3D0052A4D0

A111) Error in the Fixed Asset - Projected Value Report

Error

If the Fixed Asset - Projected Value report (5607) was printed with Group Totals = FA Posting Group and 'Print Amounts per Date' then the amounts were printed per date, and not per FA Posting Group.


Report 5607 Fixed Asset - Projected Value Internal Workbase reference: A687E297AB9A7120C1256C480030F890

2.4 Sales & Receivables

Errors fixed

A112) Item Tracking on Credit Notes

Error

If item tracking had been defined on a sales or purchase credit note any change on the line would give an error message. This was due to the receipt date/shipment date being 0D on the line, which the reservation system would react on as an error. The illegal step is in fact to change the date TO 0D - it is not possible anyway to create reservations with an undefined date. The check is changed to react only on the change from a defined date to 0D. A single statement is changed.


Codeunit 99000832 Sales Line-Reserve Codeunit 99000834 Purch. Line-Reserve Service System reference: DE-643-712-YEA2


A113) The Customer Detailed Aging Report Came up with an Error Message when the Due date field Was Blank

Error

If you had a posted document that had where the Due Date field was blank the Customer Detailed Aging report returned an error message: "The date is not valid.”

This ahs been corrected.

Report 106 Customer Detailed Aging Service System reference: DE-193-262-BHVM

A114) Field Document No. in posted document line tables did not have a table relation

Error

A table relation to the corresponding header table was missing in posted document line tables.


Table 111 Sales Shipment Line Table 113 Sales Invoice Line Table 115 Sales Cr.Memo Line Table 121 Purch. Rcpt. Line Table 123 Purch. Inv. Line Table 125 Purch. Cr. Memo Line Table 6651 Return Shipment Line Table 6661 Return Receipt Line Service System reference: NL-207-288-ZGBK

A115) Multiple Currencies

Error

Customer's Ship-to Address used instead of company address on special orders Purchase orders created from the requisition worksheet used the customer's ship-to address even in case of a special order.


Codeunit 333 Req. Wksh.-Make Order Service System reference: US-424-578-KPTQ

A116) Profit Statistics Did Not Include Non-Inventoriable Costs

Error

In the most critical places, the profit value shown now includes non-inventoriable costs. Note that e.g. the Profit (LCY) field on the Customer Card still shows the profit value based on Customer Ledger Entries, i.e. not including non-inventoriable costs.



Table 5802 Value Entry Form 151 Customer Statistics Report 113 Customer/Item Sales Report 713 Inventory - Customer Sales Service System reference: ES-860-557-XFLY

A117) Problems with Capable to Promise Calculations

Error

Date calculations were not consistent and furthermore calendars were not taken into consideration.


Table 246 Requisition Line Table 5742 Transfer Route CodeUnit 5404 Lead-Time Management CodeUnit 99000813 Carry Out Action CodeUnit 99000886 Capable to Promise Service System reference: DE-687-37-EJAU

A118) Dimensions Changed When Item Availability is "non-existent" for a Substituted Item on Sales Line

Error

If an item on a sales line was tried substituted by a registered substitute and the available amount of the substitute item was not high enough and the user chose not to accept the substitute, the dimensions of the substitute was copied to the sales line anyway.


Codeunit 5701 Item Subst. Service System reference: DK-708-395-RES3

A119) Wrong ERROR-Message When Selecting Another Location

Error

When a user tried to change the location code, shipment date or variant code via the item availability forms (Sales & Receivables|Orders|Line|Item Availability By) on a sales line for which reservation entries existed, an error message was displayed saying that "No. should not be changed [...]", which should have been "Location code/Variant Code should not be changed [...]".


Table 37 (Sales Line) Service System reference: DE-143-752-4D4U


A120) Customized Calendars on Shipping Agent Service

Error

Customized calendar for different Shipping Agent Services were mixed together.


CodeUnit 7600 Calendar Management Service System reference: SE-247-912-BJ4M

A121) Wrong Error Message When Assigning a User to a Responsibility Center

Error

If a user either deleted or changed responsibility center on a purchase header, and the user was assigned a different Purchase responsibility center in the user setup, an error message will occur correctly. But the error message referred to the "Sales Resp. Ctr. Filter", not the "Purchase Resp. Ctr. Filter".


Table 38 Purchase Header Service System reference: DE-735-671-GL2Z

A122) When You Entered Data in "Planned Delivery Date" and "Planned Shipment Date" on a Sales Line, the values were recalculated.

Error

"Planned Delivery Date" and "Planned Shipment Date" were recalculated, when data was entered.


Table 37 Sales Line Service System reference: DK-559-797-5E6Y

A123) Field Document No. in Posted Document Line Tables Did Not Have a Table Relation

Error

A table relation to the corresponding header table was missing in posted document line tables.


Table 111 Sales Shipment Line Table 113 Sales Invoice Line Table 115 Sales Cr.Memo Line Table 121 Purch. Rcpt. Line Table 123 Purch. Inv. Line Table 125 Purch. Cr. Memo Line


Table 6651 Return Shipment Line Table 6661 Return Receipt Line Service System reference: NL-207-288-ZGBK

A124) Lookup of Item Tracking Entries from Customer List Form

Error

It was not possible to lookup item tracking entries from the customer list form. The relevant code is now copied from the similar menu item on Customer Card.


Form 22 Customer List Service System reference: DE-499-265-9H52

A125) Automatic Reservations and Sales Quotes

Error

When converting a sales quote to a sales order auto-reservation was not triggered in spite of the item being set to reservation Always.


Codeunit 86 Sales-Quote to Order Service System reference: GB-264-252-W9VQ

A126) Reservations / Order Tracking

Error

Planned Delivery Date on Sales Lines The Planned Delivery Date was not updated properly on the sales lines.


Table 37 Sales Line Service System reference: GB-244-355-6JG2

A127) Reserved Quantity on Reservation Form

Error

Current Reserved Quantity on Form 498 ""Reservation"" would be incorrect if reservation was made from a supply without serial/lot no against a supply with serial/lot no. Filter on SN/Lot is now only set when the demand has a specific Lot/SN.



Form 498 Reservation Service System reference: DE-428-179-4E8U

A128) Item Tracking in Drop Shipments

Error

Item tracking functionality has been added to the Drop Shipment feature.


HQ-184-513-MDXK

A129) Cursor Jumps in Order Forms

Error

The cursor jumps in the Sales Quote, Sales Order and Purchase Quote forms were not defined as could be expected.


Form 41 Sales Quote Form 42 Sales Order Form 49 Purchase Quote Service System reference: HQ-119-409-CPLF

A130) Fields Did Not Reset When Creating Return Order

Error

When you created Return Order with functions, Copy Document Posted Invoice and Relcalculate Lines=No Fields, Appl.-to Item Entry and Appl. From Item Entry did not reset. In certain situation, Apply -to Entry No. is now set to zero when you copy it onto Sales and Purchase document.


Service System reference: RU-212-904-QH3M

A131) Overflow Error Occurred

Error

Using a Customer No. with field length > 10 on Sales Prices caused an overflow error.


Table 7002 Sales Price Service System reference: HQ-913-88-NJUY


A132) Variant Information Not Updated

Error

When you change Sales or Purchase header information, the lines are updated as well but in this case the Variant information was not updated.


Table 36 Sales Header Table 38 Purchase Header Service System reference: GB-397-960-PEKZ

A133) Undo Shipment,Receipt and Returns Did Not Use a Gen. Bus. Posting Group.

Error

Undo Shipment, Receipt and Return did not enter the Gen. Bus. Posting Group from the source document line to the Item Journal Lines during posting.


Codeunit 5813 Undo Purchase Receipt Line Codeunit 5814 Undo Return Shipment Line Codeunit 5815 Undo Sales Shipment Line Codeunit 5816 Undo Return Receipt Line Service System reference: DE-148-682-JJU8

A134) Changing ""Shipping Agent Service Code"" on Sales Header with a Sales Line with a Blank Type Returns Error

It was not possible to change the Shipping Agent Service Code on a Sales Header with a Sales Line with a blank type.


Table 36 Sales Header Service System reference: FR-142-974-AKSC

A135) Undo Shipment Doesn't Work with Item Tracking and Expiration Date

Error

For undo posting the test for expiration date has been disabled.

This has been corrected-

Codeunit 22 Item Jnl.-Post Line Service System reference: CH-947-417-7HQ8


A136) Shipping Time in Sales Order Header Was Not Shipping Time from Customer Card

Error

New function needed to be created called GetShippingTime in the Sales Header table.


Table 36 Sales Header Service System reference: DE-176-19-2HBN

A137) Upgrade of Sales Price Sometimes Resulted in the Incorrect Values Assigned

Error

During upgrade the Sales Price tables was not initialized before values were transferred.


Upgrade260360.1.fob, Upgrade310360.1.fob, Upgrade301360.1.fob, Upgrade260360.1.MFG.fob Upgrade260370.1.fob, Upgrade310370.1.fob, Upgrade301370.1.fob, Upgrade260370.1.MFG.fob" Service System reference: DE-93-977-QKNF

A138) Error in the Suggest Sales Price on Worksheet

Error

A Validation code was missing in the Sales Code field in REP 7052.


Report 7052 Suggest Sales Price on Wksh. Service System reference: HQ-210-861-GL4E

A139) Reports Were Missing Company Information

Error

CompanyInfo.Get needed to be relocated in OnAfterGetRecord trigger.


Report 204 Sales - Quote Report 205 Order Confirmation Report 206 Sales - Invoice Report 207 Sales - Credit Memo Report 208 Sales - Shipment


Report 210 Sales Reservation Avail. Report 404 Purchase - Quote Report 405 Order Report 406 Purchase - Invoice Report 407 Purchase - Credit Memo Report 408 Purchase - Receipt Report 410 Blanket Purchase Order Report 5900 Service Order Report 5902 Service Quote Report 5905 Posted Service Order Report 5970 Service Contract Report 5971 Service Contract-Detail Report 5972 Service Contract Quote Report 5973 Service Contract Quote-Detail Report 6631 Return Order Report 6636 Purchase - Return Shipment Report 6641 Return Order Confirmation Report 6646 Sales - Return Receipt Service System reference: DE-116-71-YDMQ

A140) Upgrade Error in table 104104

Error

Remove field 6 (Lead Time Calculation) in Table 104104


Service System reference: ES-964-18-RBJW

A141) Undo Shipment for Item with Item Tracking Caused an Error so that the Database Was Unable to Post Shipment Again

Error

If you performed an ""undo shipment"" on an item with Item tracking, and the item tracking code had a ""Warranty Date Formula"", then it would fail because of an undefined date.


Codeunit 5813 Undo Purchase Receipt Line Codeunit 5814 Undo Return Shipment Line Codeunit 5815 Undo Sales Shipment Line Codeunit 5816 Undo Return Receipt Line Service System reference: ID-940-504-BBY8"

A142) Copying a Sales Document to a Sales Order Missed Drop Shipment Information

Error

CompanyInfo.Get needed to be relocated in OnAfterGetRecord trigger



Codeunit 6620 Mail Handler Service System reference: DE-116-71-YDMQ

A143) Posting Credit Memo Failed Because the Wrong Shipping Advice Was Determined.

Error

The shipping advice during posting for credit memos/return order now determined using the ""Return Qty. to Receive (Base)"" and ""Return Qty. Received (Base)"" fields on the Sales Line.


Codeunit 80 Sales-Post Service System reference: SE-895-782-AH5W

A144) Wrong Item Statistics with Item Charge

Error

The inventory adjustment now ensures that a sales credit memo for an item that has been sold with item charges included can be reversed correctly.


Codeunit 22 Item Jnl.-Post Line Service System reference: CH-73-866-CCYP

A145) GUI Error in Sales Order

Error

The Hot key has been changed to ""G"" for the ""get sales price"" function on the FOR42.


Form 42 Sales Order Service System reference: HQ-569-192-LH6G

A146) Same External Doc. No. Could Be Posted as Several Partial Postings

Error

When posting sales orders, the program checked to ensure that an entered External Doc No. was not already used for the specified customer. This had negative implications when you, for example, posted as partial shipments. Since the same External order No. could be posted as several partial postings.



Codeunit 12 Gen. Jnl. Post Line Service System reference: MY-714-475-S4AE

A147) Due Date and Pmt. Discount Date Were Changed Incorrectly When Balance Account Was Entered in a Sales Journal.

Error

When you entered a due date for either G/L account or bank account the due date and payment discount date was recalculated.


Table 81 Gen. Journal Line Service System reference: DK-991-229-2GV7

A148) Error When Using the AssistButton on the Currency Code Field on a Blanket Sales Order

Error

When you used the Assistedit button on Currency Code field on a blanket order, the ChangeExchangeRate function was called with 0 days because the posting date was no longer used on blanket orders.


Form 507 Blanket Sales Order Form 509 Blanket Purchase Order Service System reference: AT-876-697-EDJ7

A149) Subledger Could Differ From General Ledger

Error

When applying a posted invoice to a payment made before the invoice, you could get in a situation where the invoice was applied even before it was made if focus was on the payment when applying. This has been changed so applying date is always postingdate of the most recent among the selected entries.


Codeunit 226 CustEntry-Apply Posted Entries Codeunit 227 VendEntry-Apply Posted Entries Service System reference: BE-816-509-WJUV


A150) Low Performance in Date Compression of Customer and Vendor Ledger Entry

Error

Because of a missing SETCURRENTKEY on DtldEntries the date compression of customer and vendor ledger entries was very slow.


Report 198 Date Compress Customer Ledger Report 398 Date Compress Vendor Ledger Service System reference: DE-290-973-9BP8

A151) Impossible to Set On Hold Under Special Circumstances

Error

When you marked a customer ledger entry or vendor ledger entry on hold, Navision was performing a validation of specific fields specified in code unit 103. This validation was causing an error message to come up. The reason for the error message was that the "Remaining Pmt. Disc possible" was less than the "Remaining Amount".


Table 21 Cust. Ledger Entry Table 25 Vendor Ledger Entry Service System reference: DE-824-448-LBYR

A152) Posting Date Missing as a Variable for Finance Charge Memo

Error

A new variable called Posting Date was missing in the Finance Charge Memo Header table (302).


Table 302 Finance Charge Memo Header Service System reference: NL-772-339-JJ2K

A153) Overdue Amounts LCY on the Customer Statistics Card

Error

On the Customer Card, if you pressed F9, and selected Overdue Amounts (LCY) you would see all entries instead of only the open entries.


Form 151 Customer Statistics Form 152 Vendor Statistics Table 21 Cust. Ledger Entry Table 25 Vendor Ledger Entry


Service System reference: ES-653-744-UJCX

A154) Get Shipment Lines in Different Currencies

Error

If sales lines on an invoice were made using the function Get Shipment Lines and the lines were in another currency than the invoice, you got the following message: "The Currency Code on the Sales Header and the Sales Shipment Header should be the same". However the program got the line but did not change the currency code on the invoice. So you posted lines in the wrong currency. A filter has now been set, so the Get Shipment form by default only shows shipments in the same currency as the invoice header. Incorrect lines will also not be created.


Codeunit 64 Sales-Get Shipment Service System reference: ES-692-958-DNJG

A155) Incorrect TransHeader and TransFooter in the Statement Report

Error

The TransHeader and TransFooter section showed incorrect amounts in the Statement report (116).


Report 116 Statement

Service System reference: DE-192-30-3BKD

A156) Payment Method Code and Credit Memos

Error

When creating a credit memo from an invoice by copying the document the Payment Method was left blank on the credit memo.


Table 36 Sales Header

Table 38 Purchase Header

Codeunit 80 Sales-Post

Codeunit 90 Purch.-Post

Internal Workbase reference: 33C75A7AA5F9B8FD4125685C0044BA8


A157) Incorrect Placement of Beginning Text in the Reminder - Test Report

Error

The beginning text was placed under the document header instead of above the document header in the Reminder - Test report (122).


Table 295 Reminder Header Table 296 Reminder Line Form 435 Reminder Lines Report 122 Reminder - Test Report 123 Finance Charge Memo - Test Codeunit 378 Transfer Extended Text Codeunit 392 Reminder-Make Internal Workbase reference: EBD52988AA69AB6A412568E100370C6A

A158) No Credit Limit Warning When Using the Copy Document Function

Error

You did not get a credit limit warning if you used the function Copy Document with the option Include Header to create sales documents.


Codeunit 6620 Copy Document Mgt. Internal Workbase reference: 67404DC5F8F241F741256838004EA6EB

A159) No Invoice Rounding Precision in the Sales Document - Test Report

Error

The invoice rounding precision was not shown in the Sales Document - Test report (202).


Report 202 Sales Document - Test Report 402 Purchase Document - Test Service System reference: DE-421-34-GLCG

A160) Update of Finance Charge Memo

Error

If you made a finance charge memo and deleted the ending text line and used the function Update Finance Change Text function, you got the following error message: "Finance Charge Memo Header does not exist".


Table 302 Finance Charge Memo Header


Service System reference: DE-238-569-MCTY

A161) Error When Applying a Payment to an Invoice

Error

If you applied a sales invoice where a payment term with a balancing account was used on an already posted payment you got the error message: "There is no Customer Ledger Entry within the Filter...".


Table 36 Sales Header Table 38 Purchase Header Service System reference: ES-115-96-8JE6

A162) Test Report Showed a Warning When Using Calc. Pmt. Disc. on Credit Memos

Error

If you created a credit memo on a journal line with a customer with a payment term with a checkmark in the Calc. Pmt. Disc. on Cr. Memos field and you ran the General Journal -Test report (2) you got the following two error messages: "Pmt. Discount Date cannot be specified" and "Payment Discount % must be 0".


Report 2 General Journal - Test Service System reference: DE-516-369-5HQD

A163) The Check Credit Limit Form Worked Incorrect

Error

If a customer had an overdue balance and had also exceeded the credit limit, only the credit limit messages were shown when you created an order, even if you had selected to show both warnings in Sales & Receivables Setup. Now both warnings are shown in the header.


Form 343 Check Credit Limit Internal Workbase reference: E832083BE651E6C6C1256B14003EFC77

A164) The Issued Reminder Form and Style Guide

Error

When you opened the Issued Reminder form (438), some of the fields that weren’t selected (for example Customer No., Post Code/City and so on) contained lookup buttons.



Form 438 Issued Reminder Form 450 Issued Finance Charge Memo Internal Workbase reference: 51B703EE9247016D412568EA004BA9D4

A165) Cursor Placement was Incorrect when Applying a Credit Memo

Error

The cursor placement was incorrect, in the Sales Header table (36), when you applied a ledger entry to apply to a credit memo.


Table 36 Sales Header Table 38 Purchase Header Service System reference: DK-74-114-SJKL

A166) You Got an Error when Setting Table Filters in Orders

Error

You got an error message if you set a filter on a primary field together with a filter on another field in a sales order. The error came because the combination of the two filters did not produce any records.


Form 41 Sales Quote Form 42 Sales Order Form 43 Sales Invoice Form 44 Sales Credit Memo Form 49 Purchase Quote Form 50 Purchase Order Form 51 Purchase Invoice Form 52 Purchase Credit Memo Form 434 Reminder Form 446 Finance Charge Memo Form 507 Blanket Sales Order Form 509 Blanket Purchase Order Form 6630 Sales Return Order Form 6640 Purchase Return Order Internal Workbase reference: 1C1F44241B9AE9F3C12566D300448997

A167) Improvable Error Message in the Get Job Usage Function

Error

You got a confusing error message if you selected the function Get Job Usage in a sales invoice that did not have a document number.



Form 43 Sales Invoice Internal Workbase reference: F795E724E8DCC1C541256881002E9F6E

A168) Link Between Customer Card and Job Card

Error

There was no link between the customer card and the job card. A link between the customer and job card has now been made. The link is on the customer card.


Form 21 Customer Card Service System reference: DE-287-38-7FE9

A169) Create Reminder Batch Job

Error

If the Reminder Nos. field in Sales & Receivables was blank, an incorrect error message would appear when making a reminder with the Create Reminder report (188).


Report 188 Create Reminders Internal Workbase reference: 6DA031DE7BE5D11341256A39002CB4EA

A170) Invoice Discount Code and No Series

Error

On the customer or vendor card, if you had more than one number series with a check mark in the Manual Nos. field, the program did not fill in the Invoice Discount Code field.


Table 18 Customer Table 23 Vendor Internal Workbase reference: 67D01A16E3443C78C1256743004314C4

A171) Default Check Mark in the Customer - Detail Trial Bal. Reports

Issue

In the Customer - Detail Trial Bal. report (104), it was not possible to exclude customers that had no entries but only a balance. Now it is possible to exclude accounts that have no entries but only a balance.



Report 4 Detail Trial Balance Report 104 Customer - Detail Trial Bal. Report 304 Vendor - Detail Trial Balance Report 1404 Bank Acc. - Detail Trial Bal. Service System reference: DE-735-801-VBBZ

A172) Error in Posting No. When Invoicing

Error

It was possible to get incorrect posted invoice numbers when the number series had Date Order = Yes and posting would fail because of e.g. missing external document numbers or missing dimensions. This has been corrected by not allowing the posting date to be changed if a posting number has been assigned.


Table 36 Sales Header Table 38 Purchase Header Service System reference: ES-927-881-DNHK

A173) Combine Shipments and Dimensions Created Incorrect Invoices

Error

When you ran the Combine Shipment report (295) for customers that had no dimensions there was a new invoice created for each shipment line instead of one invoice for one customer.


Report 295 Combine Shipments Service System reference: DE-556-610-8ARH

A174) Incorrect Value in the Amount Field on Sales Lines

Error

When you created an invoice which had a check mark in the Including VAT field on a sales or purchase order, some lines which had 0 in the Line Amount field could have an incorrect value in the Amount field after releasing the order.


Table 37 Sales Line Table 39 Purchase Line Codeunit 80 Sales-Post Codeunit 90 Purch.-Post Service System reference: DE-754-745-9GRY


A175) Invoicing Error When Bill-to Customer No Was Different from the Sell-to Customer No.

Error

When you posted a sales invoice with a sell-to customer number that was different from the bill-to customer number, the program copied the VAT registration number on the posted invoice from the sell-to customer. In this case the program should have copied the VAT registration number from the bill-to customer.


Table 36 Sales Header Table 38 Purchase Header Internal Workbase reference: 8A0447F77F94A11BC1256B6B0036BA76

A176) Incorrect Calculation of Amount Including VAT on Sales Lines

Error

In the UpdateVATAmounts function in the Sales Line table (37), the first line of the SalesLine2.COPYFILTERS(Rec);" code could result in an incorrect calculation of VAT. The code has been replaced by:

SalesLine2.SETRANGE("Document Type","Document Type");

SalesLine2.SETRANGE("Document No.","Document No.");


Table 37 Sales Line Table 39 Purchase Line Service System reference: DK-903-845-RJ8Z

A177) [The Customer - Summary Aging Simp. Report Summarized Amount instead of Amount (LCY)

Error

If you executed the Customer - Summary Aging Simp. Report, it would summarize on Amount instead of on Amount (LCY).


Report 109 Customer - Summary Aging Simp. Service System reference: ES-489-655-6F79]


Issues

A178) Blocking of Customers and Vendors

Issue

It is now possible to select different levels of blocking for customers and vendors. The different levels determine the transactions that can be performed with that customer or vendor.


A179) Customer-Sales List & Vendor-Purchase List Reports (formerly Customer and Vendor Annual Declaration Reports)

Issue

Reports for customers and vendors have been made where a company can make an annual declaration of business transactions with companies That have total sales/purchases that are greater than a specified amount.


Report 119 Customer - Sales List Report 309 Vendor - Purchase List Service System reference: HQ-242-566-CRPT

A180) Menu Item on Customer Card to Show Issued Reminders

Issue

A new menu item on the customer card where you can open issued reminders and issued finance charge memos has been implemented.


Form 21 Customer Card Form 22 Customer List Form 440 Issued Reminder List Form 452 Issued Fin. Charge Memo List Service System reference: HQ-394-333-SHSL

A181) New Key on Reminders as Additional Sorting Option Is Created

Issue

A new key (Customer No. + Posting Date) in the Issued Reminder Header table (297) was created.



Table 297 Issued Reminder Header Table 304 Issued Fin. Charge Memo Header Service System reference: HQ-698-803-SHVL

A182) History Modification to the Statement Report (116)

Issue

The Statement report (116) has been modified, to reflect exactly the situation and snapshot as if the report were printed in history.


Report 116 Statement Service System reference: HQ-519-395-CRKQ

A183) Aging Band on the Statement Report

Issue

An aging band has been added to the Statment report (116).


Table 47 Aging Band Buffer Report 116 Statement Service System reference: HQ-735-978-CRRN

A184) Filters Not Transferred to the Apply Forms

Issue

When you entered an "Applies-to Doc. Type" or "Applies-to Doc. No." in a journal the program did not use this information to filter the apply forms.


Table 81 Gen. Journal Line Service System reference: HQ-911-947-Z9V7

A185) Aged Accounts Receivables and Payables Reports

Issue

Two new reports have been made that shows the aging of receivables and payables accounts.


Table 264 Currency Amount


Report 120 Aged Accounts Receivables Report 322 Aged Accounts Payables Service System reference: HQ-930-168-CRPS

A186) Customer and Vendor - Payment Receipt Reports

Issue

Two reports have been made that specifies the customer/vendor ledger entries that have been applied to a payment. The report is designed as a receipt. You can set up your general journal templates, so that the report is printed automatically when you post and print a general journal.


Table 80 Gen. Journal Template Form 101 General Journal Templates Codeunit 232 Gen. Jnl.-Post+Print Codeunit 234 Gen. Jnl.-B.Post+Print Report 211 Customer - Payment Receipt Report 411 Vendor - Payment Receipt Service system reference: HQ-934-334-CRPV

A187) EC Sales List Report Added

Issue

A new report that shows EU 3-Party trade per VAT Registraion No. is created.


Report 130 EC Sales List Service System reference: HQ-967-431-CRPU

A188) Trial Balance Vendor and Customer Reports

Issue

New trial balance reports for both customer and vendor have been made.


Report 129 Customer - Trial Balance Report 329 Vendor - Trial Balance Service System reference: HQ-990-317-CRRP


2.5 Marketing and Sales

Features

A189) Synchronization of Contacts and Attendees information between tasks/appointments/meetings/events in Outlook and To-dos in Navision

Feature

Creating To Do and sync it to Outlook: No contact information are transferred. The same the other way round. So you know that you have meeting but not with whom. The same problem is when a meeting is entered in Outlook the corresponding to-do in Navision is not linked to the contact - only the salesperson. Manually synchronizing does not solve this either. In the To-do structure it is now possible to create To-do’s of type meeting which can have multiple attendees. New tables are added which contains both the attendees and correspondence attachment. The new structure supports the existing to-do views and therefore the conceptual perception of to-do’s has not changed. The main thing is added functionality to the meeting type to-do. The To-do wizard has changed. When making meetings it now shows a new step for adding attendees and creating attachment (used to generate ILE and meeting invitation). Also new functionality has been added to the existing To-do card so that maintenance of meeting scheduling is possible. Outlook integration has been changed to support synchronization of task with related contacts and appointments are not supporting both attendee with and without email. Attachments are linked to the invitations sent to any attendee which has an email. The integration part also supports picking up any meeting replies and synchronize it back to Navision. Synchronization of meetings are fully supported both ways.


Table 5080 To-do Table 5093 Opportunity Entry Table 5102 RM Matrix Management Table 5122 Interaction Template Setup Table 5196 To-do Interaction Language Table 5199 Attendee Form 14 Salespeople/Purchasers Form 5050 Contact Card Form 5052 Contact List Form 5086 Campaign Card Form 5087 Campaign List Form 5096 To-do List Form 5097 Create To-do Form 5098 To-do Card Form 5099 To-dos Form 5105 Teams Form 5116 Salesperson/Purchaser Card Form 5123 Opportunity List Form 5124 Opportunity Card Form 5126 Create Opportunity Form 5132 Active Opportunity List Form 5146 Assign Activity


Form 5186 Interaction Template Setup Form 5196 To-do Interaction Languages Form 5197 Attendee Subform Form 5198 Attendee Wizard Subform Form 5199 Attendees Scheduling Report 5188 Delete To-dos Service System reference: HQ-991-801-CQLH

A190) Reviewing Corresponding Items in Outlook and Navision

Feature

As a new feature in the Navision-Outlook integration, we have build an ADD-IN (OLAddin.dll) which will add a Navision lookup button to Outlook. The new Navision lookup button will use synchronized URL paths to Navision and open the correspondent item in Navision.


Codeunit 5069 Outlook Contact Handler Codeunit 5071 Contact Handler Codeunit 5073 To-do Handler C/side objects has been changed to synchronize and generate Navision URL's Service System reference: HQ-137-136-CR7G

A191) Synchronize Other Users' Changes to My Records "on the Fly"

Feature

Only contacts belonging to the current salesperson in Navision are automatically transferred to Outlook. This decision has been made in order to allow using case execution when an assistant fills in the contact information on behalf of somebody else. In order to synchronize contacts that belong to another salesperson, the user has to use the Export or Synchronize batch jobs. The same result can be achieved by changing the contact’s salesperson to the current one and then changing it back again. Once the contact appeared in Outlook, it will be updated automatically despite the fact that it belongs to another salesperson. In response to this issue, a change has been implemented Change other user's record - and make synchronization if permissions are given by the record owner. The solution will make synchronization possible through the exchange server. This feature includes notification setup which allows a salesperson to receive notification whenever another user changes and synchronizes another salesperson's records. Synchronization feature builds on existing methods for Outlook synchronization.


Codeunit 5069 Outlook Contact Handler Codeunit 5071 Contact Handler Codeunit 5072 Outlook Application Management Codeunit 5073 To-do Handler Codeunit 5074 Buffered Synchronization Form 5116 Salesperson/Purchaser Card Report 5171 Synchronize with Outlook Table 13 Salesperson/Purchaser Table 5050 Contact


Table 5080 To-do Table 5124 Current Salesperson Service System reference: HQ-330-604-CQVB

A192) Date Range Setup for Synchronization Batch Job

Feature

It would be nice if there is a possibility to set up when a synchronization batch job should run, for example, when a user starts up Navision or shuts down the application, and for which period of time the data should be synchronized. In the Salesperson Card form it is now possible to set up a date range which, by user definition, will limit the range of to-dos to be synchronized by date. The range is stated by using normal date formulas. The feature is only usable if synchronization with Outlook is enabled.


Form 5116 Salesperson/Purchaser Card Report 5171 Synchronize with Outlook Table 13 Salesperson/Purchaser Service System reference: HQ-777-747-QJGC

A193) Reviewing Corresponding Items in Outlook and Navision

Feature

As a new feature in the Navision-Outlook integration, we have build an ADD-IN (OLAddin.dll) which will add a Navision lookup button to Outlook. The new Navision lookup button will use synchronized URL paths to Navision and open the correspondent item in Navision.


Codeunit 5069 Outlook Contact Handler Codeunit 5071 Contact Handler Codeunit 5073 To-do Handler C/side objects has been changed to synchronize and generate Navision URL's Service System reference: HQ-137-136-CR7G

Errors fixed

A194) Losing Attendees With the Same E-Mail

Error

When creating a to-do; meeting in Navision, you could experience the situation that two or more of the invited attendees had the same email address. At first this would not cause


problems, except for the fact that the all invitations would be sent to the same email address. The meeting with the attendees would also be synchronized to the corresponding meeting in Outlook perfectly. But if you afterwards changed something in the attendee list in Outlook, all the attendees with the same e-mail address was deleted except for one, when the program synchronized back to the corresponding Navision meeting. The problem is solved by optimizing the function ValidateAttendees in the Attendee table. Now the user is no longer allowed to add more contacts with the same email address to the attendee list. The user will get a warning message and not be allowed to add another contact with the same email as a previous added contact. NOTE: If you create a meeting for a segment of contacts in Navision that includes more contacts with the same e-mail address, the problem still remains.


Table 5199 Attendee Service System reference: HQ-478-233-CK64

A195) Synchronization Batch Job has problems Updating Attendees from Outlook when Navision has been closed during the Outlook updating

If you created a To-do, meeting in Navision while the run time synchronization is running, closed Navision and afterwards modified the attendees or/and contact invited to the meeting in Outlook, you would experience problems when starting Navision again and running the synchronization batch job. It was not able to update the changed attendees and/or contacts. The problem has been solved by changing the functions OverwriteTodoWithTaskItem and OverwriteTodoWithAppItem in Codeunit 5073 To-do Handler. Now the modified attendees and/or contacts registered on the meeting from Outlook will overwrite those in Navision when running the synchronizing batch job.


Codeunit 5073 To-do Handler Service System reference: HQ-309-485-CKRY

A196) Check for CDO and E-mail Address

Error

Previously it was possible to enable Outlook integration without specifying an e-mail for a Salesperson and without having CDO installed. But the new Calendar Basics solution is based on these two things when it processes the Outlook meetings. Now the program performs necessary checks on the OnValidate trigger for Synchronization Enabled field (table 13 Salesperson/Purchaser). In the Outlook Application Management Codeunit the Logon function was corrected - MAPISessionLogon function call performs check for CDO installed.


Table 13 Salesperson/Purchaser Codeunit 5072 Outlook Application Management Service System reference: HQ-190-299-CKUC


A197) Modified Recipients and Related Contacts are not Updated from Navision

Error

In previous solution the program was overwriting the corresponding Outlook Item with updated data of Navision To-do, but it wasn't overwriting Outlook's recipients and related contacts. Now this problem is fixed in the OverwriteItemWithTodo function of Codeunit 5073 To-do Handler. This function now makes the following actions (in case when to-do is newer than Outlook Item): 1) Navision Attendees are overwritten with Outlook's recipients and related contacts; 2) All other Outlook fields are overwritten by corresponding To-do fields.


Codeunit 5073 To-do Handler Service System reference: HQ-312-935-CKXA

A198) Private Contacts Are Synchronized

Error

If you created a meeting in Outlook and inserted a contacts marked as private in the Contact field, the contact name would be synchronized with Navision although it is marked private. This is not supposed to happen. The problem is solved by correcting the UpdateAttendeesFromRecipients and UpdateAttendeesFromRelContacts functions in the Codeunit 5073 To-do Handler. The program did not check the private field on a Contact.


Codeunit 5073 To-do Handler" Service System reference: HQ-84-612-CLHR

A199) Double Variable in Codeunit 5055

Error

ContBusRel variable is removed from Globals and defined as a Local variable on OnRun trigger.


Codeunit 5055 Cust/VendBank-Update Service System reference: DE-848-419-KU3G

A200) Sending Email Meeting Invitation Locked the To-do Table for Other Users

Error

If you created a To-do meeting in Navision, with the ' Send E-mail invitation' activated, the To-do table would be locked for other users if you forgot to click yes in the message box, that tells you the e-mail is being send.



Codeunit 5073 To-do Handler. Service System reference: HQ-445-136-QKNF

A201) Creating a Contact for Another Sales Person Did Not Create Notification

Error

If you did created a new contact in Navision and assigned one of your sales person colleagues to this contact, the sales person would not receive a notification about this new contact assigned to him/her. This is because the contact record is not created in Navision until the program has created the related contact number. At this time the contact does not have a salesperson code – and consequently, why the program does not know whom to notify. The sales person code is not inserted on the contact card until the user closes the contact card. But at this point the program is not able to detect whether it was the contact code or the salesperson code that was newly created or changed, and this is why it does not get triggered to send a notification. The problem is now solved and the message is changed to “Since contact [Contact No.] [Contact Name] has been created or assigned to you in Navision by [Modifier SP Name], the corresponding item has been created in Outlook.


Table 5050 Contact Codeunit 5071 Contact Handler Service System reference: HQ-282-699-QLPN

A202) Using a Sales Persons as Attendees in a To-do Cause Problems

Error

If you created a to-do; meeting in Navision and added another sales person to the attendee list, (who also is setup to be synchronized) the program would act as if you are trying to change the Sales person code for the meeting organizer (which is you). This is not allowed, why you would get a warning message and not be allowed to add the sales person to the attendee list. This has been solved by adding a parameter to the OnValidate trigger in the table 5080, that checks that the sales person is an attendee and not the organizer.


Table 5080 To-do Service System reference: HQ-215-893-RB9Z


A203) Importing Contacts From Outlook with Function "Import from Outlook" sometimes Creates a Contacts twice

Error

If you changed the sales person code on a contact in Navision, you would experience that after synchronizing with Outlook and synchronizing back with Navision, the contact would be created again in the Navision contact table. The issue was fixed by changing the ImportAll function of the Codeunit 5071 Contact Handler. The program did not check the AttainSalesperson field on the Outlook contact card, why Outlook would create a new contact with the same name but assigned to another sales person, when it could not recognize the sales person code. Consequently a new contact would also be created in the Navision contact table in the synchronizing process. Now the AttainSalesperson field on the Outlook contact card is checked in the synchronizing process.


Codeunit 5073 To-do Handler Service System reference: HQ-680-186-RGVK

A204) When Creating a To-do of Type Meeting, You got an Error Message "The Attendee already Exists"

The issue is solved by correcting the ValidateMenu function on the Form 5097 Create To-do.


Form 5097 Create To-do Service System reference: HQ-302-487-SBX3

A205) Outlook Tries to Send Invitation although the "Send Invitation" for the Attendee has not been Checked Marked

The program did not check the field Send Invitation on the attendee record, why it would always send an invitation to the attendees added to a meeting, regardless of whether there was a check mark in the field Send Invitation or not. The issue is solved by correcting the SendMeetingTodo function in the Codeunit 5073 To-do Handler to check the field before sending the invitations.


Codeunit 5073 To-do Handler Service System reference: HQ-388-960-SC5W

A206) Error Message in To-do Wizard, when using Shortcut in Language Code field

Error

When creating a to-do using the to-do wizard and a template with more attachment in different languages, an error message would pop up, if you typed the first letter of the language code (using a shortcut for the language code instead of the look-up function), saying that you could not use the wizard to create a to-do interaction language for this to-do.



Table 5080 To-do Form 5097 Create To-do Service System reference: HQ-584-152-SCJ8

A207) Wrong Due Date in Outlook after Running Batch Job

Error

When creating a to-do in Navision or a task in Outlook, you would experience that the due date did change after synchronization, as Outlook and Navision does not handle calculation of due date in the same way. The issue is solved by changing the OverwriteItemWithTodo function in Codeunit 5073 To-do Handler.Now the program inserts a line; OLTask.Save after assigning the Starting Date value to the corresponding field in Outlook Task.


Codeunit 5073 To-do Handler Service System reference: HQ-687-158-SCMK

A208) Several Access Request Windows Appear when Changing Outlook Items for another User

Error

If you create or change a to-do in Navision for another sales person, who in Outlook actually has not given you permission to modify his/hers Outlook items, you will, when synchronizing with Outlook get a warning on this not once but several times.


Table 5050 Contact Table 5080 TO-do Table 5199 Attendee Table 5119 Outlook Integration Log Codeunit 5072 Outlook Application Management Codeunit 5074 Buffered Synchronization Form 5000 Relationship Management Menu Service System reference: HQ-822-667-SGUZ

A209) Error Message if you try to Print the Report Opportunity – Detail

Error

If you print the report Opportunity - Detail, you could get the following error message: You cannot base a date calculation on an undefined date.


Report 5068 Opportunity - Details


Service System reference: DE-751-344-UE8S

A210) Archived Documents Without Lines Cannot be Accessed

Error

When creating a purchase order header without adding lines, archiving the purchase order and then delete it, you would experience that the archived order no longer is available if you try to open it from the Purchase List Archive. The problem is solved by linking the field Document No. in table 5110 to the Field No. in the table Purchase Header Archive.


Table 5110 Purchase Line Archive Service System reference: DE-295-353-XAKM

A211) Wrong Default Dates on To-do Wizard Called from an Interaction Log Entries.

Error

If you created a to-do for a contact activated from an interaction log entry, you would receive an error message and were not able to continue. This is now corrected by changing the CreateTodo function in Table 5065, to define the To-do Duration in this function before running the wizard from an Interaction log entry.


Table 5065 INteraction Log Entry Service System reference: HQ-296-903-YAK4

A212) Wrong Error Message When Trying to Changing Meeting Organizer on To-do Wizard

Error

If you tried to change the meeting organizer into a required attendee on a to-do wizard, you would get a wrong error message indicating that this actually was possible under the right circumstances. This is wrong, it is not possible to change the meeting organizer in the wizard.


Form 5198 Attendee Wizard Subform Codeunit 5073 To-do Handler Service System reference: HQ-231-359-YAMY


A213) E-mail Addresses from Navision sometimes formatted with Brackets when Synchronized to Outlook

Error

You could experience that contacts e-mails addresses from a meeting created in Navision were formatted with brackets when synchronized to Outlook. This caused problems when synchronized again with Navision, as Navions then would treat the bracket e-mail addresses as the contact's name. The problem was corrected in the UpdateAttendeesFromRecipients function of Codeunit 5073 To-do Handler. It would receive the Recipients E-Mail address with brackets ('[email protected]') why the FindContactByEMail function was not able to find contacts with this E-Mail in the synchronized folder (since Contacts E-mails do not have brackets in their addresses). Now we remove brackets from recipient's e-mails and contacts will be processed correctly.


Codeunit 5073 To-do Handler Service System reference: HQ-194-523-YATJ

A214) Creating To-Dos for Other Sales Persons Cause Disruptions of Data

Error

If you create a to-do, meeting with more attendees in Navision for another sales person (with the other sales person as organizer), you would experience that the meeting was corrupted in the synchronizing process with Outlook. Attendee would be missing in the corresponding Outlook meeting, attendee to-dos would be deleted in Navision etc. This is fixed by changing the procedures of the events activated from Outlook in the synchronization process.


Codeunit 5072 Outlook Application Management Codeunit 5073 To-do Handler Table 5080 To-do Service System reference: HQ-684-947-ZNDE

A215) Creating Meeting To-do for Meeting Organizer without Outlook Integration Setup Require Attachment

Error

If you did create a to-do meeting on behalf of another sales person, who were not setup to synchronize, you would be asked to make an attachment to the meeting invitation when pressing Finish button, because the program acts as if the meeting was never meant to be synchronized, which is the correct behavior. This is corrected so that you get the error message when pressing Next button on second step of to-do wizard where meeting organizer is selected.


Form 5097 Create To-do


Service System reference: HQ-651-775-ZNMH

A216) Contacts from not Synchronized Contact Folders are Created in Navision

Error

If you created a meeting in Outlook and added contacts to the attendees list, who were not included in the folder, which are being synchronized, the program would not find this contact in the Navision contact table, and consequently create it in the table. This is not supposed to happen. Only contacts in the folder being synchronized must be synchronized with Navision. This issue is solved by optimizing the following three functions in Codeunit 5073 To-do Handler: 1. ProcessTaskRelatedContact 2. UpdateAttendeesFromRecipients 3. UpdateAttendeesFromRelContacts Now the program checks, if the contacts in the attendee list is included in the synchronized folder. If a contact is not included here it will not be synchronized to Navision. and a warning will be logged in the Outlook Integration Error log.


Codeunit 5073 To-do Handler Service System reference: HQ-45-53-6EMF

A217) SP1 E-Mail Integration ILE

Error

Exception handling on OutlookHandler.DisplayMail did not return an error message if no e-mail existed. NSAppHandler.OutlookHandler Visual Basic Class (Automation Server Class)


Table 5062 Attachment NSAppHandler.OutlookHandler Service System reference: HQ-160-108-CQL7

A218) Sales Order Archive - Unit Price Incl./Excl. GST Amount Caption

Error

Caption did not change in accordance with the ticked boolean.


Form 5160 - Sales Order Archive Subform Form 5163 - Sales Quote Archive Subform Form 5165 - Purchase Quote Archive Subform Form 5168 - Purchase Order Archive Subform


Table 5108 - Sales Line Archive Table 5110 - Purchase Line Archive Service System reference: SG-97-659-E6EK

A219) Archiving Sales Orders on Posting

Error

The error of: "Another user has modified this record" occured as there was a modify on StoreSalesDocument function that was not needed.


Codeunit 5063 ArchiveManagement Service System reference: SG-365-545-Z8UL

A220) UA1 SP1 ILEs Created by the E-Mail Logging Are Not Automatically Indexed by the Contact Search.

Error

If one was trying to find an e-mail in the interaction log entries, an error would occur as e-mails were not indexed.


Codeunit 5064 E-Mail – Logging Service System reference: HQ-875-851-CR5P

A221) Documents Not Available for Interactions

Error

Return orders were not available for Interactions. The following documents were added to the list of logged documents: Sales - Return Order, Sales - Finance Charge Memo, Sales - Return Receipt, Purchase - Return Shipment, Purchase - Return Order Confirmation, Service Contract, Service Contract Quote, Service Quote. Now when you print (post and print) these documents, appropriate records will be made in the Interaction Log Entry for the corresponding contact.


Table 5065 Interaction Log Entry Table 5077 Segment Line Table 5079 Relationship Management Setup Table 5122 Interaction Template Setup (new) Form 5000 Relationship Management Menu Form 5094 Relationship Management Setup Form 5186 Interaction Template Setup (new) Report 118 Finance Charge Memo Report 5902 Service Quote


Report 5970 Service Contract Report 5972 Service Contract Quote Report 6631 Return Order Report 6636 Purchase - Return Shipment Report 6641 Return Order Confirmation Report 6646 Sales - Return Receipt Codeunit 397 Mail Codeunit 5051 SegManagement Codeunit 5053 TAPIManagement Codeunit 5064 E-Mail - Logging Demodata: Codeunit 2 Company-Initialize Codeunit 101579 Create RM Setup 5079 Codeunit 101599 Create Interact. T. Setup 5122 Codeunit 114000 Interface Relationship Mgt. Service System reference: NL-18-664-ZHUM

A222) Creating an Opportunity for a Foreign Customer

Error

Currency search was incorrect and would give an error.


Codeunit 86 Sales-Quote to Order Service System reference: DE-589-352-FHXZ

A223) CAM NDE 002: It Is Not Possible to Delete a Logged Segment

Error

There was no possibility of deleting logged segments in Navision. A periodic activity for cleaning up canceled segments has been created (Report 5191). Changes to Form 5000 have been made, and a new menu item for the periodic activity has been added.


Form 5000 Relationship Management Menu Report 5191 Delete Logged Segments Service System reference: HQ-757-123-CQUC

A224) MultiLanguage Errors

Error

Multilanguage was not correct in error message. Removed Option value in Error Message in function GetSalutation.



Table 5050 Contact Service System reference: HQ-146-450-CQK9

A225) Missing TAPI Buttons on the General tab of the Customer and Vendor Cards

Error

TAPI buttons were not applied to all tabs where the Phone No. field existed.


Form 21 Customer Card Form 26 Vendor Card Service System reference: HQ-283-676-CP64

A226) The Customer Credit Limit Check of Sales Order/Credit Limit Is Not Performed When Creating a Service Order from the Customer Card

Error

Credit limit check is not performed when choosing any sales document or service document from the Customer Card. The Customer no. filter is used for checking when the forms are run.


Table 36 Sales Header Form 41 Sales Quote Form 42 Sales Order Table 5900 Service Header Form 5900 Service Order Form 5964 Service Quote Service System reference: NL-273-895-JBHY

A227) Campaign Entries Are Not Created

Error

Campaign entry was not created on Interaction Log Entries from segment.


Table 5077 Segment Line Service System reference: HQ-841-665-CR98


A228) Another User Has Modified the Record for This Customer

Error

The problem occurred when another user had modified the record for this customer after you had retrieved it from the database.


Table 18 Customer Table 23 Vendor Service System reference: SG-258-718-Q58C

A229) Missing Option Strings

Error

The Refund option string was missing on the Applies-to Doc. Type field in table 5107 Sales Header Archive.


Table 5107 Sales Header Archive Service System reference: HQ-793-484-CQ84

A230) Missing Filter in the Purchase and Sales Archives

Error

In archive you would get the error "There is no Purchase Header Archive within the filter ..." due to missing filter.


Form 5162 Sales Quote Archive Form 5164 Purchase Quote Archive Form 5167 Purchase Order Archive Service System reference: DE-182-228-X8LN

A231) Wrong TableRelation in Table 5110 Purchase Line Archive

Error

TableRelation was not set up correctly on "Document No."


Table 5110 Purchase Line Archive Service System reference: DE-274-751-R99U


A232) Contact Search: Overflow under Conversion from Text to Text

Error

Overflow would occur under Conversion from Text to Text when working with query. Change Datatypes for all variables/return values, which are used in Query processing. Procedure ComposeQueryLine: Data type of return value is changed from Text[250] to Text[1024].


Codeunit 5067 Search Management Form 5177 Contact Search Service System reference: DE-318-102-FLNZ

A233) UA1 Overflow Error Caused by Codeunit 5072

Error

When synchronizing, there was a problem with overflow on contact name. A user would receive a text overflow error.


Codeunit 5072 Outlook Application Management Service System reference: HQ-433-107-CR88

A234) Text Overflow in the Contact Table

Error

Text overflow in the Contact table would occur. We have made it possible to change the length of the Name field (First Name, Middle Name, and Surname) to any size (up to 250 characters).


Table 5050 Contact Service System reference: HQ-232-943-CQBJ

A235) Document Dimension Archive Show's Table ID 36/37 Instead of 5107/5108

Error

In Table 5106, the Table Id shows were 36 or 37. But the entries shown in this table were stored in Table 5107 or 5108.The Program handled this correct because it was hardcoded in the table.


Table 5108 Sales Line Archive Table 5110 Purchase Line Archive Form 5159 Sales Order Archive Form 5162 Sales Quote Archive


Form 5164 Purchase Quote Archive Form 5167 Purchase Order Archive Codeunit 5063 ArchiveManagement Service System reference: HQ-948-348-CCUA

A236) ToolTips Missing for Some Buttons in the Relationship Management Area

Error

The ToolTips were missing for some buttons in the Relationship Management area.


Form 5077- Create Interaction Form 5097- Create To-Do Form 5126- Create Opportunity Form 5148- Create Mail Service System reference: DE-619-697-MBAH

A237) FinSQL Error

Error

Even when working with different templates in a multiuser environment, SQL locking was a problem. The structure of word attachment handling was reviewed, and a different approach has been developed.


Table 5062 Attachment Table 5076 Contact Job Responsibility Table 5077 Segment Line Table 5103 Interaction Tmpl. Language Table 5104 Segment Interaction Language Codeunit 5052 AttachmentManagement Codeunit 5054 WordManagement Form 5075 Interaction Templates Service System reference: HQ-839-623-GFR7

A238) Wrong SourceExpr in Report 5068 Opportunity – Details

Error

The SourceExpr in Report 5068 was wrong.


Report 5068 Opportunity - Details Service System reference: DE-944-853-LNEZ


A239) Outlook Synchronization

Error

Wrong "LastSynchronizedDate" would be created on synchronized Outlook contacts.


Codeunit 5069 "Outlook Contact Handler" Codeunit 5071 "Contact Handler" Service System reference: AT-987-342-6CLN

A240) Error in Codeunit 5072 Outlook Application Management

Error

Text was misspelled in text variable.


Codeunit 5072 Outlook Application Management Service System reference: DE-410-113-FJDZ

A241) Vanishing of Points When Clicking OK

Error

When clicking OK, the points vanished. The form update was not sufficiently programmed.


Form 5172 Answer Points Service System reference: DE-970-318-FLXE

A242) Wrong Date Calculation in the Opportunity Details Report

Error

Before, planned to-dos were calculated from the Estimated Closing Date. This has been changed, so that now we look at the first to-do in the last active Sales Cycle Stage and calculate the planned to-dos from this date. Date Formula in Table "Sales Cycle Stage" Now this field is used in a slightly different way. If this field has the value 1W, then this stage will usually start one week after the previous stage.


Report 5068 Opportunity – Details Service System reference: DE-970-393-THDW


A243) The Name Details Window Appeared Instead of the Company Details When Clicking the AssistButton on the Company Card

Error

The AssistButton did not launch the correct form.


Form 5050 Contact Card Form 5054 Company Details Service System reference: NL-107-197-XCMP

A244) Campaign Entry Was Not Created Even When You Printed or Posted

Error

Campaign entry was not created when you printed or posted documents. A new Campaign Entry is now created when: - Logging a Segment - Printing a Sales Document The same Campaign Entry is used when: - Activating Make Phone Call, Send E-mail or Create Interaction. Campaign No. is inserted into the Log Document parameter list.


Form 5089 Campaign Entries Report 116 Statement Report 117 Reminder Report 118 Finance Charge Memo Report 204 Sales - Quote Report 205 Order Confirmation Report 206 Sales - Invoice Report 207 Sales - Credit Memo Report 208 Sales - Shipment Report 210 Blanket Sales Order Report 404 Purchase - Quote Report 405 Order Report 406 Purchase - Invoice Report 407 Purchase - Credit Memo Report 408 Purchase - Receipt Report 5055 Contact - Cover Sheet Report 5064 Service Quote Report 5902 Service Quote Report 5970 Service Contract Table 5072 Campaign Entry Table 5901Service Item Line Table 6660 Return Receipt Header Report 6631Return Order Report 6636 Purchase - Return Shipment Report 6641 Return Order Confirmation Report 6646 Sales - Return Receipt Table 110 Sales Shipment Header Table 112 Sales Invoice Header Table 114 Sales Cr.Memo Header Service System reference: HQ-930-308-CRDX


A245) Already Misspelled in a Few Places.

Error

Already was misspelled in Tab5092, Text006


Codeunit 12 Gen. Jnl.-Post Line Codeunit 5064 E-Mail - Logging Table 5092 Opportunity Service System reference: HQ-967-847-CRK5

A246) Bill-To Contact No. and Sell-to Contact No.

Error

Bill-To Contact No. and Sell-to Contact No. from table 36 was not transfered to the tables 110 and 114


Table 114 Sales Cr.Memo Header Table 110 Sales Shipment Header Service system reference: DK-350-621-DHY8

A247) Shortcut Keys in Form Contact Search

Error

Shortcut keys in Form Contact Search were not working.


Form 5177 Contact Search Service System reference: HQ-514-77-CQW2

A248) Fields on the To-do Card Were Not ML-enabled

Error

The fields Ending Date and Ending Time on the To-do Card (Form 5098) were not ML-enabled.


Form 5098 To-do Card Service System reference: DE-758-712-QJSD


A249) To-do Number Is Not Displayed in the Interaction Log Entry When Created from the To-do Card

Error

The problem would appear if you tried to make a phone call from the to-do that belonged to a campaign - there would be no Campaign number for the corresponding Interaction Log Entry (in case you made a phone call from the To-do Card).


Form 5098 To-do Card Service System reference: US-101-70-NLQ2

A250) E-Mail Logging: It Was Not Possible to View Mails That Had Been Sent As a Response to a Meeting

Error

In E-Mail Logging it was not possible to view mails that had been sent as a response to a meeting.


Table 5062 Attachment Code 397 Mail Code 5053 TAPIManagement Code 5054 Word Management Code 5064 E-Mail - Logging OutlookHandler.cls Service System reference: HQ-587-496-CQLS

A251) Credit Memos Were Not Logged in ILE

Error

Credit Memos were not logged in ILE in sales or purchase.


Report 207 Sales - Credit Memo Report 407 Purchase - Credit Memo Service System reference: HQ-380-583-CRDE

A252) The Header of the Sales List Archive Form

Error

Correct GUI error. The header of the Sales List Archive did not show the type of the document.


Form 5161 Sales List Archive


Form 42 Sales Order Service System reference: NL-963-658-2AHT

A253) E-Mail Logging User ID Error

Error

There was a problem with the NextControl - Property on the E-Mail Logging User ID Control, so the user would get an error message when setting up E-Mail Logging User ID and leaving the field with <Enter>.


Form 5094 Relationship Management Setup. Service System reference: CH-305-723-WEWR

A254) Report Leaves One Row of Labels Unused

Error

Most of the time, report #5065 left the bottom row of labels on a sheet unused, due to the fact that the report had a bottom margin of about 2 cm.


Report 5065 Segment – Labels Service System reference: NL-155-297-68FN

A255) Error When Viewing the Following Document

Error

To clean up, the file was deleted automatically, and this caused the user to loose the temp file.


Table 5062 Attachment Service System reference: HQ-209-149-CRD3

A256) Loosing Data After Sychronizing Navision with Outlook

Error

Due to Navision constrains on text length, some undesired cuts were made on the Subject field when synchronizing. Subject is synchronized if the first 50 characters have been changed, otherwise the Subject is left untouched.



OutlookSyncHandler.OTask OutlookSyncHandler.OAppointment Service System reference: HQ-505-533-KDKJ

A257) Default Correspondence Type on Segment Lines

Error

Segment line did not inherit the Interaction template correspondence type if its own was set to blank.


Codeunit 5051, "SegManagement" Service System reference: HQ-957-719-CRK7

A258) Some Fields Cannot Be Translated

Error

Fields on the Create Opportunity wizard could not be translated. Caption and CaptionML properties of the textboxes are set to the corresponding correct values.


Form 5126 Create Opportunity Service System reference: DE-323-36-FKBY

A259) Error When Creating a New Answer for a Questionnaire in the Profile Questionnaire Setup

Error

When entering a new answer lookups on the record to be found but could not since delayed insert would cause error that record could not be found.


Form 5110 - Profile Questionnaire Setup Service System reference: HQ-160-139-3CYQ

A260) Wrong Key Used for the Contact Business Relation in the Sales Header

Error

If there were a lot of customers with a relation to contacts in the system, creating a new Sales Header or changing the Bill-To / Sell-To fields in the Sales Header would be slow.


A similar problem was found in the purchase area. In response to this issue, a change has been implemented. New keys have been applied to the relevant tables in both sales and purchase areas.


Table 36 - Sales Header Table 38 - Purchase Header Service System reference: CH-46-469-KBJ7

A261) Create Interaction Error

Error

Campaign filter would erase fields on the wizard if the form was left to make comments, because campaign code was not yet entered.


Form 5077 Create Interaction Table 5076 Segment Header Table 5077 Segment Line Service System reference: BE-993-127-LM9H

A262) Permissions to Tables 5113..5118

Error

Missing permission in search in demo data. Demo tool updated with permissions.


COD101991 Create Permissions Service System reference: ES-516-881-TAXW

A263) Form Design Issues in Forms 5159, 5162, and 5167 Fehler im Formdesign für Einkaufs- und Verkaufsarchive

Error

In Form 5169 (Sales Order Archive) the Property VerGlue in the main form has to be Top - it was Both, which was wrong. In Forms 5162 (Sales Quote Archive) and 5167 (Purchase Order Archive) the controls "City" were missing on the form.


Form 5159 Sales Order Archive Form 5162 Sales Quote Archive Form 5167 Purchase Order Archive Service System reference: DE-698-236-UAJ8


A264) Changes Made to an Attachment in the Interaction Log Wizard Were Deleted When Returning to the Previous Wizard Page

Error

If any changes have been made, they are also saved if the user goes back in the wizard.


Form 5077 Create Interaction Service System reference: HQ-477-548-WH7F

A265) The Cancel To-dos with Deleted Outlook Items Batch Job Removes Recurrence Settings from Processed Items to Avoid Cyclic Operations.

Error

To-do was not recreated due to faulty handling of synchronization.


Table 5080 To-do Report 5166 Cancel Deleted To-dos Report 5171 Synchronize with Outlook Service System reference: HQ-962-602-CQVN

A266) UA1 JF17 Restoring a Contact in Outlook Can Result in Duplication

Error

Due to wrong conflicts in version no. duplicates occurred in synchronization.


Report 5171 Synchronize with Outlook Codeunit 5071 Contact Handler Service System reference: HQ-839-490-CQVA

A267) Navision Froze When Outlook Was Shut Down

Error

This was due to a kind of deadlock between the Outlook that was being closed and a new Outlook process. It was obvious that we must let the old Outlook go and then start a new one. But we could not do it from the Quit event that we received in Navision, because the old Outlook process was still alive. We now use the Timer component that is shipped with a standard Navision installation. So, when we receive quit event from ""dying"" Outlook, we don't restart Outlook right away, we set the timer instead for 1 second. Then on the Timer event we start a new Outlook process and stop the timer. Also, added public Logoff function to OLHandler object, to decrease amount of opened Outlook sessions to release them. This will also implicitly help to reduce number of security request windows.



Codeunit 5072 Outlook Application Management Outlook Application ManagementDll OLWrapper Service System reference: HQ-836-735-CQUV

Issues

A268) Restart Outlook if the Connection Is Broken During Navision Session.

Issue

If the connection from Navision to Outlook had been broken, there was no way to restore the connection to Outlook other than to restart Navision. Now functions will handle attempts to restart the Outlook connection.


Codeunit 5072 Outlook Application Management Report 5171 Synchronize with Outlook Service System reference: HQ-677-587-TE22

2.6 Service Management

Features

A269) Multiple Contracts per Service Item

Feature

The multiple contracts feature allows handling different service contracts or contract quotes for the same service items. When adding a service item to a service contract or contract quote, the system gives a warning if the service item is already registered in other service contracts or contract quotes with the same customer. It is possible to create a service contract or contract quote from an existing one by using the Copy Document function. The Change Customer in Contract function modifies all customer-related information not only in a contract it was called from, but also in all contracts and contract quotes related to it within common service items. It is possible to change the content of the Contract No. field on non-invoiced service item lines in the service order not linked to any service contract. Besides, the Contract Filter in the Service Item Statistics form did not worked, thus causing erroneous information to appear on this form. This has been corrected.


Table 5900 Service Header Table 5901 Service Item Line


Table 5907 Service Ledger Entry Table 5940 Service Item Table 5964 Service Contract Line Table 5965 Service Contract Header Form 5980 Service Item Card Form 5981 Service Item List Form 6050 Service Contract Form 6052 Service Contract Subform Form 6053 Service Contract Quote Form 6054 Service Contract Quote Subform Form 6057 Contract Line Selection Form 6075 Serv. Contr. List (Serv. Item) Form 6076 Serv. Item List (Contract) Form 6078 Service Contract Line List Report 5979 Copy Service Document Report 6037 Change Customer in Contract Codeunit 5907 ServInvLine-Post Codeunit 5912 ServLedgEntries-Post Codeunit 5940 ServContractManagement Codeunit 5944 SignServContractDoc Codeunit 6620 Copy Document Mgt. Service System reference: HQ-607-26-CR52

A270) Contractually related service ledger entry handling

Feature

The handling of service ledger entries from service contracts is changed. The system now always creates the service ledger entries as detailed. This facilitates the handling of statistics in a much more detailed way in the trendscape forms.


Codeunit 5940 ServContractManagement Codeunit 5942 ServContractQuote-Tmpl. Upd. Codeunit 5943 Lock-OpenServContract Codeunit 5944 SignServContractDoc Codeunit 5945 CreateCreditfromContractLines Form 6050 Service Contract Form 6052 Service Contract Subform Form 6053 Service Contract Quote Form 6054 Service Contract Quote Subform Form 6055 Service Contract Template Form 6057 Contract Line Selection Form 6061 Contract Trend Lines Form 6072 Filed Service Contract Form 6074 Filed Service Contract Subform Report 5985 Contract Price Update - Test Report 6031 Update Contract Prices Report 6034 Remove Lines from Contract Table 5964 Service Contract Line Table 5965 Service Contract Header Table 5968 Service Contract Template Table 5970 Filed Service Contract Header Table 5971 Filed Contract Line *Codeunit 117069 Create Service Contract Templa (new form!) For6079 Contract Amount Distribution


Service System reference: HQ-709-178-CR4L

Errors fixed

A271) New key to improve performance

Error

Replavs multiple MODIFYALL by a proper FIND('-') REPEAT...UNTIL NEXT = 0 for performance.


Codeunit 5944 SignServContractDoc Table 5970 Filed Service Contract Header Service System reference: HQ-816-822-CR3M

A272) New Filters for Service Items in Service Orders

Error

When looking up in the Service Item No. field on the service item lines all registered service items were shown in the Service Item List form. However, only service items belonging to the same customer as assigned on a service order should have been shown. In addition, if the service order was linked to a service contract, service items should have been filtered by this contract’s number. This has been corrected.


Table 5901 Service Item Line Service System reference: HQ-606-231-CPHC

A273) Lookup in the Preferred Resource Field Opened Wrong Form

Error

When performing a lookup in the Preferred Resource field on the Service Item Card, the Resource List form appeared. That form didn’t show what resources were skilled to service the corresponding service item. Besides that, there was no possibility to open the Resource Card for resources shown in that form. This has been corrected so that looking up in the Preferred Resource field on the Service Item Card causes the Skilled Resource List form to appear. The contents of the Skilled field in this form determine whether the resource is skilled to service the corresponding service item. The Resource button is added, and its Card menu item gives the possibility to open a Resource Card for a resource in the Skilled Resource List form.


Table 5940 Service Item Form 6023 Skilled Resource List Form 30 Item Card


Form 31 Item List Form 5909 Service Item Groups Form 5980 Service Item Card Form 5981 Service Item List. Service System reference: AU-658-710-N6BT

A274) The Message which Appears when Creating a Service Contract was Missing a Word

Error

When creating a service contract the following confirmation message appeared: Do you want to create the using a contract template?. The word contract was missing in it. This has been corrected.


Table 5965 Service Contract Header Service System reference: HQ-990-904-CRF6

A275) The Expiration Date Was not Copied from Contract Header to Contract Lines

Error

The Expiration Date fields in the Service Contract Header and Service Contract Lines tables were not properly linked. It resulted in the erroneous data validation in these fields. It was possible to set the expiration date of a contract line later than the expiration date of the corresponding service contract.


Table 5964 Service Contract Line Table 5965 Service Contract Header Form 6050 Service Contract Form 6053 Service Contract Quote Service System reference: US-340-240-XNSC

A276) Service Orders Handled VAT Business Posting Groups Inconsistently

Error

The Request Form in the Insert Fault/Resol. Relations report was missing a caption on the field that showed the relation based on service item group. When that field got the focus, nothing was shown in the status bar. This has been corrected. The caption of this field is Relation Based on Service Item Group and it is shown in the status bar when the corresponding control gets the focus.


Report 6007 Insert Fault/Resol. Relations Service System reference: DK-281-734-TFUX


A277) The Ship-to Phone Label on the Posted Service Order is Renamed

Error

There were two fields for showing the ship-to customer’s phone numbers on the Shipping tab in the Posted Service Order form, but the text label for them was incorrect. It had the Ship-to Phone caption. This has been corrected. Now the text label has the Ship-to Phone/Phone 2 caption.


Form 5945 Posted Service Order Service System reference: DE-347-611-5BHQ

A278) Shortcuts were Missing on the Loaner Card and Loaner List Forms

Error

Both the Loaner Card and Loaner List forms missed the shortcuts to the Loaner List and Loaner Card forms correspondingly. This has been corrected. Now, pressing Ctrl+F5 on the Loaner Card form causes the Loaner List form to appear. Conversely, pressing Ctrl+F5 on the Loaner List form causes the Loaner Card form to appear.


Form 5922 Loaner Card Form 5923 Loaner List Service System reference: DE-883-38-3FE2

A279) The Service Button on the Posted Service Order List Form is Renamed.

Error

The caption of the Service menu button on the Posted Service Order List form was incorrect according to the terminology guidelines. This has been corrected. The button was renamed to Order.


Form 5946 Posted Service Order List Service System reference: DK-434-740-KB2Y

A280) The Message which Appears when Converting a Contract Quote to a Service Contract was Missing a Number of a Sales Invoice

Error

When a service contract quote was converted into a service contract by using the Make Contract function and a new service contract was invoiced simultaneously, the following message appeared: Sales Invoice was created. This message was missing the number of the sales invoice created. This has been corrected.



Codeunit 5944 SignServContractDoc Service System reference: HQ-881-280-CR7R

A281) Captions Were Missing on some Controls in the Serv. Inv. Line Price Adjmt. Form

Error

There were no proper captions for the following controls on the Serv. Inv. Line Price Adjmt. form: the Total Amount and Amount to Adjust text boxes, the Remaining label, and the Remaining text box. This has been corrected.


Form 6084 Serv. Inv. Line Price Adjmt. Service System reference: DE-178-201-PHRG

A282) Invoicing a Service Contract Generated Needless Sales Lines

Error

Sales lines in an automatically created sales invoice for a service contract included the “Service Item included” text string which was repeated before each service item. This problem occurred when such an invoice contained a lot of lines, which caused difficulties in reading. This has been corrected.


Codeunit 5940 ServContractManagement Service System reference: DE-586-72-PHXQ

A283) Some Forms Were Inconsistently Un-editable

Error

The Service Order Types and Fault Codes forms were uneditbale which was inconsistent with other similar editable forms in Service Management. This has been corrected.


Form 5908 Service Order Types Form 5927 Fault Codes Service System reference: HQ-478-795-CPW7


A284) Looking up in the Service Item No. Field on the Posted Service Invoice Lines

Error

A lookup in the Service Item No. field on the Posted Service Invoice Lines failed. The problem occurred because the TableRelation property of the Service Item No. field in the Posted Service Invoice Lines table was set incorrectly. This has been corrected.


Table 5932 Posted Service Invoice Line Service System reference: HQ-779-248-CRSM

A285) Credit Memos for Service Contracts Could not be Posted

Error

It was impossible to post a credit memo created manually for an invoiced service contract and filled in by using the Get Prepaid Contract Entries function. This has been corrected.


Table 37 Sales Line Codeunit 80 Sales-Post Service System reference: HQ-613-458-CRHS

A286) Deleting a Service Item, Service Contract, Customer, Item, or Job did not Reflect on Service Ledger Entries

Error

When a service item, service contract, customer, item, or job was deleted the system did not empty the corresponding fields in the Service Ledger Entry table. Internal relations regarding deletion were not supported for service items, service contracts, customers, items, and jobs. For example, when a customer was deleted, the system did not empty the Customer No. field in the Service Item and Service Contract tables. This has been corrected.


Table 23 Vendor Codeunit 5906 ServLogManagement Table 18 Customer Table 27 Item Table 5905 Service Cost Table 5940 Service Item Table 5965 Service Contract Header Form 5980 Service Item Card Codeunit 361 MoveEntries Service System reference: HQ-741-763-CR7N


A287) Looking up in the Service Item No. Field on the Posted Service Header

Error

A lookup in the Service Item No. field on the Posted Service Header failed. The problem occurred because the TableRelation property of the Service Item No. field in the Posted Service Header table was set incorrectly. This has been corrected.


Table 5930 Posted Service Header Service System reference: HQ-372-365-CRAG

A288) Service Orders Handled VAT Business Posting Groups Inconsistently

Error

Changing a bill-to customer of a service order influenced all its VAT related data to be updated. This was inconsistent comparing to a Sales Order where all VAT information is automatically updated when its sell-to customer is changed. This has been corrected. Now the VAT information of a service order is automatically modified only when its customer is changed.


Table 5900 Service header Service System reference: DE-735-137-YCKZ

A289) The TableDesigner Granule Did Not Give Permissions to Design the Sales Header Table

Error

The TableDesigner did not give permissions to to design the Sales Header table. Therefore, it was impossible to change this table. This has been corrected. The special permissions were removed from the Sales Header table. Its C/Caps information was changed to give it the permissions instead.


Table 36 Sales Header Table 37 Sales Line Table 5936 Service Document Register Codeunit 5907 ServInvLine-Post Codeunit 5908 ServOrder-Post Codeunit 5912 ServLedgEntries-Post Codeunit 5940 ServContractManagement Service System reference: DK-489-126-TKJM


A290) Adding a Service Item to a Service Contract did not Reflect on the Service Item Log

Error

The Service Item Log did not contain information about adding, changing or removing a service item in a service contract. This has been corrected. The system creates entries both in the Service Item Log and Contract Change Log each time a service item is added, changed or removed in a service contract.


Table 5942 Service Item Log Table 5964 Service Contract Line Codeunit 5906 ServLogManagement Service System reference: HQ-367-405-CR9E

A291) Incorrect VAT Calculation on Service Invoice Lines

Error

The VAT calculation on a service invoice line was incorrect if it included a service item owner of which (specified by the value in the Customer No. field on the Service Item Card) had a check mark in the Prices Including VAT field in the Customer table. This has been corrected.


Table 5902 Service Invoice Line Service System reference: HQ-182-89-CR7S

A292) Function Copy Default Service Hour does not work

Error

Nothing happened when trying to copy default service hours to a service contract unless the user were using English language.


Form 5916 Service Hours Service System reference: DE-19-374-LGKB

A293) The Create Credit Memo Function does not Work

Error

It was not possible to create a sales credit memo using the Create Credit Memo function for a service contract without a check mark in the Automatic Credit Memos field in the Service Contract Header table. This has been corrected.


Codeunit 5944 SignServContractDoc Codeunit 5940 ServContractManagement


Table 5964 Service Contract Line Table 5965 Service Contract Header Form 6052 Service Contract Subform Service System reference: HQ-258-326-CR9D

A294) The Confirmation Message Upon Receiving a Loaner was Missing

Error

When trying to receive a loaner, only the Loaner has been received message appeared after the loaner had been received. Besides that, the Receive menu item under the Functions button on the Loaner Card form didn’t work. This has been corrected. Now, when receiving a loaner, the following confirmation message appears: Do you want to receive a loaner?. The Loaner has been received message has been removed.


Form 5921 Available Loaners Form 5922 Loaner Card Codeunit 5901 ServLoanerManagement Service System reference: HQ-168-514-CRF5

A295) GUI Issues

Error

Minor GUI issues solved, i.e. corrected widths, leader dots, etc.


Form 5915 Service Tasks Form 5921 Available Loaners Form 5922 Loaner Card Form 5923 Loaner List Form 5926 Symptom Codes Form 5927 Fault Codes Form 5930 Fault/Resol. Codes Rlship. Form 5944 Service Shelves Form 5948 Posted Service Inv. Lines Form 5968 Service Document Registers Form 5983 Service Item Trendscape Form 5993 Troubleshooting Setup Form 6004 Res. Availability (Service) Form 6008 Res. Alloc. per Service Order Form 6009 Res. Gr. Alloc. per Serv Order Form 6010 Res.Gr. Availability (Service) Form 6019 Resource Skills Form 6023 Skilled Resource List Form 6056 Service Contract Template List Form 6058 Contract/Service Discounts Form 6060 Contract Trendscape Form 6061 Contract Trend Lines Form 6062 Service Contract Groups Form 6066 Contract Gain/Loss (Groups) Form 6067 Contract Gain/Loss (Customers) Form 6068 Contract Gain/Loss (Reasons)


Form 6069 Contract Gain/Loss (Resp.Ctr) Form 6071 Contract Gain/Loss (Contracts) Service System reference: HQ-702-878-CR3K

A296) Zeros in Service Hours Led to Errors

Error

The error occurred after setting up service hours for a service contract with zeros in both the Starting Time and Ending Time fields. If a service item which was serviced under such a service contract was added to a service order, the error message appeared: The time is invalid. This has been corrected.


Table 5901 Service Invoice Line Table 5910 Service Hours Service System reference: HQ-288-188-CR7Q

A297) Incorrect C/AL Code Placement

Error

Some C/AL code regarding comments was placed on forms - this conflicted with Navision guidelines. This has been corrected. The code is now moved to tables.


Table 5901 Service Item Line Table 5931 Posted Service Item Line Table 5964 Service Contract Line Form 5900 Service Order Form 5902 Service Order Subform Form 5945 Posted Service Order Form 5947 Posted Service Order Subform Form 5964 Service Quote Form 5965 Service Quote Subform Form 6050 Service Contract Form 6052 Service Contract Subform Form 6054 Service Contract Quote Subform Service System reference: HQ-64-81-CR47

A298) No Number Series for Sales Credit Memos Created for Service Contracts

Error

The Sales Credit Memos created for service contracts did not have their own number series. The number series for them were generated using the contents of the Contract Invoice Nos. field in the Service Mgt. Setup table. This has been corrected. The Contract Credit Memo Nos. field is created in the Service Mgt. Setup table which holds the credit memos number series in Service Management a new separate field is used called "Contract Credit Memo Nos."



Codeunit 5940 ServContractManagement Form 5919 Service Mgt. Setup Table 5911 Service Mgt. Setup Codeunit 117012 CreateServiceMgtSetup Codeunit 117556 AddNoSeries Codeunit 117557 AddNoSeriesLine Service System reference: HQ-310-18-CRG2

A299) Terminology in the Application (Object Names, etc.)

Error

The following forms have been renamed: 6072 Filed Contract -> Filed Service Contract 6073 Filed Contract List -> Filed Service Contract List 6074 Filed Contract Subform -> Filed Service Contract Subform


Form 6072 Filed Service Contract Form 6073 Filed Service Contract List Form 6074 Filed Service Contract Subform Service System reference: HQ-861-804-CPPR

A300) There Was No Possibility to Set Flowfilters on Global Dimensions on the Item Card

Error

The system didn’t allow setting flowfilters on global dimensions on the Item Card. The following error message appeared: Service Invoice Line has no appropriate Key containing Shortcut Dimension 1 Code when trying to set a flowfilter on the Global Dimension 1, and Service Invoice Line has no appropriate Key containing Shortcut Dimension 2 Code when trying to set a flowfilter on the Global Dimension 2. This has been corrected. Now it is possible to set flowfilters on global dimensions on the Item Card.


Table 5902 Service Invoice Line Service System reference: DE-560-980-8NJU

A301) The Invoice After Service Field was not Used when Invoicing Service Contracts

Error

It was possible to invoice a service contract that had a check mark in the Invoice After Service field in the Service Contract Header table and did not have any posted service orders linked to it. This has been corrected. The system does not allow invoicing a service contract if there are no service orders linked to it and there is a check mark in the Invoice After Service field in the Service Contract Header table. If the Invoice After Service field is selected the Prepaid check box on the Service Contract form, Invoice Details tab is automatically disabled.



Codeunit 5940 ServContractManagement Form 6050 Service Contract Form 6053 Service Contract Quote Report 6030 Create Contract Invoices Table 5965 Service Contract Header Service System reference: HQ-198-992-CQQN

A302) Deleting a Service Order Log was Dangerous

Error

Deleting a service order log could make the system delete logs for all service orders. The same problem occurred when deleting a service item log. Also, the Delete Service Order Log and Delete Service Item Log batch jobs were run non-modally. Therefore, the Service Order Log and Service Item Log windows were not always refreshed. This has been corrected.


Form 5920 Service Order Log Form 5989 Service Item Log Report 6002 Delete Service Order Log Report 6010 Delete Service Item Log Service System reference: HQ-759-270-CRF3

A303) A Service Item did not Use Proper Item Translations

Error

If a service item was created as a result of shipping an item with item translations, the content of the Description field on its Service Item Card was copied from the description of the corresponding item. Therefore, the item translations included in the sales shipment were ignored. This has been corrected. Now the content of the description of the service item is copied from the description of the corresponding sales line in the sales shipment. Thus, correct item translations are used.


Codeunit 5920 ServItemManagement Service System reference: DE-30-453-ZHY6

A304) The System Did Not Respond if the Default Service Hours Were Not Set

Error

The system did not respond when creating new service item lines if the default service hours had been not set before. The similar problem occurred when setting up default service hours in a way that they would result in erroneously huge period till the response date (for example, one minute office open hours per week). This has been corrected. If the default service hours were not set, they are interpreted as the 24-hour open service hours. If the period between the working and response dates on a service item line is more than one year, the error message appears.



Table 5901 Service Item Line, Codeunit 5900 ServOrderManagement Service System reference: HQ-832-723-CRTR

A305) Mistakes in the Message when Converting a Service Contract Quote into a Service Contract

Error

After clicking the Make Contract button on the Service Contract Quote form, the confirmation message appeared: Do you want convert the contract quote to a contract?. This text message contained grammar mistakes. This has been corrected. The confirmation message is changed to: Do you want to convert the contract quote into a contract?.


Codeunit 5944 SignServContractDoc Service System reference: HQ-309-745-CRPZ

A306) The Service Quote and Service Order Form Missed the Make Phone Call and New Mail Message Buttons

Error

There were no Make Phone Call and New Mail Message buttons on the General tabs of the Service Order and Service Quote forms. This has been corrected.


Form 5964 Service Quote. Form 5900 Service Order Service System reference: DE-177-737-ZHCG

A307) Deleting a Sales Invoice for a Service Contract Kept its Service Ledger Entries Open

Error

The system refused to post a sales invoice for a service contract if the previous one for it had been deleted manually. The following error message appeared: Old Open service ledger entries have been found for the service contract. The problem occurred because the program didn’t update the corresponding service ledger entries after a sales invoice had been deleted manually. This has been corrected. Now the system does not allow manual deleting a sales invoice created for a service contract. When such an attempt occurs, the system responds with an error message: “You cannot delete invoice <Invoice No.> because one or more service ledger entries exist for this invoice”.


Form 47 Sales Invoice Subform Table 36 Sales Header Service System reference: DE-176-758-LGYY


A308) Captions of Description Label on the Serv. Inv. Line Price Adjmt. Form was Missing

Error

The Description label on the Serv. Inv. Line Price Adjmt. form missing a caption.


Service System reference: DE-699-49-LLJ8

A309) Undoing Shipments Didn’t Delete the Corresponding Service Items

Error

After undoing a shipment the program didn’t delete service items that were created when the shipment occurred. This has been corrected. Now, when undoing a shipment the system checks whether the corresponding posted shipment includes any associated service items. If the system detects at least one service item that meets this condition, the confirmation message appears: “Some shipment lines may have unused service items. Do you want to delete them?”


Codeunit 80 SalesPost Codeunit 363 PostSalesLines-Delete Codeunit 5815 UndoSalesShipment Codeunit 5920 ServItemManagement Table 111 Sales Shipment Line Table 5940 Service Item Service System reference: DK-314-783-HEFR

A310) Comments Were Lost

Error

After manually changing the contents of the Contract No. field on the Service Contract form, the existing comments to it were lost. The same error occurred to service contract quotes, service quotes, service orders, and service items. This has been corrected. Now the system updates comments each time the number of a service contract, service contract quote, service quote, service order, or service item is modified.


Table 5906 Service Comment Line Service System reference: HQ-350-503-CREU

A311) The Item Ledger Entries were not Shown from the Service Item Lines

Error

If a contract line contained a service item created while shipping the corresponding item, pressing the AssistEdit button in the Serial No. field caused the Item Ledger Entry form to


appear. That form was always empty. The problem occurred because of the incorrect filter which was used to show the corresponding item ledger entries for the service item.


Table 5901 Service Item Line Service System reference: DE-526-284-LGM6

A312) The Job Scheduler Management Feature Worked Incorrectly

Error

The job scheduler stopped its running at the end of the same day it had been started. This problem occurred when the job scheduler had to run for more than one day. Besides that, when the job scheduler finished running a job, all remaining jobs were also stopped. This has been corrected.


Form 6094 Job Scheduler Management Service System reference: DE-429-113-EDWN

A313) Some Fields on the Contract Lines Were Not Updated

Error

Changing the contents of the Starting Date, Starting Time, Finishing Date or Finishing Time fields in a service order did not reflect on a service contract it was linked to: the system did not modify the value of the Service Time (Hours) field on the contract lines. The similar errors occurred when changing the contents of the Order Date or Order Time fields in a service order linked to a service contract: the system did not update the value of the Actual Response Time field on the contract lines.


Table 5900 Service Header Service System reference: HQ-508-917-BERP

A314) Service Discounts were Lost when Converting a Service Contract Quote into a Service Contract

Error

Service discounts were not copied to a service contract created from a service contract quote. This problem occurred when the service discounts were previously assigned to a service contract quote. This has been corrected.


Codeunit 5944 SignServContractDoc Service System reference: HQ-223-781-BEXC


A315) The Fields on the Service Order Log Form were Editable

Error

All fields on the Service Order Log form were editable which was inconsistent because only the system could create new logs. This has been corrected. The fields on the Service Order Log form are now non-editable.


Form 5920 Service Order Log Service System reference: HQ-806-545-BF4W

A316) Posting Prepaid Contract Entries Created Wrong Amounts

Error

The amounts on the service ledger entries were not always posted completely from prepaid to income accounts when running the Post Prepaid Contract Entries batch job. This was caused by wrong amounts calculation when the service ledger entries were generated in the process of invoicing a service contract. In particular, the system rounded line amounts before posting them in the corresponding service ledger entries. Then, when summed up, the amounts in the service ledger entries could be not equal to the amounts summed up and then rounded in the corresponding invoices. This has been corrected. The system calculates the amounts posted in service ledger entries in the same way as in sales invoices. Besides rounding, the problem occurred with invoicing the contract lines that were to expire in the current invoice period. The amounts posted in the service ledger entries for the contract lines that were to expire in the period for which the service contract was to be invoiced, were calculated incorrectly. Such contract lines were invoiced not for the periods until their expiration dates, but for the whole invoice period.


Codeunit 5940 ServContractManagement Service System reference: DE-297-133-MF5J

A317) Items Were Not Returned to Stock after Posting a Sales Credit Memo

Error

When a credit memo was posted, the corresponding items were not returned back to the Inventory. This problem occurred only in case of credit memos created manually or using the Copt Document function.


Codeunit 80 Sales-Post Service System reference: FR-343-714-RJ7V


A318) Deleting Contract Lines on a Signed Service Contract

Error

When a contract line was deleted manually from a signed service contract, the system did not inform if the line could be credited.


Table 5964 Service Contract Line Service System reference: HQ-825-212-RJWB

A319) Failure in Posting a Service Order Containing a Renamed Service Item

Error

After a service item was renamed directly on service invoice lines in a sales order, the system disallowed to post it. The problem occurred because the system could not rename a service item directly on service invoice lines. This has been corrected. The Service Invoice Line table now has a relation to the Service Item table. Therefore, renaming a service item does not cause any problems when posting a sales invoice containing it.


Table 5902 Service Invoice Line Service System reference: DK-488-588-2JQW

A320) The Next Planned Service Date Field is Updated Incorrectly

Error

When a new contract line was added in the service contract or contract quote, the program automatically copied the value of the Starting Date field of the contract quote into the Next Planned Service Date field on the contract line. This error occurred even if the First Planned Service Date field of the service contract or contract quote was not empty. If the value in the Next Planned Service Date field was modified before converting the contract quote into a service contract, its contract lines received the same service quote’s starting date in the Next Planned Service Date field. This has been corrected. The program copies the value of the Next Planned Service Date field from the First Planned Service Date field when a new contract line is added or the contract quote is converted in the service contract.


Table 5964 Service Contract Line Table 5965 Service Contract Header Service System reference: HQ-580-313-YC7T

A321) Sales/Purchase Order Archive - Missing Fields

Error


[The missing fields: Allow Line Disc. and Customer Disc. GroupAllow Line Disc. were added to table

5107 Sales Header Archive and table 5108 Sales Line Archive. The new fields' numbers and properties

are the same as the corresponding fields' numbers and properties in the Sales Header and Sales Line

tables.


Table 5107 Sales Header Archive Table 5108 Sales Line Archive

Service System reference: GB-822-7-DDZH]

2.7 Purchases & Payables

Errors fixed

A322) Combine shipment uses application language instead of Customer's language

Error

The reports now sets the language based on the customer's language set on the sales order document header that is being combined


Report 295 Combine Shipments Report 6653 Combine Return Receipts Service System reference: CH-443-101-KJ2G

A323) EntringEntering Unit Cost (LCY) in Purchase Order (Purchase Line)

Error

It was possible to manually enter a Unit Cost (LCY) in a purchase line, but when you posted the line, the Unit cost was recalculated to another value. The Indirect Cost % was not updated when you changed the Unit Cost (LCY) on the line.


Table 39 Purchase Line Service System reference: DE-503-579-LMLH


A324) Entering Unit Cost (LCY) in Purchase Order (Purchase Line)

Error

It was possible to manually enter a Unit Cost (LCY) in a purchase line, but when you posted the line, the Unit cost was recalculated to another value. The Indirect Cost % was not updated when you changed the Unit Cost (LCY) on the line.


Table 39 Purchase Line Service System reference: DE-503-579-LMLH

A325) Carry Out Action Message for Special Sales Orders

Error

Carry out action message for special sales orders provided more than one purchase order for the same customer and the same vendor.


CodeUnit 333 Req. Wksh.-Make Order Service System reference: BE-412-823-XH5A

A326) Drop Shipment Caused Quantity Differences at Shipment

Error

If you used Requisition Worksheet to create a purchase order for a Drop Shipment Sales order, it was possible to end up with different Unit of Measure Codes on the Sales Order and the purchase Order. This has been corrected, so that the Purchase Order will always have the same Unit of Measure code as the Sales order.


Report 698 Get Sales Orders Codeunit 333 Req. Wksh.-Make Order Sevice System reference: DE-53-301-RBGV

A327) Table Relation to Production Order Table Missing from Various Tables

Error

Table relation to Production Order table was missing from various tables.


Table 121 (Purch. Rcpt. Line) Table 123 (Purch. Inv. Line) Table 5110 (Purchase Line Archive)


Service System reference: HQ-449-558-9J2V

A328) Manual Number Series on Credit Memos

Error

It was not possible to post purchase and sales credit memos with manually entered document numbers, even though the Posted Credit Memo Nos. field was blank on the Numbering tab of the Setup windows, and you had placed a check mark in the Manual Nos. field for the credit memo codes in the No. Series window.


Codeunit 80 Sales-Post Codeunit 90 Purch.-Post Service System reference: ES-471-173-NMEL, DK-49-787-ZEN9

A329) Get Receipt Lines Could Pick Up Documents with a Different Currency Code

Error

It was possible to use Get Receipt Lines to pick up a Receipt that was made under a different Currency Code.


Service System reference: GB-273-497-PCE5"

A330) Table Relations from Purchase Lines

The table relations from the purchase and requisition lines to production orders were not defined correctly.


Table 39 Purchase Line Table 246 Requsition Line Codeunit 5403 AddOnIntegrManagement Service System reference: HQ-609-61-CQGH

A331) Dates on Purchase Header and Purchase Line

Error

The dates on the purchase lines are not updated correctly, when the Promised Receipt date was modified.


Table 39 Purchase Line Service System reference: DE-926-14-YEL9


A332) Item Tracking and Item Charge for Purchase Orders

Error

Posting of Item Charge per order failed if it was assigned to the order lines containing item tracking information.


Codeunit 22 Item Jnl.-Post Line Codeunit 80 Sales-Post Codeunit 90 Purch.-Post" Service System reference: DE-953-746-SKHC

A333) Texts in Reservations

Some text in the reservation form was formatted incorrectly.


Codeunit 99000831 Reservation Engine Mgt. Service System reference: DE-394-284-HJTK

A334) Drill-Down to Tables

Error

Table 123 and 125 did not define the correct form as the drill-down from.


Table 123 Purch. Inv. Line Table 125 Purch. Cr. Memo Line Service System reference: HQ-275-625-CPCS

A335) Partial Receipt of Items with Item Tracking

Error

When running dynamic order tracking and only define the item tracking quantity partly, it leads to a situation where the order line carries reservation entries with as well as without item tracking. Due to the sorting that was used when transferring reservation entries during posting, the "empty" entries were transferred firstly, leading to the error. A special set of procedures have been added for sorting the entries to make sure that the sorting will make the right priorities.


Codeunit 99000831 Reservation Engine Mgt. Codeunit 99000832 Sales Line-Reserve Codeunit 99000834 Purch. Line-Reserve


Codeunit 99000836 Transfer Line-Reserve Codeunit 99000837 Prod. Order Line-Reserve Codeunit 99000838 Prod. Order Comp.-Reserve Codeunit 99000842 Service Invoice Line-Reserve Codeunit 99000843 BOM Jnl. Line-Reserve Service System reference: DK-281-637-ZCE6

A336) Menu Changes in Requisition Worksheet

Error

The menus on the requisition worksheet have been renamed and rearranged to comply with the rest of the application.


Form 291 Requisition Worksheet Form 296 Recurring Req. Worksheet Service System reference: HQ-70-183-CP7R

A337) Production Orders Invoicing With Item Tracking

Error

When invoicing using Get Receipt (or Shipment) Lines for lines carrying item tracking the system would fail during posting if the quantity was lowered.


Codeunit 99000832 Sales Line-Reserve Codeunit 99000834 Purch. Line-Reserve Service System reference: GB-816-818-ZDCS

A338) Vendor Item No. on Purchase Line Was Not Correctly Dated with Change of Responsibility Center

Error

Vendor Item No. on purchase line was incorrectly dated with change of responsibility center. The item vendor variable needed to be initialized in TAB39 in the UpdateDirectCost trigger.


Table 39 Purchase Line Service System reference: NZ-960-443-MUB4

A339) Error When Creating Transfer Orders Form Req. Worksheet

Error

The Line No for the transfer line was not set correctly.



Codeunit 99000813 Carry Out Action Service System reference: HQ-935-434-PDP9

A340) The Quantity Received on the Blanket Order is not updated when a related Return Order / Credit Memo is posted.

Error

The Quantity Received on the Blanket Order is now updated appropriately when a related Return Order/ Credit Memo is posted.


Codeunit 90 Purch.-Post Service System reference: US-668-325-2QNH

A341) Item Charge Assignment on Purchase Orders Created from Subcontracting Worksheet

Error

"On a Purchase Order, it was possible to assign an item charge to a subcontracted Purchase Order which was created from the subcontacting worksheet. This resulted in a ""division by zero"" error when trying to post this Purchase Order. This has been corrected."


Codeunit 5805 Item Charge Assgnt. (Purch.) Service System reference: SE-28-49-ZCG8

A342) No Update of No. Series When Posting Payment Journal with an Empty Line

Error

When journal lines included an empty line, the document no. was not updated.


Codeunit 13 Gen. Jnl.-Post Batch Service System reference: SE-984-385-FK9A

A343) Pay-to Vendor No. Field Was Not Filled in by the Program

Error

If you copied a posted purchase invoice to a purchase credit memo and then changed the Quantity field you got the following message: "Vendor No. does not exist". This was because the program did not fill in the Pay-to Vendor No. field on the line of the credit memo.



Codeunit 6620 Copy Document Mgt. Service System reference: BE-580-142-DDC2

A344) Purchase Lines Could Not Be Changed After Using Copy Document Mgt. Report

Error

If you used the Copy Document Mgt. report (6620) to create documents, the Pay-to Vendor No. field was not copied. This resulted in an error message if you tried to change the purchase lines.


Codeunit 6620 Copy Document Mgt. Service System reference: CH-303-637-EJY3

A345) Error Using Get Receipt Function on a Purchase Invoice

Error

If you made purchase lines on an invoice using the function Get Receipt and the selected lines had another Pay-to Vendor No. than the invoice, you got the following message: “Get Receipt Lines cannot close because the system is currently busy."


Table 121 Purch. Rcpt. Line Service System reference: US-278-23-QRSU

A346) Variant Code Was Not Included in Job Ledger Entries After Posting

Error

If you posted a purchase invoice with a variant code, the job ledger entry had no variant code.


Codeunit 80 Sales-Post Codeunit 90 Purch.-Post Service System reference: DE-542-946-YKE4

A347) Error in Vendor - Detail Trial Balance Report

Error

The Vendor - Detail Trial Balance report (304) calculated the exchange rate adjustment entries incorrectly if the batch job was run several times.



Report 104 Customer - Detail Trial Bal. Report 304 Vendor - Detail Trial Balance Service System reference: SG-62-261-FBD7

A348) Incorrect Amount in Vendor Balance Due

Error

The Calcformula of the Vendor Balance Due field looked up to an incorrect field. The source field should be Amount instead of Amount (LCY). The Vendor Balance Due field and the Vendor Balance Due (LCY) field showed the same amount.


Table 23 Vendor Service System reference: CH-581-595-9GY3

A349) The Summarize per Dimension Field in Suggest Vendor Payment Report Was Incorrect

Error

The “Summarize per Dimension” field in the Suggest Vendor Payment report (393) was incorrect. It has been changed to “By Dimensions” and is now indented below the Summarize per Vendor field.


Report 393 Suggest Vendor Payments Internal Workbase reference: EE84C8EDE4AC86DDC1256B3E0043B040

A350) Incorrect Message in Suggest Vendor Payment Batch Job

Error

If you ran the Suggest Vendor Payment batch job for a vendor with the same vendor number as the pay-to vendor number you got the following error message: "The Vendor xxx has a pay-to Vendor No. xxx. Do you still want to use Vendor xxx in this journal line?"


Table 81 Gen. Journal Line Service System reference: DE-463-284-BFTS


A351) Void Check in Payment Journal where Account Type Was G/L Account

Error

When financially voiding a check, the program handled the balancing of the G/L Accounts incorrectly when VAT was involved. The incorrect base amount was used to reverse the initial entry.


Codeunit 367 CheckManagement Service System reference: SG-506-701-AE6G

A352) Incorrect VAT Difference Posted in Purchase Orders

Error

If there was a partial sales or purchase invoice and the VAT amount was changed on that invoice before releasing the order, the VAT difference was calculated/distributed incorrectly when you released the order.


Table 37 Sales Line Table 39 Purchase Line Service System reference: HQ-186-850-LALG

A353) Mandatory Dimensions Were Ignored If No Other Dimensions Were Specified

Error

If you created a purchase order without specifying any dimension value code, the program would still let you receive the order even if you had set a certain dimension code to be mandatory. This was because Navision did not check the Dimension Setup table if no document dimensions were specified.


Codeunit 80 Sales-Post Codeunit 90 Purch.-Post Service System reference: GB-600-234-XFCK

A354) Sales Tax on Purchase Order and Jobs

Error

When you created a purchase order that required sales tax and linked it to a job, only the amount (quantity x price) was charged to the job, the sales tax was not included.


Codeunit 90 Purch.-Post Internal Workbase reference: 26838FD7AE387C2C412567F200492EF9


A355) Print Check, Description of the Applied Invoices

Error

When you printed a check that was a payment of two invoices, one in local currency and one in a foreign currency, the printed check had an extra line and the net amount was in different currencies. This has been corrected and two new columns have been added to the report: Currency Code and Net Amount.


Report 1401Check Internal Workbase reference: BBF3F7112F67747BC125673C002DA44D

A356) Incorrect Field Layout on Batch Jobs Containing Dimension Fields

Error

The By Dimension field in report (393) had an incorrect field layout. The field was grey and the Edit button was first visible after you had clicked the field. The Edit button should be visible to the user without having to click the field.


Report 393 Suggest Vendor Payments Internal Workbase reference: 06580D09CA1C98C0C1256AD90034FCA9

A357) Purchase VAT Account and Payment Discount

Error

If you posted an invoice that had a VAT Bus. Posting Group/ VAT Prod. Posting Group combination that gave 0 in VAT% and you invoiced the lines with different dimensions, and then applied a payment with a payment discount to the invoice. the program would still post the entry to the purchase VAT account when you posted the payment.


Codeunit 12 Gen. Jnl.-Post Lineagement Service System reference: DE-987-110-6F4Q

A358) Creating Purchase Orders from a Requisition Worksheet Could Be Very Slow

Error

Creating purchase orders from a requisition worksheet was very slow if you had a large number of lines including dimensions.


Codeunit 333 Req. Wksh.-Make Order Service System reference: CH-123-55-7B77


A359) Purchasing Code error in Item Ledger Entries

"In COD5702, the ""GetSpecialOrders"" trigger, an assigment of the purchasing code from the corresponding sales line to the purchase line has been added in order for the item ledger entry to have the right purchasing code for the purchase."


Codeunit 5702 Dist. Integration Service System reference: NO-845-596-9EZU

Issues

A360) Standard Sales Codes

Issue

This feature allows the user to specify Standard Sales Codes. Each Standard Sales Code specifies often used sales lines and can include default G/L accounts, dimensions, items, quantities, and item charges. The user then attaches one or more Standard Sales Codes to a customer. When creating orders for customers with Standard Sales Codes, the user uses a function to have the sales lines filled in automatically. The feature can be used if a customer always orders the same bundle of items or if the customer is always charged the same fee (which is posted to a specific revenue account). This feature minimizes data entry and minimizes incorrect postings to G/L accounts. The same functionality is also implemented for vendors.

In response to this issue, changes have been implemented

Table 170 Standard Sales Code Table 171 Standard Sales Line Table 172 Standard Customer Sales Code Table 173 Standard Purchase Code Table 174 Standard Purchase Line Table 175 Standard Vendor Purchase Code Table 357 Document Dimension Form 21 Customer Card Form 22 Customer List Form 26 Vendor Card Form 27 Vendor List Form 41 Sales Quote Form 42 Sales Order Form 43 Sales Invoice Form 44 Sales Credit Memo Form 49 Purchase Quote Form 50 Purchase Order Form 51 Purchase Invoice Form 52 Purchase Credit Memo Form 170 Standard Sales Code Card Form 171 Standard Sales Code Subform Form 172 Standard Sales Codes Form 173 Standard Customer Sales Codes Form 175 Standard Purchase Code Card Form 176 Standard Purchase Code Subform


Form 177 Standard Purchase Code Form 178 Standard Vendor Purchase Codes Form 333 Sales & Receivables Menu Form 334 Purchases & Payables Menu Report 83 Change Global Dimensions Service System reference: HQ-579-839-CPXQ

A361) Description 2 in Purchase Line Got Deleted

Issue

In COD5702 both EnterSalesItemCrossRef and EnterPurchaseItemCrossRef triggers have been altered to correctly show the description2 for an item on both sales and purchase lines.

In response to this issue, changes have been implemented.

Codeunit 5702 Dist. Integration Service System reference: DK-687-393-WEG6

2.8 Inventory

Errors fixed

A362) Unit amount on test report for item journal

A363) Profit Calculation on Report 113 Could Be Incorrect

Error

The fields Unit Cost and Cost Amount have been added on the test report 702If a non-inventoriable cost was added to a shipment, then this cost was not included in the profit calculation in report 113 Customer/Item Sales.


Report 702 Inventory Posting - Test Service System reference: NO-6-835-QG75


A364) Item charges for Transfer Receipt Lines with IT-Information caused Incorrect Costing

Error

In COD90 the splitting of item charges according to it-information was missing, when item charges were posted for transfer receipt lines. This has been corrected. Now item charges are split according to item entry relation, when item tracking is involved.


COD90 Service System reference: US-764-994-JNQ3

A365) ERROR deleting a line with item created from a nonstock item.

Error

The purchase line is now checked for at least one line using the non-stock item on the procedure NonStockSalesDel in codeunit 5703.


Codeunit 5703 Nonstock Item Management Service System reference: DE-214-680-7KY5

A366) Minor errors on Form 5731 "Product Groups"

Error

The Item Category Code has been added onto the form and also been setup as the caption for the form Product Groups.


Form 5731 Product Groups Service System reference: DE-940-908-AT7W

A367) Product Group Code not initialized on change of Item Category Code in Item table

Error

The Product Group Code on the Item table is now blanked out when the Item Category Code is changed


Table 27 Item Service System reference: DE-947-483-BJE8


A368) Item Tracking With Unit of Measures

Error

If using a UOM smaller than 1 you would sometimes run into rounding differences which would eventually block the invoicing of the sales or purchase order. The error was due to an internal remaining quantity not being zero. The problem is solved with a patch in the existing rounding adjustment procedure.


Codeunit 6500 Item Tracking Management Service System reference: US-621-874-3MLX

A369) Apply-to and Specific Item Tracking

Error

Apply-to entry could overrule specific item tracking. The posting routine will check that the item tracking on the applied item ledger entry match what is defined in the item tracking for the posted line.


Cod 22 Item Jnl.-Post Line Service System reference: ES-499-256-4ECX

A370) Item Tracking Lines Not Deleted

Error

Item Tracking lines were left over in the Reservation table if the Entry Type field was changed on an Item Journal line.


Codeunit 99000835 Item Jnl. Line-Reserve Service System reference: DK-4-426-XH4H

A371) Profit calculation on report 113 could be incorrect

Error

If a noninventoriable cost was added to a shipment, then this cost was not included in the profit calculation in report 113 Customer/Item Sales Service System reference: AT-891-116-RE6H


A372) Profit Calculation on Report 113 Could Be Incorrect.

Error

If a non-inventoriable cost was added to a shipment, then this costs was not included in the profit calculation in report 113 Customer/Item Sales.


Report 113 Customer/Item Sales Service System reference: AT-891-116-RE6H

A373) Calculation of Indirect Cost % on Item Journal with Entry Type Negative Adjustment or Sale

Error

The calculation of unit cost in Item journal Line is changed because the Indirect cost and overhead rate was added twice to the cost price when posting entry type negative adjustment or sales line in the item journal. This cost was updating on the item form after posting.


Table 83 Purchase Header Service System reference: CH-896-103-LEMC

A374) Average Cost on Item Card Could Always Display 0

Error

If a company stopped using Additional Reporting Currency, then in some cases, the AverageCost on the item card would always show 0.


Codeunit 5804 ItemCostManagement Service System reference: DE-832-242-ZKDD

A375) Calculation of Item (Variant) Availablity Not Correct

Error

"Planning Release (Qty.)" and "Planning Receipt (Qty.)" should be removed from the calculations in Form 5415.


Form 5415 Item Avail. by Variant Lines Service System reference: NL-529-92-RK86


A376) Problems When Using Location Mandatory Together with Adjust Cost - Item Entries

Error

If Location Mandatory was set to Yes in Inventory Setup, the Adjust Cost - Item Entries batch job would fail sometimes with the error saying that New Location Code must be specified.


Codeunit 21 Item Jnl.-Check Line Service System reference: DK-68-882-KEH7

A377) Missing Permissions for Table 6507 and 6508

Error

Indirect permission for table 6507 and 6508 were missing from various codeunits.


Codeunit 5704 TransferOrder-Post Shipment Codeunit 5705 TransferOrder-Post Receipt Codeunit 5813 Undo Purchase Receipt Line Codeunit 5814 Undo Return Shipment Line Codeunit 5815 Undo Sales Shipment Line Codeunit 5816 Undo Return Receipt Line Codeunit 5907 ServInvLine-Post Codeunit 5908 ServOrder-Post Codeunit 6500 Item Tracking Management Service System reference: DK-95-937-SBJ2

A378) Automatic Extra Texts on Nonstocking Items

When creating an item from a non-stock item, the "Automatic Ext. Texts" field was set to Yes by default. This was inconsistent with the default value in "Automatic Ext. Texts" for items that are created manually, i.e. on the Item Card.


Codeunit 5703 Nonstock Item Management Service System reference: SE-697-814-YPHT

A379) Permission Error When Posting Item Journal for Specific User Role

Error

A User with Roles "ALL", "INVT-ITEM JNL", "INVT-ITEM JNL, POST" couldn't post an Item Journal purchase line on an average costed Item.


Report 798 Date Compress Item Ledger


Codeunit 22 Item Jnl.-Post Line Codeunit 361 MoveEntries Codeunit 5810 Change Average Cost Calc. Type Codeunit 5895 Inventory Adjustment Codeunit 5899 Calc. Inventory Value-Check Service System reference: HQ-557-0-VHEC

A380) Shortcut dimension codes cannot be changed on new transfer lines

Error

An error message was displayed when users tried to set the Shortcut Dimension 1 Code or Shortcut Dimension 2 Code on transfer lines that were not yet inserted.


Table 5741 Transfer Line Service System reference: NL-709-866-XDBS

A381) Purchase orders with job relation distort the planning result

Error

Job-related Purchase lines were taken into account as possible supply in inventory profile offsetting.


Codeunit 99000854 Service System reference: DE-516-643-8D8C

A382) Supply Lower Than Reorder Point

If the supply was less than the reorder point the planning calculations would not suggest a new supply.


Codeunit 99000854 Inventory Profile Offsetting Service System reference: GB-174-405-WKPE

A383) Planning with Sales Blanket Orders

Error

The planning calculations ignored quantities on the sales blanket orders.


Codeunit 99000854 Inventory Profile Offsetting Service System reference: DE-94-120-YG4U


A384) Planning error with Reorder Point and Safety Stock

Error

If the Order relation is of the type safety stock, the planning will not suggest to reorder the reorder point but the qty needed.


Codeunit 99000854 Inventory Profile Offsetting Service System reference: HQ-123-245-YK8R

A385) Reservations on Journal Lines

Error

When renaming of records in Item Journal Line or BOM Journal Line carrying reservation entries (tracking, reservations, item tracking) the reservation entries would be lost as they were not renamed accordingly. Standard procedures have been added in the reservation system to handle renaming on all records being able to carry reservation entries, in order to be future-prepared. Renaming statements have been added to Item Journal Line and BOM Journal Line to handle the specific issue.


Table 82 Item Journal Template Table 83 Item Journal Line Table 88 BOM Journal Template Table 89 BOM Journal Line Table 337 Reservation Entry Codeunit 99000831 Reservation Engine Mgt. Codeunit 99000832 Sales Line-Reserve Codeunit 99000833 Req. Line-Reserve Codeunit 99000834 Purch. Line-Reserve Codeunit 99000835 Item Jnl. Line-Reserve Codeunit 99000836 Transfer Line-Reserve Codeunit 99000837 Prod. Order Line-Reserve Codeunit 99000838 Prod. Order Comp.-Reserve Codeunit 99000840 Plng. Component-Reserve Codeunit 99000842 Service Invoice Line-Reserve Codeunit 99000843 BOM Jnl. Line-Reserve Service System reference: BE-709-753-8B4T

A386) Item Journal With Item Tracking

Error

If the number of item tracking lines that was posted exceeded the number of item ledger entries in the database prior to posting, the insertion of the tempitemtracking record would fail and give a run-time error. Insertion has been changed so that the conflicting record will be moved to a free space in the row of entries.


Codeunit 22 Item Jnl.-Post Line


Service System reference: ID-24-121-L52T

A387) Blocked Field on Serial / Lot Number Information Card

Error

The setting of ""blocked"" on SN/Lot Info card was not always checked. The check was only done if SN/Lot info was setup as required. The check has been changed to activate in any case. The checking code has been placed in a separate local procedure CheckItemTrackingInfo in Codeunit 22.


Codeunit 22 Item Jnl.-Post Line Service System reference: BE-424-949-RKMR

A388) Description in Inventory Purchase Orders Report

Error

The report used the description from the last purchase line. In the future, the item description will be used.


Report 709 Inventory Purchase Orders Service System reference: DE-662-269-UACS

A389) Check for Existing Serial Numbers

Error

No check of whether Serial No. already existed was made when posting reclassification journal. The existing check in cod 22 procedure "InsertItemLedgEntry" has been expanded with statements checking "New Serial No." when the journal line is of type "Transfer".


Codeunit 22 Item Jnl.-Post Line Service System reference: ES-860-538-YN3N

A390) Order Tracking on Posted Receipts / Shipments With Item Tracking

Error

Order tracking on the posted receipt/shipment did not work if item tracking had been used; a TESTFIELD on Item Rcpt. Entry No/Item Shpt. Entry No would give an error. Special handling has been added to take care of this specific situation.



Form 131 Posted Sales Shpt. Subform Form 137 Posted Purchase Rcpt. Subform Form 99000822 Order Tracking Codeunit 99000778 OrderTrackingManagement Service System reference: US-211-901-7R32

A391) Check for Item Tracking on Order Lines

Error

When changing item no. on an order line, checks for item tracking were only done if an item tracking code was defined for the new item. Also, check was only done if the current item tracking code was set up as "specific".


Codeunit 99000832 Sales Line-Reserve Codeunit 99000833 Req. Line-Reserve Codeunit 99000834 Purch. Line-Reserve Codeunit 99000835 Item Jnl. Line-Reserve Codeunit 99000836 Transfer Line-Reserve Codeunit 99000837 Prod. Order Line-Reserve Codeunit 99000838 Prod. Order Comp.-Reserve Codeunit 99000840 Plng. Component-Reserve Codeunit 99000842 Service Invoice Line-Reserve Codeunit 99000843 BOM Jnl. Line-Reserve Codeunit 99000845 Reservation Management Service System reference: HQ-372-720-SEUF

A392) Reservations / Order Traking

Error

Upgrade of Purchase and Sales Orders With Item Tracking Purchase and Sales Orders with item tracking received/shipped in 2.60 (2.60 MFG) could not be invoiced in 3.60 after the upgrade.


Codeunit 104099 Upgrade 3.60 Step 3 Repair IT - created Service System reference: HQ-888-501-BFXK

A393) Lookup of Item Tracking Entries from Item List Form

Error

It was not possible to lookup Item Tracking Entries from the Item List form.


Form 31 Item List


Service System reference: GB-524-371-3M4N

A394) Inactive Menu Item on Applied Item Entries Form

Error

The menu item Item Tracking Entries was left over on the Applied Item Entries form.


Form 5804 Applied Item Entries Service System reference: DE-307-499-3M2R

A395) Decimal Places in Item Tracking Form

Error

In the Item Tracking Lines form the field ""Undefined"" could not display more than 2 decimals. Decimal places in "Undefined" column changed to 2:5.


Form 6510 Item Tracking Lines Service System reference: DE-454-714-BNZ4

A396) Orphan Surplus Record

Error

When Reservation and Item Tracking was used in combination it lead to leftover surplus records.


Codeunit 99000831 Reservation Engine Mgt. Service System reference: DE-919-565-KJQL

A397) Upgrade of Value Entries

Error

Value Entries created for items with item tracking during the upgrade from 3.01 and 3.10 to 3.60 had wrong rounding precision in unit amount and amount fields.


Codeunit 104049 Item Trkg. Upgrade Step 2 Service System reference: DK-110-352-8J7J


A398) Item Tracking Comments

Error

If you attempted to insert item tracking comments before the item tracking information card had been inserted in the database you would get an error.


Form 6504 Serial No. Information Card Form 6505 Lot No. Information Card Service System reference: HQ-576-393-PFVX

A399) Lot Application Method Field on The Item Tracking Code Table

Error

The field "Lot Application Method" on Table 6502 Item Tracking Code was not used anywhere. The field is now deleted.


Table 6502 Item Tracking Code Form 6512 Item Tracking Code Card Service System reference: US-782-776-EUUF

A400) Use of Lower Case

Error

Use of LOWERCASE caused problems in some languages.


Codeunit 99000845 Reservation Management Service System reference: DE-409-298-QQCR


Error

Apply-to entry could overrule specific item tracking. The posting routine will check that the item tracking on the applied item ledger entry match what is defined in the item tracking for the posted line.


Cod 22 Item Jnl.-Post Line Service System reference: ES-499-256-4ECX


A402) Net Change Field at the Item Table

Error

The formatting and decimal properties were not set correctly for this field.


Table 27 Item Service System reference: HQ-445-115-CPVT

A403) Item Tracking Entries for Invoices

Error

Item Tracking Entries for invoices got lost during the upgrade from 3.01 and 3.10 to 3.60 in case of the invoices combined for several receipts/shipments.


Codeunit 104050 Item Trkg. Upgrade Step 1 Codeunit 104098 Repair IT ( 3.01,3.10 -> 3.60) Service System reference: DK-430-320-8LM8

A404) Item Tracking on Item Journal Lines

Error

The location code could be changed in the item journal line although item tracking had been defined.This was due to a too narrow filter when searching for underlying reservation entries in procedure VerifyChange. The filter has been redefined.


Codeunit 99000835 Item Jnl. Line-Reserve Service System reference: DE-844-863-4EFM

A405) Reservations With Unit of Measure

Error

Reservations against purchase orders with Unit of Measure <> 1 gave wrong quantities in reservation form. This was due to the updating of ""Total Reserved Quantity"" being wrongly based on the quantity in units of measure.


Codeunit 99000845 Reservation Management Service System reference: DE-833-744-CF5H


A406) Stockkeeping Units and Item Tracking Entries

Error

Item Tracking Entries could not be open from the Stockkeeping Unit Card


Form 21 Customer Card Form 26 Vendor Card Form 30 Item Card Form 5700 Stockkeeping Unit Card Form 6504 Serial No. Information Card Form 6505 Lot No. Information Card Codeunit 6500 Item Tracking Management Service System reference: ES-687-927-9CYT

A407) Double Reservations

Error

Due to lack of locking it was possible to reserve the same quantity more than once. Locking statements have been added in the central procedures in the reservation system. The procedure Lock has been added in Tab337. Call of this procedure has been added in the central procedures in the reservation system.


Table 337 Reservation Entry Codeunit 99000832 Sales Line-Reserve Codeunit 99000833 Req. Line-Reserve Codeunit 99000834 Purch. Line-Reserve Codeunit 99000835 Item Jnl. Line-Reserve Codeunit 99000836 Transfer Line-Reserve Codeunit 99000837 Prod. Order Line-Reserve Codeunit 99000838 Prod. Order Comp.-Reserve Codeunit 99000840 Plng. Component-Reserve Codeunit 99000842 Service Invoice Line-Reserve Codeunit 99000843 BOM Jnl. Line-Reserve Codeunit 99000845 Reservation Management" Service System reference: INT-298-503-R8UX

A408) Item Tracking on Transfer Orders

Error

Item tracking entries in Transfer orders were not correct for the Average costing method. Some Item Tracking Entries were missing when shipping Transfer Lines for the items with Costing Method = Average if they were originated from different incoming Item Ledger Entries.


Codeunit 22 Item Jnl.-Post Line


Service System reference: IN-844-798-CGM9

A409) Lookup from Order Tracking Form

Error

When looking up documents from the order tracking form, sometimes the wrong documents were shown.


Form 99000822 Order Tracking Service System reference: HQ-920-73-CQRQ

A410) Available-to-Promise Calculations

Error

The Available-to-Promise calculations sometimes failed because of incorrect use of filters.


Codeunit 5790 Availabe to Promise Report 705 Inventory Availability Report 707 Inventory - Availability Plan" Service System reference: NL-866-473-TJD3

A411) Deletions of Item Tracking Lines

Error

The Item Tracking Line was not updated correctly when it was deleted and created again. A run-time error occured when closing the Item Tracking form if an item tracking line has been deleted and created again.


Form 6510 Item Tracking Lines Service System reference: DE-110-470-QQQ9

A412) Reservations With Different Unit of Mesaures

Error

When reservations with different units of measure were used, this could result in rounding errors during post of purchases.


Codeunit 90 Purch.-Post Service System reference: HQ-179-946-CQRE


A413) Missing Expiration Date During Reclassifications

Error

No warning was displayed when the expiration date was missing during reclassification.The reason was that the journal line became negative and checks were only made for posting of supply.The check has been expanded to react on transfer regardless on whether it is supply or demand.


Codeunit 22 Item Jnl.-Post Line Serivice System reference: DK-169-131-PD74

A414) Item Availability in BOM Journal

Error

The Check Availability form was shown two times, when items in the BOM Journal were not on stock.


Table 89 BOM Journal Line Service System reference: HQ-297-4-CPN3

A415) Order Tracking from Sales Order Planning Form

Error

It was not possible to open the order tracking form from the sales order plannng form more than once.


Form 99000833 Check Prod. Order Status Service System reference: DE-883-163-UCKS

A416) Change Quantity to Invoice on Partial Posted Orders

Error

It was not possible to change the quantity to invoice on the item tracking lines, when the order was partially posted.


Form 6510 Item Tracking Lines Service System reference: HQ-871-265-CQLC


A417) Item Tracking on Partially Posted Production Orders

Error

Item Tracking on partially posted production orders showed the wrong quantities.


Form 6510 Item Tracking Lines Service System reference: HQ-712-681-CRCY

A418) Availability Forms Included Drop Shipments

Error

On the Item Availability forms, Quantity on Sales Order included drop shipments.


Form 157 Item Availability by Periods Form 492 Item Availability by Location Form 5414 Item Availability by Variant" Service System reference: CH-973-22-5KA7

A419) Upgrade of Lot Numbers from Navision Financials 2.60

Error

The upgrade from Navision Financials 2.60 or Navision Manufacturing 2.60 could fail if the same lot number was used more than once.


Codeunit 104090 Upgrade 3.60 Step 1 ItemTrkg Service System reference: HQ-579-978-FLBT

A420) Assign Lot No. Batch Job

Error

The function "Assign Lot No." did not work for quantities with decimal places In Form 6510 procedures AssignSerialNo, AssignLotNo and CreateCustomizedSN handling of integer-decimal conversion has been added, introducing an extra variable.


Form 6510 Item Tracking Lines Service System reference: DE-908-363-JJB2


A421) Serial/Lot No. Filters on Item Table

Error

“Lot No." and "Serial No." filter fields were not used in the quantity flowfields calculations in the Item table. The filters are now used in the calculations.


Table 27 Item Service System reference: DE-704-342-8MVQ

A422) Location on Sales and Purchase Orders

Error

Mandatory location was not checked when sales and purchase orders were released and when activating order promising. These checks are now added.


Codeunit 414 Release Sales Document Codeunit 415 Release Purchase Document Service System reference: SE-794-894-2FUF

A423) Variants on Components In BOM Journal

Error

Even though a variant code was defined for a component in the BOM journal, the variant code was not transfered to the item ledger entries during posting


Table 37 Sales Line Table 89 BOM Journal Line Codeunit 32 BOM Jnl.-Post Line Service System reference: HQ-435-340-CPGD

A424) Item Tracking Summary Form

Error

The Item Tracking Summary form was not designed according to the GUI Style Guide All columns with quantities have been set to width 1650. The form has been made non-editable.


Form 6500 Item Tracking Summary Service System reference: DE-507-340-PDLV


A425) Transfer Receipts with Item Tracking and Item Charge

Error

Item Charge assigned to Transfer Receipts with Item Tracking produced wrong Value Entries.


Codeunit 90 Purch.-Post Service System reference: DE-444-73-PDZ6

A426) Split of Item Ledger Entries During Upgrade

Error

Item Ledger Entries created during the upgrade from 3.01 and 3.10 have a check-mark in the Open field, even though they are closed.


Codeunit 104049 Item Trkg. Upgrade Step 2 Service System reference: HQ-814-621-ZEVL

A427) Upgrade of Item Tracking Entries

Error

In 3.01 and 3.10 Item Tracking Entries for the items with non-specific item tracking had wrong values in the "Remaining Quantity" and "Invoiced Quantity" fields. These wrong values got transferred into the Item Ledger Entries created during the upgrade from 3.01 to 3.60. The same problem caused a run-time error in the upgrade from 3.10 to 3.60.


Codeunit 104049 Item Trkg. Upgrade Step 2 Service System reference: DK-993-858-PDCF

A428) Order Tracking from Planning Lines

Error

From a planning line, it was not possible to lookup a demand from a related planning component.


Codeunit 99000845 Reservation Management Service System reference: HQ-52-938-CQRU


A429) Refresh of Simulated Production Order

Error

When a simulated production order with source type "Sales Header" was refreshed, it resulted in a reservation error. The section in PROCEDURE CopyFromSalesOrder making the binding reservation has been made conditional and will only be run for sales orders. Two obsolete MODIFY statements have been removed, stemmed from the days where reserved quantity was not a flowfield but was written onto the record."


Codeunit 99000787 Create Prod. Order Lines Service System reference: DK-576-290-VCGC

A430) Problem with Posting of BOM with Components with Alternative Units of Measure

Error

Parent Item in BOM now posted with correct costs when components do not use Base Unit of Measure


Codeunit 32 BOM Jnl.-Post Line Service System reference: SI-799-296-VEPK

A431) Transfer Order Item Shipped to Transit Could Be Applied and Posted Using Another Transaction

Error

Transfer Order item shipped to transit location can no only be posted by the original transfer


Codeunit 22 Item Jnl.-Post Line Service System reference: DK-923-241-XCN8

A432) Location Transfers

Error

Standard Cost was not set correctly. For items with costing method Standard the unit cost of the line was used to calculate the cost amount. This has been changed. Now the actual standard cost of the item or sku is used for the calculation.



Codeunit 22 Item Jnl.-Post Line Service System reference: HQ-179-565-YK8Z

A433) Standard Cost Not Updated by Batch Job if Costing Method Other Than Standard

Error

In the Standard Cost Worksheet, when you used the batch job Implement Standard Cost Change, on items with a costing method other than Standard, the standard cost of these items was not updated .


Codeunit 5804 ItemCostManagement Service System reference: HQ-807-758-YMHB

A434) Dependent on the Entry Type Rounding residual was not always eliminated

Error

In the adjustment batch job the rounding amount is calculated correctly. In codeunit 22 the sign of the cost amount can be reversed dependent on the entry type. This has been changed. If a rounding entry is created, the cost amount isn't reversed anymore.


Codeunit 22 Item Jnl. –Post Line Service System reference: HQ-742-20-YTNX

A435) Revaluation Posting Didn't Check, Whether Re-valuable Quantity Had Changed

Error

During splitting revaluation lines to item ledger entries the loop distributed costs until all revaluable quantity of the revaluation lines is used. This has been changed. It is now checked that revaluable quantity of the revaluation lines and revaluable quantity of the item ledger entries match.


Codeunit 23 Item Jnl.-Post Batch Service System reference: HQ-826-937-2KX2


A436) When Getting Document Lines from Item Charge Assignment Forms, Filter Would Sometimes Be Set Incorrectly

Error

Filters were not recalculated before get document lines were open from Item Charge Assignment forms


Form 5805 Item Charge Assignment (Purch) Form 5814 Item Charge Assignment (Sales) Service System reference: DE-297-417-4H7A

A437) Cycle Counting - Last Pys. Invt. Date field on Item Card/Warehouse Tab - Inconsistency Between Online Help and Flow Field

Error

Until now, the field ""Last Phys. Invent. Date"" was only affected by cycle counting. Normal phys. inventories were not regarded. This is now addressed in the field.


Table 27 Item Table 5700 Stockkeeping Unit Service System reference: HQ-962-229-7EF6

A438) A filter Was Removed in Both the Transfer Header and the Transfer Line Document Dimensions

Error

Report 5703 ""Transfer Order"" did not show internal info when requested. Report 5703 Transfer order- Service System reference: DE-77-537-GCNT

A439) Report 712 Inventory - Sales Statistics Could Be Wrong When Partial Shipment Was Posted.

Error

Report 712 now shows correct profits including non-inventoriable costs and also when posting partial shipments.


Report 712 Inventory Sales Statistics Service System reference: SE-320-785-HESR


A440) Incorrect Item Costs in Report 706 and 5801 for Average Costed Items and Revaluation

Error

For items using Average Costing method the report calculates cost using the Item Ledger Entry Quantity instead of the Value Entry Valued Quantity field.


Report 706 Status Report 5801 Invt. Valuation - Cost Spec. Service System reference: CH-630-48-9JCN

A441) Big Rounding Entry

Error

Due to a missing line, the sum of the InvtAdjmtBuffer.""Adjusted Cost"" was 0. Therefore a rounding entry for the whole adjusted cost was created.


Code 5895 Inventory Adjustment Service System reference: HQ-742-689-UNWN

A442) Halfway COMMIT in Undo Receipt/Shipment Could Leave Ghost Records in Reservation Entries.

Error

If an Undo Receipt / Shipment failed, it could leave ghost records in the Reservation Entry table preventing posting of further orders.


Codeunit 5813 Undo Purchase Receipt Line Codeunit 5814 Undo Return Shipment Line Codeunit 5815 Undo Sales Shipment Line Codeunit 5816 Undo Return Receipt Line Form 6510 Item Tracking Lines Service System reference: HQ-549-719-VFTR

A443) Report 715 Price List: Sales Prices

Error

The report did not correctly handle the starting dates and currency codes of sales prices.


Report 715 Price List Service System reference: DE-948-395-YJYU


A444) Error in Phys. Inventory Journal - Calculate Inventory by Dimensions

Error

Calculate Inventory by Dimension now creates Item Journal correctly


Report 790 Calculate Inventory Service System reference: SI-233-255-ZGUT

A445) Get Price/ Get Line Discount Used Incorrect Dates

Error

The wrong field captions were being used in the error messages called in the GetSalesPrice ans GetSalesLineDiscounts triggers.


Codeunit 7000 Sales Price Calc. Mgt. Service System reference: SE-861-755-RC27

A446) Negative Output Causes Value Entry with Entry Type Rounding

Error

The total amount of ‘Cost cost posted to G/L’ [L Value entry] and the total amount posted on G/L account 7100 (Inventory account) iswas wrong [G/L entry]. The correction ensures the cost amount buffered for output entries in the Inventory Adjustment Buffer is correct.


Service System reference: NL-697-699-NF6E

A447) Sales Prices Upgrade Did Not Handled Multi-Language

Error

Upgrade of Sales Prices now handles Multi-Language.


Upgrade310370.1.fob, Upgrade301370.1.fob, Upgrade260370.1.fob, Upgrade260370.MFG.1.fob Service System reference: DE-2-418-KKJZ


A448) 3.60 Upgrade Toolkit Item Tracking Error

Error

Valued Quantity of rounding entries is filled with the quantity of the linked item ledger entry


Service System reference: HQ; US-395-140-YV3P

A449) Impossible to Run Adjust Cost - Item Entries Batch Job

Error

The system runs into a loop.When you tried to run the Adjust Cost – Item Entries Batch Job, the batch job failed.


COD 5895 Inventory Adjustment Service System reference: SE-286-211-ZH2D

A450) Inventory Age Component - Value - Invalid amounts

Error

The period shown on each column has been shifted by one day for the report.


Service System reference: HU-141-753-6LVZ

A451) The Valued Quantity in the Value Entries Could Have an Incorrect Sign

Error

In Codeunit 5895 the posting of adjustments is triggered. The sign of the Quantity (Base) and Invoiced Qty. (Base) of the item journal line was filled dependent on the item ledger entry type. Codeunit 22 was called afterwards. But in Codeunit 22 the sign of the quantity fields for adjustment entries is NOT dependent on the item ledger entry type. Therefore the sign of the field Valued Quantity of negative adjustment entries was wrong. Because in Codeunit 22 the sign of Valued Quantity of adjustment entries is not changed, the quantity fields of the item journal line in Codeunit 5895 are now filled independent from the item ledger entry type."


Codeunit 5895 Inventory Adjustment Service System reference: HQ-214-60-HDRS


A452) Help Text Was Incorrect for Item Variant Code

Error

The help was incorrect and has been changed.


Service System reference: SG-686-171-24B8

A453) The Stockkeeping Unit Did Not Do a Check on the Unit Cost when the Standard Cost Was Changed.

Error

A similar check as in the Item table is now made on the SKU table when the standard cost is changed.


Table 5700 Stockkeeping Unit Codeunit 5804 Average Cost Adjustment Service System reference: NZ-847-411-QUGV

A454) Inventory Valuation and Expected Cost Posting

Error

"The quantity shown in the As of... column was not correct in when the item was not invoiced


Report 1001 Inventory Valuation Service System reference: GB-943-20-WLRW

A455) Value Entry Could Have Zero Amounts

Error

The amount of the adjustment is now transferred using the Amount and Amount (ACY) from Codeunit 5895 to Codeunit 22. This amount is used to create the adjustment value entries thus avoiding rounding problems.


Codeunit 21 Item Jnl.-Check Line Codeunit 22 Item Jnl.-Post Line Codeunit 5895 Inventory Adjustment Service System reference: CZ-799-772-8G6F, CZ-803-600-KKG8


A456) Too Many Item Value Entries Were Created from the Adjust Cost Batch Job for Adjusting an Item Charge

Error

The incorrect additional adjustment value entries are no longer created. The sum of the costs will still not equal zero, however, because the cost of the Credit Memo should not be applied to the Sale.


Code 22 Item Jnl.-Post Line Code 5895 Inventory Adjustment Service System reference: DE-155-33-RCCC

A457) Incorrect Item Ledger Entries Created Using SKU's and Transfer Orders

Error

The Inventory Posting Group has been removed from the Stockkeeping Unit table. The Inventory Posting Setup will ensure costs are posted correctly by Location. Upgrade to 3.70 has also ensure that the field in the Stockkeeping Unit is blanked out in step 1.


Codeunit 22 Item Jnl.-Post Line Codeunit 99000855 Planning-Get Parameters Form 5700 Stockkeeping Unit Card Table 83 Item Journal Line Table 5700 Stockkeeping Unit Table 37 Sales Line Table 39 Purchase Line Report 717 Inventory - Reorders Report 5706 Create Stockkeeping Unit Upgrade301370.1.fob Upgrade310370.1.fob Upgrade360370.1.fob Service System reference: AU-146-690-UW4M

A458) Unit-Amount Rounding Precision Could Cause Endless Loop in Adjust cost Batch Job

Error

The amount of the adjustment is now transferred using the Amount and Amount (ACY) from Codeunit 5895 to Codeunit 22. This amount is used to create the adjustment value entries avoiding rounding problems.


Codeunit 21 Item Jnl.-Check Line Codeunit 22 Item Jnl.-Post Line Codeunit 5895 Inventory Adjustment CZ-803-600-KKG8, CZ-799-772-8G6F


A459) Lookup Button Not Working On Form ID field on Whse. Worksheet Templates Form

Error

The lookup button for the field Form ID on the Whse. Worksheet Templates form did not work, but it has been fixed so that this button will now access the Objects form as a lookup.


Form 7353 Whse. Worksheet Templates Service System reference: GB-608-886-LJJW

A460) Error Occurred When Using Blank Cross Reference Type

Error

"The OnLookup trigger for the item cross-reference in the sales line was calling validation code in the field of the item cross-reference table. This code should have been placed in the ""OnRename"" and ""OnModify"" triggers instead. It has now been relocated. The filters on the Onlookup trigger for the Cross Reference No. have also been altered on the both the purchase and sales lines."


Table 5717 Item Cross Reference Table 37 Sales Line Table 39 Purchase Line Service System reference: HQ-624-651-WSZU

A461) Error on Item Ledger Entry Filter Selection

Error

The correction now ensure that it is possible to enter any type of filter on the Item Ledger Entry, Value Entry, and Capacity Ledger Entry forms.


Form 5832 Capacity Ledger Entries Form 38 Item Ledger Entries Form 5802 Value Entries Service System reference: LT-207-644-QCCH

A462) Function "Assign Lot No." Did Not Work for Quantities with Decimal Places

In Form 6510 procedures AssignSerialNo, AssignLotNo and CreateCustomizedSN handling of integer-decimal conversion has been added, introducing an extra variable.


Form 6510 Item Tracking Lines


Service System reference: DE-908-363-JJB2

A463) Sales Prices Upgrade Did Not Handled Multi-Language.

Upgrade of Sales Prices now handles Multi-Language.


Upgrade310370.1.fob Upgrade301370.1.fob Upgrade260370.1.fob1 Upgrade260370.MFG.1.fob Service System reference: DE-2-418-KKJZ

A464) Calculation of Indirect Cost % on Item journal Was Incorrect

The calculation of unit cost in Item journal Line was incorrect because the Indirect cost and overhead rate was added twice to the cost price when you posted an entry type negative adjustment or sale line in the item journal. This cost was updated on the item form.


Table 83 Item Journal Line Service System reference: CH-896-103-LEMC

A465) No Dimension in the Phys. Inventory Journal After Using the Calculate Inventory Batch Job

Error

When you used the Calculate Inventory on Phys. Inventory Journal function, the program filled in Global Dimension fields on the journal lines using the item's default dimension value, so you would get the global dimension value on the lines but not in the Journal Line Dimension table. This has been corrected so that the selected global dimensions on the journal lines are copied from the posted item ledger entries. Therefore in the Journal Line Dimension table some lines will have Dimensions others will not which reflect the actual inventory more accurately.


Report 790 Calculate Inventory Service System reference: SE-914-336-7LG9

A466) Changing Unit Cost on Sales Line for Item with Costing Method Average

Issue

Due to the changed exit condition the sale is now valued with the unit cost of the item journal line in codeunit 22.



Codeunit 5804 ItemCostManagement Service System reference: SE-769-186-FFKQ

2.9 Warehouse Management

Features

A467) Order-by-order warehousing

Feature

This new feature supports customers with basic requirements to organize their warehouse and to register information (receipts, movements and shipments) necessary to gain an overview of the warehouse processes. The order-by-order warehousing is divided in three granules:

• Bin granule

• Pick granule

• Put-away granule

The Bin granule enables the user to assign bin code information directly to items on source documents, the Pick and Put-away granules provide a simple interface to the user for performing the same assignment but with limited access to the source documents. This offering supports the order-by-order processes, and the functionality resides in the Inventory Management area. The bin code information is stored on the Warehouse Entries instead of the Item Ledger Entries.

The order-by-order warehousing offering represents an entry point to warehousing, and it is supplemented by the offering of multiple-order warehousing and Warehouse Management Systems.

Multiple-order warehousing is a redefinition of the Warehouse Management offering where the offering is more detailed:

• Warehouse Receipt

• Warehouse Shipment

• and any of the granules of the order-by-order warehousing

The Warehouse Management Systems solution is not affected for 3.70 except the extraction of the Bin creation and the Bin content creation worksheets that are proposed to all warehousing customers as the new granule:

• Bin Setup



A468) [Inconsistent data when posting warehouse receipt or shipment

Feature

The existing code for WhseSetup."Receipt Posting Policy"::" Posting errors are not processed" is disabled and it will always behave as if the parameter would have been set to "Stop and show the first posting error".

This feature has been changed

COD 5760 Whse.-Post Receipt COD 5763 Whse.-Post Shipment Service System reference: HQ-327-230-GMVJ

Errors fixed

A469) Transfer Orders and Item Tracking: When posting a Whse. Shipment, Whse. Entries can loose Item Tracking Information

Error

In codeunit 5704 TransferOrder-Post Shipment item tracking information is stored in temporary tracking lines. Using derived transfer lines these temporary lines weren't created. Therefore the following whse. registering didn't regard item tracking information. This has been changed. Temporary tracking lines are now created using the transfer lines.


COD5704 TransferOrder-Post Shipment Service System reference: DE-468-938-3LZ2

A470) WMS/IT: Usage of reclassification jnl does not support IT info

Error

There is a new menu item in the Whse. Reclassification Journal added to enter item tracking specifications, when performing a whse reclassification with Item tracked item. However, it is not possible to change lot or serial numbers to new ones from the Whse. Reclassification Journal. To do this, the user should use the Whse. Item Journal to create a negative adjustment for the old item tracking numbers and a positive adjustment to the same bin for the new item tracking numbers. In addition, the user must make the change to the tracking numbers in the Item Ledger Entries as well by creating an entry in the Item Reclass. Journal and assigning new tracking numbers there.


Form 7365, Codeunit 7304 Service System reference: HQ-795-14-CQL6


A471) Partial Shipment of Same Lot No.

Error

Partial shipment of the same Lot No. was not possible. Item Tracking lines related to Shipment were not updated in case of partial picking of the same Lot, and that prevented the Shipment to be posted later on.


Codeunit 7307 Whse.-Activity-Register Service System reference: DK-853-347-ZAS9

A472) Lines Could Be inserted by Copy&Paste in Warehouse Documents

Error

The Warehouse Shipment Line, Whse. Internal Put-away Line, and Whse. Internal Pick Lines have been corrected so that it is no longer possible to copy and paste lines in these documents.


Table 7321 Warehouse Shipment Line Table 7332 Whse. Internal Put-away Line Table 7334 Whse. Internal Pick Line Service System reference: DE-288-292-NGFZ

A473) Changing Shipping Time in Transfer Order works incorrect

Error

Shipment Date was recalculated inclrrectly because Shipping Time was not updated on the lines.


Table 5740 Service System reference: DE-904-462-NKRE

A474) Incomplete error message on deleting document with attached warehouse lines

Error

When attempting to delete a document line with attached warehouse lines, the error message that appeared was incomplete and contained a misspelling. This has been corrected.


Codeunit 5777 Whse. Validate Source Line Service System reference: DE-564-997-QBAE


A475) Blank Location Requires Pick on Outbound Documents

Error

When the Warehouse Mgt. Setup was set up to Require Pick, it was not possible to put a quantity on a line for an outbound source document with a blank location. This has been fixed so that this is now possible.


Service System reference: HQ-234-367-QK58

A476) Could Set a Zone Code for a Location without Directed Put-away and Pick

Error

It was possible to set up a Zone for a location that was not set up to use directed put-away and pick. This has been fixed so that it is now only possible to set up zones for locations with directed put-away and pick.


Service System reference: HQ-120-240-RHD6

A477) Item Tracking Lines Not Found When Performing Partial Shipment

Error

When performing a partial shipment, the program was not finding item tracking lines for items that had been picked. This was corrected so that the program can properly find the appropriate item tracking lines.


Codeunit 7307 Whse.-Activity-Register Service System reference: HQ-554-314-WJRS

A478) Undo Quantity Posting Created Inconsistency in Warehouse Data Using Undo Receipt for WMS Locations

Error

The following code has been added to the undo functions: PostWhseRcptLine.SETCURRENTKEY(""Source Type"",""Source Subtype"",""Source No."",""Source Line No.""); PostWhseRcptLine.SETRANGE(""Source Type"",DATABASE::""Purchase Line""); PostWhseRcptLine.SETRANGE(""Source Subtype"",1); PostWhseRcptLine.SETRANGE(""Source No."",""Order No.""); PostWhseRcptLine.SETRANGE(""Source Line No."",""Order Line No."");


IF PostWhseRcptLine.FIND('-') THEN ERROR(Text014,""Line No.""); PostWhseShptLine.SETCURRENTKEY(""Source Type"",""Source Subtype"",""Source No."",""Source Line No.""); PostWhseShptLine.SETRANGE(""Source Type"",DATABASE::""Purchase Line""); PostWhseShptLine.SETRANGE(""Source Subtype"",1); PostWhseShptLine.SETRANGE(""Source No."",""Order No.""); PostWhseShptLine.SETRANGE(""Source Line No."",""Order Line No.""); IF PostWhseShptLine.FIND('-') THEN ERROR(Text015,""Line No.""); The 2 used keys were added to the tables."


Codeunit 5813 Undo Purchase Receipt Line Codeunit 5814 Undo Return Shipment Line Codeunit 5815 Undo Sales Shipment Line Codeunit 5816 Undo Return Receipt Line Table 7319 Posted Whse. Receipt Line Table 7323 Posted Whse. Shipment Line Service System reference: HQ-489-327-CJJG

A479) Incorrect Description of Item Variant in Physical Inventory Journal

Error

Bin code and variant Code information is retrieved again whenever the item no. field in the Item Journal Line table is validated.


Table 83 Item Journal Line Service System reference: HQ-235-661-MHNG

A480) Deleting Warehouse Movements with Associated Movement Worksheet Lines

Error

When deleting a warehouse movement that had movement worksheet lines still existing and associated with it, the user received no warning that the related warehouse worksheet lines must be re-created. The user now receives this warning.


Table 7326 Whse. Worksheet Line Form 7351 Movement Worksheet


Form 7354 Whse. Internal Put-away Report 7391 Whse. Get Bin Content Codeunit 7308 Replenishment Service System reference: HQ-987-546-CQDR

A481) Warehouse Entries and Manufacturing Output Journals

Error

If you enter (and post) an output journal for a negative quantity, to correct and earlier erroneous entry for example, the warehouse adjustment is for a posistive quantity to the outbound production bin.


Codeunit 7302 WMS Management Service System reference: GB-867-400-PH27

A482) Data Compressing Warehouse Entries

Error

There was previously no way to compress warehouse entries to save database space. Data compression of warehouse entries has now been implemented.


Table 87 Date Compr. Register Table 242 Source Code Setup Table 7313 Warehouse Register Form 279 Source Code Setup Form 5765 Warehouse Mgt. Menu Codeunit 2 Company-Initialize Service System reference: HQ-806-53-CQL2

A483) Qty to Cross-dock Changes if Use Autofill More than Once

Error

In some situations, clicking Autofill Qty. to Cross-dock more than once could change the quantity in the Qty. to Cross-dock field. This has been corrected.


Table 5768 Whse. Cross-Dock Opportunity Form 5783 Cross-Dock Opportunities Service System reference: HQ-725-173-CQTL


A484) Spill Overflow on Description Fields on Warehouse Tables

Error

The Description fields have been lengthened to 50 characters on warehouse tables to prevent spill overflow.


Table 5767 Warehouse Activity Line Table 5773 Registered Whse. Activity Line Table 7317 Warehouse Receipt Line Table 7319 Posted Whse. Receipt Line Table 7321 Warehouse Shipment Line Table 7323 Posted Whse. Shipment Line Table 7326 Whse. Worksheet Line Table 7332 Whse. Internal Put-away Line Table 7334 Whse. Internal Pick Line Service System reference: SE-846-759-ZJCQ

A485) Item Tracking Information Corrupted in Warehouse Pick

Error

When creating a warehouse pick for an order where a previous line is with item tracking information and the next line is without item tracking information, the item tracking information a boolean triggering the presence of item tracking information was not being reset to False for the second line without item tracking information. This has been corrected.


Codeunit 7312 Create Pick Service System reference: BE-798-217-GGGE

A486) Incorrect Error Message in Warehouse Movement

Error

When creating a movement with two lines for the same item but different variants in the warehouse movement worksheet, and attempting to change the Qty. to Place, the program rightly produces an error, but the error message shows incorrect quantities for the line by totaling the quantities of the two lines. This has been corrected so that the error message shows the correct quantities.


Codeunit 7302 WMS Management Service System reference: US-128-570-PKGS


A487) Error in Calculate Bin Replenishment, when you use the put-away worksheet

Error

When there are items in bins with Bin Type Receive, the Calculate Bin Replenishment function in the Movement Worksheet shows an error. This is corrected so that the bin replenishment will run without the error when there are items in the Receive bins.


Form 7351 Movement Worksheet Report 7300 Calculate Bin Replenishment Codeunit 7308 Replenishment Service System reference: DE-765-860-2GSK

A488) Wrong Bin Numbers Calculated In Bin Creation Worksheet

Error

When creating bins in the Bin Creation Worksheet using the Calculate Bins function, if Rack numbers were used to define the new bin codes, too many bins could be calculated. This has been corrected so that the string length is taken into account by the Calculate Bins function, and only the correct bins are created.


Report 7310 Calculate Bins Service System reference: DE-972-641-RBNC

A489) Item Can Be Taken Out of a Bin That Is Blocked for Outbound Movement

Error

"Even though a bin was blocked for outbound movement, the ""block movement"" value was not passed to the bin content for the bin, so that an item placed in the bin could still be taken out. This has been corrected so that Block Movement value is passed from the bin to the bin content when bin content is created."


Codeunit 7301 Whse. Jnl.-Register Line Service System reference: DE-311-836-SKSN

A490) Shipping Time was not retrieved appropriately when Sell-to Customer, Ship-to Code, Shipping Agent Code, or Shipping agent Service Code is changed.

Error

Shipping Time is now retrieved appropriately on the following triggers Sell-to Customer, Ship-to Code, Shipping Agent Code, or Shipping agent Service Code is changed.


Table 36 Sales Header


Service System reference: AT-422-498-TCBL

A491) Property TestTableRelation Wrong in Some Fields

Error

Some fields on Table 5773 Registered Whse. Activity Line and Table 7319 Posted Whse. Receipt Line contained incorrect TestTableRelation properties. These properties have been corrected.


Table 5773 Registered Whse. Activity Line Table 7319 Posted Whse. Receipt Line Service System reference: DE-314-204-BM24

A492) Wrong Filter in the Warehouse Entries in a Released Production Order

Error

After posting the output for a released production order, the warehouse entries for the output were not visible from the released production order form. The filter for showing the warehouse entries from this form has been corrected so that all entries will be shown for the released production order.


Form 99000831 ""Released Production Order Form 99000867 Finished Production Order Form 99000815 Production Order List Service System reference: DE-432-5-GJKF

A493) Wrong Version mentioned in the Upgrade Manual

Error

The wrong version was mentioned in the upgrade manual on page 86. Where the manual states ""An empty Warehouse Location Filter in the User Setup Table in 3.60 means....."", the version number should be 3.01.


Service System reference: HQ-88-546-F83B

A494) Job No. in Warehouse Management

Error

Sales or Purchase lines for job numbers were being transferred to Warehouse Management for receipt or shipment. This has been changed so that lines with job numbers are no longer carried over to warehouse management documents.



Report 5753 Get Source Documents Codeunit 5771 Whse.-Sales Release Codeunit 5772 Whse.-Purch. Release Service System reference: DE-571-285-2DBB

A495) "Item Tracking Lines Not Found When Performing Partial Shipment

Error

When performing a partial shipment, the program was not finding item tracking lines for items that had been picked. This was corrected so that the program can properly find the appropriate item tracking lines.


Table 7320 Warehouse Shipment Header Codeunit 5763 Whse.-Post Shipment Codeunit 7307 Whse.-Activity-Register Service System reference: GB-442-522-ZL8S

A496) Incorrect DataItemTableView in report 7305 (Whse.-Source - Create Document)

Error

In Report 7305 (Whse.-Source - Create Document), the third data item, Whse. Put-away Worksheet Line, was filtering only on Whse. Document Types of Internal Putaway, but now filters correctly on Whse. Document Types of both Receipts and Internal Putaways.


Report 7305 Whse.-Source - Create Document Service System reference: HQ-931-185-8EQV

A497) Incorrect table relation

Error

The table relation in the Journal Batch name field of the Value Entry table has been removed. It no longer causes problems with setting up filters.


The table relation in the Journal Batch name field of the Value Entry table has been removed. Service System reference: HU-473-967-BFL3


A498) Put-away Document Created From Posted Receipt Does Not Contain Item Tracking Information

Error

A put-away document created from a posted receipt was not created with item tracking information. This has been corrected.


Report 7305 Whse.-Source - Create Document Service System reference: NL-730-203-7KWN

A499) Shelf Number Not Appearing in the Pick Line When Created From the Production Order

Error

When there was a Shelf No. defined on the item, the shelf number was not appearing on the pick line when the pick line was created directly from the production order. This has been corrected so that the item's shelf number will appear on the pick line.


Codeunit 7312 Create Pick Service System reference: DE-270-13-RC2S

A500) Bin content line with zero quantity is created when putaway bin is changed

Error

After changing the put-away bin on a put-away to a different bin, a bin content line with 0 quantity was created for the original bin. This has been corrected so that this line is no longer created.


Table 5767 Warehouse Activity Line Service System reference: US-431-134-QKLF

A501) The Description entered in the Whse. Item Journal is not in the Warehouse Entries

Error

There was no description field on the warehouse entries to reflect the description entered in the Whse. Item Journal. A description field has now been added to the warehouse entries.


Table 7312 Warehouse Entry Form 7318 Warehouse Entries Codeunit 7301 Whse. Jnl.-Register Line


Service System reference: DE-455-841-2GEP

A502) Potential Deadlocks when Posting a Receipt

Error

Places for potential deadlocks existed in the code for posting a warehouse receipt. The code for this process has been changed to eliminate the potential deadlocks.


Codeunit 80 Sales-Post Codeunit 90 Purch.-Post Codeunit 5704 TransferOrder-Post Shipment Codeunit 5705 TransferOrder-Post Receipt Codeunit 5763 Whse.-Post Shipment Service System reference: ZA-112-932-YAHK

A503) Error in Posting Whse. Shipment with Item Tracking Lines

Error

The program was showing an error when attempting to post a shipment for a lot.-number-tracked item that had been put-away into two different bins, with a lower quantity putaway first. This problem has been corrected so that the program finds both the item tracking entries, rather than only the first with the low quantity.


Codeunit 5763 Whse.-Post Shipment Service System reference: NL-642-95-VDXP

A504) Changing Shipping Advice for Warehouse Shipment

Error

It was not possible to change the Shipping Advice for an order so that a warehouse shipment would acknowledge the change and post the shipment. This has been corrected.


Codeunit 5781 Whse. Validate Source Header Service System reference: GB-733-518-SGYE

A505) Qty to Cross-dock Changes if Use Autofill More than Once

Error

In some situations, clicking Autofill Qty. to Cross-dock more than once could change the quantity in the Qty. to Cross-dock field. This has been corrected.



Table 5768 Whse. Cross-dock Opportunity Form 5783 Cross-dock Opportunities Service System reference: US-253-843-YR7Z

A506) Warehouse Put Away - Change of Item Unit of Measure in the place line

Error

It was not possible to change the unit of measure of an item in a put-away’s place line if the new calculated quantity to be placed was not whole-numbered.


Report 7314 Whse. Change Unit of Measure Service System reference: GB-69-44-LP7K

A507) Invalid TableID in Upgrade Step 2 Function UpdateItemJournalLine

Error

Table reference used is now Item Journal Line as intended


Upgrade260370.2.MFG.fob,Upgrade260370.2.fob,Upgrade 265370.2.CG.fob,Upgrade 265370.2.CP.fob Service System reference: DE-447-29-MC4Z

A508) Using Post+Print in Warehouse Shipment for Shipment Document and Invoice

Error

When using Post+Print in the Warehouse Shipment and choosing Ship and Invoice, the program would print only the shipment document. This has been changed so that when choosing Ship and Invoice, both the shipment document and the invoice will print.


Codeunit 5763 Whse.-Post Shipment Service System reference: DE-863-661-MD9L

A509) Difficulties in Posting Partial Put-aways with Item Tracking

Error

It was not possible to post a partial put-away document with lot-tracking information (partial, meaning that the remaining lines were deleted from the put-away document) and to go back and post the remaining quantities. This has been corrected so that one can now delete the unwanted lines from the put-away document and later post the remaining quantity correctly.



Codeunit 6500 Item Tracking Management, Codeunit 7307 Whse.-Activity-Register Service System reference: GB-796-533-9GN5

A510) Possible to Undo Receipt in a Location Using Warehouse Receipts

Error

It was possible to perform an undo receipt for a posted purchase receipt when a warehouse receipt was used to post. This has been corrected so that it is no longer possible to undo a posted receipt that originated from a warehouse receipt.


Service System reference: DE-911-771-ADLD

A511) "Display mode of forms ""Posted Transfer Shipment Lines"" and ""Posted Transfer Receipt Lines"" not consistent"

Error

"Display mode of form ""Posted Transfer Shipment Lines"" made to look like ""Posted Receipt Lines"""


Form 5758 Posted Transfer Shipment Lines Service System reference: DE-399-947-EHKG

A512) ADCS Crashes NAS Service Without Error Message When 2 or More Handhelds Used At Same Time

Error

When mulitple handhelds are used, a situation could occur that the VT100 Plugin became blocked, this occurred when Information was received from 2 or more handhelds at allmost the same moment in time, and was caused by the NamedPipe being kept open by the first Handheld. This issue has now been solved.


Service System reference: BE-610-498-EJJ8

A513) Terminology in Client

Issue

1. Renamed the name of Form 399 name from Purchase Shipment Statistics to Purchase Receipt Statistics


2. The term abbreviation for Non-Inventoriable, i.e. Non-Invt. in Table 32,Table 5821, and Table 5802 has now been changed to Non-Invtbl.


Service System reference: NO-581-495-6CKM

A514) Item Reclassification Journal Does Not Support Dimensions

Issue

1. The New Dimension Values was not filled out by default. 2. A check for New Dimension Values were missing, e.g. if the dimension was Code Mandatory, you could post without having the New Dimension Value field filled out.

In response to this issue, a change has been implemented

Codeunit 21 Item Jnl. - Check Line Codeunit 408 Dimension Management Service System reference: DK-364-279-2JW7

2.10 Manufacturing

Errors fixed

A515) Fault in the calculation of Expected Operation Cost. Amt.

Error

Expected Operation Cost Amt. was not correctly calculated. A New function has been added. This function is responsible for calculation "Expected Cost". ProdOrderQty := ExpectedOperOutput - ActualOperOutput; has been changed to ProdOrderQty := ExpectedOperOutput;"


C99000774, function CalculateRoutingLine Service System reference: DE-588-458-YH8V

A516) Production Order can be changed to Finished, while Purchase Orders are still open

Error

It is now made possible to finish the production order as long as the related purchase order has been fully received. Invoicing can be postponed till after finishing.


In Cod 5407 procedure CheckBeforeFinishProdOrder that will test whether related purchase order lines with outstanding quantity still exist. If this is the case an error message will be issued. In Cod 6500 procedure RetrieveSubcontrItemTracking a GET statement on routing line has been made conditional to avoid error if the lines cannot be found due to the order having been finished.


Codeunit 5407 Prod. Order Status Management Codeunit 6500 Item Tracking Management" Service System reference: NL-556-246-8CVW

A517) Table 5407 Prod. Order Component (FA-Komponente) Contains Wrong Property in Field 35 Supplied-by Line No.

Error

The TableRelation property for field Supplied-by Line No. in table Prod. Order Component was incorrect.


Table 5407 Prod. Order Component Service System reference: DE-934-125-7BJ3

A518) Bad Performance

Error

Calculation formula for Reserved Quantity and Reserved Quantity (Base) did not filter on all relevant fields. This gave rise to bad performance.


Table 5406 (Production Order Line) Service System reference: DE-389-972-8CRH

A519) Change Production Bom No. on an Item

Error

Changing Production BOM No. on an Item gave a permission error if the BOM Version granule was not in the user's license.

This has been changed

Table 99000850 (Planning Assignment) Service System reference: SE-219-314-JD9S


A520) Missing Variant Description

Error

The Function Update Description. from Table 246, Requisition Line is now called from Validation Code on field "No.".


Table 246 Requisition Line Service System reference: US-900-874-8K3N

A521) Empty "Ending Date-Time" on Planning Worksheet could lead to a too early "Starting Date-Time"

Error

“The problem was because of empty ""Ending Time"" the planning system suggested the nearest date-time.


Table 246 Requisition Line Service System reference: HQ-955-922-UKFU

A522) Rename function causes extreme performance issue.

Error

There was a performance problem in the Calculate Consumption batch job, due to the fact that codeunit 408 called TempDimBuf2.RENAME where a TempDimBuf2.DELETE and TempDimBuf2.INSERT would be sufficient.


Codeunit 408 (DimensionManagement) Service System reference: US-37-233-5T5N

A523) Routing status on Production Order Didn't Change to Finished for fully received subcontracted Purchase Order

Error

When fully receiving a subcontracted purchase order for a Procuction Order, the Routingstatus on Production Order didn't change to Finished.


Table 39 Purchase Line Codeunit 90 Purch.-Post Report 99001015 Calculate Subcontracts Codeunit 5403 AddOnIntegrManagement Service System reference: SE-641-462-NG3P


A524) Base Calendars and Lead Time

Error

The leadtime calculation did not always consider calendars for vendor and location. This has been corrected, and a general refurbishment of the leadtime calculation procedures has been made. Now all date calculations are made in Codeunit 5404 Lead-Time Management.


Table 246 Requisition Line Table 5405 Production Order Table 5406 Prod. Order Line Codeunit 5404 Lead-Time Management Codeunit 99000809 Planning Line Management Codeunit 99000854 Inventory Profile Offsetting Codeunit 99000886 Capable to Promise Service System reference: DK-158-569-KBWB

A525) Transfer Orders With Item Tracking

Error

Transfer Orders with several lines containing item tracking could not been shipped. Whse. Tracking Lines were created for transfer lines and derived transfer lines.


Codeunit 5704 TransferOrder-Post Shipment Service System reference: DE-598-427-ZEB9

A526) Transfer Orders in Planning

Error

The planning calculation suggested incorrect actions, when transfer orders was needed but already existed.


Table 99000853 Inventory Profile Service System reference: HQ-856-152-CR78

A527) Validation of Starting Date on Production Orders

Error

When a date was entered in the starting date field of a production order, it sometimes resulted in strange results. Leftover functionality from before version 2.00 where some dating is calculated based on reservation entries has been removed.


The Procedure GetNeededDate in Codeunit 99000845, and all references to this procedure in other objects, has been removed.


Table 246 Requisition Line Table 5405 Production Order Table 5406 Prod. Order Line Table 5407 Prod. Order Component Table 5409 Prod. Order Routing Line Table 99000829 Planning Component Report 99001026 Replan Production Order Codeunit 99000845 Reservation Management Service System reference: DE-462-399-PDVC

A528) Incorrect Description of Produced Items

Error

When an item was posted as output from a production order, the incorrect description was used.


Codeunit 22 Item Jnl.-Post Line Service System reference: HQ-97-942-CPRR

A529) Cost on Planning Components

Error

The costing fields at the planning components were not initialized correctly.


99000829 Planning Component Service System reference: HQ-919-888-CPFY

A530) Dimensions on Production Order Lines and Components

Error

The dimensions were not passed properly from the production order header to the production order lines and production component lines.


Table 358 Production Document Dimension Table 5406 Prod. Order Line Table 5407 Prod. Order Component Codeunit 408 DimensionManagement Service System reference: US-306-753-KUYE


A531) Incorrect Spelling in Report.

Error

A spelling error has been corrected in the Calculate Plan - Plan. Wksh. report.


Report 99001019 Calculate Plan - Plan. Wksh. Service System reference: HQ-578-56-CPA5

A532) Load / Bar Reports

Error

The Work Center Load / Bar and Machine Center Load / Bar reports did not show the correct bars in all cases.


Report 99000785 Work Center Load / Bar Report 99000786 Machine Center Load / Bar Service System reference: SE-914-731-PLYC

A533) Capacity Load Quantity Explosion of BOM Report

Error

The report showed incorrect total quantities. When the BOM structure contained more than two levels the calculation of the total quantities might fail. The error was caused by the report not multiplying the quantities down through the BOM tree structure; only the immediate previous level was taken into account. The solution was to ensure that every time we step to a new, lower, level, we multiply the quantity on the new level with the current quantity.


Report 99000753 Quantity Explosion of BOM Service System reference: DE-407-586-GFQN

A534) Reservations and Item Tracking

Error

If a production order line was reserved for a sales order, the reservation was deleted, if the item was posted with item tracking from the output journal.


Codeunit 6500 Item Tracking Management Codeunit 99000830 Create Reserv. Entry Codeunit 99000837 Prod. Order Line-Reserve Codeunit 99000838 Prod. Order Comp.-Reserve"


Service System reference: DK-353-119-VAUP

A535) Forecast Consumption

Error

The consumption of component forecast did not always give the correct results.


Codeunit 99000854, Inventory Profile Offsetting Service System reference: HQ-319-213-CQUN

A536) Dimensions on Production Order Components

Error

When a production order was created from a sales order, the dimensioncodes was not transfered the the component lines. The dimensions would normally be passed down via validation code to the component lines when these were created. However in the functionality in the dimensions was transferred to the line AFTER component lines had been created, meaning that although the dimension handling code would be activated, there would be nothing to transfer. The correction is aiming at getting the transfer from the sales line done before component lines are created.


Codeunit 99000787 Create Prod. Order Lines Codeunit 99000792 Create Prod. Order from Sale Service System reference: DK-429-347-VD7W

A537) Capable-to-Promise and Reservations

Error

The calculation of the Capable-to-Promise sometimes failed, when reservations was used. The FlowField 108 ""Res. Qty. on Inbound Transfer"" in Table 27 ""Item"" did not calculate the correct value, leading to a wrong calculation of unavailable quantity in order promising.


Table 27 Item Service System reference: DK-607-325-VEA4

A538) Finished Date on Production Orders

Error

When a production order was finished, the finished date was not set.



Codeunit 5407 Prod. Order Status Management Service System reference: DE-284-566-3F6F

A539) Manually Insertion of Planning Lines

Error

In some cases, it was not possible to insert a planning line manually when the lines were sorted in a non-default sequence.


Table 246 Requisition Line Service System reference: HQ-854-603-CP6K

A540) Planning With Reorder Point and Fixed Reorder Quantity

Error

In some cases the planning calculations did not suggest the correct values, when Reorder Point and Reorder Qty. was used.


Codeunit 99000854 Inventory Profile Offsetting Service System reference: DK-541-484-EC2C

A541) Planning Lines With Blank Action Message

Error

In some situations an attempt to forward reschedule an order suggestion could result in planning line with no suggested action. The reason for this error is that it is necessary to create a planning line to work on when forward scheduling in order to calculate the new due date. Normally this line will be updated with an action including 'Reschedule'. But in some cases the Due Date does not change after the line has been forward scheduled. Now the system will remove such obsolete planning lines.


Codeunit 99000854 Inventory Profile Offsetting Codeunit 99000809 Planning Line Management Service System reference: DE-178-659-BHKE


A542) Quantities on M-T-O Production Orders

Error

In some cases, the quantities on the production order lines was not correct for M-T-O production order. Low-level code field is added to production order componet line in order to get the right sorting.


Table 5407 Prod. Order Component Codeunit 99000773 Calculate Prod. Order Codeunit 99000787 Create Prod. Order Lines Service System reference: CZ-988-832-GEAC

A543) Prod. Order Gantt Chart Report

Error

Various errors was reported concerning this reports. These have now been addressed.


Report 99000782 Prod. Order Gantt Chart: Service System reference: HQ-805-896-CQE8

A544) Location Filters on Production Forecast Form

Error

The OnLookUpTrigger of the Location Filter field didn't comply to multilanguage standard of coding.


Form 99000919 Production Forecast Service System reference: DK-907-817-TBS2

A545) Program Constants

Error

Numeric constant was used instead of symbolic constant.


Table 99000853 Inventory Profile Service System reference: HQ-761-177-PJNZ


A546) Deletion of Planning Line

Error

It was not possible to delete a planning line if the corresponding item was deleted.


Table 27 Item Service System reference: US-441-811-KHHZ

A547) Dimensions in Planning Worksheet

Error

Dimensions were not deleted when action messages Change Quantity was carried out in the requisition worksheet. This would lead to an ""Journal Dimension already exists""-error when running planning second time.


Codeunit 333 Req. Wksh.-Make Order Service System reference: DE-124-466-4DRG

A548) Production Order Statistics Report

Error

In some cases the report displayed an error message.


Report 99000791 Production Order Statistics Service System reference: DK-677-271-YDEP

A549) Dimensions on Lines in the Output Journal

Error

Dimensions were not assigned to the lines in the output journal, when the Explode Routing batch job was used. The reason for the error was that the validation code that would normally retrieve the dimensions would be surpassed if the validated field value was not changed compared to xRec. This works fine normally as it prevents unnecessary updates, but the structure of the code in Codeunit 5406 lead to the update not being performed at all.


Codeunit 5406 Output Jnl.-Expl. Route Service System reference: DK-788-286-NC96


A550) Reschedule of Multi-level Production Orders

Error

The Planning calculations sometimes suggested the wrong Due Date for the child lines in the multilevel Production Orders.


Codeunit 99000809 Planning Line Management Service System reference: SE-666-911-3QM3

A551) Incorrect Calculation of Comment Flowfield

Error

Version Code was ignored in the calculation of the Comment flowfields.


Table 99000764 Routing Line Table 99000772 Production BOM Line Service System reference: DK-829-57-2JC5

A552) Where-used and BOMs with versions

Error

Even though BOM versions was certified, they were ignored by the Where-used function.


Codeunit 99000770 Where-Used Management Service System reference: DK-57-104-HBKT

A553) Capacity Gantt Chart and Prod. Order Gantt Chart Reports

Error

Graphical representation of operations failed in the reports 99000781 Capacity Gantt Chart and 99000782 Prod. Order Gantt Chart if periods were different from weeks.


Report 99000781 Capacity Gantt Chart Report 99000782 Prod. Order Gantt Chart Service System reference: BG-184-942-MFBN


A554) Statistics for Multi-line Production Orders

Error

The statistical values for multi-line production orders was not correct. The function in codeunit 5836 did not take the old values into account when calculating the standard cost.


Codeunit 5836 Cost Calculation Management Service System reference: GB-488-631-WDMQ

A555) Request Filter on Carry Out Action Msg. - Plan. Report

Error

“Requisition Line" was displayed as a request filter caption on the report Report 99001020 Carry Out Action Msg. - Plan. This has been renamed to "Planning Line".


Report 99001020 Carry Out Action Msg. - Plan. Service System reference: HQ-109-887-NDB5

A556) Routing No. Field on Production Orders

Error

The "Routing No." field on Production Orders was not updated by the Refresh function.


Report 99001025 Refresh Production Order Service System reference: DK-278-651-MD5A

A557) Reservations and Partial Posting

Error

Due to the way reservation entries were transferred during posting from the order line to the Item Ledger Entry, it would in some cases, where partial posting has been used, happen, that the posting would stop with a run-time error claiming that items were not on inventory even though this was not true. A correction has been made that will ensure, that when posting a shipment the system will always post quantities reserved against inventory before trying to post any other reserved quantities. The existing algorithm changed so that the loop transferring T337 entries with status Reservation will be run in two tempis when the quantity transferred represents demand. In the first tempi the records will only be transferred if they are related to an item ledger entry.


In the second tempi all types of entries will be transferred. This means that only if the quantity reserved against inventory is not sufficient to cover the quantity that is transferred will entries reserved against non-inventory supply be transferred (which will later lead to the run time error in the posting). IMPORTANT NOTE: However, when reservations exist they will always during posting be given priority over non-reserved quantities. In the described scenario reserved and non-reserved items are mixed and this scenario will never work.


Codeunit 99000830 Create Reserv. Entry Codeunit 99000832 Sales Line-Reserve Codeunit 99000834 Purch. Line-Reserve Codeunit 99000836 Transfer Line-Reserve Codeunit 99000837 Prod. Order Line-Reserve Codeunit 99000838 Prod. Order Comp.-Reserve Codeunit 99000842 Service Invoice Line-Reserve Codeunit 99000843 BOM Jnl. Line-Reserve" Service System reference: BE-288-904-XF7A

A558) Priorities of Production Orders

Error

The system prioritized demand and supply on Due Date only. The production order status was added to priorities.


Codeunit 99000854 Inventory Profile Offsetting Service System reference: DK-370-252-LDKA

A559) Refresh of Multilevel Production Orders

Error

When the due date was changed on a multilevel production order, the refresh batch job, failed to calculate the proper starting and ending dates.


Table 5405 Production Order Service System reference: US-902-264-A82E


A560) Dimensions on Production Order Components

Error

The dimension fields on the production order lines were not filled in with the global dimensions 1 and 2 when the production order was created from a sales order.


Codeunit 408 DimensionManagement Codeunit 99000787 Create Prod. Order Lines Table 246 Requisition Line Form 99000886 Subcontracting Worksheet Report 99001015 Calculate Subcontracts" Service System reference: DE-474-551-NHQL

A561) Not Ordering Up to max. with Maximum Quantity in Planning

Error

The decrease Qty function would not increase the supply even though it was needed. A new name for this function is neeeded.


Codeunit 99000854 Inventory Profile Offsetting Service System reference: HQ-330-388-NN2A


Error

Apply-to entry could overrule specific item tracking.The posting routine will check that the item tracking on the applied item ledger entry match what is defined in the item tracking for the posted line.


Codeunit 22 Item Jnl.-Post Line Service System reference: ES-499-256-4ECX

A563) Item Tracking Lines Not Deleted

Error

Item Tracking lines were left over in the Reservation table if the Entry Type field was changed on an Item Journal line.


Codeunit 99000835 Item Jnl. Line-Reserve Service System reference: DK-4-426-XH4H


A564) Item Tracking on Credit Notes

Error

If item tracking had been defined on a sales or purchase credit note any change on the line would give an error message.This was due to the receipt date/shipment date being 0D on the line, which the reservation system would react on as an error. The illegal step is in fact to change the date TO 0D - it is not possible anyway to create reservations with an undefined date. The check is changed to react only on the change from a defined date to 0D. A single statement is changed.


Codeunit 99000832 Sales Line-Reserve Codeunit 99000834 Purch. Line-Reserve" Service System reference: DE-643-712-YEA2

A565) Item Tracking With Unit of Measures

Error

If using a UOM smaller than 1 you would sometimes run into rounding differences which would eventually block the invoicing of the sales or purchase order.The error was due to an internal remaining quantity not being zero.The problem is solved with a patch in the existing rounding adjustment procedure.


Codeunit 6500 Item Tracking Management Service System reference: US-621-874-3MLX

A566) Planning with Sales Blanket Orders

Error

The Sales Blanket Orders were sometimes ignored by the planning calculations.


Report 99001019 Calculate Plan - Plan. Wksh. Service System reference: NL-457-377-5J9F

A567) Incorrect Result When Running the Req. Worksheet for Item Set Up without Reorder Point

Error

When you set up an item using reorder policy Fixed Reorder Qty. or Maximum Qty.

And you set 500 as Safety Stock and the Reorder point was left as zero

And you ran the Requisition Worksheet calculate plan, you got no lines.


Service System reference: HQ-184-346-LLKB


A568) Basic Supply Planning

Error

No planning lines, when qty on stock is lower than reorder point


Service System reference: DE-164-213-QKAQ

A569) Output on the Last Operation Could Be posted with no Gen. Prod. Posting Group

Error

Output on the Last Operation will always will always have a Gen. Prod. Posting Groups assigned to it.


Codeunit 22 Item Jnl.-Post Line Service System reference: DE-334-151-UMEL

A570) Applying an Output to a Consumption on the same Item on a Production Order caused WIP accumulation

Error

Output and Consumption applied on the same Item on a Production Order will no longer be allowed.


Codeunit 22 Item Jnl.-Post Line Service System reference: DK-205-527-JJWS

A571) Production Order Status Field in Posted Entries

Error

"If two production orders exist with the same number, one finished or released and the other not released yet then their might confilct."


Table 5118 Search Word Detail Table 39 Purchase Line Table 123 Purch. Inv. Line Table 121 Purch. Rcpt. Line Table 99000853 Inventory Profile Form 99000914 Change Production Order Status Form 99000816 Machine Center Task List Codeunit 5836 Cost Calculation Management Codeunit 99000813 Carry Out Action Codeunit 99000778 OrderTrackingManagement


Service System reference: HQ-82-868-AE8N

A572) The Prod. Order Line did retrieve the Unit Cost from the SKU if there was one setup. COD5406

Error

The Prod. Order Line retrieves Unit Cost from the Item if there isn't one set on the SKU


Codeunit 5406 Output Jnl.-Expl. Route Service System reference: DE-725-451-9TR5

A573) The Expected Operation Cost and the Expected Capacity Ovhd. Were Not Updated

Error

The Expected Operation Cost and the Expected Capacity Ovhd. on the Prod. Order Routing Line were not updated for work centers with Unit Cost calculation = Time and the Unit Cost Per was changed. Work Center calendar is now calculated on the Unit Cost per validate trigger in Table 5409


Table 5409 Prod. Order Routing Line Service System reference: US-677-466-QTQZ

A574) The Test Report for the Consumption Journal Did Not Report Items Not on Inventory

Error

The test report for the Consumption Journal did not provide a warning of items not in inventory. Thus, the user might run the posting of the Consumption Journal unaware that it would not run to the end.


Report 702 Inventory Posting - Test Internal Workbase reference: 1C43969A4502B3D9412567BA00470995

A575) The Mat. Requisition Report Included Make-To-Order Items on the Main Item’s BOM

Error

When a main item had a BOM with Make-To-Order items, the Make-To-Order items were reported when running the Mat. Requisition Report.



Report 99000765 Mat. Requisition Internal Workbase reference: 78A0FC0D90909545412567AF00481615

A576) It Was Possible to Certify a BOM or Version BOM with “Type” = “Item” and Without an Item Number Present in the No. Field

Error

In a BOM or Version BOM, it was possible to insert a line with “Type” = “Item” without an item number in the No. field. When creating a production order using such a BOM, the message “Item No. doesn’t exist” appeared.


Table 99000771 Production BOM Header Table 99000779 Production BOM Version

Internal Workbase reference: 7FC8EBBEFC694CDA412568AA0057760F

A577) Creating Production Orders from Sales Orders Resulted in the Wrong Quantity Information for Project Orders

Error

Due to errors in the conversion of the UOM, when creating production orders from sales orders using the Project Order option on Sales Order lines having a UOM different to the base UOM, the wrong values appeared in various Quantity fields of the Production Orders. For example, errors were present on the Remaining Quantity field on the Production Order line and the Expected Quantity field and the Remaining Quantity field on the Production Order Components line.


Codeunit 99000787 Create Prod. Order Lines Internal Workbase reference: E1E415CC00164DAF4125689A004D74A6

A578) Where-Used Did Not Show the Correct Items When Items Had Starting- and/or Ending Dates

Error

When using Starting- and/or Ending Date fields on BOM items, the Where-Used function showed the opposite of what was the case. For example, if a BOM item had a Starting Date after the Working Date, the Parent Item of this BOM was shown on the Where-Used list.


Codeunit 99000770 Where-Used Management Internal Workbase reference: DE8AF504C3DE7792412568500037E442


A579) After Changing Standard Task Code on the Prod. Order Routing Line, Related Information Could Not Be Seen

Error

When changing Standard Task Code on the Prod. Order Routing line, related information for that Standard Task code, for example, Tools and Personnel, could not be seen.


Table 5409 Prod. Order Routing Line Service System reference: HQ-953-301-HENG Internal Workbase reference: 2EE5DF31256DFAA5C1256BB3003E0EA8

A580) Document No. Was Not Copied Automatically on the Consumption and Output Journal

Error

When a number series was selected for the batch name for the worksheet and then, later, when the Consumption and Output Journal was filled out using Calculate Consumption, the number series was not copied automatically to the lines in the worksheet – as it should have been.


Report 5405 Calc Consumption Service System reference: DK-785-837-KEFY Internal Workbase reference: 3E1214A8441B3DB6C1256B9F0049B636

A581) Work Center Load / Bar and Machine Center / Bar Displayed the Bar (Load) Incorrectly

Error

When running the Work Center Load / Bar and Machine Center / Bar reports the bar (load) was displayed incorrectly


Report 99000785 Work Center Load / Bar Report 99000786 Machine Center / Bar Service System reference: SE-914-731-PLYC Internal Workbase reference: 20CBC062D8B1A40AC1256B8700375F2B

A582) The BOM Version Number Was Not Correctly Updated When Running Exchange Production BOM Item

Error

When running Exchange Production BOM Item, the new versions of the BOMs containing the updated item were always given the consecutive numbers 1, 2... However, if a No. Series for the Version Number was defined, it was ignored.



Report 99001043 Exchange Production BOM Item Internal Workbase reference: 5A5B1989413B3073412568D40049046D

A583) Subcontracting Worksheet Refreshed Incorrectly

Error

When creating a new Subcontracting Worksheet, a line from the old Subcontracting Worksheet appeared erroneously.


Form 99000886 Subcontracting Worksheet Service System reference: ES-393-127-FFSZ Internal Workbase reference: 293E50BCE4240DDAC1256B6100407A6F

A584) Lookup on Product Orders Routing Caused Problems

Error

When changing the routing number on the Routing card, performing a lookup on Production Orders using that routing caused different referential problems.


Table 99000763 Routing Header Service System reference: DK-616-731-UF5K Internal Workbase reference: B31BF6C452BADFF5C1256B590042110F

A585) A Dimension Warning Appeared on the Production Order When Not Using Dimensions

Error

When changing status from planned to released production order in a company with no dimensions, the following erroneous warning appeared: “This shortcut dimension is not defined in the general ledger setup”.


Codeunit 408 DimensionManagement Codeunit 5407 Prod. Order Status Service System reference: SE-664-275-RGST Internal Workbase reference: 9F145603B2080B3BC1256BEB00409D15


A586) Descriptions Fields on the Planning Worksheets Form Did Not Update When Changing Company

Error

When changing company, the Item Description and Routing Description fields on the Planning Worksheets were not updated.


Codeunit 330 ReqJnlManagement Codeunit 99000812 PlanningWkshManagement Form 990000851 Planning Worksheet Internal Workbase reference: 16BD90E3C4365C704125699900488755

A587) When Running Report 99001043, the Last Date Modified on the Production BOM Version Was Erroneously Set to “Work Date”

Error

When running report 99001043 Exchange production BOM Item, the Last Date Modified on the Production BOM version was erroneously set to “Work Date”. It should have been “Today”.


Report 99001043 Exchange Production BOM Item Internal Workbase reference: 54DC094B15B88F5B4125685E00379AB7

A588) Report 99000787 Did Not Print Routing Versions

Error

Report 99000787 did not print routing versions: only the routing header was printed, not the actual active routing version.


Report 99000787 Internal Workbase reference: EDBA1CA2F5B6ABFE412567B60056FEAA

A589) Error in Backwards Flushing

Error

"When finishing a released production order which only had posted full output on the last operation on the route in the Output Journal, components on the BOM having flushing method ""backwards"" didn't post comsumption. Thus, Remaining Quantity for backward flushing components on the BOM for the finished production order was not 0 as it should be."


Codeunit 408 DimensionManagement Codeunit 5407 Prod. Order Status


Service System reference: DK-953-247-ZHRY

2.11 Cap. Reqts. Planning

Errors fixed

A590) The "Task List" menu on the Work Center List form looked up the Machine Center Task List

Error

Wrong Lookup: Form 99000916 Machine Center Task List replaced by Form 99000915 Work Center Task List.


Form 99000755 Work Center List Service System reference: HQ-952-445-TKA6

A591) Calendar Shift Overlap

When user inserted a new record which overlaped with another record an error message was correctly displayed. But the user could rename the record without this check. This has been corrected.


Table 99000752 Shop Calendar Service System reference: GB-620-467-FG6U

A592) Forward Replanning of Production Orders

Error

It was not possible to replan a production order with forward scheduling. The setting in the request form was not used.


Rep 99001026 Replan Production Order Service System reference: HQ-213-630-QHRF


A593) Concurrent Capacity in Standard Cost and Expected Cost

Error

Now the Expected Cost of a production order is similar to the Standard Cost of the item. When "Concurrent Capacities" from Routing Line = 0 then "Concurrent Capacities" is set to 1 on Prod. Order Routing Line.


CodeUnit 99000773 Calculate Prod. Order Service System reference: HQ-53-560-QGLV

A594) Expected Cost and Concurrent Capacities

Error

The Expected Cost was not affected by Concurrent Capacity. It should multiply the setup cost by the number of concurrent capacities.


Codeunit 99000774 Calculate Routing Line Service System reference: HQ-60-23-RB9C

A595) [Planning parameters Maximum Inventory and Reorder Point were not handled correctly.

Error

In COD 99000855 adjustments of invalid settings have been added to protect the planning engine against illogical setups of planning parameter values. In COD 99000854 a new functionality has been added to keep track of the current inventory level. This functionality is used in connection with Maximum Inventory and identification of reorder point violations.


Codeunit 99000854 Inventory Profile Offsetting Codeunit 99000855 Planning-Get Parameters Service System reference: DE-830-691-TE69]

A596) [Planning parameters Maximum Inventory and Reorder Point were not handled correctly.

Error

In COD 99000855 adjustments of invalid settings have been added to protect the planning engine against illogical setups of planning parameter values. In COD 99000854 a new functionality has been added to keep track of the current inventory level. This functionality is used in connection with Maximum Inventory and identification of reorder point violations.


NB: Scenario no 1 will lead to the creation of two planning lines: First one 50, triggered by the fact that we are below reorderpoint from the very start. This line will be backward scheduled from the planning date. Second one 30, triggered by reorderpoint violation caused by the sales order. Will be forward scheduled from the SO shipment date.


Codeunit 99000854 Inventory Profile Offsetting Codeunit 99000855 Planning-Get Parameters Sevice System reference: GB-510-243-YFJY]

2.12 Resources

Errors fixed

A597) Not Possible to Enter the Value 'ALL' in the Suggest Res. Price Chg.(Price)

Error

The first time report 1192 was opened the fields Work Type and Job No. had the value 'ALL' but when it was changed the user was not allowed to enter 'ALL' due to a table relation validation.


Report 1192 Suggest Res. Price Chg. Service System reference: HQ-708-108-CPUU

A598) Source Type and Source No. in Resources

Error

When posting a Resource sale. the Res. Ledger Entry was not linked to the involved customer as it is with item posting.


Table 203 Res. Ledger Entry Table 207 Res. Journal Line Codeunit 80 Sales-Post Codeunit 202 Job Jnl.-Post Line Codeunit 212 Res. Jnl.-Post Line Report 1198 Date Compress Resource Ledger Service System reference: HQ-139-869-CP5K


A599) There Was a Maximum Value for the Indirect Cost % Filed on the Resource Table

Error

The Maximum Value property was set to 100 for the Indirect Cost % and the Profit % field on the Resource table (156). This has now been changed so that there is no maximum for either of these properties.


Table 156 Resource

Service System reference: DK-384-760-7HEJ

A600) Job No. Included in the Show Column Fields in the Resource Journal Form

Error

In the Resource Journal form (207), the user could select the Show Column function for the Job No. field. However this filed was not necessary, because the job usage can only be posted from the Job Journal window.


Form 207 Resource Journal Service System reference: DK-415-621-WKNH

A601) The Resource Title Field Was Incorrect

Error

The “Title” field in the Resources table was incorrect. It has been changed to “Job Title”.


Table 156 Resource Codeunit 5200 Employee/Resource Update Internal Workbase reference: CCD4DFECB3711952C12564B5004DC70B

A602) Error in the Resource - Find Cost Codeunit

Error

There was an error in the function "FindResUnitCost" in the Resource - Find Cost codeunit (220). The code was:


IF GET("Cost Type"::Fixed,Code,"Work Type Code") THEN

EXIT;

Res.GET(Code); IF GET("Cost Type"::"% Extra",Res."Resource Group No.","Work Type

Code") THEN

EXIT; IF GET("Cost Type"::"LCY Extra",'',"Work Type Code") THEN

EXIT;

It has been changed to:

IF GET(Type::Resource,Code,"Work Type Code") THEN

EXIT;

Res.GET(Code); IF GET(Type::"Group(Resource)",Res."Resource Group No.","Work Type

Code") THEN

EXIT; IF GET(Type::All,'',"Work Type Code") THEN

EXIT;


Codeunit 220 Resource-Find Cost Service System reference: DK-897-352-HCJ9

A603) Some Text Fields in the Resources Table Were Only 20 Characters Long

Error

The Education and Contract Class field in the Resources table (156) could only contain 20 characters.


Table 156 Resource Internal Workbase reference: B0A8E16794C53A53C1256443002783D5

A604) Incorrect Property on the Resource - Price List Report

Error

On the Resource - Price List report (1115) the property HorzGrid was not set to 210, like the other "out of the house" reports.


Report 1115 Resource - Price List Internal Workbase reference: 673EE32FDB2DBA01C125667A00490F91


A605) Inconsistency in Resource Journal and Recurring Resource Journal

Error

The “Account Name” field in the Recurring Resource Jnl. form (290) was incorrect. It has been changed to “Resource Name” as in the Resource Journal form (207).


Form 290 Recurring Resource Jnl. Internal Workbase reference: B206649BA20564A7C12564B5003A2B8F

2.13 Jobs

Errors fixed

A606) Overflow Error in the Job Journal When Posting G/L Account

Error

When posting a job journal to a G/L account the Job Posting Group field was set to the G/L account number, but the two fields were not of same length.


Table 169 Job Ledger Entry Table 210 Job Journal Line Service System reference: IT-968-849-FMD8

A607) Correction to Print Preview Modifying the Database

Error

The application would post entries in the general ledger and modify Job Ledger Entries, even if the user clicked Preview for the Post Job Recognition to G/L report (1213). Some users may have expected the program only to post if the reports were physically printed - not just previewed. On the other hand, other users may require posting in both cases. This has been changed with a Post checkbox like the report Post Inventory Cost to G/L. Should the defualt value be No? Unless the user ticks this checkbox, the report will not post anything in the database.


Report 1213 Post Job Recognition to G/L Report 1214 Post Job WIP Value to G/L Service System reference: HQ-839-747-CRKP


A608) Naming in Jobs

Error

The option Template in the field Job Status was incorrect for the Job Budget entry table (211). Template is changed to Planning to the corresponding value in the Job table (167).


Table 211 Job Budget Entry Service System reference: HQ-412-993-CP63

A609) Incomplete CalcFormula for the Budgeted Res. Gr. Qty. field in the Job Table

Error

The field Budgeted Res Gr. Qty. did not filter to only include Resource Groups.


Table 167 Job Service System reference: HQ-547-832-CPX2

A610) Job No. Field was Blanked Out

Error

The problem was that when opening job budgets from the Planning button on the job card, the Job No. field was grayed and blanked out.


Form 212 Job Budget Service System reference: HQ-121-984-CPV7

A611) Job Budget Line - Quantity, Unit Price and Total Price Were Not Updated Correctly

Error

When changing Unit price or Cost indirectly, totals was not recalculated.


Table 168 Job Budget Line Service System reference: DK-400-351-QN6C


A612) Dimensions Missing When Posting Job Journal From Own Code

Error

When some functionality posted indirectly to the job module,Codeunit 202 could cause dimensions missing.


Codeunit 202 Job Jnl.-Post Line Service System reference: DK-962-44-BFCR

A613) Unit Cost Not Filled in Job Ledger Entry When Posting Purchase Line

Error

Unit Cost was not filled in job ledger entries when posting a purchase line with a Job No.


Codeunit 90 Purch.-Post Service System reference: DE-745-114-4DMT

A614) Job Journal and Item Ledger Entries

Error

If you tried to post sales before usage, and then tried to apply the usage to the sale, you would end up with an incorrect stock situation, because the program had made two general ledger entries.


Codeunit 12 Gen. Jnl.-Post Line Internal Workbase reference: 2A4CCC2E098C40B1412569430046AE8B

A615) Triple Availability Check in Job Journal Line

Error

If you created a job journal line for an item that had no quantity in stock, you got the availability message three times.


Table 210 Job Journal Line Service System reference: DE-599-75-2FVM


A616) Unable to Enter Job Budgets

Error

If you created a new job budget line with a G/L Account, you got a permission error.


Table 168 Job Budget Line Service System reference: GB-367-693-KDF3

A617) Job Description Was Not Updated in Job Journals

Error

After deleting a job journal, the Job Description field in the lower left corner still showed the old job description.


Codeunit 280 JobJnlManagement Service System reference: DE-40-541-LK4H

A618) ItemJnlLine.Amount Was Assigned Twice in the Job Jnl. -Post Line Codeunit

Error

ItemJnlLine.Amount was assigned twice in the Job Jnl. –Post codeunit (202). The second assignment now overrides the first.

ItemJnlLine.Amount := JobJnlLine2."Total Cost";

ItemJnlLine."Applies-to Entry" := JobJnlLine2."Appl.-to Item Entry";

ItemJnlLine."Department Code" := JobJnlLine2."Department Code";

ItemJnlLine."Project Code" := JobJnlLine2."Project Code";

ItemJnlLine."Transaction Type" := JobJnlLine2."Transaction Nature Code";

ItemJnlLine."Transport Method" := JobJnlLine2."Transport Method";

ItemJnlLine."Entry/Exit Point" := JobJnlLine2."Entry/Exit Point";

ItemJnlLine.Area := JobJnlLine2.Area;

ItemJnlLine."Transaction Specification" := JobJnlLine2."Transaction Specification";

ItemJnlLine."Country Code" := JobJnlLine2."Country Code";

ItemJnlLine."Unit Amount" := JobJnlLine2."Unit Price"; ItemJnlLine.Amount := JobJnlLine2."Total Price";


Codeunit 202 Job Jnl.-Post Line Internal Workbase reference: 266BE5A9A5ED75FA412568490040F67F


A619) Naming in Jobs

Error

The “Template” option in the Job Status field was incorrect in the Job Budget Entry table (211). “Template” has changed to “Planning” so it matches the corresponding value in the Job table (167).


Table 211 Job Budget Entry Internal Workbase reference: CEC99D940528021FC125652300401154

A620) Ending Date Was Not Taken into Account in the Date Compr. Job Budget Entries Report

Error

If you filled in the Ending Date field in the Date Compr. Job Budget Entries report (1297), the program ignored the ending date.


Report 1297 Date Compr. Job Budget Entries Internal Workbase reference: 9EB8D8144F9D89E94125698A003EB1D7

A621) No Header on Page 2 of the Job Register Report (1203)

Error

There was no header printed on page 2 of the Job Register report (1203).


Report 1203 Job Register Internal Workbase reference: AB2D35FF41B3B853C12564AA002E02D8

A622) Overlapping Controls on the Recurring Job Jnl. Form (289)

Error

There were buttons hidden under the Functions and Posting buttons on the Recurring Job Jnl. form (289).


Form 289 Recurring Job Jnl. Internal Workbase reference: 4CA97C0EEF564E894125692200505F8D


A623) Job No. Was Not Editable on Resource Journals

Error

The Job No. field was not editable on the Res. Journal Line table (207).


Table 207 Res. Journal Line Internal Workbase reference: 21FBA268962754C1C125660C005D2D4B

2.14 Human Resources

Errors fixed

A624) Employee Relative Comments Did Not Get Deleted

Error

When you deleted an employee relative, the comments for that relative did not get deleted.


Table 5205 Employee Relative Internal Workbase reference: 3C028BE6155AA29A4125677D004A0FEC

A625) Sorting Problem in the Misc. Article Information Form

Error

In the Misc. Article Information form (5219), if you made several lines with the same misc. article code for the same employee, you got the following error message: "The Misc. Article Information already exists".


Table 5214 Misc. Article Information Form 5219 Misc. Article Information Internal Workbase reference: 427E7157CB0FE78F412568E2003822B8

A626) Resource Specific Unit of Measures as in Items

Issue

Resource postings in different Units of measures needed a general measure when totals was created.


This issue has been implemented

Table 37 Sales Line Table 156 Resource Table 203 Res. Ledger Entry Table 205 Resource Unit of Measure Table 207 Res. Journal Line Table 210 Job Journal Line Form 76 Resource Card Form 92 Job Ledger Entries Form 210 Resource Units of Measure Report 1105 Resource Statistics Report 1106 Resource Utilization Report 1198 Date Compress Resource Ledger Codeunit 80 Sales-Post Codeunit 202 Job Jnl.-Post Line Codeunit 212 Res. Jnl.-Post Line Codeunit 7000 Sales Price Calc. Mgt. Sevice System reference: HQ-812-80-UK59

2.15 Commerce Portal

Features

A627) Feature Request - Button To Next Documents In Search

Feature

The DocSearch.asp is made more user friendly; now the user may enter 5 digits in the No. of Records to Show field. Also previous and Next buttons have been added, plus a list of the pages generated as we have it in other parts of the site."


DocSearch.asp Service System reference: HQ-957-507-CRAV

A628) Image Selector able to handle more file type than jpg/gif

Feature

The Image Selector can now handle any type of picture (or file).


Service System reference: HQ-874-748-CRLM


Errors fixed

A629) Missing menu bullet "Register New Customer" in 2. language

Changed webpage property for Localmenu,Sales Person,Menu,Register New Customer, Activity code. Here the 2. language e.g. CPL needs to change to 10053 instead of 10101.


Service System reference: DE-991-209-WL4M

A630) Posted drop shipment not synchronized

Error

By triggering the OnInsert Trigger for the SalesShptHeader in Codeunit 90 - Purch.-Post, the synchronization of the record is guaranteed


Codeunit 90 - Purch.-Post Service System reference: DE-720-792-5LCE

A631) Customer Credit Limit is not synchronized to Navision

Error

The "Customer" Procedure in the Codeunits that handles the Decoding of XML documents contained an EVALUATE instruction for the CUSTOMER_CREDIT_LIMIT tag. It has been replaced by the appropiate call in the Conventions codeunit, so computer locale doesn't play a role when interpreting numbers.


COD6226 Service System reference: HQ-153-471-6G24

A632) Contact Data Inherited From Company Contact

Error

When a new Web Portal User is registered from the WebSite, procedure CreateWebPortalUser is invoked in COD6219 - Contact Management. In this procedure, contact data is validated but Company No. must be validated before communication data, otherwise it will get overwritten.


COD6219 Service System reference: HQ-809-805-SFD6


A633) Fail in Statistics.asp When No Customer Is Selected

Error

A check has been added to ensure that a Customer Number is present before the link to statistics are displayed. If the CustomerNo is not present, the link is not displayed.


Statistics.asp Service System reference: HQ-796-43-3FKC

A634) Fail in Contactlist.asp When No Customer Is Selected

Error

A check has been added to ensure that a Customer Number is present before the link to Contacts is displayed. If the CustomerNo is not present, the link is not displayed.


Contactlist.asp Service System reference: HQ-789-119-3FWF

A635) Minor code optimization have been made in table 5050 Contact - trigger ‘Online User Type’

Minor code optimization has been made in table 5050 Contact - trigger “Online User Type”. There are no changes to logics.


Table 5050 Contact - trigger “Online User Type” Service System reference: DE-473-353-VG2E

A636) Description field empty after submitting bid in reverse auction

Error

RevAuctionInfo.asp is updated not to request the description field from what is submitted in the reverse auction by the vendor. Vendor doesn't submit a description field in the reverse auction, therefore description field value should come from the default reverse aution information.


RevAuctionInfo.asp Service System reference: DE-714-278-4FDQ


A637) Continue buttons in "Saved Shopping Cart"

Error

The demodata has changed like this: LOCALMENU/Customer/Save_basket/saveforlater "saveforlater" cannot have any capital letters.


COD102219 COD102220 Service System reference: HQ-269-284-CQ64

A638) Only 1 NAS with Synchronization can be started

Error

If you try to specify synchronization for more than one Application Server Setup, a warning is issued. By answering yes, it is possible, but not recommended to keep this setup. It can however be useful to have two or more different setups containing synchronization when they are used exclusively as alternatives.


Service System reference: HQ-952-990-CPQ7

A639) Timeout of Synchronizations

Error

If a new customer was registered from the Web site, you got a timeout error that synchronization service didn't run or was busy after a long time.


MQ.asp Service System reference: HQ-516-454-CRMG

A640) No Permission Check For Vendor Role

Error

If you logged on as a vendor, permission was missing many places, and changing the permission in Navision for a vendor contact didn't have any effect on the Website.


v_account.asp Service System reference: HQ-738-647-CQ5Z


A641) problems with default language

Error

Changed Len(userinfo_UserLang) > 0 to userinfo_UserLang <> " ".".


Service System reference: SE-644-918-5G9D

A642) Rejected Quote on Web Site

Error

It was not possible to see if the status for a quote was rejected on the Web site.


Orders.asp Service system reference: HQ-344-865-CRP6

A643) Change User Data As An Sales Person Didn't Work

Error

When you logged on as a sales person, chose customer, and tried to change user data; no users were listed for the customer.


Service System reference: INT-735-755-3V5F

A644) Some new PROCESS_TYPEs are not going to the Attain Message Log

Error

In order to ensure correct update of the Message Log, these command names are inserted into table Message Log Setup: CREATEWEBPORTALUSER DELETECUSTOMERDELETEWEBPORTALUSER READCONTACTINTERACTIONS READCONTACTORDERS READCONTACTTODOS READCUSTOMERSTATS READCUSTORDERS READPOSTEDRETURNRECEIPT UPDATEWEBPORTALUSER


Service System reference: HQ-335-52-CQJF


A645) Paging on customermain.asp

Error

On customermain.asp there was no support for paging so if you had a big catalog you would see all products on one page.


customermain.asp Service System reference: INT-899-410-3V4U

A646) Search Function in My Account Must Handle Permissions

Error

In My Account it is possible can search order, quote, shipment etc. no matter whether you have the apropriate permission.


Service System reference: HQ-484-538-CQ63

A647) The Button: Check Here to Create a Sales Order - Possibility Should Be a Permission

Error

We already have the permission 10006 Create Sales Quote and 10007 Create Sales Order. A button Accept Quote has been added to the processorder.asp page. Now both buttons are checked for permissions. If you have permission 10006 the button "Accept Quote" is displayed. If you have permission 10007 the button "Purchase" is displayed. The next page, and last in the check out process, now checks which button was selected by the user. A click on "Accept Quote" sends an ACCEPTQUOTE xml to Navision. A click on "Purchase" sends an CREATESALESORDERFROMQUOTE xml to Navision. If neither was clicked an error message is displayed. The old checkbox Click here to Create Order has been deleted.


processorder.asp Service System reference: HQ-125-757-CPFN


A648) Missing Date Format Label

Error

The new pageproperty is entered in Navision and the label is diaplyed at each date field.


VendoritemsInfo.asp Service System reference: HQ-33-974-CR7D

A649) Text Hardcoded in CommerceDisable Function in Contact Table

Error

In table 5.050 in function CommerceDisable there is a hard coded error message.


TAB 5050 Contact Service System reference: HQ-874-493-CQCE

A650) Account Still Open On Web Site Although Deleted In Navision

Error

When a contact in Navision was deleted, the account was still open on the Web site.


xt_checkuser.asp Service System reference: HQ-726-259-CPW3

A651) Security Bug in Role Concept

Error

Users could get gain access to confidential information without having the proper authorization. This has been corrected. Now, the full primary key is used to test if the user has access rights to the particular page.


Service System reference: DE-379-421-ZJHG

A652) Problems with the Synchronization on the SQL-Server Caused by a Missing COMMIT in Commerce Portal 3.60.

Error

In Navision 3.10, the mentioned COMMIT used to exist OUTSIDE the loop that puts the messages into the actual queue. That presented the inconvenient of not deleting the


messages from the Navision table until the end of the transaction, and for a synchronization of a large size that could mean a memory error. For Navision 3.60, in order to solve that problem, a COMMIT was introduced inside the loop. That made apparently, the outter COMMIT irrelevant, so it was removed. Given that experience in real life scenarions has shown that the presence of the outter COMMIT brings performance benefits, it has been reintroduced (without removing the inner COMMIT, of course).


COD6208 Service System reference: DE-468-334-SFBZ

A653) Missing CASE-Command in RevAuctions.asp

Error

CASE-command implemented to handle status=0 and status=3 when presenting the revers auction list, so everything is aligned and presented nice, on the CommercePortal website.


RevAuctions.asp Service System reference: DE-915-13-FBVN

A654) Search Function Ignores Catalog Sets

Error

Results.asp has been modified to only search in the Commerce Server catalog sets assigned for authentic users when an authenticated user activates a search from the Web site. This includes anonymous users.


results.asp Service System reference: DE-948-4-4G27

A655) Incorrect Coding on OnValidate Trigger for table 5050

Error

Minor code optimization in table 5050 Contact - trigger "Online User Type". No change to logics made.


5050 Contact Service System reference: HQ-127-855-CQKW


A656) Create Ship-to-Address Appeared Incorrect in Commerce Portal although It Was Correct in Navision

Error

When updating a Ship-to address from the Web, the used name in the updating command is synchronized back to the SQL Server.


Service System reference: HQ-134-453-CRB8

A657) Incorrect Synchronization of Table 124 Purch. Cr. Memo Header

Error

When posting a sales credit memo, it is synchronized to the SQL Server.


Service System reference: HQ-162-882-CPKB

A658) Could Not Delete Page Property

Error

It is now possible to delete a Web Page (Page property collection) even if it is defined by a template. When all page property collections related to a template were deleted, the template could be deleted.


Service System reference: HQ-203-904-CRRM

A659) No-CC-Required Permission Not Used

Error

Permission check for 10055 inserted in orders.asp The orders.asp page now checks whether the user has permission to order without a credit card. If this is the case, and the user is allowed to create a sales order, the option to do so is displayed.


orders.asp Service System reference: HQ-214-722-CR6K


A660) Reverse Auction and E-mail Notification Missing Filter

Error

In COD6203 - Notification Management, in procedure SendRevcAuctLostMail, a filter was missing to prevent the winning bidder in the reverse auction to get the mail sent to those vendors whose offering wasn't made into an order.


COD6203 - Notification Management Service System reference: HQ-244-466-CQTB

A661) Changing Catalog for a Contact Didn't Show on Web Site.

Error

In the xt_checkuser.asp, a Profile.GetInfo() call has been made. This updates the profile with the lastest changes. I.e a change of CatalogSets and deletion of contacts is updated.


checkuser.asp Service System reference: HQ-264-967-CQAY

A662) Page Property Collection Descriptionnews Removed

Error

Page Property Collection descriptionnews was removed from Web Pages and Web Templates in demo company CRONUS International Ltd.


Service System reference: HQ-29-348-CRTU

A663) Some New PROCESS_TYPEs Were Not Going to the Navision Message Log

Error

In order to ensure correct update of the Message Log, these command names are inserted into table Message Log Setup.


Service System reference: HQ-335-52-CQJF

A664) Extra Text Lines in Webshop Were Not Removed from SQL Table

Error

When deleting an Extended Text Header, deletion of all related Extended Text Lines were not synchronized to the SQL Server.



Service System reference: HQ-368-493-CPSV

A665) When Reordering a New Item Basket was Not Updated

Error

If you logged on as customer and clicked reorder in local menu, items added to shopping cart didn't update the basket.


reorder.asp Service System reference: HQ-837-347-CR74

A666) Problem with Order Addresses

Error

1) It was not possible to make an order address with more than 10 characters in the code field; it would fail with "No reply received from Navision".

2) When deleting an order address, the page returns in blank without links, only a header to tell the user to create new address.


Maintain_address.asp Service System reference: HQ-73-64-CPZR

A667) Field Validation In basket.asp

Error

If an invalid value was typed in the quantity field in basket.asp an error message should be displayed and the field value changed to "1". This did not happen.


basket.asp Service System reference: HQ-903-519-CQQ7

A668) Contact Name Was Changed When Creating Commerce Portal Password

Error

When assigning a new password to a contact through the Contact Card, the contact's name was overridden with the company name. Now only if the Name field is blank when the password is assigned, then the field is filled out with the related company- or sales person name.



Service System reference: HQ-425-875-YGNE

A669) Was Not Possible to Search for Serial No. with Wild Card

Error

General optimization The routine for returning documents containing a specific serial no. has been optimized. Wild card serial no. search Now it is possible to do a wild card search for a serial no. E.g. search for 12*. All sales documents related to this serial no. / customer are returned. The returned XML Document now includes a SERIAL_NO element containing the actually found serial no. Handling of Return Receipts It is now possible to handle Return Receipts in the same way as Sales Shipments. They are now synchronized (Type = 3) and it is possible to send a 'READPOSTEDRETURNRECEIPT' command to read a specific posted Return Receipt. Furthermore when searching for a specific serial no. they will show up instead of posted Credit Memos if the Sales Setup specifies "Return Receipt on Credit Memo".


Service System reference: HQ-468-814-CQ9H

A670) Changing Company Information from Web Site Didn't Update Company Contacts

Error

Changing the adress of a customer or vendor on the Web site would change the adress fields in the customer/vendor table in Navision, but not in the contact table. The MODIFY triggers in the Customer (TAB18) and Vendor (TAB23) tables compared the values in xRec and Rec before updating the related contact. The problem with this sequence of actions was that each call of a VALIDATE trigger from outside the table, updates the xRec variable and therefore the comparision never found a difference.


Service System reference: HQ-483-684-CQDC

A671) Web Site Returned Error When Basket Was Saved for Later

Error

When the OrderForm object wasn't initialized at an earlier stage then an error occured; the program tried to access an object that didn't exist.


Service System reference: HQ-516-954-CQTN


A672) When Creating a New User From Web Site An Extra Contact Was Created

Error

When you registered a new customer from the Commerce Portal Web site, a new customer was created in Navision, together with two new contacts.


Service System reference: HQ-557-697-CQDK

A673) Not Possible to Distinquish between Requested and Accepted Quotes

Error

A new message has been added to the page informing the user that a quote will be created. The user will see this : "By clicking Continue > a quote is created. Later you have the opportunity to accept or reject this quote."


Service System reference: HQ-597-275-CR6M

A674) Date Handling and Multilanguage

Error

The format for displaying dates on the Web site can now be controlled from within Navision. Languages enter the Windows Language ID to be used to format dates for the current Language Code. This field is now synchronized to the SQL Server. Under Commerce Portal Setup it is also possible to specify the Windows Language ID for the specified default Language Code. This is also synchronized. All Windows Language ID's are now filled out in CRONUS Company.


Service System reference: HQ-624-857-CR7J

A675) Missing Multilanguage Captions

Error

In Report 6297 Create Reverse Auctions the "Vendors to Include" option on the request form is now multi-language enabled.


Service System reference: HQ-717-141-CQ4W


A676) Updating Contact Field for Customer Blanks Field in Navision

Error

When the contact field was updated on the Web site, the corresponding field in Navision was changed to company name.


Service System reference: HQ-718-471-CRTV

A677) When To Update/Clean Out Basket in Order Process

Error

Once the quote is created the basket should be removed. The quote is created when the page ProcessOrder.asp is loaded (before content of the page is displayed). If the quote is created then the MSCS basket is cleared. (before it was not cleared at this stage but on the next page (placeorder.asp)). This change also helps solve this issue where a new quote is created if the user selects refresh in the frame. If the user selects refresh now, then the basket is detected empty and a message is displayed with a link to the OrderInfo page where the quotes may be searched.


Service System reference: HQ-749-819-CQ8Y

A678) Remove Filter for E-Mail Status

Error

On form 6210 the field No. of Unprocessable E-Mail Msgs. Has changed to CaptionML=ENU=No. of Unprocessable E-Mail Msgs. It now shows all e-mails in the queue not only unprocessable.


Service System reference: HQ-779-186-CRLR

A679) Text Hardcoded in CommerceDisable Function in Contact Table

Error

In table 5.050 in function CommerceDisable, there was a hard coded error message. Text constants added.


Service System reference: HQ-874-493-CQCE


A680) Deleting of Page Property Does Not Delete Multilang.

Error

When a Web Page was deleted, the related compiled "Comp. Prop. Multilang." were not deleted as well. Additionally a delete command was not synchronized with the SQL Server.


Service System reference: HQ-923-897-CQ3V

A681) Problems With Default Language In Web Site

Error

All Len(userinfo_UserLang) <> 0 are now replaced with userinfo_UserLang <> " ".


properties.asp Service system reference: HQ-413-726-CQTX

A682) LOGINNAME on Web Site Should Be Changed To Create More User Friendly Welcome Page

Error

In the userinfo.asp a new var is defined userinfo_UserFullname. The variables are assigned the value stored in the profile system under Generalnfo.last_name. In the 3 welcoming pages, the variable is now used to display the full name instead of the loginname. Customermain.asp SalesMain.asp VendorMain.asp Userinfo.asp


userinfo.asp Service System reference: HQ-668-955-CQS4

A683) Refresh Created New Quotes

Error

When the user reached the processorder.asp page of the Web site and selected to refresh the frame in their browser, a new quote was created within Navision.


processorder.asp Service System reference: DK-11-48-FCHL


A684) Missing Multilanguage Captions

Error

In Report 6297 Create Reverse Auctions the "Vendors to Include" option on the request form is now multi-language enabled.


Report 6297 Create Reverse Auctions Service System reference: HQ-717-141-CQ4W

A685) Serial No. page does not show Multilanguage

Error

When you chose 'Search by Serial No' you always got the localized (Dutch) text regardless which language you chose, while in Navision the text in the web pages were filled in right. There is an English text for ENU and a Dutch text for NLD.


SerialNoSearch.asp Service System reference: HQ-902-396-CRB9

A686) No-CC-Required Permission Not Used

Error

Permission check for 10055 inserted in orders.asp


orders.asp Service System reference: HQ-214-722-CR6K

A687) Restructuring of Date handling and multi-language

Error

Changes To the Website Three new functions in UserInfo.asp is implemeted: DisplayDate, DisplayDateTime, getLocale. These use the DataFunctions object from Commerce Server to handle the date's based on the users locale. Every place in the site where a date is displayed the date is wrapped in the DisplayDate. In the reverse auction section the function DisplayDateTime is used. getLocale is used by the two other functions to get the Locale for the current user. Changes to Navision The format for displaying dates on the web site can now be controlled from within Attain.


It Languages enter the Windows Language ID to be used to format dates for the current Language Code. This field is now synchronized to the SQL Server. Under Commerce Portal Setup it is also possible to specify the Windows Language ID for the specified default Language Code. This is also synchronized. All Windows Language ID's are now filled out in CRONUS Company."


UserInfo.asp Service System reference: HQ-624-857-CR7J

A688) Dynamically dimensioning of arrays

Error

The redim of the array is used, and the following has been implemented. Sub SortDictionary(byref oDic) Dim altems() redim altems(oDic.count).


DK-27-119-NEUV

A689) NASMSMQInitialise.EXE and CS2KMSMQInitialise.EXE deletes queues/registry

Error

Previously the two utility tools cs2kmsmqinitialise and nasmsmqinitialise would delete registry information if they had already been executed and if they were given incorrect parameter lists (including empty strings).


NASMSMQInitialise.exe CS2KMSMQInitialise.exe HQ-932-733-CQSW

A690) Avoid Synchronization of Templates in Contacts

Error

In order to avoid having login data in the SQL server for contacts that are used as templates, the following changes have been made: All contacts represented by the Login ID specified in Web Site/ Consumer Contact Tmpl. Or Standard Contact Tmpl. are not synchronized when changes are made to them or their assigned Web Portal Roles. When specifying a Login ID in one of the fields, a new synchronization delete command is created for the contact and the related roles. When removing the Login ID again, a new insert synchronization command is issued. These rules are also used when performing a total synchronization.



Service System reference: HQ-828-440-CP69

A691) Overflow when creating password

Error

In COD6219 - Contact Management, Proceudre CreatePassword, the length of the "LoginID" parameter has been changed from 20 to 30, to be aligned with the length of the corresponding field on the Contact Table.


COD 6219 Service System reference: HQ-507-437-CRLT

A692) Showprop.asp Is Not Used

Error

The showprop.asp is not used anymore and has been deleted.


showprop.asp Service System reference: HQ-640-945-CR6X

A693) No Message Type Makes Message Logging Fail

Error

When Request Logging has been selected for the current Application Server and the current process type used in the XML request did not match any entries in the Message Log Setup List, a new incoming Log Entry was created containing the first used process type in the log. Now log entries are inserted now when the current process type does not match any entries in the Message Log Setup table.


Service System reference: HQ-931-376-CQDU

A694) EXIT Command Without Telling Why

Error

All the EXIT commands following an IF NOT FindNode(...) statement, have been replaced by a multilanguage enabled version of: ERROR("The incoming XML Document doesn't include the required tag TAGNAME");



Service System reference: HQ-321-141-CQ7P

A695) Dates Handles in Different Ways

Error

The functions handling dates have been changed to make it easier to update the handling of dates. Cleaning up: The functions below are changed ->to: cnvDate -> cnvDateFromAttain (now in Transport.asp) cnvDate2 -> cnvDateFromUsFormat (now in Util.asp) cnvDateToSend -> cnvDateToAttain (now in Transport.asp) The date handling in reorder.asp and xt_modifyVendorItems.asp has been replaced with calls to function "cnvDateToAttain". The new names should make it easier to understand what the functions are used for. cnvDateFromAttain (in Transport.asp) converts a date from the Attain Format yyyymmdd to dd/mm/yyyy. cnvDateFromUSFormat (now in Util.asp) converts a date formatted as mm/dd/yyyy to dd/mm/yyyy. cnvDateToAttain (now in Transport.asp) converts a date formatted as dd/mm/yyyy to the Navision Format yyyymmdd. Total changes made in the site For cnvDateFromAttain 28 changes have been made in the site. For cnvDateFromUSFormat 8 changes have been made in the site. For cnvDateToAttain 6 changes have been made in the site. New functionality: In the userinfo.asp file two new methods has been added. The function DisplayDate and the DisplayDateTime. You can use these functions to format the dates so they correspond to the language currently being displayed on the site. The functions use the value stored in the variable “userinfo_userlang”. This value is either the users language or the sites default language. If the users preferred language is supported by the site then it is the users language otherwise it is the site default language. The DisplayDateTime function is used for Reverse Auction (RevAuction.asp and RevAuctionInfo.asp). The DisplayDate function is used when ever a date is displayed in the site (53 different places in the code). The function cnvDateToAttain has been modified to use locale information when converting dates.


Service System reference: HQ-695-377-CQA9

A696) Security Hole in Commerce Portal

Error

The problem is that users can gain access to confidential information that they do not have authorization to. They can edit and delete the information and thereby cause damage to the business of the owners of the information.



Service system reference: DE-37-244-RKXB Service system reference: DE-7-940-RLFT

A697) [COMMIT command reintroduced in codeunit 6208

Error

In Navision 3.10, the command COMMIT in codeunit 6208 was not a part of the loop that adds the messages into the queue. That could result in a memory error when running a large synchronization because the messages were not deleted from the Navision table until the end of the transaction. For Navision 3.60, in order to solve that problem, the COMMIT was made a part of the loop. That made apparently made the COMMIT command placed outside the loop irrelevant, and it was therefore removed. However, tests have shown that the presence of the COMMIT command outside the loop brings performance benefits. It has therefore been reintroduced (without removing the COMMIT command inside the loop).


Service System reference: DE-468-334-SFBZ]

A698) [Minus sign is not displayed for negative amounts on website

Error

The function NFUtilMoney removes minus signs from negative values before displaying them on the website. This function is used every time an amount is displayed on the site. The function has been changed so the minus is not removed anymore.


util.asp Service System reference: HQ-880-52-QGBV]

2.16 Commerce Gateway

Features

A699) Enhanced Transaction Support

Feature

Enhanced Transaction Support has been introduced to provide "immediate" response to clients when sending large documents.


For further description please refer to the "Installation & System Management: E-Commerce Solutions" Manual.


A700) TCPCom

The use of NSComCom and SocketBusAdapter has been replaced with a new .Net component: TCPCom. This is done to provide increased stability. TCPCom is used by the following components CGReqClient.dll, CommerceGateway.dll, and the TCPVBCom. TCPVBCom has been created to expose TCPCom functionality in NAS, since the NAS is COM compliant and not .Net Framework compliant.


A701) Commerce Gateway Broker

Feature

The CG Broker has been created to enable scalability over multiple application servers (NAS) on incoming traffic from MS BizTalk Server. The broker is a .Net service operating between the Application Integration Component (AIC) and the Navision Application Servers (NAS), where it handles assignments of available application servers when requested by an AIC. Installing the CG Broker is optional; the original functionality with a single NAS works as usual. For further description, please refer to the "Installation & System Management: E-Commerce Solutions" manual.


A702) CGRS handles requests from Navision 3.60 as well as 3.70.

Feature

The Commerce Gateway Request Server (CGRS) acts as a proxy server handling requests from the Navision client and passes them on to BizTalk Server. To ease upgrade scenarios with multiple companies, the CGRS is now capable of handling requests from both version 3.60 as well as version 3.70 of a Microsoft Business Solutions-Navision Commerce Gateway installation.


For further description please refer to the following note in the Navision Service System Service System reference: HQ-589-260-3KU7


A703) A version check in CG

Feature

Version check has now been extended to include the communication between the AIC and the NAS.


Service System reference: HQ-151-764-CR7Z

A704) Missing Posting Groups for item when importing product catalog (Demo purpose)

Feature

The following fields have been added to TAB99008513 - BizTalk Partner Setup Header - 40 "Def. Inv. Posting Group"; Code10; TableRelation="Inventory Posting Group" - 91 "Def. Gen. Prod. Posting Group"; Code10; TableRelation="Gen. Product Posting Group" - 99 "Def. VAT Prod. Posting Group"; Code10; TableRelation="VAT Product Posting Group"


FOR99008523 BizTalk Partner Setup COD99008530 Product Catalog Line-Accept Service System reference: HQ-626-34-CQP4

A705) Promissed Delivery Date Support in Commerce Gateway

Feature

A mapping has been made between the following fields, which are filled out under the same principle: PurchaseDoc."Expected Receipt Date" to SalesDoc."Planned Delivery Date"


NavisionSN.xml NavisionSQ.xml NavisionSOC.xml NavisionSO.xml NavisionRSQ.xml NavisionSN_to_PR.xml NavisionSQ_to_PQ.xml NavisionSOC_to_POC.xml NavisionPO_to_SO.xml NavisionRPQ_to_RSQ.xml Codeunit 99008517 XML Document-Create Codeunit 99008518 XML Document-Transform Codeunit 99008520 BizTalk Sales Quote Codeunit 99008522 BizTalk Sales Order Cnfmn. Codeunit 99008524 BizTalk Sales Shipment Notif. Codeunit 99008500 Request for Sales Quote-Accept Codeunit 99008502 Sales Order-Accept Table 99008501 Outbound Sales Document Line Table 99008507 Inbound Sales Document Line


Service System reference: DK-568-734-7H8U

A706) Sent Product Catalogs Were Not Saved

Feature

In the Commerce Gateway solution, all purchase and sales documents sent over the Biztalk Server were saved in a managed way. This means, that Outbound Headers and Outbound Lines are stored in the database (business related data), alongside an Outbound Document record (communication related data9. The Outbound Header has an interface such that it's possible to resend the entire document, in case of a failure, or for any other purposes. The case is different for Product Catalogs, where the lines were saved, and Outbound Documents created, but not a Header for it, making the managing of persisting documents difficult.


New Objects: Table 99008534 - Outbound Product Catalog Hdr. Contains information about the Customer to whom the Catalog was sent, as well as data about the success or failure of the sending as such. Form 99008534 - Unsent BizTalk Prod. Catalog Form 99008535 - Sent BizTalk Prod. Catalog Form 99008536 - Outbound Prod. Catalog Subform Form 99008537 - Outbound Product Catalog List Modified Objects: Codeunit 99008514 - XML Document-Send Codeunit 99008526 - BizTalk Product Catalog Form 335 - Inventory Menu Report 99008500 - Send BizTalk Product Catalog Table 99008511 - Outbound Document Service System reference: INT-455-956-3V6K

Errors fixed

A707) CGTimer.dll Only Installed with the Navision Client

Error

Previously the CGTimer.dll was installed with the Navision Client only, but primarily being used with the NAS. This has been changed so the CGTimer.dll is now installed with both the Navision Client and the NAS.


Service System reference: CH-559-670-CGLP


A708) Missed Mapping for Expected Receipt Date

Error

Shipment date and Expected Receipt Date cannot be directly mapped, that would assume immediate delivery, or at least always within the same day of Shipment. But, the mapping can be made between the following fields, which are filled out under the same principle: PurchaseDoc."Expected Receipt Date" to SalesDoc."Planned Delivery Date"


NavisionSN.xml NavisionSQ.xml NavisionSOC.xml NavisionSO.xml NavisionRSQ.xml NavisionSN_to_PR.xml NavisionSQ_to_PQ.xml NavisionSOC_to_POC.xml NavisionPO_to_SO.xml NavisionRPQ_to_RSQ.xml COD99008517 COD99008518 COD99008520 COD99008522 COD99008524 COD99008500 COD99008502 TAB99008501 Outbound Sales Document Line TAB99008507 Inbound Sales Document Line Service System reference: HQ-93-721-CPQK

A709) In the CGReqClient the returncode '0' is generally used to signal 'Success'.

Error

Previously in all MoveXXX methods (where XXX is 'First, Last, Previous, or Next') '0' was used to signal an error situation like 'Cannot move longer that way'. This has changed to a more ADO-like use of data sets. The move methods have no return value but instead BOF and EOF flags are used, so - In case of an error both BOF and EOF flags are set to true. - In case of success both BOF and EOF are set to false. - Movenext from the last record sets the EOF flag to true and the BOF flag to false. - Moveprevious from the first record sets the BOF flag to true and the EOF flag to false."


Service System reference: HQ-708-408-CQMM

A710) Send product catalog to several partners

Error

Two main changes have been introduced to solve this issue:


1) The primary key of TAB99008534 - Outbound Product Catalog Hdr., has been extended to: Outbound Document No.,Customer No. 2) Procedure SendXMLDocument in COD99008514 - XML Document-Send, has now the following parameters: OutboundDocumentNo,OutboundDocumentType,PartnerNo This to differentiate Outbound Documents according to the Partner to which their are sent to. The change in the SendXMLDocument function implied changes in all the other above mentioned objects.


COD99008508 COD99008512 COD99008514 FOR99008500 FOR99008501 FOR99008509 FOR99008510 FOR99008534 FOR99008535 TAB99008534 Service System reference: INT-402-166-3V6H

A711) Improved NAS performance on Decoding XML Documents for Product Catalogs

Error

Two main changes have been introduced: 1) The previous implementation of the XML DOM Management in the Biztalk Codeunits, made use of the selectSingleNode method on XML objects. That method, uses XPath to locate a particular Node based on a Path, sweeping through the entire XML document. On Large files, this can be costly. With the correction made in COD99008518 - XML Document Transform, the method nextNode() is used instead. It assumes a certain fixed XML Document Structure, but it makes no searches, it simply displaces the current node value. In this codeunit, all calls to FindNode (in COD99008516 - XML DOM Management, the one using selectSingleNode() ), have been replaced with calls to nextNode, assuming a static structure on the incoming XML Document. 2) The previous implementation worked on Nodes in the whole XML document. In the new version, each Item is temporary handled in a separate XML document., where schemas are applied.


COD99008518 Service System reference: HQ-951-426-CQFM

A712) Not able to install CGRS on Windows .Net Server

Error

Previously it was possible to install CGRS on Windows 2000 with a Biztalk Server installed.


Now the only prerequisite for installation is the presence of a Biztalk Server.


Service System reference: HQ-394-156-CRKT

A713) Wrong length of local variable PartnerNo in cu99008509

Error

With a long PartnerNo (ie CustomerNo or VendorNo) an overflow error was raised when updating agreements. To correct this problem, the variable PartnerNo in codeunit 99008509 has been changed from a CODE 10 to a CODE 20.


COD 99008509 Service System reference: HQ-229-898-CRNT

A714) CGRS dump log feature now includes response documents

Error

Previously the CGRS Dump Log feature only worked for the requests received. Now it also works for the responses sent back. Please refer to the documentation for details.


Service System reference: HQ-402-134-CQH9

A715) Execute Method In AIC Offered No Error Handling For IP Address And Port No

Error

If an IP address and/or port number were malformed/missing, it was not handled properly in the Application Integration Component.


CommerceGateway.dll Service System reference: HQ-985-68-CR8P

A716) Converting SalesQuote to Order and Dimensions

Error

When a Vendor accepts a PO and converts the related Sales Quote to a Sales Order, the related dimensions were lost.


COD99008502 - Sales Order-Accept


Service System reference: SE-890-465-UKDR

A717) Request Client method SuspendedQueue::ItemExists never finds the first item.

Error

Previously the method SuspendedQueue::ItemExists would never find the first Item in a list.


Service System reference: HQ-704-713-CQMX

A718) Line Type "Fixed Asset" is enabled on Sales Docuements

Error

Previously the line type "Fixed Asset" was being handled in Purchase Documents only. This has been implemented for Sales Documents as well.


NavisionRSQ.xml NavisionSCM.xml NavisionSI.xml NavisionSN.xml NavisionSO.xml NavisionSOC.xml NavisionSQ.xml NavisionPO_to_SO.xml NavisionRPQ_to_RSQ.xml NavisionSCM_to_PCM.xml NavisionSI_to_PI.xml NavisionSN_to_PR.xml NavisionSOC_to_POC.xml NavisionSQ_to_PQ.xml So the Data Type Values property of the Line_Type element is: "blank account item resource fixedasset", and therefore sales document with lines of type Fixed Asset can be handed over by the BizTalk server to Attain, where an error message when trying to accept can be displayed on a more user friendly manner. For that purpose, some text constants and CASE structures are changed in the following objects in Navision COD99008501.TXT COD99008500.TXT COD99008518.TXT COD99008502.TXT COD99008503.TXT COD99008504.TXT COD99008505.TXT COD99008506.TXT COD99008517.TXT And in the follwoing CG Sales Line tables the Option field Type has been extended to include "Fixed Assets" TAB99008501.TXT


TAB99008503.TXT TAB99008507.TXT TAB99008509.TXT" Service System reference: HQ-556-10-CQJ9

A719) Document Specifications cannot include an underscore ("_")

Error

The BizTalk Editor doesn't accept underscores '_' in data type values. Thererfore the 'fixed_asset' value has been replaced by 'fixedasset' in all occurrences.


- NavisionPCM.xml - NavisionPI.xml - NavisionPO.xml - NavisionPOC.xml - NavisionPQ.xml - NavisionPR.xml - NavisionRPQ.xml - NavisionRSQ.xml - NavisionSCM.xml - NavisionSI.xml - NavisionSN.xml - NavisionSO.xml - NavisionSOC.xml - NavisionSQ.xml - NavisionPO_to_SO.xml - NavisionRPQ_to_RSQ.xml - NavisionSCM_to_PCM.xml - NavisionSI_to_PI.xml - NavisionSN_to_PR.xml - NavisionSOC_to_POC.xml - NavisionSQ_to_PQ.xml" Service System reference: HQ-315-710-CPZA

A720) Multiple NAS for Each Company

Error

It is now possible to start the NAS with a startup parameter like: CG Port=7520. So it’s now possible to have multiple NAS on the same computer.


Codeunit 1 Service System reference: HQ-587-0-CQGY


A721) Failure When Registering the CGReqClient

Error

MS Windows 98 doesn't include the file MSVBVM60.dll which is used by CGReqClient.dll. This caused a failure when registering the CGReqClient and therefore an error was raised on MS Windows 98 clients when connecting to CGRS. To fix this issue msvbvm60.dll must be copied into the \windows\system directory and registered. A .NET replacement of NSComCom2 and SocketBusAdapter has been created and compiled into a single file called "TCPCOM.dll". This component will provide increased stability in the TCP communication.


Service System reference: DE-174-761-VL9B

A722) CGReqClient had poor error handling

Error

Previously the Commerce Gateway Request Client had poor error handling, using "On Error Resume Next" all over.


Service System reference: HQ-457-718-CR7U’

A723) CGRS stops processing during high load

Error

In the previous version of CGRS a very high load occasionally resulted in - The CGRS stopped processing incoming documents - Everything else looked normal: No entries in the event log, and an available TCP port


Service System reference: HQ-465-612-EFNJ

A724) Validation of Post-Codes and Cities for BizTalk Documents

Error

Navision accepts now the presence of multiple Postal Codes associated to one single city. When filling out one of those fields on a Business Document, the user is presented to a lookup form to choose the desired combination of Postal Code and City. This lookup form is RUNMODAL. When accepting Documents received via the Commerce Gateway, this fields are taken from the Inbouind Documents, and therefore its validation would trigger a RUNMODAL in the middle of a Write Transaction To prevent this, this fields are validated after the Biztalk fields are filled (e.g. Date Received, Time Received...), and only if Date Received is still 0D (not a BizTalk document) the lookup form is issued.



COD99008500 COD99008506 TAB36 TAB38 Service System reference: HQ-942-472-WKLE

A725) Wrong textconstant used in Error-Msg. of codeunit 99008505

Error

A new Text Constant (009) has been introduced in the codeunit, consistent with all other messages displayed in the case of currency mapping in the Commerce Gateway. The message reads: The currency code on the inbound purchase document header does not map to any currency specified for the Partner.


COD99008505 Service System reference: DE-259-464-LKH4

A726) [Cannot update purchase documents with comment lines

Error

In the Biztalk Partner Setup Header (TAB99008513), the Update Purchase Comments field (34) has been introduced. Update Purchase Comments is an option field:

- "Ignore New and Updated Comments" : The comment lines in incoming documents will not be copied to existing documents.

- "Accept New and Updated Comments" : The comment lines in existing documents will be replaced by the comment lines in the incoming documents.

Notice that if you choose "Accept New and Updated Comments" all comment lines in the existing document will be deleted and replaced by the comment lines from the incoming document.


Objects Modified: COD99008503.TXT COD99008501.TXT COD99008505.TXT COD99008519.TXT COD99008520.TXT COD99008521.TXT FOR99008523.TXT TAB99008513.TXT

Service System reference: HQ-589-916-CP6F]


Issues

A727) Enhanced Transaction Support

Issue

A new entry in the configuration file CGRS_Config.Xml has been added. The value under the key “Settings/Thresholds/DocSizeImmediateReply” (threshold) has impact on how XML documents are handled when going from the Navision client to the Commerce Gateway Request Server (CGRS). The value in threshold is in bytes. Two possibilities exist: 1. The size of the XML document is smaller than, or equal to, the value of the threshold. The CGRS will process the XML document, through BizTalk Server, and return with a valid BizTalk Server Tracking ID to the Navision client. This approach will safeguard against duplicate documents being send through the system. 2. The size of the document is larger than the threshold value, and thereby potentially requiring a lot of processing time. The CGRS will immediately return with an answer indication that it has received the XML document successfully. The BizTalk Server Tracking ID will be returned later through the Navision Application Server. The reason for the immediate answer (and without a valid Tracking ID), ensures that the client will not be blocked.

This has been implemented


3 Development Environment and Database Changes

3.1 Microsoft Business Solutions–Navision Database Server

Features

P1) Database Collations Can Now be Altered

Feature

It is now possible to change the collation of a database using the Collation tab of the Database Alter window.


Service System reference: HQ-793-143-HD2N

P2) Linked Object Creation Change

Feature

Previously, a table that was created (either from the designer or during an import or restore) with the 'Linked Object' property set to 'Yes' required that the corresponding SQL object was present in the database when the table was created. Now it is possible to create these tables without the SQL object having first been created. This allows a backup of linked objects to be restored successfully into a database that does not yet have the corresponding SQL objects. The presence of the SQL object is now checked when the table is run.


Service System reference: HQ-666-894-CQS6

P3) Database Test Enhancement

Feature

When performing a database test from either the File/Database/Test or File/Database/Information/Tables menu, it is now possible to direct the error messages of the


test to a file or to the Windows Event Log, as well as to the screen. The Test window includes a new Options tab that controls the error message destination. When performing a test from the command line, a new command line parameter 'TestTarget' also allows the destination to be specified. Full details can be found in the Installation & System Management manuals.


Service System reference: HQ-326-565-CPQF

Errors fixed

P4) Microsoft Business Solutions-Navision Database Server Crashes When Started with More Than About 900 MB Cache

Error

The Navision Database Server crashes when started with more than about 900 MB cache.


Max. cache is 1 GB as stated in the online Help. Service System reference: HQ-384-45-CPJZ

P5) Corrupted Data created by the AutoIncrement Field Property of a BigInteger on the AIX Platform

Error

When the AutoIncrement field property is set to 'Yes' for a BigInteger data type, the values generated in the field do not follow the expected initial values of 1, 2, 3 ..., and so on. Instead, the field contains large corrupted values. This error applies only to the Microsoft Business Solutions-Navision Database Server, running on the AIX operating system.


Service System reference: HQ-77-441-CQTM

P6) Exceeding 80 Permissions in the Permission Property

Error

When you enter more than the allowed 80 permissions in the Permission property, these extra permission entries are not saved. In response to this issue, a change has been implemented.


You will now get a warning when you exceed the limit of 80 permissions. If you have chosen to ignore this warning, a second warning will inform you that only the first 80 permissions will be saved.


Service System reference: HQ-981-504-CPUS

P7) Field with the Autoincrement Property Set to Yes does not Continue Data with the Maximum Value after a Restore

Error

If a backup is made of a table that contains a field with data and where the AutoIncrement property for the field is set to Yes, then the seed for the autoincrement value should be the maximum value for that field when the table is restored. Instead, the seed is reset to 0, which gives 1 as the next value to be used. This error applies only to the Microsoft Business Solutions-Navision Database Server. An example of this error in the base application is the Change Log functionality, which would fail after performing a restore of change log entries and an attempt to add further entries to the change log.


Service System reference: HQ-835-911-H9WN

3.2 Microsoft SQL Server Option for Microsoft Business Solutions–Navision

Features

P8) Sessions Can Be Killed in the Session Window or in the Session Virtual Table

Feature

The Session window that you open by clicking File/Database/Information/Sessions now allows a session record to be deleted, which will kill the session in question (i.e. the SQL Server SPID). The user cannot kill his own session. It may be necessary to update the session display after killing a session using Ctrl+Alt+F5, if the server takes some time to kill the session. This functionality is also available when you delete the current record of a C/AL Record or a RecordRef variable that is based on the Session virtual table. More details are available in the documentation.


This feature is only available in the SQL Server Option for Navision. Service System reference: HQ-551-596-CQS7


P9) Clients with Code Pages that Differ from the Database Code Page Can Now Work with the Database.

Feature

The requirement that a client OEM or ANSI code page must match the code page of a database to be opened, can now be removed with a new database option. The 'Validate Code Page' check box in the Database New and Database Alter windows can be disabled to allow incompatible code page clients to open and use the database. Full details can be found in the Installation & System Management manual, including issues to be aware of with character conversion problems that can arise from relaxing this constraint.


This feature is only available in the SQL Server Option for Navision. Service System reference: HQ-635-127-CQWR

P10) Collation Enhancements - Windows Collations

Feature

You can now create SQL databases that use a dictionary sorted Windows Collation. A Windows Collation is preferable to a SQL Collation, because it closely matches the operating system methods of comparing and sorting character data. Using a Windows Collation will also avoid certain ordering problems that exist in Navision's use of SQL Collations with some character sets. When you create a database the default collation is now a Windows Collation. If the server collation (set when installing SQL Server) is a Windows Collation, the new database's Windows Collation will be the same. If the server collation is a SQL Collation, the new database's collation will be a Windows Collation for Western European languages, and will be case and accent sensitive. It is possible to alter a database collation from a SQL Collation to a Windows Collation. See the documentation for details. It is recommended that collation settings are always set correctly, according to your language requirements, when you create a database.


Service System reference: HQ-782-221-CPXC

P11) A Single File Database can be Attached in the Database Open Window

Feature

The Database Open window contains an Advanced tab that allows a single database file to be specified for attaching to the server - with the database name specified. Note: Additionally, the Net Type has been moved to the new Advanced tab.



This feature is only available in the SQL Server Option for Navision. Service System reference: HQ-600-70-CR65

P12) Filters Can Include <> with Wildcards

Feature

When using the * wildcard operator in a filter, it has previously only been possible to find positive matches, for example, all occurrences matching '*ea*'. It is now possible to perform negative matches. For example, to find all occurrences that do not match *ea*, you write <>'*ea*'. The <> wildcard operator can be combined with other filter operators in the normal way, for example, ='Bear' | <>'*ea*'.


This feature is only available in the SQL Server Option for Navision. Service System reference: HQ-778-979-CPTB

P13) New field in the Session Window and in the Session Virtual Table

Feature

The Session window and the Session virtual table contain a new field called 'Blocking Object', which shows the name of the SQL object that is involved in a blocking situation, that is to say when the 'Blocked' field is True.


This feature is only available in the SQL Server Option for Navision. Service System reference: HQ-320-66-HG3G

P14) New License Granule Allows Access to the Microsoft SQL Server 2000 Desktop Engine

Feature

It is possible to connect to and use the Microsoft SQL Server 2000 Desktop Engine with a new Desktop Engine server license granule, without having the standard SQL Server Option license granule. The Desktop Engine granule does not give access to Microsoft SQL Server 2000 editions other than the Desktop Engine.


Service System reference: HQ-594-827-JC79


Errors fixed

P15) Using Find on a Card Form causes a Permission Error when Security Filters are being Applied

Error

When the correct security filters have been set up for the necessary tables for a user, and the user initiates a Find when using a card form on one of the tables (e.g. the Item card), an incorrect permission error occurs. Immediately after this, the user is asked to rename the record. This error applies only to the Microsoft Business Solutions-Navision SQL Server Option.


Service System reference: NZ-426-840-93EU

P16) Crash During Long Running Batches

Microsoft Business Solutions-Navision crashed during long running batch jobs. This was caused by an occasional internal object cleanup combined with certain performance optimizations. This only applies to the Microsoft Business Solutions-Navision SQL Server Option.


Service System reference: HQ-254-818-UE6G

P17) Indirect Permissions are not Considered when Security Filters are Applied

Error

When security filters have been configured for an indirect permission, the indirect permission is not considered when the security filter is applied by the system, which leads to a permission error. This applies only to the Microsoft Business Solutions-Navision SQL Server Option.


Service System reference: US-332-273-RU6L

P18) FIND('-/+') without Looping with NEXT Places Range Locks on Fetch Buffer

Error

When performing a FIND('-') or FIND('+') within a transaction type other than Browse, any C/SIDE SQL cursor used for the operation (the default behaviour) will place locks for all rows in the internal cursor fetch buffer. The default behaviour for these operations has been


changed to always begin with a single row buffer, therefore placing fewer range locks, and to switch to a fetch buffer when and if a NEXT is performed. After a NEXT, the fetch buffer will always be used initially for the same filter and current key. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-787-399-7DM6

P19) Lower-Case Characters in Code Fields are not Handled with an Informative Error

Error

If lower-case characters are present in a Code field due to a modification by an external application that has not converted to upper-case, an internal error occurs that does not give information about the bad value. It is also possible to successfully perform a database backup containing the bad data, which subsequently cannot be restored. This error applies only to the SQL Server Option for Navision.


An error message is displayed showing the erroneous Code field and value. This occurs as soon as the value is encountered, which means that a backup of the bad data cannot be made. This is consistent with the handling of bad Boolean or Date values. Service System reference: HQ-526-909-CPLQ

P20) The SQL Server Name is Retrieved and Stored in the ZUP File when Connecting with Fully Qualified Name or IP Address

Error

When using a fully qualified server name or an IP address to connect to a SQL Server, Microsoft Business Solutions - Navision retrieves the SQL Server instance name and stores it in the ZUP file. The next time Navision is opened, it will try to connect to the server using this instance name, which will often fail when there is a need to use a fully qualified name or an IP address.


In these cases the fully qualified name or IP address is stored in the ZUP file for later connections. Service System reference: HQ-280-672-DEU2

P21) Users with the SQL 'db_owner' Role Cannot Create/Design Tables

Error

To create or design tables, the user must normally be a member of the SQL 'db_owner' role for the database. The error causes this permission to be too weak and the user is instead required to be a member of the 'sysadmin' server role to perform these activities.


This error applies only to the SQL Server Option for Navision.


Service System reference: DE-706-270-RFGV

P22) Altering a Database to Use a Per-Database License Does Not Validate the Provided License

Error

If the 'Save license in database' option is checked when altering a database in the Microsoft SQL Server Option for Microsoft Business Solutions-Navision, the license file provided for upload to the database is not validated for expiry or for the 'Per-database' granule.


Service System reference: HQ-602-286-CQQY

P23) Incorrect Functionality When Performing a Database Test from the Command Line

Error

The test for relationships between primary and secondary keys is erroneously run when performing a test that includes this test level from the command line. This test should not be done against SQL Server using record reads since the DBCC statement will cover the test of indexes. It is correctly disabled when performing the test from the user interface. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-518-810-CR64

P24) FlowFields in Security Filters

Error

When entering a Security Filter in the permission table, FlowFields are either missing from the filter if using assist edit windows, or when entered manually are ignored by the security filter at the time that the filter is applied for the user's role(s). This error applies only to the SQL Server Option for Navision.


FlowFields are now fully supported in Security Filters. Service System reference: DK-227-651-GCQ7


P25) LOCKTABLE(TRUE,TRUE) and LOCKTABLE(FALSE) Do Not Raise an Error

Error

When calling LOCKTABLE with either of these parameter value combinations in the Microsoft SQL Server Option for Microsoft Business Solutions-Navision, no operation is performed since the parameters are invalid for the SQL option. Therefore an error message should be raised to indicate that the program logic will not produce the intended results. Currently an error message does not occur.


Service System reference: HQ-770-860-CPNA

P26) Locks Left in tempdb When Using Database Authentication

Error

When using Database authentication to open a database, locks are left on system tables in 'tempdb' directly after opening the database. This can cause tools such as Enterprise Manager to block awaiting locks when performing various activities. The locks are cleared when the first transaction is committed. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-450-395-CRHR

P27) Wildcard Performance Issue for Code Fields

Error

When a filter operation is performed on a Code field (either in C/AL or from the user interface), lower-case characters are sometimes included in the search operand, depending on the data in the value to be searched for. This can lower performance in some situations. Since Code fields contain only upper-case characters, there is no need to include lower-case combinations when searching. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-89-618-CRAP

P28) ODBC Error When Running Tables with a Large Number of Fields

Error

If a table contains a large number of fields, the memory size occupied by the field lengths can overflow an internal buffer, causing an ODBC error: 'Invalid argument value'. Since the problem depends on field lengths for character fields, the error is not directly dependent on the exact number of fields, but rather on the total of the memory used.


This error applies only to the SQL Server Option for Navision.


Service System reference: DE-215-232-BGUT

P29) The SQL LIKE Operator Fails on SQL Server with Certain Central European Character Combinations

Error

When C/SIDE sets a '@*' wildcard filter internally for a lookup operation, it is possible that some values cannot be found although they exist in the lookup set. In some languages these values contain certain character combinations, which combine to form other characters. The SQL LIKE operator, used by the C/SIDE '@' filter operator, does not match the characters correctly. An example is the 'CRF' currency in the Czech collation. As a workaround, C/SIDE now first tries an exact match of the value being searched for, and then a wildcard filter if the exact value cannot be found. If the value is entered in full by the user (it does not need to be entered in upper case if it is a Code field), an exact match will be found. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-846-713-CPZT

P30) Duplicate Key Error Message When Inserting in a Form with AutoSplitKey Set to Yes

Error

When inserting a new record with F3 in a form in which the AutoSplitKey property is set to Yes, a duplicate key error message is incorrectly displayed. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-365-154-FD6P

P31) Character Data Corruption when the Database Code Page Differs from the Server Code Page

Error

If the database currently in use has a collation that uses a different code page to that of the server (and therefore the tempdb database as well), it is possible for character data (in fields of the Code, Text or DateFormula data types) to be corrupted due to code page conversions when one of the following occurs:


An internal optimization is initiated for bulk copying data into a table, when the table contains SumIndexFields as well as one of the above data types. A table is designed, enabling the AutoIncrement property of an Integer or BigInteger field, and the table also contains one of the above data types. This error applies only to the SQL Server Option for Navision.


Service System reference: RU-569-604-ZLKV

P32) Error When Bulk Inserting Records into a SQL Table

Error

When bulk inserting records (for example, in a C/AL loop or as part of a dataport import) into a table that contains the RecordID data type, an error occurs when running against SQL Server.


Service System reference: HQ-974-568-CQWE

P33) Database Testing from the Command Line Raises an Error

Error

When using the dbtest= command line parameter, the error "Activity must be performed within an Update or Snapshot transaction." occurs. This error applies only to the SQL Server Option for Navision.


Service System reference: HQ-8-658-CR63

P34) Table Relation and user filters are removed by a Security Filter

Error

When a Security Filter is being applied for a user, it removes and replaces any additional filters that the system places automatically, for example during drill-down, or that the user places manually. This error applies only to the SQL Server Option for Navision. Note: the correction for this error causes the security filter to be placed into a separate internal C/SIDE filtergroup, and it is therefore no longer visible in the user's own filter (although it is still applied), which is easier for the user to understand. Data that is being filtered because of a security filter will cause the FILTER indicator to appear in the status bar.



Service System reference: GB-783-27-WJY5

3.3 Development Environment

Features

P35) The 'Find as You Type' Option can be Disabled

Feature

The 'Find As You Type' option can be disabled for a database. This prevents excessive server calls being issued per user key press when running against SQL Server. The option 'Allow Find As You Type' controls this behaviour in the Options tab of the Database New and Database Alter windows. The checkbox will be grayed in the Find and Quick Find windows if this option is enabled. This feature is only available on the SQL option. Note: The behaviour of the Quick Find window has changed slightly for all server platforms. When the Quick Find window is displayed for the first time for a particular form, the 'Find As You Type' checkbox will be disabled by default, and not enabled as before. From this point onwards, the checkbox will be set to the state the user sets it to now in the Quick Find window. Therefore, to obtain the previous behavior, the checkbox must be checked the first time the Quick Find window is displayed for a form.


Service System reference: HQ-911-767-CRAN

P36) Symbol Menu - Paste Value to Property Sheet

Feature

It is now possible to copy a value from the Symbol menu and paste it into the Property sheet (SourceExpr).


Service System reference: HQ-25-13-CRHC


Errors fixed

P37) [FieldRef and RecordRef Errors

Error

In general the area of FieldRef and RecordRef has been reviewed, and a number of errors have been corrected. This has been corrected. Service system references: DE-456-23-PRS4, DE-564-575-PUD9, DE-687-882-CBKS]

P38) Error using Dataports with Fixed Length

Error

When importing data using a dataport set up to fixed file format with the AutoUpdate and AutoSave properties set to True and AutoReplace set to FALSE, the dataport clears all fields in the related table that are not included in the dataport.


Service system reference: DE-460-536-ZMJP

P39) Report can be Designed without the Report Designer Granule

Error

It is possible to design a report without having the Report Designer granule. This can be done by first running the report and then choosing the Report Designer.

This error has been corrected.

Service System reference: HQ-179-168-CPK8

P40) Security Error when Changing Permissions

Error

If a permission-related error message occurs when a user tries to change permissions, any changes previously made to logins or roles can be overwritten.


Service System reference: HQ-136-493-CR2U


P41) FieldRef.LENGTH Function is Missing?

Feature

This function has been implemented. A number of other FieldRef and RecordRef functions have also been implemented. For more information, see the C/SIDE online Help."


Service System reference: NL-228-654-Q9UY

P42) Error 1355 in Module 19 Keeps Appearing After Stack Overflow

Error

After "An insufficient memory (stack)" error message, error 1355 in module 19 keeps appearing.


The program will now clean up the memory stack and the error 1355 in module 19 will not appear. Service System reference: HQ-922-554-CRTT

P43) The 'RemoteServerNo' Table Property Has Been Removed

Error

The 'RemoteServerNo' table property was part of an unimplemented feature and has now been removed.


Service System reference: ZA-50-409-UFT2

P44) Microsoft Business Solutions-Navision does not Jump to a Syntax Error in a Function in a Report

Error

When a compiler error occurs in a report, Microsoft Business Solutions-Navision does not jump to the line where the error is located.


Navision now places the cursor in the Trigger and in the line where the compiler error is located. Service System reference: NL-950-750-XE4J


P45) C/AL Editor - Ctrl-F Finds Function Headers

Error

When using Ctrl+F (Find) in the C/AL Editor, C/SIDE does not find matching words in the Trigger headers.


Now C/SIDE also searches in Trigger headers. Service System reference: HQ-864-974-CP7V

P46) The READPERMISSION and WRITEPERMISSION C/AL functions do not take Security Filters into account.


Service System reference: HQ-287-332-SJDV

P47) Unable to Use Conv-ml.bat With, For Example, Cyrillic Characters

Error

The tool could not convert strings that only contain national characters. This was a problem specific to Russian speaking countries.


CONV-ML can now be run so that it will also convert strings that only contain national characters. Service System reference: RU-681-392-PD6Y

P48) Form - OnQueryCloseForm() - Not Always Executed When in Lookup Mode

Error

Call missing to "Form - OnQueryCloseForm()" with PushAction = OK, Cancel , LookupOK, LookupCancel, Yes or No.


Now "Form - OnQueryCloseForm()" is called. Service System reference: HQ-665-420-3C39

P49) Error Message of Modify Command uses Wrong Language Layer

Error

If the AL function MODIFY is used to modify a non-existent record, the error message uses the Name of the table instead of its Caption name.



The error message now uses the Caption of the table. Service System reference: DE-216-99-NCLT

P50) When You Use the Context Menu on a Selection Bar in Design Mode, Microsoft Business Solutions-Navision Crashes

Error

When You Use the Context Menu on a Selection Bar in Design Mode, Microsoft Business Solutions-Navision Crashes


Service System reference: HQ-416-292-3C3R

P51) RecordRef/FieldRef types declared as global variables cause a program crash

Error

When using RecordRef/FieldRef variables declared as global variable, Navision may crash in some situations.


Service System reference: HQ-44-879-BHLC Service System reference: CH-505-564-GJ5F

P52) Strange Behavior of IF codeunit.Run:: THEN (Command Buffer flushed too late)

Error

During an IF CODEUNIT.RUN(...) call, the command buffer is not automatically flushed until control is returned to the calling process. If the command buffer contains an error-producing call, an error message is displayed and the current transaction is rolled-back. This is not correct.


The codeunit that is called with IF CODEUNIT.RUN(...) now flushes the command buffer immediately before returning control to the calling process. Service System reference: NL-335-607-9C8E


P53) The Error Message “';' Should Come Here", is Displayed When Importing a Text Object

Error

When importing an object in text format where the return value for a PROCEDURE has been assigned a Unique ID but not a name, the import fails and the following error message appears: An ";" should come here.


The object is now imported successfully. Service System reference: HQ-719-890-CQML

P54) Output "Global Dimension 1 Code" in Report Headline

Error

When a field uses the CaptionClass property and the caption is in the header section of a report and the field is in the body section, the caption is not resolved.


Service System reference: DE-251-213-THR5

P55) Navision Crashes When a Variant Parameter is Handed Over as a Parameter

Error

There was a problem using a Variant as a parameter when: 1. The variant was holding a complex type. 2. This variant will be used as a parameter for a second function. 3. Both variants were declared as parameters for function calls.


Variants are now copied correctly, even when holding complex types. Service System reference: DK-740-975-4HKK

P56) Error 1355 in Module 19 When Using Scroll Bar and Filter on Non-Indexed Data.

Error

When the use of the scroll bar on a table causes the database to work for a long time, error 1355 in module 19 occurs.


Now the scroll bar will not send any scroll bar messages when the database is busy. Service System reference: HQ-152-501-CRPX


P57) Problem with ID When Creating a Tabular-Type Form with the Wizard

Error

When creating a tabular form using the wizard, controls are not assigned unique IDs in the range defined in the license file.


Controls are now correctly assigned IDs in the range defined in the license file. Service System reference: IT-5-743-YHEC

P58) Error in "Shell" Command

Error

The Shell command ignores parameters in the command. For example, shell('cmd.exe','/k','dir'); does not work.


The Shell command can now use parameters as described in the online Help. Service System reference: DE-791-13-2CE8

P59) XP-Look Scroll Bar Disabled in Field Menu Window

Error

The scrollbar is disabled in the Field Menu window.


Service System reference: HQ-236-492-CQCR

P60) Header Creates Blank Page

Error

When setting the property NewPagePerRecord = Yes, C/SIDE prints out an empty page at the end.


Now the empty page is not printed. Service System reference: HQ-615-311-CPH5


P61) Mismatched Field Types Give Unpredictable Results

Error

Mismatched flow field types were allowed to be summed up resulting in unpredictable behaviour.


A runtime type check is made between the destination (flow field) type and the source type (the field that is summed up). An error message appears if there are different types. Service System reference: HQ-858-128-CPS6

P62) File.TEXTMODE Always Returns TRUE

Error

When reading the File.TEXTMODE function, it always returns TRUE no matter what value it holds.


TEXTMODE returns TRUE/FALSE as it should. Service System reference: HQ-956-184-CP7M

P63) Changing a Field or Copying a Field from One Table to Another Leads to Loss of MLcaption

Error

When making changes to a field or when copying a field from one table to another, the first caption of the MLcaption is lost.


Service System reference: NO-411-846-3FHW SG-624-51-X8M5 DK-667-686-QD4F NL-534-535-ABDH

P64) Problems When Running a Report Without a Request Form

Error

If an attempt to run a report - without a request form - fails for some reason, Microsoft Business Solutions-Navision will terminate both the report and the object that called the report. This can be seen in Invoice | Post and Print.


Now only the report is terminated. Service System reference: NO-797-233-WE7Q


P65) Not Possible to Export Objects of the Size 0 - Also Known as "Killer Objects”

Error

A GP error occurs when trying either to export objects of the size 0 or to backup a database with objects of the size 0. It is now possible to create and export "Killer Objects" for the purpose of importing them again to delete objects of the same ID and type.


Service System reference: DK-376-355-6AZM

3.4 User Portal

Errors fixed

P66) Multiple UPAS and load balancing

Multiple UPASes can coexist, but each new server will get a new incremental TCP port number.


fin.exe SocketConnector.dll BOProcessor.js dashboard.asp default.asp NSUPDate.asp dashboard_const.inc Service System reference: FR-616-760-8FBM

P67) Not Possible to Access User Portal in a Secure Manner

Error

From the internet connecting to Navision User Portal, it was possible to access the Navision database without proper authentication. This has been corrected Database authentications by using TCP/Sockets have been developed.

P68) Problems with User Portal and Internet Explorer 6.0 on the clients

Error Internet Explorer 6.0 introduced some changes in functionality, which is why Microsoft Business Solutions - Navision had some problems using Internet Explorer 6.0 together with


User Portal. If Internet Explorer 6.0 with the latest patches ran on the client machine, you were not able to see the content of some Web Parts when accessing the User Portal site. One example is the Sales Categories web part folder, which does not display any lines. This has been corrected

The file dbview_ie.js has been updated to address this issue.

3.5 Microsoft Business Solutions–Navision Application Server

Errors fixed

P69) Not Possible to Start NAS Snap-In for MMC on XP

Error

After installing the Microsoft Business Solutions-Navision Application Server on an XP machine, the MMC fails to start up our Navision Application Server Snap-In.


The Snap-In now starts successfully after the installation of the Navision Application Server. Service System reference: HQ-468-574-CQB2

P70) Application Server Handles Lost TCP Connection Incorrectly

Error

Application server incorrectly handles lost connection


Service System reference: CZ-576-647-UGPH

P71) NAS - Application Server Service Cannot Restart Properly (error 1262 in module 19)

Error

The Application Server sometimes fails to start.


Now it does not fail. Service System reference: DE-630-152-58VR


4 Installation

4.1 Installation Program

Features

I1) MSDE 2000 and a SQL CRONUS Database Can Now Be Installed as Part of the Client Installation

Feature

We now offer users the possibility of installing the Microsoft SQL Server 2000 Desktop Engine (SP3) and a SQL CRONUS database as part of the client installation.


Service System reference: HQ-502-741-CQET

I2) Default Installation should be "Minimal Installation"

Feature

The default installation option should be changed from Complete Installation to Minimal Installation.


The default installation is now a Minimal Installation that in addition to the clients and associated files includes online Help and MDAC. This means that features such as the demo database, demo database backup, MSDE, Commerce Integration, VIP-Integration Broker and Navision Toolbar for Outlook will not be installed. Please note that when you install either Commerce Integration or the VIP-Integration Broker, the .Net Framework is automatically installed too. Service System reference: HQ-604-533-YHXQ

Errors fixed

I3) Company Notes Inaccessible from Windows 98 Clients

Error

The user could not use the Company Notes feature because the DLL "msvbvm60.dll" was not installed together with our product.



The DLL "msvbvm60.dll" is now installed. Service System reference: AU-613-964-K7B7

I4) Uninstalling Microsoft Business Solutions-Navision 3.60 on XP SP1 Disables MMC

Error

After uninstalling Microsoft Business Solutions-Navision 3.60 on XP, the Microsoft Management Console (MMC) does not work properly. It is not possible to save Snap-ins or open them by double clicking on a saved Snap-in. It was caused by the installation of the DLL for MS XML version 2.0.


Now we only install version 3.0 Service System reference: US-740-339-KPEY

5 Tools

5.1 Debugger

P72) Setting Breakpoints in C/AL Editor and Saving Breakpoints

Feature

It is now possible to set breakpoints in the C/AL Editor. The breakpoints are saved in an XML file when you close Microsoft Business Solutions-Navision. This breakpoint file is used when you start Navision to load the breakpoints from the previous session."


Service System reference: HQ-977-835-CR9Y

P73) Ability to See Values of Arrays

Feature

When debugging, it is now possible to expand an array structure to see the values of all the dimensions in the variable.


Service System reference: DK-885-508-UB9Q


P74) Showing Detailed Info about Object Types in the Debugger

Feature

When viewing variables of the type Form, Record, Dataport, Codeunit or Automation, the debugger just showed that the variable was ""In Use"" when it was initialized.


The debugger now shows the name of the object. Service System reference: HQ-838-233-CPJB

P75) Ability to See All Values in an Array Structure When Debugging

Feature

When debugging, it is now possible to expand an array structure to see the values for all the dimensions in the variable.


Service System reference: CZ-14-701-AJAL

Errors Fixed

P76) The Format of the Content Shown for a Record Ref Variable in the Debugger is Incorrect

Error

When viewing the content of a RecordRef variable in the debugger, the content has an incorrect format.


Now RecordRef is formatted like a normal Record. Service System reference: DK-741-73-JECQ

P77) The Local Var View in the Debugger is Empty

Error

In some situations, the Local Variable view is empty when debugging.


Service System reference: HQ-86-979-CQPZ


5.2 Upgrade Toolkit

Errors fixed

A728) Field 48 Salutation Text in Table 5079 Relationship Management Setup Caused an Error During an Upgrade

Error

When you ran an upgrade from Attain 3.01 to Attain 3.60 (using the newest toolkit), you would find an error in step 7 when you imported the objects from Attain 3.60, and there was a value in field 48 in table 5079.


Upgrade301370.txt Upgrade301370.fob Service System reference: DE-73-93-FEZK

A729) Upgrade Toolkit 2.xx to 3.60: Error in Codeunit 104050 Upgrade 3.60 Step 2 Contact

Error

Codeunit 104050 Upgrade 3.60 Step 2 Cont were not inserted in these Upgrade files: Procedure CreateProfile: ContactProfileAnswer.VALIDATE("Contact No.","Contact No."); ContactProfileAnswer."Answer Priority" := ContactProfileAnswer."Answer Priority"::Low;


Upgrade260360.2.fob Service System reference: HQ-54-552-WKW2

A730) Upgrade Toolkit, Codeunit 104048

Error

In the contact management part the name is split into two fields, and the first name that this codeunit extracts can be over the limit of 20 characters. The upgrade codeunit should either trim the field to 20 or produce an exception report that lists the names over 20 characters before running codeunit 104048. In response to this issue, a change has been implemented.


First, Middle and Surname has been changed from 20 to 30 characters. This has been done to prevent the Upgrade Toolkit from issuing an error. The Breakdown function results in text overflow if First, Middle and Surname exceeds 20 characters.


Codeunit 5071 Contact Handler Table 5050 Contact Service System reference: HQ-517-939-CQEE

6 Documentation

6.1 Online Help

Features

D1) Long Help IDs Not Found

Feature

Previously, the Help ID could only be max. 20 characters long. This limit has been increased to 40.


Service System reference: US-518-41-9SQL

D2) Update Online Help for RecordRef, RecordId etc.

Feature

The online Help for all of these new data types has been completely overhauled for Microsoft Business Solutions-Navision 3.70. New topics have been added and old ones revised. A few examples have also been added.

This Feature has been implemented

Service System reference: HQ-747-214-CQTF


Errors fixed

D3) Wrong Online Help on field Service Period, Contract

Error

The online help for this field T_5965_59) is said: This field contains the estimated time that elapses until service starts on the service item, that is, how many hours elapse from the creation of the service order to the time when the repair status of the service item changes from Initial Status to In Process. This is incorrect, and the field has been corrected to: This field contains the default service period for the service items in the service contract. The service period cannot be longer than invoice period on the contract header if the Invoice after Service check box is selected. Note that before you add service items to the contract quote, this field must be filled in.


T_5965_59 Service System reference: HQ-690-710-CR7T

D4) Topic T_6081_4 contains "old" currencies

Error

The online help for this field contained examples of currencies that have become obsolete after the Euro was introduced. The online help has been corrected, and the section about the currencies now reads: "Use codes that are easy to remember and descriptive, for example, the international currency abbreviations: DKK, USD, GBP, ZAR, SEK, NOK, PLZ, EUR".


T_6081_4 Service System reference: HQ-785-577-CR9B

A731) Topic T_5968_16 contains an error

Error

In this field there used to be written: "This field contains the of the <a HREF="T_5966.htm">contract group code</a> service contract". The text has been corrected to "This field contains the <a HREF="T_5966.htm">contract group code of the service contract".


T_5968_16 Service System reference: HQ-178-303-CR9A


A732) link Salesperson Code and User ID

Error

In the Online-Help for the Salesperson Code in the Service Header there used to be written: "If the current user is a salesperson, the program copies the code automatically from the Salesperson/Purchaser table." The online help has been corrected, and it now reads:"If the contact number appears on the list of a salesperson, the code of this salesperson/purchaser is copied automatically from the Salesperson/Purchaser table".


T_5900_39 Service System reference: HQ-122-355-CQ87

D5) Numbering of numbered list is wrong of smtask_7009, smtask_7010, smtask_7012, smtask_7013, smtask_7032 and smtask_7038

Error

Due to an error in the html-code for these online help topics, the numbered list inside these topics appeared incorrect. By adjusting the <ol start=> tag in the html-code, the issue has been corrected


smtask_7009 smtask_7010 smtask_7012 smtask_7013 smtask_7032 smtask_7038 Service System reference: HQ-276-193-CRA9

Issues

D6) No Online Help on the field Posted in the Loaner Ledger Entry table (T_5914)

Issue

There used to be no online help explaining the functionality of this field (T_5914_13). Now there is. The online help for this field reads: "A check mark in this field means that the service order with the service item to which the loaner belongs is posted. If this field is blank, it means that the service order is not (yet) posted".

This has been implemented

T_5914_13 Service System reference: NL-142-314-HEVJ


D7) T_27 Item, missing field online Help

Error

The online Help for T_27_5901 and T_27_5902 was missing. This online help has been created.


T_27_5901 T_27_5902 Service System reference: HQ-397-65-CQ69

D8) “Object Type" On-line Help

Error

In the Job Scheduler Setup window, the Object Type field said: "This field contains the type of the object that carries out the job. There are four options: Blank, Report, Dataport and Codeunit". This is incorrect. There are only three options: Report, Dataport and Codeunit. The online help has been corrected accordingly.


T_5981_4 Service System reference: INT-258-886-3V3R