AXForum  
Вернуться   AXForum > Microsoft Dynamics CRM > Dynamics CRM: Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск Все разделы прочитаны

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 02.09.2008, 13:23   #1  
Blog bot is offline
Blog bot
Участник
 
19,193 / 651 (60) +++++++
Регистрация: 28.10.2006
Summary: Uploaded



== Overview ==

This document describes the changes between Microsoft Navision Attain W1 3.10.A and Microsoft Navision Attain W1 3.60.

== Application Changes ==

=== General Changes ===

==== Errors fixed ====

A1) Roles are Not Correct in the Demonstration Data
Error
Some of the roles were not properly updated. They had read-only permissions to the Posted Document Dimension table.
This has been corrected.
Codeunit 101991

Service System reference: SG-51-401-3654
Internal Workbase reference: 6484EF10CBF9FDD0C1256AFB0033EAC1
A2) Table Caption ML Length Should be Able to be Longer than 30 Characters
Error
If you inserted a Caption ML for e.g. the G/L Entry table that was longer than 30 characters, a text overflow error appeared when running Navigate. You can now enter a Caption ML containing more than 30 characters.
This has been corrected.
Table 265 Document Entry
Form 344 Navigate

Service System reference: DE-306-102-HHSR
Internal Workbase reference: 3451CEC7C1286DCDC1256B5800374862
A3) Usability Issues Concerning Lookup and Drilldown Buttons in the Base Calendar Code Field (Customer, Vendor, Shipping Agent, Location)
Error
Usability of the lookup and drilldown buttons in the Base Calendar Code field was not satisfactory. A new field, called Customized Calendar, needed to be added to the relevant forms, which will drill down to the Customized Calendar Entries form. This field should show 'Yes' if there is a customized calendar for a particular business partner (customer, vendor, shipping agent, location) and 'No' if there is no calendar.
This has been corrected.
The new Customized Calendar field has been added at the following forms and controls:
Form 1, control ID 69
Form 21, control ID 146
Form 26, control ID 121
Form 5703, control ID 47
Form 5790, Control ID 13

Service System reference: N/A
Internal Workbase reference: 49EB30D946A1F3E1C1256AFD0034471E
A4) Application Stopped Responding When Using a Calendar with All Non-Working Days
Error
The application would stop responding (“hang”) when calculating a production line using a calendar with all non-working days. This error was also present all other areas affected by the calendar, for example, Purchase and Sales.
This has been corrected.
Codeunit 7600 Calendar Management

Service System reference: N/A
Internal Workbase reference: 5B19A9003EFEE0E9C1256B100037A1E6
A5) Manufacturing Tab on General Posting Setup Card Confusing
Error
The manufacturing tab had setup information that was confusing because it was not manufacturing specific.
This has been corrected.
Service system reference: DE-606-437-RL7C
A6) Impossible to Establish a Link between Return Order and Blanket Order
Error
The blanket order was not updated if a related return order was posted.
This has been corrected.
Service system reference: CZ-799-902-2GMH
A7) “Customized Cal. Entries Subfm” (form 7605) Was Not Multilanguage Enabled
Error
Form 7605, “Customized Cal. Entries Subfm” (a subform of form 7606 “Customized Calendar Entries”), was not Multilanguage enabled.
This has been corrected.
Form 7605 Customized Cal. Entries Subfm.

Service System reference: DE-542-639-LE6Y
Internal Workbase reference: 62CB518A3D910871C1256BB50041948B
A8) Generation of Demonstration Data With Currency Other Than GBP
Error
It was not possible to change the local currency in the demonstration data without changing code in the demonstration data tool. The Currency Code field on the Demonstration Data Tool form (101900) has now been made editable so it is possible to change the currency without having to change any code.
This has been corrected.
Form 101900 Demonstration Data Tool
Codeunit 101004 Create Currency
Codeunit 101098 Create General Ledger Setup

Service System reference: SG-949-773-XGPX
Internal Workbase reference: 83D058BFE4633487C1256BDB002A5651
A9) Permission Errors in S&R Roles
Error
The error occurred for users who only had the following roles: ALL, S&R-CUSTOMER, S&R-Q/O/I/R/C, if they created a sales order, the program would show a Read-permission error to the Source Code Setup table (242) and the Contact table (5050).
This has been corrected.
Codeunit 101991 Create Permissions

Service System reference: CH-90-698-4G2J
Internal Workbase reference: 247B9ED5316ED9F8C1256BDB0041DCDA
A10) No Permissions to VAT Amount Line
Error
No role had permissions to the Vat Amount Line table (290), so nobody except super users could press F9 on a sales order to show the statistics. Now permission to Read, Insert, Modify and Delete in the VAT Amount Line table has been added to the following roles: P&P-Q/O/I/R/C, P&P-Q/O/I/R/C, POST, S&R-Q/O/I/R/C and S&R-Q/O/I/R/C, POST.
This has been corrected.
Codeunit 101991 Create Permissions

Service System reference: HQ-464-29-RHEY
Internal Workbase reference: D89FF0595D1CA1F2C1256BF0002FC6DE
A11) Monthly Calendar Date Error
Error
When you looked up the first system date on the monthly calendar, the program responded with an error message informing you that you were outside the permitted date range.
This has been corrected.
Service system reference: GB-990-499-WBZR
A12) Erroneous Responsibility Center Data
Error
On some reports that contained orders that came after an order to a responsibility center, for example 205, the orders that came after the one to the responsibility center also contained responsibility center data – even though they did not have a responsibility center.
This has been corrected.
Service system reference: NL-103-69-XHQD


=== General Ledger ===

==== Features ====

A13) XBRL Specification 2
Feature
In this release, our existing XBRL functionality has been revised to accommodate the release of XBRL Specification 2 by the XBRL Consortium late last year. XBRL is an XML-based electronic markup language based on accepted financial reporting standards and practices that enables the exchange of financial information across all software and technologies, including the Internet.

With XBRL-enabled Navision Attain, you can: import unlimited numbers of taxonomies from public authorities, credit institutions, banks, and so on; view information attached to taxonomy; map taxonomy lines to any combination of general ledger accounts, using standard Navision Attain filters; view and print out XBRL document file for appraisal before sending; export XBRL document that can then be sent as e-mail.
This feature has been implemented.
A14) Analysis Views to Excel
Feature
The dimensions functionality has been extended by adding the facility to export the dimensional information in the Analysis Views to Microsoft Excel. This will give the opportunity to analyze and work with Attain data in Excel.
This feature has been implemented.
A15) Payment Tolerance
Feature
We have included two new options.

• Payment Discount Tolerance: Payment discount tolerance is a new feature providing a payment discount ‘grace period’. It will now be possible to set a tolerance level for a number of days in order to apply and close the invoice and payment, even if the discounted payment is made later than the payment discount date specified in the payment terms.

• Payment Tolerance: It will now be possible to set a tolerance level (in local or other currency) on an invoice in order to be able to apply and close the invoice and payment – even if there is a difference in the amounts.
This feature has been implemented.
A16) Change Log
Feature
We have developed a new granule, which enables you to log user changes made to Navision Attain master data. It is possible to log all direct modifications a user makes to the data in the database, except changes to “working documents” such as journals and sales and purchase orders. The change log functionality makes it possible to get a chronological list of all changes to any field in any table (except the above mentioned) and to see who (what user ID) made the changes.
This feature has been implemented.
Errors fixed
A17) Entry in the Default Dimension Table Was Not Deleted when the Dimension Was Deleted
Error
If a default dimension had been set up for a table and that dimension was deleted, the entry in the Default Dimension table was not deleted.
This has been corrected.
Table 348 Dimension

Service System reference: DK-898-724-2KKK
Internal Workbase reference: BC3F09B9C39D7555C1256B3A00544DC7
A18) Wrong Error Message in General Journal
Error
If a general journal line was posted with Settlement entered in both Gen. Posting Type field and Bal. Gen. Posting Type field, an error message would appear. The error message read "The Purchase option can only be used.....", but it should have read "The Settlement option can only be used....".
This has been corrected.
Table 81 Gen. Journal Line

Internal Workbase reference: 4E28270DA295FCF341256A8B00545483
A19) Dimension Setup and Renaming of Codes
Error
It was not possible to rename a dimension code or a dimension value code if there had been any postings containing these codes. This was not in accordance with standard Navision functionality, where you should be able to rename after posting and have the program update any ledger entries and other tables.
This has been corrected.
Table 348 Dimension
Table 349 Dimension Value
Table 369 Selected Dimension
Table 379 Detailed Cust. Ledg. Entry
Table 380 Detailed Vendor Ledg. Entry

Internal Workbase reference: 5D21452078A71E6441256A72004AB5D0
A20) Incorrect Window Caption in Form 547
Error
The window caption in the Posted Document Dimensions form (547) was incorrect.
This has been corrected.
Form 547 Posted Document Dimensions

Service System reference: DK-122-566-4HQG
Internal Workbase reference: 4350D52043436CA2C1256B5A00303591
A21) Form 314 General Posting Setup Missing Code for the "OnActivate" Trigger
Error
In the General Posting Setup window (314), the code for the OnActivate trigger was missing for the following fields: Sales Line Disc. Account, Sales Inv. Disc. Account, Purch. Line Disc. Account, Purch. Inv. Disc. Account, Direct Cost Applied Account, Overhead Applied Account, Purchase Variance Account and Purch. FA Disc. Account.
This has been corrected.
Form 314 General Posting Setup
Service System reference: BE-101-155-SLSE

Internal Workbase reference: 05ABD7B864E22C2FC1256B6F00472D0B
A22) Detail Trial Balance Report Heading No Longer Corresponded to Report Name
Error
The heading of the printed Detailed Trial Balance report was "G/L - Detail Trial Balance". Due to changes in the program, this was no longer correct. It has now been changed to "Detail Trial Balance".
This has been corrected.
Report 4 Detail Trial Balance

Internal Workbase reference: 19A436237CC30C54C125649F002309A0
A23) Application Inconsistency
Error
There was an inconsistency option in the Type field on the sales and purchase lines. One of the account type options was Account (G/L), but it should have been G/L Account as elsewhere in the program.
This has been corrected.
Table 37 Sales Line
Table 39 Purchase Line
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 167 Job
Table 168 Job Budget Line
Table 169 Job Ledger Entry
Table 210 Job Journal Line
Table 211 Job Budget Entry
Table 212 Job Posting Buffer
Table 246 Requisition Line
Table 5108 Sales Line Archive
Table 5110 Purchase Line Archive
Table 6651 Return Shipment Line
Table 6661 Return Receipt Line
Table 99008501Inbound Sales Document Line
Table 99008503 Inbound Purchase Document Line
Table 99008507 Outbound Sales Document Line
Table 99008509 Outbound Purchase Document Line
Codeunit 408 DimensionManagement

Internal Workbase reference: 40361E5DE7D2B3FDC125646E0023185F
A24) General Journal – Test Report and Ext. Doc. No.
Error
If you chose to have an Ext. Doc. No. for customers and you created an invoice without an external document number and ran the test report, an error message appeared. In Purchase & Payables, you are given a warning in the text of the report instead of an error message.
This has been corrected.
Report 2 General Journal - Test

Service System reference: DE-257-127-GFHR
Internal Workbase reference: 32732C9C630769F0C1256B0600370D3E
A25) Budget and Negative Sign in Cell Amount
Error
It was not possible to enter a cell amount like this: 200-, in a budget.
This has been corrected.
Form 113 Budget

Service System reference: DE-267-906-9KSA
Internal Workbase reference: F93040E358E1473FC1256B060037F694
A26) Combination of a Zero Amount and Dimensions Resulted in an Inconsistency Error
Error
When consolidating with the option "Copy Document" set to true an inconsistency error would appear if the last G/L entry on an account contained a zero.
This has been corrected.
Report 90 Import Consolidation from DB

Service System reference: BE-557-359-QLDK
Internal Workbase reference: 85595E051A3193EAC1256B870033DF18
A27) VAT Statement Preview Was Incorrect
Error
Amounts shown in the VAT Statement preview window were shown in local or additional currency, but without any indication of which one. Now the currency of the amounts is clear.
This has been corrected.
Report 12 VAT Statement
Form 474 VAT Statement Preview

Service System reference: NL-593-600-9AUP
Internal Workbase reference: B76279A15F14F675C1256B5D003D7068
A28) Consolidation Error when Consolidating More than One Company at a Time
Error
When consolidating more than one company at a time and these companies had dimensions with the same code, the Consolidation - Test Database report (14) and the Import Consolidation from DB report (90) produced an error, since the dimension was inserted without checking whether it already existed.
This has been corrected.
Report 14 Consolidation - Test Database
Report 90 Import Consolidation from DB

Service System reference: N/A
Internal Workbase reference: 2234CBA6768E4056C1256B6500327F44
A29) Incorrect VAT Amount with Unrealized VAT
Error
When an invoice, purchase or sale, was posted and unrealized VAT was used, then VAT was posted to the VAT Unreal. account. When the invoice was applied the VAT-amount was moved from the VAT Unreal. account to the normal VAT account. This was incorrect, for example if a credit memo was applied to an invoice. This has been corrected. Now the movement from the VAT Unreal. account to the normal VAT account is carried out only if the Document type is blank or Payment.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: CH-368-992-YDDU
Internal Workbase reference: C0FA086A1877155EC1256B75002F314C
A30) No VAT Amount in G/L Entry for Payment Discount Accounts
Error
If an invoice was posted and applied with a payment so that payment discount was granted, no VAT amount was inserted in the G/L entry for the payment discount accounts.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: DE-596-337-9ED8
Internal Workbase reference: CBE4DDF49D809DCDC1256B80002E6231
A31) VAT Codes Not Initialised in Journals When Using Fixed Asset
Error
In a Fixed Asset G/L Journal Line, VAT codes were not retrieved to the line if Fixed Asset was entered in the Account Type field. This was the case even if a check mark had been inserted in the Copy VAT Setup to Jnl. Lines field.
This has been corrected.
Table 81 Gen. Journal Line

Service System reference: NO-456-685-3K7W
Internal Workbase reference: 8BAE766F4FEF59D8C1256B58004F4D7D
A32) Consistency Error When Voiding a Check with Discounts
Error
When posting a check with payment discounts, the check could not be financially voided from the Check Ledger Entries in the Bank Account card.
This has been corrected.
Codeunit 367 CheckManagement

Service System reference: ZA-904-127-WA54
Internal Workbase reference: C1436B5C51686DF4C1256B95004CECD3
A33) Consistency Error When Financially Voiding a Check
Error
Financially voiding a check that was debited against a G/L Account produced a consistency error.
This has been corrected.
Codeunit 367 CheckManagement

Service System reference: ZA-347-165-UF39
Service System reference: US-61-566-3PJV
Internal Workbase reference: 412B39643180C58FC1256B99003F8CE2
A34) Analysis Views and Setup Checklist
Error
When copying settings for a company, the settings of the analysis views also copied the data of the previous entry number and previous budget entry number when using the setup checklist. This was incorrect as the program would not accept data with these numbers.
This has been corrected.
Codeunit 406 Setup Checklist Management

Service System reference: BE-51-741-5G3Q
Internal Workbase reference: A254AA778A5E01D9C1256B5F002EF605
A35) The Check Type Field in Report 1406 Is Not Used
Error
The Check Type field in report1406 could only have value ‘Total Check' in the W1 version. It has therefore been removed from the report.
This has been corrected.
Report 1406 Bank Account - Check Details

Service System reference: N/A
Internal Workbase reference: EC490777E6D970CBC1256ABD002D528F
A36) The Dimension Buffer Already Exists
Error
When the Calculate Inventory function was executed including dimensions, an error message appeared saying that the dimension buffer already existed.
This has been corrected.
Codeunit 411 Dimension Buffer Management

Service System reference: NL-584-771-ZJA2
Internal Workbase reference: 46C24F0E9AE97744C1256B97004163EC
A37) In Codeunit 13 - Function CopyFields - GenJnlLine5 is Both a Global and a Local Variable
Error
In the CopyFields function in codeunit 13, there was a variable defined both as a global and a local variable.
This has been corrected.
Codeunit 13 Gen. Jnl.-Post Batch

Service System reference: DK-639-191-PCMM
Internal Workbase reference: 3E33C8FF804AAB1CC1256BAD0029223D
A38) XBRL Document with Source Type Rollup
Error
The XBRL document did not show any amounts when Rollup was entered in the Source Type field.
This has been corrected.
Report 504 XBRL Export Instance - Spec. 1

Service System reference: DE-490-893-7NGN
Internal Workbase reference: A5ED8013EB12FF52C1256B7C00318348
A39) XBRL Document and Amounts over 10000000.00
Error
It was not possible to see amounts over 10000000.00 in XBRL Export Instance – Spec. 1 report (504).
This has been corrected.
Report 504 XBRL Export Instance - Spec. 1

Service System reference: DE-29-703-7NPX
Internal Workbase reference: EA349DCBD24F38DDC1256B7C0030841B
A40) Responsibility Center Had Incorrect Properties
Error
Field 6, Post Code, in Table 5714, Responsibility Center, should have had the Test TableRelation and Validate TableRelation properties set to No.
This has been corrected.
Table 5714 Responsibility Center

Service System reference: INT-641-467-8GDL
Internal Workbase reference: 44AA0BFB9DF9C54D41256AB00030F191
A41) Default Dimensions Remained in the Default Dimensions Table after Deleting the Responsibility Center
Error
After deleting a responsibility center, the entries created for it remained in the Default Dimensions table.
This has been corrected.
Table 5714 Responsibility Center

Service System reference: INT-641-467-8GDL
Internal Workbase reference: E67D9B017CC7A470C1256B6D0049102C
A42) Mapped Totaling G/L Accounts Showed No Amount when Export XBRL Taxonomy
Error
Totaling G/L Account which had been mapped to a taxonomy line no were not exported when the taxonomy was exported.
This has been corrected.
Codeunit 420 XBRL Management

Service System reference: DE-458-637-QCW6
Internal Workbase reference: ADFDA9579654950DC1256B6C00409CF9
A43) Filters on the XBRL Export Instance Form Did Not Work
Error
Filters on the XBRL Export Instance report (504) were not taken into consideration when exporting the XBRL Taxonomy.
This has been corrected.
Codeunit 420 XBRL Management

Service System reference: DE-456-822-7NRK
Internal Workbase reference: C91E426C819ABD81C1256B7C0030CBE6
A44) Performance Issue In The Function CopyLines In The Posting Gen. Jnl Line Codeunit (13)
Error
There were some performance issues when posting several lines from the Gen. Journal Line table (81).
This has been corrected.
Codeunit 13 Gen. Jnl.-Post Batch

Service System reference: NL-433-592-KAKN
Internal Workbase reference: 103CDC9AE7C3784DC1256BB8004480AD
A45) Incorrect DecimalPlaces for the Amount Field on Intrastat Journal Line
Error
The Amount field (14) on the Intrastat Jnl. Line table (263) had the property DecimalPlaces to 0:5 instead of 0:0.
This has been corrected.
Table 263 Intrastat Jnl. Line

Service System reference: DE-269-169-7BUT
Internal Workbase reference: 3D7D52DD61B91A1DC1256BBC004B97B0
A46) C/AL-Code on Documentation-Trigger in the Account Schedule Report (25)
Error
There was some C/AL-Code in the Documentation-Trigger on the Account Schedule report (25) which should not have been there.
This has been corrected.
Report 25 Account Schedule

Service System reference: DE-620-714-SFMG
Internal Workbase reference: C66A0A6C5E59201EC1256BB300341BAF
A47) Incorrect C/AL-Code in The Function UpdateColumnDim in The Dimensions - Total Report (27)
Error
The following line of C/AL code could be found in the UpdateColumnDim function defined on the Dimensions - Total report (27):

TempDimSelectionBuf.SetDimSelection(
3,REPORT::"Dimensions - Detail",AnalysisViewCode,ColumnDim,TempDimSelectionBuf);

It should have read:

TempDimSelectionBuf.SetDimSelection(
3,REPORT::"Dimensions - Total",AnalysisViewCode,ColumnDim,TempDimSelectionBuf);
This has been corrected.
Report 27 Dimensions - Total

Service System reference: DE-171-567-SFT7
Internal Workbase reference: 7B6DEB7AE72146B2C1256BB300320CFE

A48) Blocked Analysis View Card
Error
No error message appeared when trying to update a blocked analysis view.
This has been corrected.
Codeunit 410 Update Analysis View
Report 84 Update Analysis Views

Service System reference: DE-484-525-XEVP
Internal Workbase reference: 2AA8F3582CC35008C1256B7400310624
A49) Copy Document Did Not Copy Dimensions Properly
Error
If an invoice was created using Copy Document the dimensions attached to the lines were not copied.
This has been corrected.
Codeunit 6620 Copy Document Mgt.

Service System reference: US-176-20-8SHZ
Internal Workbase reference: 912733BFC397A8BAC1256B590046B4FE
A50) Separators in Account Numbers
Error
If separators were used in g/l account number and dimension values, budgets could be exported to Excel but could not be imported back into Navision Attain.
This has been corrected.
Report 82 Export Budget to Excel
Table 370 Excel Buffer

Service System reference: AU-391-617-393X
Internal Workbase reference: C78EA58FEC0C0B2DC1256B1800380CA8
A51) Dimension Name Had an Extra Space
Error
When entering a new dimension code, the dimension name was defaulted to the code plus one extra space. Now there is no space after the dimension name.
This has been corrected.
Table 348 Dimensions

Service System reference: CA-690-202-FR25
Internal Workbase reference: 150D9F513E8CCB97C1256BA50038B26B
A52) Difference in Codeunit 12 Could Cause Unrealized VAT Errors
Error
There was a difference in the code between ApplyCustLedgEntry and ApplyVendLedgEntry which could cause errors in the calculation of unrealized VAT.

ApplyCustLedgEntry(VAR NewCVLedgEntryBuf : Record "CV Ledger Entry Buffer";VAR DtldCVLedgEntryBuf : Record "Detailed CV Ledg. Entry Buf
CustUnrealizedVAT(NewCustLedgEntry,RemainingAmtToBeApplied);

ApplyVendLedgEntry(VAR NewCVLedgEntryBuf : Record "CV Ledger Entry Buffer";VAR DtldCVLedgEntryBuf : Record "Detailed CV Ledg. Entry Buf
VendUnrealizedVAT(VendLedgEntry,RemainingAmtToBeApplied);

A "new" is added to the code in ApplyVendLedgEntry.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: DE-314-829-QGQG
Internal Workbase reference: D0E3111712BA8DFEC1256BC1002C2220
A53) Posting to a G/L Account with Dimensions Value Posting = Code Mandatory
Error
Global Dimensions were transferred incorrectly when posting journal lines to a g/l account with Dimension Value Posting = Code Mandatory.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: CH-478-782-DEH8
Internal Workbase reference: C51124D12DA507A4C1256BB300298371
A54) Missing Additional Reporting Currency in Account Schedule Report (25)
Error
Additional reporting currency was missing when running the Account Schedule report (25) with the Show Amount in Add. Reporting Currency option selected.
This has been corrected.
Codeunit 8 AccSchedManagement

Service System reference: DE-811-556-WF5Y
Internal Workbase reference: 03485CC6D94DC67FC1256BC1002A5DCC
A55) Consolidation Amount Size
Error
The maximum amount size you could import and export when consolidating was 13 bytes. This has been changed to 22 bytes.
This has been corrected.
Report 91 Export Consolidation
Report 92 Import Consolidation from File

Internal Workbase reference: 8729624163DFEC6E412562A700494A02
A56) Problem with Consolidation and Analysis by Dimension
Error
If you ran the consolidation more than once for the same period the amounts in the analysis view increased although the corresponding G/L account balance did not.
This has been corrected.
Report 90 Import Consolidation from DB
Report 92 Import Consolidation from File

Service System reference: DE-590-636-QH6X
Internal Workbase reference: B0C4A04DAC8F9287C1256BC8002F75F5
A57) Changes of Transaction No. After Running the Adjust Exchange Rate Report (595)
Error
The Adjust Exchange Rate report (595) changed the contents of the Transaction No. field on detailed customer and vendor ledger entries, when an adjustment was made twice with same filters.
This has been corrected.
Report 595 Import Adjust Exchange Rates

Service System reference: FR-929-520-LGMG
Internal Workbase reference: F029B424A2B7D82CC1256BC8004D3279
A58) Check Numbers Were Skipped
Error
The system skipped the first check number when a payment journal contained more than 10 lines.
This has been corrected.
Report 1401 Check

Service System reference: SG-38-856-2GYW
Internal Workbase reference: D60424689FA42318C1256B9900466784
A59) Error Message When Exporting Analysis View to Excel
Error
If you exported an Analysis View from Attain to Excel and the Analysis View contained a hyphen (-) in its name, an error message appeared in Excel.
This has been corrected.
Codeunit 424 Export Analysis View

Internal Workbase reference: 90D0574D4FE06709C1256BCD0034125F
A60) Correction of Remaining Amount
Error
When you applied customer ledger entries in different currency you got an incorrect Correction of Remaining Amount entry.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Internal Workbase reference: E1FB6E5CBB1E737AC1256BD70050BB40
A61) Inefficient Key Used In Codeunit 12
Error
An incorrect key was used in codeunit 12 for posting customer payments.
This has been corrected.
Table 21 Cust. Ledger Entry
Table 22 Vendor Ledger Entry
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: DK-484-150-ZDGJ
Internal Workbase reference: F45E29C57C892023C1256BD8002D7937
A62) Decimal Overflow in Account Schedules
Error
A check mark in the Show Amount in Add. Reporting Currency field in the Account Schedule Overview form could result in a decimal overflow error.
This has been corrected.
Codeunit 8 AccSchedManagement

Service System reference: HQ-327-124-2FH5
Internal Workbase reference: 49BA0A228C47BDD9C1256BDE00458C63
A63) Date and Time Was Not Rounded in Change Log Entry
Error
It was difficult to filter the change log entries by time, because the Date and Time field and Time field were not rounded to the nearest second. The reason for not rounding was originally a C/SIDE error, which caused the contents of the Time field to differ from the content of the Date and Time field, by one second.
This has been corrected.
Codeunit423 Change Log Management

Internal Workbase reference: 3C56C7BC103F30EBC1256BE40041AC8A
A64) Programming Rules Not Followed in the Currency Exchange Rate Table (330)
Error
Programming rules were not followed in the Currency Exchange Rate table (330).
This has been corrected.
Table 330 Currency Exchange Rate

Internal Workbase reference: 7442AE8FC99E021BC1256688003619F0
A65) The Document Dimensions Table (357) Was Not Updated when Making an Order from a Quote
Error
In the Document Dimensions table (357) a quote created document dimensions for tables (36) and (37). But when converting the quote to an order, the document dimension for table (36) was not changed accordingly.
This has been corrected.
Codeunit 86 Sales-Quote to Order
Codeunit 96 Purch.-Quote to Order

Service System reference: FR-403-156-NMRU
Internal Workbase reference: 884ADF534234F6D2C1256B4F00468759
A66) Redundant Code in the Acc. Schedule Line Table (85)
Error
There was some redundant code in the Acc. Schedule Line table (85) for the Dimension 1 Totaling, Dimension 2 Totaling, Dimension 3 Totaling, and the Dimension 4 Totaling fields (19 - 22). This has been removed.
This has been corrected.
Table 85 Acc. Schedule Line

Service System reference: DE-579-107-NC2W
Internal Workbase reference: 0F169079974F80C5C1256B9000282FD1
A67) Wrong Posting Date when Using Date Compression in Analysis by Dimension
Error
When setting the starting date of a period of the same length as the compression level in the Analysis View (e.g. some date in the middle of the month when date compression is set to month), the entries prior to the starting date were given a date that was later than the compressed entries for the rest of the month.
This has been corrected.
Table 363 Analysis View
Codeunit 410 Update Analysis view

Internal Workbase reference: 5AAEF1F4B5C699FFC1256BAA00337B24
A68) Obsolete Code in the Update Analysis View Codeunit (410)
Error
Due to a C/SIDE error there was a DELETEALL statement in the Update Analysis View Codeunit (410):

<PRE>
Function FilterIncludesBlanks(VAR TheFilter : Code[250]) : Boolean
WITH TempDimBuf2 DO BEGIN
DELETEALL; // Necessary because of C/SIDE error
INIT;
INSERT;
SETFILTER("Dimension Code",TheFilter);
EXIT(FIND('-'));
END;
</PRE>

The error in C/SIDE is now corrected, and the entire line has been removed.
This has been corrected.
Codeunit 410 Update Analysis View

Service System reference: DK-364-58-6JH4
Internal Workbase reference: 3F0A6B8E6D52A449C1256BBB002B57CD
A69) Apply Linkbases to Taxonomy
Error
If you click in the blank box in the upper left-hand corner of the XBRL Linkbases window, the system highlights all created Linkbase types. If you then clicked the Function button and chose Apply to Taxonomy, only the linkbase where the cursor was, was applied to the taxonomy.
This has been corrected.
Form 589 XBRL Linkbases

Internal Workbase reference: 0B6B0E05779D9054C1256BBB00350EFE
A70) Not All Filters Were Exported from Account Schedules to Excel
Error
Only some of the filters from the Acc. Schedule Overview were shown on the top of the Excel worksheet when Account Schedules were exported to Excel.
This has been corrected.
Report 29 Export Acc. Sched. to Excel

Internal Workbase reference: 7D9B02774C270F9E4125691E005AADBF
A71) Exclude Closing Entries Disabled Drill Down to Budgets
Error
If you entered the option Exclude in the Closing Entries fields on the G/L Account Balance/Budget form, and drilled down in the Budgeted Amounts fields, the program generated an error.
This has been corrected.
Form 120 G/L Budget Entries

Service System reference: INT-692-572-3UU6
Internal Workbase reference: D0DE01998A706AE7C1256AE1004138CF
A72) Strange Message when Posting a Purchase Account and a Customer Account
Error
When posting journal lines using a purchase account and a customer account, a strange message occurred when trying to post. The same thing happened with a sales account and a vendor account.
This has been corrected.
Codeunit 13 Gen. Jnl. Post Batch

Service System reference: DK-126-604-MJA7
Internal Workbase reference: 1A472B48BAE50576C1256B3A0051D815
A73) Wrong Date Filter and Total Amount Field in Analysis by Dimensions
Error
When setting up the Date Filter for an Analysis View, the program showed some entries with posting dates outside the date filter. The Total Amount fields also contained incorrect values when Balance at Date was selected.
This has been corrected.
Form113 Budget
Form408 G/L Balance By Dimension
Form554 Analysis By Dimensions

Internal Workbase reference: 5F4339609052EC20C1256B4F0051F08F
A74) Missing Dimensions on Invoice Rounding Entry
Error
There were no dimensions on invoice rounding entries, when posting documents which triggered invoice rounding. Now the invoice rounding entry is given the same dimensions as the document header.
This has been corrected.
Codeunit 80 Sales-Post
Codeunit 90 Purch.-Post

Service System reference: CZ-520-644-2K5W
Internal Workbase reference: F05CF498E125F114C1256B5700374470
A75) Analysis View Budget Entries Were Filtered Incorrectly when Used in Account Schedule
Error
The entries in the Analysis View Budget Entry table (366) were not filtered with the analysis view code used in the account schedule, and therefore each budget entry appeared once for each analysis view that used the entry.
This has been corrected.
Codeunit 8 AccSchedManagement

Service System reference: DK-74-820-DGCP
Internal Workbase reference: 077F6406E4E1E5D5C1256B9100375464
A76) Budgeted Amounts Were Not Rounded in Additional Reporting Currency
Error
Budgeted amounts in additional reporting currency were not rounded in the Analysis by Dimensions form (554).
This has been corrected.
Form 554 Analysis By Dimensions
Codeunit 424 Export Analysis View

Internal Workbase reference: 70053158EC7E3744C1256B9800419ADC
A77) Journal Line Allocation Dimensions Were Not Deleted
Error
Journal line allocation dimensions were not deleted when you deleted a journal line.
This has been corrected.
Table 81 Gen. Journal Line

Service System reference: AU-954-378-35Z8
Internal Workbase reference: 2AB89320614910F9C1256BD80031CDBB
A78) The Budget Report (8) Showed Incorrect Amounts
Error
If you had a budget with both positive and negative amounts and, in the Budget report, set a filter on Budgeted Amount: "<0", only the first negative amount was shown.
This has been corrected.
Report 8 Budget

Service System reference: DE-643-735-3F6M
Internal Workbase reference: BF9F571DF2CF635EC1256BDC002EA0AB
A79) Incorrect Country Codes in the VAT VIES Report (19)
Error
The country code for Austria on the top of the VAT VIES report (19) was "AU", but should have been "AT".
This has been corrected.
REP19 VAT- VIES Declaration Tax Auth

Internal Workbase reference: D6B8DB1A9BDE38CEC1256BE3003A9CDE
A80) The Change Log Entries Report (509) Had a Wrong Caption for Date
Error
The field caption for date was "Date and Time". It has now been changed to "Date" in the Change Log Entries report (509).
This has been corrected.
Report 509 Change Log Entries

Internal Workbase reference: AFB82904C74FA660C1256BE50046CB7E
A81) Change Log Logged Blank Fields when Inserting and Deleting
Error
The program logged insertions and deletions of blank/zero fields. Doing this cluttered the picture and did not provide much useful information. Modifications of these fields are now not logged.
This has been corrected.
Codeunit 423 Change Log Management

Internal Workbase reference: E8AEC59D3DD52BDCC1256BD1003BDF18
A82) Export Account Schedule to Excel With Not Calculated Column Formula
Error
If an Acc. Schedule Overview with blank values in the Variance% field were exported to Excel, Excel would show -100 in the Variance% column.
This has been corrected.
Report 29 Export Acc. Sched. to Excel

Service System reference: DE-388-759-MNQ9
Internal Workbase reference: 5D326B4E1AA97DB7C1256B4B0032BE53
A83) Dimension Value Did Not Exist when Importing a Budget from Excel
Error
When a dimension value code was the same as a date code, and you exported a budget to Excel and then imported back into Attain, an error message which read "Dimension Value Does Not Exist". What happened was that the value was translated into a date instead of into a text value.
This has been corrected.
Report 81 Import Budget from Excel

Service System reference: US-72-678-MQXM
Internal Workbase reference: C1B485C850BA9FDAC1256BCD002EC1AD
A84) Missing Key in the Adjust Exchange Rate Report (595)
Error
The performance was very slow in the Adjust Exchange Rates report (595) because of a missing key.
This has been corrected.
Report 595 Adjust Exchange Rates

Service System reference: DE-752-716-NCFT
Internal Workbase reference: CEE428A3B87915F9C1256BCE0026BCB4
A85) When Using Manual VAT for Prices Including VAT the VAT Base Was Not Updated
Error
When changing the VAT amount on the VAT Specification form (574) for Prices Incl. VAT, the Amount Including VAT field was updated but the VAT Base field was not.
This has been corrected.
Table 37 Sales Line
Table 39 Purchase Line
Table 290 VAT Amount Line
Form 576 VAT Specification Subform

Service System reference: DE-705-810-MMKF
Internal Workbase reference: 015C0BB1F0403FA1C1256BD100258BF7
A86) Warning when Force Doc. Balance Was Set to False
Error
If Force Doc. Balance was set to false for a journal template and that journal contained lines with both customers and vendors, a warning messages appeared which read "Customer and Gen. Posting Type Purchase are not allowed." when running the test report (2).
This has been corrected.
Report 2 General Journal - Test

Service System reference: DE-770-837-REEB
Internal Workbase reference: 8CB76185863B74ACC1256BD100459F5C
A87) Performance Problems when Inserting a New Record in the Dimension Value Table (349)
Error
There was no proper key in the Dimension Value table (349), which could result in performance problems when adding and deleting dimensions.
This has been corrected.
Table 349 Dimension Value
Table 355 Ledger Entry Dimension
Table 356 Journal Line Dimension
Table 357 Document Dimension
Table 358 Production Document Dimension
Table 359 Posted Document Dimension
Table 361 G/L Budget Dimension

Service System reference: LT-352-725-4BSU
Service System reference: SE-804-847-4GUA

Internal Workbase reference: 26070A949B1B74DFC1256BF90028A1AA
Internal Workbase reference: 1D1DA65320511048C1256BDC002BC604
A88) Import Budget from Excel

Error

If you had G/L Account with leading zeroes (e.g. 0001) and imported budgets from Excel the budgeted amounts for these accounts were deleted.
This has been corrected.
Report 81 Import Budget from Excel

Service System reference: DE-634-920-MLNQ
Internal Workbase reference: C5F853AB2F368B76C1256BFA00273B37
Issues
A89) Payment Tolerance Date and Payment Tolerance Amount in Customer Ledger Entries
Issue
Payment tolerance days and payment tolerance amount are inserted in the customer ledger entries the user had to manually change the open customer ledger entries one by one to activate the payment tolerance feature. Two new functions have been implemented on the Customer Ledger Entry table (21). These functions either create or delete the payment tolerance days and payment tolerance amount based on what is set up. The function is called when you either check or uncheck the Allowe Payment Tolerance field on the customer card.
In response to this issue, a change has been implemented.
Table 21 Cust. Ledger Entry
Table 25 Vendor Ledger Entry
Form 21 Customer card
Form 26 Vendor card

Service System reference: DE-683-939-VG8H
Internal Workbase reference: 51915A225185BFF2C1256BD6002ED089

=== Sales & Receivables ===

==== Features ====

A90) Sales Price and Line Discount
Feature
The number of conditions for when a sales price applies has been extended. For example, it is now possible to define quantity breaks for sales prices.

Quantity discount and cust./item discount have been combined into line discount.
This feature has been implemented.
Errors fixed
A91) Orders Made from Blanket Orders Can Not Be Posted
Error
If an order was made from a blanket order and the blanket order contained sales lines with no value in the Qty. to Ship field, the order could not be posted.
This has been corrected.
Codeunit 87 Blanket Sales Order to Order
Codeunit 97 Blanket Purch. Order to Order

Service System reference: DK-603-730-7EX6
Internal Workbase reference: 2CF6245CFB2E69DBC1256B3B00538300
A92) Creation of Sales Orders Using Keyboard and Not Mouse
Error
If you pressed Enter after inserting the document date on a sales order, the program did not take you automatically to the lines, as it does on all other documents.
This has been corrected.
Form 42 Sales Order

Service System reference: SG-903-115-3597
Internal Workbase reference: C3FF3E822B849952C1256B1900311EA5
A93) Closed by Amount (LCY) has Wrong Sign
Error
In some cases, the amount in the Closed by Amount (LCY) field on a customer ledger entry had the opposite sign to the amount in the Closed by Amount field.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: GB-368-761-3K2X
Internal Workbase reference: 9A8B810901B406E7C1256B3A0041CF59
A94) Not Possible to Make a Post Batch With Released Sales Orders
Error
If you had released an order, you could not make the post batch, and you could also not change the posting date.
This has been corrected.
Table 36 Sales Header
Table 38 Purchase Header

Service System reference: DK-241-146-WDZB
Internal Workbase reference: C561F14CE75E5EC9C1256B3B0048F0C8
A95) Incorrect Invoice Lines Calculation With Line Discount
Error
There was an incorrect rounding of the line amount on documents when using the line discount.
This has been corrected.
Table 37 Sales Line
Table 39 Purchase Line

Service System reference: LV-171-539-X2H7
Internal Workbase reference: F26EF19294908675C1256B57003D9645
A96) Change VAT and Price Incl. VAT
Error
In the Order and Invoice Statistic windows the amounts were not calculated correctly if prices were inclusive of VAT.
This has been corrected.
Form 160 Sales Statistics
Form 161 Purchase Statistics
Form 402 Sales Order Statistics
Form 403 Purchase Order Statistics

Internal Workbase reference: 611FDD0A8006DFF3C1256B4A002F3708
A97) Combination "Calc. Inv. Discount" and "Allow VAT Difference" Causes Problems
Error
The error occurred if the program was set up to calculate invoice discount automatically and VAT differences were allowed. If a sales invoice was made where the VAT amount was modified in the statistics window, the modified VAT was not posted.

This was not corrected in BETA 1. A new solution has been implemented, and now the VAT difference is only zeroed when the invoice discount amount is actually changed.
This has been corrected.
Table 290 VAT Amount Line

Service System reference: ES-902-873-8F2Q
Internal Workbase reference: D17121F4829F1490C1256B7D0050F8BE
A98) Reminder Text Variables Include Wrong Content
Error
The reminder text variable did not always give the correct beginning text in the reminder.
This has been corrected.
Table 295 Reminder Header

Service System reference: DE-70-157-5LC2
Internal Workbase reference: A588B2E82E610F28C1256B6B00397178
A99) Original Pmt. Disc. Possible - Obsolete Code
Error
The code behind the validation of the Original Pmt. Disc. Possible field (39) in table 21 Customer Ledger Entry table (21) was obsolete, because the field is not editable anymore.
This has been corrected.
Table 21 Cust. Ledger Entry
Table 25 Vendor Ledger Entry
Codeunit 103 Cust. Entry-Edit
Codeunit 113 Vend. Entry-Edit

Service System reference: BE-121-446-6GSH
Internal Workbase reference: 3E33C8FF804AAB1CC1256BAD0029223D
A100) Shipment Date before Work Date on the Sales Line Created Two Error Messages
Error
When inserting a sales line when the shipment date was before the work date, an error message appeared twice.
This has been corrected.
Table 37 Sales Line

Service System reference: BE-223-601-VFDR
Internal Workbase reference: 9FAE93866E4CDEC6C1256B66006638D8
A101) Deleting the Purchase Code on a Sales Line Did Not Delete the Corresponding Fields on the Sales Line
Error
When deleting the purchase code on a sales line, the corresponding fields, such as Special Order or Reserve, were not updated according to the new blank purchase code.
This has been corrected.
Table 37 Sales Line

Service System reference: SE-768-347-ACXV
Internal Workbase reference: EA186C95B6CCF54EC1256B65004A4756
A102) Wrong UOM Used When Using Capable to Promise
Error
When using Capable to Promise, the UOM was taken from the item card, not the sales line.
This has been corrected.
Codeunit 99000886 Capable to Promise

Service System reference: INT-567-421-3V29
Internal Workbase reference: C4CE4F5AB030A916C1256B09004FCADC
A103) Wrong Location Code Used When Calculating the Planned Delivery Date and the Planned Shipment Date
Error
When calculating the planned delivery date and the planned shipment date on the sales lines, the sales header default location code was used instead of the location code on the sales line.
This has been corrected.
Table 37 Sales line

Service System reference: DK-9-385-VCYM
Internal Workbase reference: 85FAF45DA0277D08C1256B51004A0666
A104) A Missing Semicolon (“;”) Caused Problems When Adding Code in a Batch Job
Error
Using a batch job to add code to an object resulted in a compiler error due to a missing semicolon.
This has been corrected.
Form 99000959 Order Promising Lines

Service System reference: N/A
Internal Workbase reference: E12C32BE167E3519C1256B460025D6F5
A105) Variant Descriptions Did Not Overrule Item Descriptions
Error
When using the variant of an item on a sales line, the variant description did not overrule the item description.
This has been corrected.
Table 5715 Item substitution

Service System reference: N/A
Internal Workbase reference: 89A72A8F0B95813EC1256BBD004E187A
A106) Changes to Bill to Customer / Pay to Vendor No. fields on Sales and Purchase Orders Did Not Update the Gen. Bus. Posting Group
Error
When making a change to the Bill to Customer No. field on sales orders, or the Pay to Vendor No. field on purchase orders, the Gen. Bus. Posting Group was not updated.
This has been corrected.
Table 36 Sales Header
Table 38 Purchase Header

Service System reference: N/A
Internal Workbase reference: 42CB42096FA2239341256AB1006798BC
A107) Unit Price and Line Amount Fields Should Not Be Updated When Changing Job No.
Error
When changing the Job No., the Unit Price and Line Amount fields on the sales lines were updated, whereas they should have stayed the same.
This has been corrected.
Table 37 Sales Line

Service System reference: DE-661-125-VGJN
Internal Workbase reference: 0299E13A8495C80CC1256B050048D3E0
A108) Wrong Text in Sales Order Planning Window
Error
The text “shipment date” should be “Shipment Date” in Sales Order Planning window.
This has been corrected.
Form 99000883 Sales Order Planning

Service System reference: N/A
Internal Workbase reference: F8151B257586E6F9C1256B290043126C
A109) Shipping Agent Service Code for Customers’ Ship-to Address
Error
It was not possible to assign a separate Shipping Agent Service code for each customer’s Ship-to Address.
This has been corrected.
Table 222 Ship-to address.
Form 300 Ship-to address.
Table 36 Sales Header.

Service System reference: N/A
Internal Workbase reference: 85768CB008DAF513C1256B5300522AD9
A110) GLSetup.GET on Reports 202 and 402
Error
On Reports 202 and 402, GLSetup.GET was unnecessarily executed more than once.
This has been corrected.
Report 202 Sales Document - Test.
Report 404 Purchase Document - Test.

Service System reference: N/A
Internal Workbase reference: 47006B383F99888B41256AB000328993
A111) VAT Identifier Must Not Be The Same when VAT Percentages Are Different
Error
If the VAT Identifiers were the same on VAT Posting Setups with different VAT, the VAT was calculated incorrect on sales and purchase documents.
This has been corrected.
Table 325 VAT Posting Setup

Service System reference: DK-154-548-PHY6
Internal Workbase reference: 12034A33708C3DCDC1256BAE003B123E
A112) Standard Text Code on an Order
Error
If you had a text line on an order with a standard text code entered in the No. field and you tried to change the vendor or customer on the header, an error message appeared saying that you were not allowed to have a type of (blank) on the line.
This has been corrected.
Table 36 Sales Header
Table 38 Purchase Header

Service System reference: GB-157-15-6HD3
Internal Workbase reference: 621C16A7DE6F4EBEC1256B5F003291BF
A113) Field Description 2 Was Not Filled Out in Purchase and Sales Documents
Error
If a sales order was made with sales lines containing for example, a fixed asset that had text in the Description 2 field. The Description 2 field on the sales lines was not filled out.
This has been corrected.
Table 37 Sales Line
Table 39 Purchase Line

Service System reference: DE-137-203-VKTL
Internal Workbase reference: 2C482CFC6411EB06C1256B92003D855B
A114) Obsolete Code in Sales-Calc. Discount Codeunit (60)
Error
There was some obsolete code in the CalculateInvoiceDiscount function in the Sales-Calc. Discount codeunit (60):

<PRE>
SalesLine2.RESET;
SalesLine2.SETRANGE("Document Type","Document Type");
SalesLine2.SETRANGE("Document No.","Document No.");
SalesLine2.Setrange(Type,'<>0');
SalesLine2.SETRANGE("System-Created Entry",TRUE);
SalesLine2.SETRANGE(Type,SalesLine2.Type::"G/L Account");
SalesLine2.SETRANGE("No.",CustPostingGr."Service Charge Acc.");
IF SalesLine2.FIND('+') THEN BEGIN
ServiceChargeLineNo := SalesLine2."Line No.";
SalesLine2.VALIDATE("Unit Price",0);
SalesLine2.MODIFY;
END;
</PRE>

The line in bold has been deleted.
This has been corrected.
Codeunit 60 Sales-Calc. Discount

Service System reference: NL-371-825-GH23
Internal Workbase reference: 75AD1154326CDE2FC1256BAB00536C98
A115) Not Possible to Post Zero-Amount Orders
Error
It was not possible to post zero-amount sales orders using Payment Method Code on the header that had a Bal. Account No. An error message would appear saying that the Amount must not be zero.
This has been corrected.
Codeunit 80 Sales-Post
Codeunit 90 Purch.-Post

Service System reference: GB-488-548-4ETQ
Internal Workbase reference: 8020A46533687FABC1256B5800524B4A
A116) Missing Key in the Statement Report (116)
Error
A missing key in the statement report (116) caused a performance issue when running the report if there were a lot of detailed ledger entries.
This has been corrected.
Report 116 Statement

Service System reference: DK-448-527-DJUA
Internal Workbase reference: AF2CB530258A11C4C1256BC200316D9A
A117) VAT Calculation Error Using Orders with and without Price Including VAT
Error
Unit Price/Direct Unit Cost on documents was not calculated to include or exclude VAT, in accordance with what was on the actual invoice and the original documents.
This has been corrected.
Table 111 Sales Shipment Line
Table 121 Purch. Rcpt. Line

Service System reference: SE-983-720-7D4E
Internal Workbase reference: 29494F48F714A035C1256BC0004235B9
A118) Amount Including Tax was Calculated Incorrectly
Error
If you added a non-item line to a released invoice, the amount including tax was calculated incorrectly, because the tax group code was not taken into consideration.
This has been corrected.
Table 37 Sales Line
Table 39 Purchase Line

Service System reference: US-248-647-HTFD
Internal Workbase reference: 1FE192A85FB68499C1256B6600347594
A119) Missing Permission When Deleting Posted Invoices
Error
It was impossible to delete a posted invoice if you used a user license without item tracking.
This has been corrected.
Granule 4010 Basic Inventory in C/CAPS

Service System reference: ES-259-791-ZJYS
Internal Workbase reference: 326E9E592B24424EC1256B99002B3512
A120) “Get Shipment Lines” Could Not Be Executed on Sales Invoices for Shipped Special Orders
Error
When you tried to execute “Get Shipment Lines” on a sales invoice for a shipped special order, error messages appeared and it was not possible to retrieve the shipment line.
This has been corrected.
Table 111 Sales Shipment Line

Service System reference: NL-489-469-JFB8
Internal Workbase reference: F7919A4FB1DF08C5C1256B36004E8497
A121) “Combine Shipments” Could Not Be Executed for Special Orders
Error
When you tried to execute “Combine Shipments” for a special order, error messages appeared and it was not possible to finalize the operation.
This has been corrected.
Table 111 Sales Shipment Line

Service System reference: DE-472-440-4GKJ
Internal Workbase reference: 6CA8F35002071460C1256B5F0039134F
A122) The Profit % Field Did Not Work as Expected
Error
The Profit % on sales lines was not retrieved from the Item table.
This has been corrected.
Table 37 Sales Line

Service System reference: DK-281-988-7JDC
Internal Workbase reference: 42CB98676656CCFEC1256B3C003ED074
A123) Applied to Doc Type and Apply to Id Were Incorrect Copied
Error

If you created an invoice using copy document and copied a credit memo which itself was created using copy document, the applied-to doc type and id were also copied. This prevented the invoice from being posted.
This has been corrected.
Codeunit 6620 Copy Document Mgt.

Service System reference: GB-947-921-ZEKX
Internal Workbase reference: D778FFC25909762CC1256B98004E5777
A124) Missing Table Filter in the Customer Table (18)
Error
The table filter for the Payment field (69) in the Customer table (18) was missing a filter for entry type.
This has been corrected.
Table 18 Customer
Table 23 Vendor

Service System reference: FR-334-713-AFZM
Internal Workbase reference: 987B39E2FF44FBACC1256B9E004AE58F
A125) Statistics Windows Did Not Check for Overflow
Error
The Statistics windows did not check for credit limit overflow when the credit limit was very small.
This has been corrected.
Form 160 Sales Statistics
Form 397 Sales Invoice Statistics
Form 398 Sales Credit Memo Statistics
Form 402 Sales Order Statistics

Service System reference: GB-306-806-AKK3
Internal Workbase reference: 321F3D11D398B218C1256B9F00275203
A126) Error When Creating a Reminder
Error
The maximum number of reminders that could be created for an invoice was dependent on the number of levels that were defined. For example, if you had set up three levels and entered 5 in the Max No. of Reminders field, the program would only allow a given invoice to appear on up to three reminders. The program should, however, have allowed a given invoice to appear on up to five reminders (the first one on level 1, the second on level 2 and the rest on level three).
This has been corrected.
Codeunit 392 Reminder-Make

Service System reference: SE-276-669-3N6D
Internal Workbase reference: 6058C5999EC22258C1256BB900310809
A127) Missing Filter on Entry Type in Several Flowfields
Error
The table filter for the Cr. Memo Amounts field (71) and the Reminder Amounts field (105) in the Customer table (18) was missing a filter for entry type
This has been corrected.
Table 18 Customer
Table 23 Vendor

Service System reference: DK-39-1-CJQX
Internal Workbase reference: 36677CFFAB198442C1256BC1003053F3
A128) Incorrect Field Length of the Description Variable in the Statement Report (116)
Error
The field length of the description variable in the Statement report (116) was 30 but should have been 50.
This has been corrected.
Report 116 Statement

Service System reference: ES-379-582-4EMB
Internal Workbase reference: A5FAB11D40E23F4DC1256BDD002F7046
A129) Incorrect Filter for Flowfields in the Customer Table (18)
Error
In the Customer table (18) and the Cust. Ledger Entry table (21), some flowfields did not have the right filters.
This has been corrected.
Table 18 Customer
Table 21 Cust. Ledger Entry
Table 23 Vendor
Table 25 Vendor Ledger Entry

Service System reference: AT-524-919-YCAS
Service System reference: DE-560-594-WK95
Internal Workbase reference: 9105D4BB4124A241C1256BD60031D259
Internal Workbase reference: B1A0F2248137A1FAC1256B53003CF523
A130) Incorrect Transaction Number
Error
If an application was posted containing only detailed customer and vendor ledger entries (not G/L Entries), the application functionality in codeunit 12 gave the detailed customer and vendor ledger entries a new transaction number. If you then posted an invoice, the transaction number on the created G/L entries was incorrect.
This has been corrected.
Codeunit 12 Gen. Jnl.-Post Line

Service System reference: SI-399-620-NLEC
Internal Workbase reference: C9A6362E676E8A88C1256BD60041D4B4
A131) The On Hold Field Was Not Editable
Error
It was not possible to edit the On Hold field on closed customer ledger entries.
This has been corrected.
Table 21 Cust. Ledger Entry
Table 25 Vendor Ledger Entry
Codeunit 113 Vend. Entry-Edit

Service System reference: DK-956-647-5QJK
Internal Workbase reference: 922306D60FAE79EBC1256BBA0032F45C
A132) Incorrect Payment Discount % on Credit Memo and Return Order
Error
If you changed the Sell-to Customer No. or Buy-from Vendor No. on credit memos or return orders, and the first entered customer had a payment term where Calc. Pmt. Disc. on Cr. Memos was set to YES, the Pmt. Discount Date and Payment Discount % on the credit memo or return order were updated. If you then changed the Sell-to Customer No or Buy-from Vendor No. to a customer where Calc. Pmt. Disc. on Cr. Memos was set to NO, the Pmt. Discount Date and Payment Discount % on the credit memo or return order were not updated.
This has been corrected.
Table 36 Sales Header
Table 38 Purchase Header

Service System reference: DE-701-137-QGH7
Internal Workbase reference: E8C57BEBA5D869D7C1256BD4004BB6A0
A133) Payment Discount % Was Not Updated on Sales and Purchase Headers
Error
The Payment Discount % field on sales or purchase headers was not updated to account for relevant changes in payment terms.
This has been corrected.
Table 36 Sales Header
Table 38 Purchase Header

Internal Workbase reference: F674999D0FCA49D1C1256BDB004E5E86
A134) Error with Copy Document
Error
If there was a check mark in the Mark Cr. Memos as Corrections field in the General Ledger Setup table, and a Credit Memo or Return Order was created, the value in the Correction field was YES on the header. But when creating a credit memo or return order using the Copy Document function with the Include Header option selected, the value in the Correction field was changed to NO.
This has been corrected.
Codeunit 6620 Copy Document Mgt.

Service System reference: DE-524-762-7L8G
Internal Workbase reference: 611246937FBC14B6C1256BE600306FFF
A135) The Sales Document Test Report (202) Did Not Consider Prices Including VAT
Error
If you had a sales document with Prices Including VAT which also had payment discount excluding VAT, and you printed the test report, the payment discount on VAT was incorrect.
This has been corrected.
Report 202 Sales Document-Test

Internal Workbase reference: A603320993390CD2C1256BE9003E3114
A136) The Customer - Detail Trial Bal. Report (104) Varied Depending on the Starting Date and Where You Had Focus while Applying
Error
Detailed ledger entries with posting dates within the date range but relating to documents with posting dates outside the date range were not included in the Customer – Detailed Trial Bal. Report (104). This has been corrected by introducing a correction of Opening Balance at the beginning of the report. Detailed ledger entries of the type Corr. of Remaining Amount were not included in the report either, resulting in a balance that was different from the one on the customer card. This has been corrected by adding a separate correction line for remaining amount.
This has been corrected.
Report 104 Customer - Detail Trial Bal.
Report 304 Vendor - Detail Trial Balance

Service System reference: DE-536-748-2K39
Service System reference: DE-251-380-QGEZ
Service System reference: BE-603-424-VB4D

Internal Workbase reference: CF91C0163583531DC1256BDF0048F048
Internal Workbase reference: FEA841C081C09367C1256BC9002784BF
Internal Workbase reference: 6AEFA0CDEA2F0A69C1256BEA002BE192
A137) A SETRANGE in The Applied Customer Entries Form (61) Made SQL Server Choose Wrong Index
Error
In the Applied Customer Entries from (61) a SETRANGE statement made SQL Server selected an incorrect index.

<PRE>
SETCURRENTKEY("Entry No.");
SETRANGE("Closed by Entry No.");
MARKEDONLY(TRUE);
//SETRANGE("Customer No.",CreateCustLedgEntry."Customer No.");
</PRE>

The SETRANGE has been deleted from both the Applied Customer Entries form (61) and the Applied Vendor Entries form (62).
This has been corrected.
Form 61 Applied Customer Entries
Form 62 Applied Vendor Entries

Internal Workbase reference: DD73E1C17098FE95C1256BDD00340180
A138) The Issued Reminder Header Table (297) Was Missing in Permission For The Change Global Dimensions Report (83)
Error
In the Change Global Dimensions report (83), the permission for the Issued Reminder table (297) was missing.
This has been corrected.
Report 83 Change Global Dimensions

Service System reference: DE-664-609-3AA7
Internal Workbase reference: A18E4C3A2DD18A87C1256BF7002DEAF9
A139) Quantity Field Values on Blanket Orders
Error
The value in the Quantity to Ship field changed the value in the Quantity field when you made an order from a blanket order.

This has been corrected.
Service system reference: DK-489-996-YCET
A140) Due Date Overwritten during Batch Invoicing
Error
If you placed a check mark in the Replace Posting Date field on the Batch Post Sales Orders batch job, the batch job automatically replaced the Document Date as well, which in turn caused the system to recalculate the due date. This happened even when you did not select "Replace Document Date".

This has been corrected.
Service system reference: SE-175-485-WKYS
A141) Modified Bill-to Information Not Included on New Sales Orders
Error
When you changed the bill-to (pay-to) address on a sales order and then created a new sales order, the bill-to address information was not included on the new sales header.

This has been corrected.
Service system reference: SE-612-8-DBDJ
A142) Batch Postings and Posting Dates on Released Orders
Error
You could not make a batch posting when you had a released order, and the posting date could not be changed.
This has been corrected.
Service system reference: BE-848-842-8D2S
A143) Copying a Sales Document with a Blanket Order Number
Error
When posting an invoice with a blanket order number into a credit memo, the Blanket Order No. could not be copied without recalculating the lines.

This has been corrected.
Service system reference: DE-286-271-CKKZ
A144) Blanket Order Posting Date
Error
The program used the wrong number series for new sales orders when you made them by copying a sales order into a blanket order; you would end up with a posting date that was copied from the order to the blanket order.
This has been corrected.
A145) Posting Stopped in Codeunit C5920
Error
Posting was halted in Codeunit C5920 when you tried to post a sales line which had an item type but no item number.

This has been corrected.
Service system reference: NL-573-548-XHP2
A146) Change of Sell-to Customer on a Sales Order
Error
You could not change the sell-to customer on a sales order when there was standard text included on the sales line.

This has been corrected.
Service system reference: BE-446-956-8EQU
A147) Erroneous Message When Deleting a Sales Person
Error
When you deleted a sales person from a sales header and then paged down to the next sales order, you received the following message: “Do you want to rename the record?”.
This has been corrected.
Service system reference: SE-341-704-WD4Y
A148) Ship-to Code Incorrectly Transferred
Error
The ship-to code was not transferred correctly when you used the req. worksheet; Multiple purchase orders were created from multiple lines in the sales order when you ran the requisition worksheet.

This has been corrected.
Service system reference: NL-318-985-QKKW
A149) No Shipment Date When Creating a Sales Order from a Sales Quote
Error
When an order was created from a sales quote, the shipment date was not taken by default to be the working date (as when making a standard order).
This has been corrected.
Service system reference: DE-945-233-RKUZ
A150) Missing Variant Code
Error
When you copied a purchase/sales document into a new purchase/sales document and placed a check mark in the Recalculate Lines field, the variant code would be missing from the new document.
This has been corrected.
Service system reference: GB-492-92-QGWH
A151) Missing Statement
Error
In the function "IsFirstLine", the statement "TempSalesLine.COPYFILTERS(Rec);" was missing below the RESET statement.

This has been corrected.
Service system reference: NL-21-417-QDBF
A152) Error in Extended Text, Item and G/L Account with Get Receipt Lines
Error

When you created an invoice and used the function Get Receipt Lines following the creation of a purchase order for items with extended text (3 lines) – and then inserted another line with a G/L Account between the item line and the extended text – and then posted it (receive only) – an error message would appear.

This has been corrected.
A153) Tax Liable Data Missing from Sales Orders
Error

The Tax Liable Boolean field information in the Ship-to Address table, was not copied to sales orders when you specified the Ship-to code on the sales order.

This has been corrected.
A154) Error Using Undo Qty Posting and Item Tracking
Error

An error was created when you tried to undo lines on a purchase order with item tracking before final posting and invoicing if you had sold some of the items and created a sales order with several lines using item tracking and then tried to undo all the lines.

This has been corrected.
A155) Combined Shipment Deadlock
Error
Deadlock resulted when using the SQL option if more than one user started a combined shipment when Calc. Inv. Discount was set to YES.
This has been corrected.

=== Relationship Management ===

==== Features ====

A156) E-mail Logging for MS Exchange
Feature
A new functionality that gives users the ability to log all e-mail correspondence has been implemented.

Internal Workbase reference: 6BFE82FB8F6A8B9EC1256BC2002F389A
This feature has been implemented.
Table 13 Salesperson/Purchaser
Table 5050 Contact
Table 5051 Contact Alt. Address
Table 5062 Attachment
Table 5065 Interaction Log Entry
Table 5079 Relationship Management Setup
Table 5112 E-Mail Logging Semaphore
Form 5000 Relationship Management Menu
Form 5094 Relationship Management Setup
Report 5181 Relocate Attachments
Report 5192 Patch Exchange References
Codeunit 1 ApplicationManagement
Codeunit 5051 SegManagement
Codeunit 5064 E-Mail – Journaling
Codeunit 5065 E-Mail Dispatcher
A157) New Way of Classifying Contacts called Rating
Feature
We have introduced a new way of classifying contacts called Rating. Rating allows the user to classify his contacts using all the existing classification data. It is possible to set up your own classifications and show the result on the Contact card subform. The Rating Questions are updated instantly when a user sets or changes checkmarks in the form Contact Profile Answers – it is not necessary to run the batch job first.

Internal Workbase reference: B937A5C23443DCAAC1256BC2002FA295
This feature has been implemented.
Table 5088 Profile Questionnaire Line
Table 5089 Contact Profile Answer
Table 5101 Contact Value
Table 5111 Rating
Form 5051 Contact Card Subform
Form 5110 Profile Questionnaire Setup
Form 5112 Profile Question Details
Form 5114 Contact Profile Answers
Form 5170 Answer Where-Used
Form 5172 Answer Points
Form 5173 Answer Points List
Form 5189 Create Rating
Form 5190 Rating Answers
Form 5191 Create Rating Subform
Report 5199 Update Contact Classification
Codeunit 5059 ProfileManagement
A158) Client Outlook Integration
Feature
Integration between Navision Attain and the Microsoft Outlook client has been implemented.
The following items are synchronized:
Navision Attain Microsoft Outlook
To-do (of type other than Meeting) Task
To-do (of type Meeting) Appointment
Contact Contact

Internal Workbase reference: 9791F340B6787706C1256BC2004D43B0
This feature has been implemented.
Table 13 Salesperson/Purchaser
Table 5050 Contact
Table 5079 Relationship Management Setup
Table 5080 To-do
Table 5119 Outlook Integration Log
Table 5120 Outlook Int. Conflict Field
Table 5121 Synchronization Entry
Form 5000 Relationship Management Menu
Form 5077 Create Interaction
Form 5094 Relationship Management Setup
Form 5097 Create To-do
Form 5098 To-do Card
Form 5116 Salesperson/Purchaser Card
Form 5126 Create Opportunity
Form 5182 Outlook Profiles List
Form 5183 Outlook Integration Error Log
Form 5184 Outlook Int. Conflict Fields
Form 5185 Conflict Resolution Worksheet
Report 5166 Cancel Deleted To-dos
Report 5167 Export Contacts to Outlook
Report 5171 Synchronize with Outlook
Codeunit 1 ApplicationManagement
Codeunit 5069 Outlook Contact Handler
Codeunit 5071 Contact Handler
Codeunit 5072 Outlook Application Management
Codeunit 5073 To-do Handler
A159) Contact Search
Feature
A new functionality that gives users the ability to search for contacts, based on text fields on contacts, comments, interactions, opportunities and to-dos has been implemented. To improve the search result, the search string that you enter does not have to be an exact match.

Internal Workbase reference: FAAD413F77658A61C1256BC2004D7F1A
This feature has been implemented.
Table 5050 Contact
Table 5061 Rlshp. Mgt. Comment Line
Table 5065 Interaction Log Entry
Table 5079 Relationship Management Setup
Table 5080 To-do
Table 5092 Opportunity
Table 5113 Search Result
Table 5115 Search Detail
Table 5116 Search Result Detail
Table 5117 Contact Search Word
Table 5118 Contact Search Details
Form 5000 Relationship Management Menu
Form 5050 Contact Card
Form 5052 Contact List
Form 5094 Relationship Management Setup
Form 5077 Create Interaction
Form 5097 Create To-do
Form 5126 Create Opportunity
Form 5175 Search Details
Form 5176 Search Result List
Form 5177 Contact Search
Form 5178 Search Delimiters
Report 5170 Generate Search Index
Report 5172 Generate Contact Search Index
Report 5173 Gen. Interaction Search Index
Report 5174 Generate To-do Search Index
Report 5175 Gen. Opportunity Search Index
Report 5176 Generate Comment Search Index
Report 5182 Delete Opportunities
Report 5190 Delete Interaction Log Entries
Codeunit 5051 SegManagement
Codeunit 5067 SearchManagement
A160) Comments on Interactions
Feature
Comments have been added on the Interaction Log Entries list. Furthermore a comment button has been added to the following wizards at the end of the Description field:

• Create Interaction
• Make Phone Call
• Create Mail

Internal Workbase reference: 509826EE8EA36067C1256BC2002FB6A2
This feature has been implemented.
Table 5065 Interaction Log Entry
Table 5123 Inter. Log Entry Comment Line
Form 5076 Interaction Log Entries
Form 5077 Create Interaction
Form 5147 Make Phone Call
Form 5148 Create Mail
Form 5187 Inter. Log Entry Comment Sheet
Form 5188 Inter. Log Entry Comment List
Report 5190 Delete Interaction Log Entries
Codeunit 5051 SegManagement
A161) Integration to Purchases & Payables
Feature
The Purchase Integration covers the integration of the Contact field on the Vendor Card and on several purchase documents.

The purchase documents where the Contact field is integrated to the Contact Card in CRM - Marketing & Sales are:

• Quotes
• Blanket Orders
• Orders
• Invoices
• Return Orders
• Credit Memos
• Posted Invoices

Internal Workbase reference: 90A1325A222CAD0CC1256BC2002FC634
This feature has been implemented.
Table 23 Vendor
Table 38 Purchase Header
Table 122 Purch. Inv. Header
Form 26 Vendor Card
Form 49 Purchase Quote
Form 50 Purchase Order
Form 51 Purchase Invoice
Form 52 Purchase Credit Memo
Form 138 Posted Purchase Invoice
Form 509 Blanket Purchase Order
Form 6640 Purchase Return Order
Codeunit 5057 VendCont-Update
A162) Integration to Service Management
Feature
The Integration to Service Management covers the integration of the Contact table into several Service documents.

The Service documents where Contacts are integrated from the Contact Card in CRM – Marketing & Sales are:

• Contract Quotes
• Contracts
• Quotes
• Orders
• Posted Orders

Internal Workbase reference: FADA14F3EB36BDD3C1256BC2002FD430
This feature has been implemented.
Table 5900 Service Header
Table 5930 Posted Service Header
Table 5965 Service Contract
Form 5900 Service Order
Form 5945 Posted Service Order
Form 5964 Service Quote
Form 6050 Service Contract
Form 6053 Service Contract Quote
Codeunit 5900 ServOrderManagement
A163) Opportunity Details
Feature
A new feature has been introduced in order to show the sales stages that an opportunity is going through. It also shows the related to-dos and planned to-dos.

Internal Workbase reference: 4EFCD7841558199FC1256BC2002FDDF7
This feature has been implemented.
Table 5080 To-do
Table 5091 Sales Cycle Stage
Table 5093 Opportunity Entry
Form 5073 Sales Cycle Stages List
Form 5121 Sales Cycle Stages
Form 5123 Opportunity List
Form 5124 Opportunity Card
Report 5068 Opportunity – Details
Codeunit 101243 Create Report List
A164) Improvement of Opportunity Management
Feature
The management of opportunities is now more flexible. It is possible to move the opportunity between contacts within the company, move it to another salesperson or campaign and change the priority when the opportunity is in progress.

Furthermore it is possible to follow up on the whole sales process from the opportunity.

Now it is possible to create and activate the first sales cycle stage of an opportunity in one step.

Internal Workbase reference: 1574F94E9BD8955DC1256BC2002FE911
This feature has been implemented.
Table 36 Sales Header
Table 5092 Opportunity
Table 5093 Opportunity Entry
Form 5123 Opportunity List
Form 5124 Opportunity Card
Form 5128 Close Opportunity
Codeunit 80 Sales-Post
Codeunit 86 Sales-Quote to Order
Codeunit 6210 Sales Management
A165) Improvement of Usability
Feature
In various places in the CRM – Marketing & Sales we are able to view numbers and names at the same time. In wizards, numbers have been replaced with names.

Internal Workbase reference: C516CE4D88E4020BC1256BC2002FE956
This feature has been implemented.
Table 5065 Interaction Log Entry
Table 5076 Segment Header
Table 5080 To-do
Form 5076 Interaction Log Entries
Form 5077 Create Interaction
Form 5091 Segment
Form 5093 Segment List
Form 5096 To-do List
Form 5097 Create To-do
Form 5098 To-do Card
Form 5123 Opportunity List
Form 5124 Opportunity Card
Form 5126 Create Opportunity
Form 5129 Update Opportunity
Form 5132 Active Opportunity List
Form 5146 Assign Activity
Form 5150 Contact Segment List
Errors fixed
A166) Change Error Message
Error
When the "Attachment Storage Type" field = "Disk File" and the “Attachment Storage Location” field = ‘’ strange error messages appeared. This has been improved.

Internal Workbase reference: ABE0A90BB7449A6FC1256A090072DDF7
This error has been corrected.
Table 5062 Attachment
Codeunit 5054 WordManagement
A167) Text Overflow When Changing Contact Details
Error
When changing “First Name,” “Middle Name” or “Surname” and the total length of the name exceeded the maximum length of the “Name” field a strange error message appeared. A better message is now provided.

Internal Workbase reference:
0FD333DB5B0310BCC1256B75002FB228
ED6D21D407BDF1EDC1256B21005B01B8
This error has been corrected.
Table 5050 Contact
A168) Button Renamed
The button on Form 5110 used to be named “Function.” We have renamed it “Functions.”

Internal Workbase reference: 2094AC23FC1177C141256A1B002FBFB1
This error has been corrected.
Form 5110 Profile Questionnaire Setup
A169) Filters Not Stored in the Segment Criteria
Error
When a user tried to use the Segment Wizard, the Reduce report or the Refine report to set filters on contacts, the filters were not stored in the segment criteria.

Internal Workbase reference: E4EBEF13CFC0BFA0C1256B29002CF920
This error has been corrected.
Report 5186 Remove Contacts
A170) Recurring To-Do's Were Given an Incorrect Status
Error
When closing a recurring to-do, a new to-do is created as a copy of the old one and still marked “Completed.” This has been changed, so that the to-do is now given the status “Not Started.”

Internal Workbase reference: F002400232164CBCC1256B35002DA8EF
This error has been corrected.
Table 5080 To-do
A171) It's Not Possible to Create a New Segment from a Campaign Card
Error
When you want to create a new segment linked to a campaign on the campaign card you get an error.
This has been corrected.
Table 5076 Segment Header

Internal Workbase reference: 06940D51D9E1B253C1256B7B004C101C and CAB8E4828C7D4ED1C1256B7B0049A8D0
A172) Campaigns on Interaction Types and Segments.
Error
If you set up a campaign against an Interaction template and then try to use that template on a segment, Attain will crash.
This has been corrected.
Table 5076 Segment Header

Internal Workbase reference: B1191098936C5646C1256BA6002B925E
A173) SQL - Segment Header, Not Possible to Change Interaction Template
Error
On the SQL it was not possible to change Interaction Template.
This has been corrected.

Table 5076 Segment Header

Internal Workbase reference: BF7D0614A866CA9FC1256BC200422ED4
A174) Profile Questionnaire Setup
Error
In Profile Questionnaire Setup it was possible to delete questions with underlying answers. It was also possible to move answers and questions freely.
This has been corrected.
Table 5088 Profile Questionnaire Line

Internal Workbase reference: 6A936FBD352110B5412569900048CCAC
A175) Using Nonexistent Key in To-Do Matrix
Error
This caused the To-Do matrix to collapse.
This has been corrected.
Form 5099 To-dos

Internal Work base reference: E0E5DF811FEDBAC7C1256B44004B4C6B
A176) Default Value of the Type Field in Profile Questionnaire Setup
Error
Default value has been changed from Question to Answer.
This has been corrected.
Form 5110 Profile Questionnaire Setup

Internal Work base reference: 48A8DE7057CB03BA41256A090055DBD3
A177) Incorrect Filter When Drilling Down in the Opportunity Matrix
Error
The filter had wrong value only the first time a drill down was performed in the initial matrix field.
This has been corrected.
Form 5131 Opportunities

Internal Work base reference: 8E0730E1DE4A20C7C1256B2500375375
A178) Zip code and City Missing When Creating a Word Document
Error
When using the Address Format “Blank Line+Post Code+City" the Zip code and City were missing on the Word document.
This has been corrected.
Codeunit 5054 WordManagement

Internal Work base reference: A20DE15A003C8B0BC1256B80002EF785
A179) Improved Error Message in the Make Phone Call Wizard
Error
The user got this error message when the phone number was missing in the wizard:
“You have to fill in the Contact Via field”
This has been corrected.
Form 5147 Make Phone Call

Internal Work base reference: A1A7E821150B0995C1256B21005789BC
A180) An Error Could Occur in the Interaction Template List
Error
An error could occur in the Interaction Template List when entering a new record.
This has been corrected.
Form 5075 Interaction Templates

Internal Work base reference: 1FCEE934DE87EEA8C1256B7B004CFE6B
A181) An Opportunity Changes Status to "Closed" When Aborting the Make Order Function
Error
An Opportunity changes status to "Closed" even if the Make Order is aborted due to a warning.
This has been corrected.
Codeunit 86 Sales-Quote to Order

Internal Work base reference: 804FC474C1485475C1256B21002E4C28
A182) Search Index Mode in Relationship Management
Error
The “Search Index Mode” field could not be changed to Automatic Mode.
This has been corrected.
Table 5079 Relationship Management Setup

Internal Work base reference: DE27770A75335B16C1256BE6002CDF14

A183) Unable to Restore Sales Document
Error
When a Released quote was archived, the archived quote could not be restored. It is now possible to restore a released doc. Restored documents will always be open - also if they are archived as released.
This has been corrected.
Codeunit 5063 ArchiveManagement

Internal Work base reference: CEE517770DE78CAFC1256BD8004325BC
A184) Lookup from Relationship Management Setup to the Interaction Templates window
Error
It was not possible to add new records in the Interaction Template window if you opened it by doing a look up on some specific fields in the Relationship Management Setup window.

All the Interaction Template fields on the Relationship Management window now have the same table relation to the Interaction Template table. Several fields missed the "WHERE (Attachment No.=CONST(0))" clause. When pressing F3 the system failed because of the filter on "Attachment No.". This has been fixed without deleting the filter.
This has been corrected.
Table 5079 Relationship Management Setup
Form 5075 Interaction Templates

Internal Work base reference: E31428DA3AD59EF6C1256BD80031E727
A185) Report 5198 "Add Contacts" - Filtering Sequence
Error
The function "UpdateSegLines" on report 5198 "Add Contacts" contained two filters whose sequence needed to be swapped to improve performance on the SQL option.
This has been corrected.
Report 5198 Add Contacts

Internal Work base reference: 403D9041D46F6D93C1256BC6002B6312
A186) Overflow When Using High Number Series for Segments
Error
When you used a number series for segments as high as allowed (for example, SM000000000000000001) and you tried to log a segment and set a check mark in the field "Create Follow-Up Segment" an overflow occurred. The text constant Text002 has been changed and a CopyStr statement has been inserted to avoid Segment Header Descriptions exceeding 50 characters.
This has been corrected.
Codeunit 5051 Segmentation Management

Internal Work base reference: 3684D46C9D271551C1256BB100263CD2
A187) Missing Company Name When Exporting Segment Contact Info
Error
When you exported contact information from a selected segment, most of the contact information was exported but the Company Name was missing.
This has been corrected.
Dataport 5050 Export Contact
Dataport 5051 Export Segment Contact

Internal Work base reference: 0E4CA34DE625D273C1256BA300712406
A188) No Updating of Correspondence Type When You Change it in Interaction Templates
Error
When on a segment, the Interaction Template Code was validated twice, the field Correspondence Type (Default) was not updated if it had been changed between the first and the second insertion of the interaction template code.
This has been corrected.
Table 5076 Segment Header
Table 5077 Segment Line
Form 5091 Segment

Internal Work base reference: 3F24DF62974DF960C1256B7B004D4CF3
A189) Incorrect Table Relation: Table 5107, Sales Header Archive/Field 34, Price Group Code field
Error
There was an incorrect table relation in table 5107 for field 34; it appeared as “Table0”
This has been corrected.
Table 5107

Internal Work base reference: 68FF62E4162D10E7C1256BDB004116A0
A190) Attachments to Interaction Log Entries Could Not Be Handled
Error
When opening attachments from the interaction log that were not Word documents, the application waited a very short time before deleting the exported file again. Several applications were not able to start in the specified time, so the delay has now been changed to 10 seconds.
This has been corrected.
Table 5062 Attachment

Internal Work base reference: 5037FC77405E5DE5C1256BC1004F4A91
A191) Report Sales Cycle Analysis
Error
In Report Sales Cycle - Analysis the Total Amounts for "Estimated Value (LCY)" and "Calcd. Current Value (LCY)" were calculated incorrectly.
This has been corrected.
Form 5122 Sales cycle stage statistics
Table 5091 Sales Cycle Stage

Internal Work base reference: 8C62D70257D4D427C1256BD80030E63B
A192) Sell-to-Customer No. on Sales Line Not Populated
Error
When you created a quote for a contact and afterwards made an order from this quote, the fields "Sell-to-customer No.” and “Bill-to Customer No.” were not populated on the sales lines.
This has been corrected.
Table 5050 Contact

Internal Work base reference: 0C459087696517FFC1256BC1004E9436
A193) Incorrect "Bill-to Contact No." on Several Documents
Error
When entering a contact person in the "Sell-to Contact No.", the "Bill-to Contact No." was sometimes updated with the Contact Company “No.” instead of the Contact Person “No.” that had been entered.
This has been corrected.
Table 36 Sales Header
Table 38 Purchase Header
Table 5900 Service Header
Table 5965 Service Contract Header
Codeunit 5900 Service Order Management

Internal Work base reference: 5309C8F931F48D25C1256BD80026F629
A194) Automatic Cancellation of To-dos
Error
When a synchronized task or appointment was deleted in Outlook, the corresponding to-do was not cancelled in Attain.
This error has been corrected.
Report 5166 Cancel Deleted To-dos
Codeunit 5072 Outlook Application Management

Internal Workbase reference: 8B28DBF60C031329C1256C01003C44B8
A195) Synchronize With Outlook Batch Job Doesn’t Update All Contacts in Outlook.
Error
The Synchronize with Outlook batch job did not update all contacts in Outlook. All Contacts that were in the Outlook folder of one salesperson but belonged to a different salesperson were not synchronized.
This error has been corrected.
Report 5171 Synchronize with Outlook

Internal Workbase reference: 571A5E79FD749444C1256C01003C825A
A3) Users Are Not Informed That They Need To Synchronize With Outlook
Error
Once a user started Attain, no warning was given that he needed to launch the Synchronize with Outlook batch job to make sure that information was up to date.

This error has been corrected.

Codeunit 5072 Outlook Application Management

Internal Workbase reference: 76D2B32CE95BD03EC1256C01003D49B2
A196) No Error Messages Are Given If You Set Up Synchronization Incorrectly
Error
No error messages were given to the user if synchronization with Outlook was set up incorrectly. The same happened when changes occurred in Outlook after the last synchronization and therefore synchronization was not possible (for example, if the synchronization folder had been deleted), the user was not informed with an error message that synchronization had been disabled. When user modifications created a conflict – items were modified in both Outlook and Attain and the system could not determine which version was the last, the conflict was logged but the user was not prompted to resolve the conflict.
This error has been corrected.
Form 5185 Conflict Resolution Worksheet
Codeunit 5071 Contact Handler
Codeunit 5072 Outlook Application Management.
Codeunit 5073 To-do Handler

Internal Workbase reference: 27F70E1BF7F194A4C1256C01003DBA14
A197) Update Entry ID Functionality
Error
When applying a service pack to an Exchange Server (or upgrading from E5.5 to E2000) every Item got a new Entry ID. This destroys the link from Attain to the Appointment, Task and Contact Items resulting in a lot of errors. In worst case every item was duplicated in both applications.
This error has been corrected.
Update Entry ID has been added to allow updating of synchronization entries when the service pack has been applied to Exchange Server.

Table 5121 Synchronization Entry

Internal Workbase reference: 59173AA61A175241C1256BF10039222B
A198) Creating Tasks for a Period of More Than One Day
Error
In Attain, you have a duration field with minutes but no end date or time like you have in Outlook. Therefore a two day workshop would appear with duration, of 7230 minutes making it very hard for the user.
This error has been corrected.
Table 5080 To-do
Table 5119 Outlook Integration Log
Form 5097 Create To-do
Form 5098 To-do Card

Internal Workbase reference: F0FC66406B569F7BC1256BDC0036E4C6
A199) Not All Contacts Are Automatically Created in Outlook
Error
When you change the Salesperson on the Contact card of a Company, the new Salesperson code is also changed on the card of the Person belonging to the Company. This is not reflected in Outlook.

If you change a Salesperson code in Attain, the corresponding contacts will remain in Outlook. As soon as the contacts are changed in Outlook, the solution will switch back to the original Salesperson code again.
This error has been corrected.
Report 5171 Synchronize with Outlook
Codeunit 5071 Contact Handler

Internal Workbase reference: 6EFF83AD648AE266C1256BDC003A4BA8
A200) Private Items
Error
If a user marks an item as private after it has been synchronized in Attain, it will remain in Attain. If you then run the synch batch, you got a message ‘Conflict found: See Conflict Resolution Worksheet’ but when you went to the conflict resolution worksheet it was empty.
This error has been corrected.
Table 5119 Outlook Integration Log
Form 5185 Conflict Resolution Worksheet
Codeunit 5071 Contact Handler
Codeunit 5069 Outlook Contact Handler
Codeunit 5073 To-do handler

Internal Workbase reference: A45341C9332E5EFFC1256BDC00369DA1
1.5 Service Management
Errors fixed
A201) Text to Text Overflow in Report 6000
Error
When changing Dimension CUSTOMERGROUP:MEDIUM to CUSTOMER:SMALL an error message appears stating: “Overflow under type conversion Text to Text.”
This has been corrected.
Report 6000 Service Order - Test

Internal Workbase reference: 1817CFC1C37DB61041256AA100562FED
A202) Creating Service Order from Customer Card
Error
When creating a service order directly from the customer card, some fields on the service order were not automatically updated with data from the customer card.
This has been corrected.
Codeunit 5906 ServLogManagement
Table 5900 Service Header

Internal Workbase reference: D52194F5797685D5C1256B1F003E0E4F
A203) Incorrect Code in Troubleshooting Header Table
Error
When checking for number series in Trouble Shooting Header, the check was done on the wrong number series.
This has been corrected.
Table 5943 Troubleshooting Header

Internal Workbase reference: B87077A42C94FDB1C1256B20005359EC
A204) Sourcecode Not Created Automatically
Error
When a new company was created, Sourcecode for Service was not created automatically.
This has been corrected.
Codeunit 2 Company-Initialize

Internal Workbase reference: 50625572C54244B4C1256B200053883E
A205) Incorrect usage of Cost Used field in Service Item Trendscape
Error
The Cost Used field was not correctly updated in the Service Item Trendscape.
This has been corrected.
Table 5902 Service Invoice Line
Table 5905 Service Cost
Form 5910 Service Costs
Codeunit 5908 ServOrder-Post

Internal Workbase reference: CEAC5AF5B68773C5C1256B200054B42A
A206) ValidateTableRelation on Post Code in Service Header
Error
Validation on table relations on Post Code field has been changed to validate on No.
This has been corrected.
Table 5900 Service Header

Internal Workbase reference: 98AE6A8ACDA9A742C1256B200056491E
A207) Calculation of Default Response Duration
Error
When entering spare parts in the Service Item table, the warranty date on the entered parts was in some cases not calculated as expected.
This has been corrected.
Table 5940 Service Item
Codeunit 5920 ServItemManagement

Internal Workbase reference: 8654A4A8AC841CDCC1256B20005C2916
A208) Error in Service Item Log
Error
When service item components were replaced, the service item log did not show the correct entries in the Before and After fields.
This has been corrected.
Codeunit 5906 ServLogManagement

Internal Workbase reference: E8CFF304D2D44854C1256B41004B20C4
A209) Wrong Allocation Status
Error
When a Service Order was created from a Quote, and the used resources were reallocated, the repair status for the resources was incorrect.
This has been corrected.
Table 5901 Service Item Line

Internal Workbase reference: FF104A5C85463649C1256B41004BD249
A210) Service Management and Fault/Resolution Codes Relationship
Error
When entering Symptom Code, the filter on that code remained active even though it was not shown.
This has been corrected.
Form 5930 Fault/Resol. Codes Rlship.

Internal Workbase reference: 0E8D588E23D5F7C4C1256B41004C13ED
A211) Service Item created several times from Sales Order.
Error
The same service item could under certain circumstances be created several times.
This has been corrected.
Codeunit 5920 ServItemManagement

Internal Workbase reference: 5D653613AFC77E04C1256B41004CDC24
A212) Service Item Log Incorrect When Changing Customer and Ship-to-Code.
Error
When Customer or Ship-to-Code was changed on a service item, the entries in the service item log were incorrect.
This has been corrected.
Report 6037 Change Customer in Contract

Internal Workbase reference: 74DC412AD825BB51C1256B41004D463D
A213) Service Order Log Incorrect When Changing Resources
Error
In the service order log, the recording of activities was not consistent.
This has been corrected.
Table 5950 Service Order Allocation

Internal Workbase reference: A19676262D2FBB54C1256B41004D85D8
A214) Job Scheduler at Midnight
Error
The job scheduler would stop processing tasks at midnight.
This has been corrected.
Form 6094 Job Scheduler Management

Internal Workbase reference: AE743ECA72A1C499C1256B6E0043BADD
A215) Get Service Order Usage
Error
When several service invoice lines had the same item, location and quantity, and the function Get Service Order Usage was used, it was not possible to post the sales invoice.
This has been corrected.
Table 5933 Service Order Posting Buffer

Internal Workbase reference: D9A760532F899337C1256B6E00441C59
A216) Repair Status Setup
Error
It was possible to activate the repair status several times.
This has been corrected.
Table 5927 Repair Status

Internal Workbase reference: 18646C07C8ED761DC1256B6E004716C1 and 2C0423833DB85BE841256A80003DA315
A217) Incorrect Description on Service Order
Error
When using translation, the description of Service Item Lines was not translated.
This has been corrected
Table 5901 Service Item Line

Internal Workbase reference: 8507DDC1CE1E403AC1256B1F00514623
A218) Order Date Incorrect After Running the “Create Contract Service Orders” Batch Job
Error
When creating Service Orders from a batch job, the order date was changed from Work Date to Next Planned Service Date.
This has been corrected
Report 6036 Create Contract Service Orders

Internal Workbase reference: D4973C26B7667A7AC1256BFA002CDA62
A219) Dimensions Not Updated When Kate Decker Was Used as a Salesperson
Error
In the Demo data, Kate Decker was listed as a sales manager and if you used her as a salesperson, the dimensions for “Salesperson” were not updated.
This has been corrected
Codeunit 117565 Add Salesperson/Purchaser

Internal Workbase reference: 930AB4C5098E72A9412569E000589383
A220) Service Order Log Inconsistent
Error
When allocating and reallocating resources for a Service Order, the logging in the Service Order Log was not consistent.
This has been corrected
Table 5950 Service Order Allocation
Codeunit 5906 ServLogManagement

Internal Workbase reference: A19676262D2FBB54C1256B41004D85D8
A221) Creating Contract Service Orders via Periodic Activities
Error
When creating service orders from service contracts via periodic activities, the Repair Status field on the Service Item lines of the created service order was not updated.
.
This has been corrected
Report 6036 Create Contract Service Orders

Internal Workbase reference: 25AC8DA43C2824B8C1256B43004FD2DD
A222) Requisition When Creating a Service Quote
Error
When a Service Order Quote including stock out items is generated, no requisitions were made until the Quote was made into an order.
.
This has been corrected
Table 5902 Service Invoice Line
Report 99001019 Calculate Plan - Plan. Wksh.
Codeunit 5923 Service-Quote to Order
Codeunit 99000854 Inventory Profile Offsetting

Internal Workbase reference: E8E0A325D86CEF64C1256B4B004F09D7
A223) Unable to Delete Unposted Sales Invoice Lines
Error
You were unable to delete an unposted Sales Invoice Line created from a Service Contract.
This has been corrected
Table 37 Sales Line

Internal Workbase reference: A6E5561B5F2FFBBDC1256B75005201C8
A224) Renaming a Service Contract or Service Quote Caused an Error
Error
If you tried to rename a Service Contract or Service Quote an error would occur.
This has been corrected
Table 113 Sales Invoice Line

Internal Workbase reference: BE057E8637A07BD3C1256B7500526FE5
A225) Error Message during Posting When Making a Service Contract Quote into a Contract
Error
If a posting error occurred when you were making a Service Contract Quote into a Contract, the post dialog box did not disappear, and had to be canceled manually.
This has been corrected
Codeunit 5940 ServContractManagement
Codeunit 5944 SignServContractDoc

Internal Workbase reference: 2960AC0C5243FDA6C1256B97004706E6
A226) Service Contract Lines Could Be Posted Twice
Error
If new Service Item Lines were added to a Service Contract, which already had been invoiced, the new lines could be posted twice; first when the line was added and later during the periodic invoicing.
This has been corrected
Codeunit 5940 ServContractManagement
Codeunit 5944 SignServContractDoc

Internal Workbase reference: EB62E5C1521575A8C1256BE30046BEDE
A227) Incorrect Fields Updated When Changing Default Response Time on Service Contract
Error
When changing the Default Response Time on the Service Contract Header, the Line Value field and Line Amount field were updated in the Service Item Lines.
This has been corrected
Table 5965 Service Contract Header

Internal Workbase reference: DB09CA018575B629C1256BE3004732D7
A228) Error When Job Scheduler Passed Midnight
Error
When the Job Scheduler came to jobs to be performed after midnight, it stopped processing of all jobs.
This has been corrected
Form 6094 Job Scheduler Management

Internal Workbase reference: C1FFABD3FD8076EAC1256BE300485466
A229) Last Service Date Was Not Filled Out on the Service Item Card
Error
The program did not filled out the Last Service Date field automatically on the Service Item Card after service on the item was finished.
This has been corrected
Form 5980 Service Item Card
Codeunit 5908 ServOrder-Post

Internal Workbase reference: F52472E6EC29FBD1C1256BE5002C06DB
A230) Error Message When Showing Column Fault Comment
Error
When you attempted to show the column “Fault Comment” on the Service Order, an error message occurred. The column has now been removed and the Fault Service Comment Sheet can be reached by clicking the Line button and selecting the Comments command and then the Faults command.
This has been corrected
Form 5902 Service Order Subform
Form 5965 Service Quote Subform

Internal Workbase reference: 5BEF714F9CCDEC34C1256BE9004CCDAE
A231) Shortcut for Dimensions Missing
Error
Shortcuts for the dimensions (Shift+Ctrl+D) below were missing. Shortcuts have been added to the Service Contract, the Service Contract Quote, and the Posted Return Receipt forms.
This has been corrected
Form 6050 Service Contract
Form 6053 Service Contract Quote
Form 6660 Posted Return Receipt

Internal Workbase reference: B508F4661447C58FC1256BE9004DEA8C
A232) Exclude Warranty for Resources on Service Invoice Lines
Error
The program set line discounts to 100 on the Service Invoice Lines. The functionality has been changed, so the Line Discount is set to zero, if Exclude Warranty is checked.
This has been corrected
Codeunit 7000 Sales Price Calc. Mgt.

Internal Workbase reference: D1F6E725884C941CC1256BED0030D31F
A233) Creating Sales Invoices from Service Contracts
Error
When Item Lines on Service Contracts only contained a Description, this line was duplicated on the Sales Invoice.
This has been corrected
Codeunit 5940 ServContractManagement

Internal Workbase reference: B003E1D705C17C84C1256BE3004A3217
A234) Update on Forms in the Service Area
Error
The forms Comments -> Faults and Order -> E-mail Queue were not updated automatically. The first form has been removed, and the second has been corrected.
This has been corrected
Form 5961 Service E-Mail Queue

Internal Workbase reference: 5813F531F8BC879AC1256BE9004EC3F0
A235) Wrong Error Message on Table 37
Error
An error message on Table 37 was called with incorrect parameters, which resulted in unusable messages.
This has been corrected
Table 37 Sales Line

Internal Workbase reference: 543CFD23ADA4C6EEC1256BF7003F0161
A236) AssistEdit Button Missing for Serial No. on the Service Item Card
Error
On the Service Item card, the AssistEdit button was missing from the Serial No field. An AssistEdit button has been added to Serial No. on the Service Item Card. Clicking AssistEdit will show Item Ledger Entries created from Purchase or Sale.
This has been corrected
Form 5980 Service Item Card

Internal Workbase reference: E7AF2BC050058012C1256BED0031573C
A237) Telephone Numbers Missing on Reports
Error
Telephone numbers were missing on the following reports: Service Order, Service Quote, Posted Service Order, Service Contract, Service Contract-Detail, Service Contract Quote and Service Contract Quote Detail. The telephone numbers have been added to the below mentioned reports.
This has been corrected
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

Internal Workbase reference: DAB043335C26AD13C1256BF0004B48E1
A238) No Read Permission for Service Order Allocation Table
Error
Certain granule combinations resulted in no read permission for the Service Order Allocation Table.
This has been corrected
Table 5940 Service Order Allocation

Internal Workbase reference: 2F7ABF58CEDA495FC1256BAD003FFE78
A239) Error When Changing the Name for a Service Contract Template
Error
When you tried to change the name of a Service Contract template, an error occurred.
This has been corrected
Table 5968 Service Contract Template

Internal Workbase reference: 71A262C4F2FBD478C1256BAD0045F78F
A240) Service Item Statistics Incorrect
Error
When Service Item Lines were removed from a Service Contract, the posted Credit Memo was not deducted from the statistics for the Service Item.
This has been corrected
Codunit 5940 ServContractManagement

Internal Workbase reference: 19D2FFB5A7344B9DC1256BC3003F34C8
A241) Service Item No. Field Not Filled In on Sales Invoice and Credit Memo
Error
When creating Sales Invoice Lines and Sales Credit Memo Lines on the Service Contract, the Service Item No. field on the line was not automatically filled with the item being serviced.
This has been corrected
Codunit 5940 ServContractManagement

Internal Workbase reference: D3CBCAED8C6F721DC1256BC3003F6218
A242) Format of Addresses in Service Management
Error
The format of addresses in Service Management was inconsistent with the format of addresses in the rest of the application.
This has been corrected
Codunit 365 Format Address

Internal Workbase reference: D8E8CF5A5A934750C1256BDC0030C7AC
A243) Response Date Filter in Service Tasks
Error
It was not possible to use the dates “T” (Today) and “W” (Workdate) in the Response Date Filter on Service Tasks.
This has been corrected
Form 5915 Service Tasks

Internal Workbase reference: A351F90888FF8F9BC1256BE30048FADE
A244) Filter Error in Service Contract Templates
Error
A filter error occurred when switching between Service Contract Template List and Service Contract Template Card.
This has been corrected
Form 6055 Service Contract Template

Internal Workbase reference: EA362A59106CF7D3C1256BE30049832D
A245) Description Was Not Updated in Service Item Lines
Error
The description was not updated in Service Item lines when you changed a Service Item No. field or an Item No. field.
This has been corrected
Table 5901 Service Item Line

Internal Workbase reference: BF51843DB8AB8B2CC1256BE30049DCFC
A246) Change Bill-To Customer No. in the Service Header
Error
When you changed the Bill-To Customer on the Service Header errors occurred concerning dimensions and multiple Service Item Lines.
This has been corrected
Table 5900 Service Header

Internal Workbase reference: 215A62F1FAF496A2C1256BE3004A5A1D
A247) Updating a Locked Service Contract Quote
Error
When trying to update a locked Service Contract Quote, the form closed when accepting the error message.
This has been corrected
Table 5965 Service Contract Header

Internal Workbase reference: 1594475AFDB6D632C1256BE9004D46B5
A248) Invoicing a Non-Prepaid Service Contract
Error
When you posted a non-prepaid contract, the incorrect date would appear when you posted it.
This has been corrected
Codeunit 5944 SignServContractDoc

Internal Workbase reference: 39488573867941C4C1256BE9004EEF1E
A249) Error in Gain/Loss Entries on Service Contracts
Error
The Gain/Loss Entries for Service Contracts were not updated when Service Item Lines are added to the Service Contract.
This has been corrected
Table 5964 Service Contract Line
Table 5965 Service Contract Header
Codeunit 5944 SignServContractDoc

Internal Workbase reference: E17B73ABACBDEC44C1256BED00312522
A250) No Permission to Access Report 5936 Service Item Worksheet
Error
You were unable to access Report 5936 Service Item Worksheet since it was not added to the C/CAPS file.
This has been corrected
C/CAPS

Internal Workbase reference: 965C96D66E248243C1256BF30041B759

=== Purchases & Payables ===

==== Features ====

A251) Purchase Price and Line Discount
Feature
The number of conditions for when a purchase price applies has been extended. For example, it is now possible to define quantity breaks for purchase prices.

Quantity discount has been converted to line discount.
This feature has been implemented.
Errors fixed
A252) The Balance (LYC) Field on Form 161 Was Editable
Error
The Balance (LCY) field on the Vendor tab in the Purchase Order Statistics window was editable and should not have been.
This has been corrected.
Form 161 Purchase Statistics

Service System reference: DK-242-512-JBPZ
Internal Workbase reference: 979D54CBCD349382C1256B06003EDA31
A253) Dimensions of Purchase Order Lines Not Being Posted to Posted Receipt Header and Lines
Error
When creating a purchase order using drop shipment, no dimensions appeared on either the header or the lines of the posted purchase receipts.
This has been corrected.
Codeunit 80 Sales-Post

Service System reference: GB-238-211-XER4
Internal Workbase reference: BC7C0F58504251DBC1256B58004751F6
A254) Creating a Purchase or Sales Line Using Cross Reference No. Lost Dimension Information from the Item Card on the Line
Error
When creating a purchase or sales line using Cross Reference No. instead of Item No., the dimensions from the item card were lost from the line.
This has been corrected.
Table 37 Sales line
Table 39 Purchase line

Service System reference: SE-668-167-5B5L
Internal Workbase reference: 31B68D75A2FB73E9C1256BA3004ADCE7
A255) Vendor Order No. Was Not Transferred to the Posted Purchase Invoice and the Posted Purchase Receipts
Error
The Vendor Order No. was not transferred to the posted purchase invoices and the posted purchase receipts, as it should have been.
This has been corrected.
Table 120 Purch. Rcpt. Header
Table 122 Purch. Inv. Header
Form 136 Posted Purchase Receipt
Form 138 Posted Purchase Invoice

Service System reference: NO EXTERNAL LINK PROVIDED
Internal Workbase reference: 1C05327AF30A9E11412568F8004F9D82
A256) Item Substitutions Caption on Customer Item Substitutions Misleading
Error
The item substitutions caption shown in the Customer Item Substitutions form (5718) was not related to any customer. The caption was, therefore, misleading.
This has been corrected.
Form 5718 has been renamed “Item Substitution Entries”

Service System reference: N/A
Internal Workbase reference: EA3D413035AEBFD141256A14005626D8
A257) Missing Menu Item on Special Order for Purchase Orders
Error
The Get Sales Order menu item was missing under Functions, Special Order for Purchase Orders but present as a Drop Shipments menu item.
This has been corrected.
Form 50 Purchase Order
Codeunit 5702 Dist. Integration

Service System reference: INT-838-843-3USM
Internal Workbase reference: 7841C36645F927B441256AAA004F9F30
A258) Impossible to Specify a Ship-to Code for Drop Shipments – an Error Message Appeared in Requisition Worksheets
Error
In sales orders using Drop Shipment and Ship-to code, an error message appeared in the requisition worksheets when attempting to carry out an action message.
This has been corrected.
Codeunit 22 Item Jnl.-Post Line

Service System reference: CH-499-181-MN7W
Internal Workbase reference: 32E0C43218945A97C1256B4C0036E486
A259) Transfer-from Code Field Missing on Requisition Worksheet (and on Planning Worksheet)
Error
If was impossible to enable and see the Transfer-from code on the requisition worksheet or on the planning worksheet.
This has been corrected.
Form 291 Req. Worksheet.
Form 99000851 Planning Worksheet

Service System reference: DK-591-433-RE8L
Internal Workbase reference: CBD942AAA17E91D9C1256B6100488BAF
A260) Error in the Get Sales Orders Batch Job on the Requisition Worksheet
Error
In certain cases, when the Get Sales Orders batch job on the Requisition Worksheet was executed several times, the existing lines were ignored and new lines were added.
This has been corrected.
Report 698 Get Sales Orders

Service System reference: AT-574-153-8K62
Internal Workbase reference: 015F50CC976B2DA8C1256B5100372211
A261) Error in Posting No. on Posted Purchase Invoices
Error
It was possible to create gaps in the posting number series on posted purchase invoices.
This has been corrected.
Codeunit 90 Purch.-Post

Service System reference: ES-517-436-JE4F
Internal Workbase reference: 02C9FA02092C0E31C1256B66004301A9
A262) Missing Permissions to Carry Out Action Messages
Error
When you tried to initiate the Carry Out Action Messages batch job from the requisition worksheet with a user license that did not include Basic Manufacturing, permissions to the Carry Out Action codeunit were missing.
This has been corrected.
In granule 3550 Purchases & Payables – Requisition Management in C/CAPS

Service system reference: BE-753-274-XH6L
Internal Workbase reference: 3551E0B6E81344C5C1256B5D0042EC7E
A263) Error in Validate Trigger
Error
The validate trigger for field 99000751 in the Requisition Line table contained a call to the GET-function with incorrect parameters.
This has been corrected.
Table 246 Requisition Line

Service system reference: AT-863-672-6HAL, IT-439-138-9FL5
Internal Workbase reference: 74ECFC7969F1390DC1256B4C00436DD7
A264) Defining Filters in the Calculate Plan Batch - Req. Wksh. Batch Job
Error
It was impossible to define filters using the “|” operator in the Calculate Plan - Req. Wksh. batch job.
This has been corrected.
Report 699 Calculate Plan - Req. Wksh.
Report 99001019 Calculate Plan - Plan. Wksh.

Service system reference: DK-320-346-DHJF
Internal Workbase reference: 39B3D446517DE5F8C1256B95004B5AF2
A265) Suggest Vendor Payment Did Not Take Posting No. Series into Account
Error
When setting up a Posting No. Series on a batch name in the payment journal and afterwards running the suggest vendor payment batch job, the posting no. series was not taken into account.
This has been corrected.
Report 393 Suggest Vendor Payments

Service System reference: DK-992-164-WF9L
Internal Workbase reference: 2C3AA0CB32D56B95C1256B52004CDF14
A266) Error Calculating Last Direct Cost with VAT and Invoice Discounts
Error
There was an incorrect calculation of the Last Direct Cost field on the item card when you purchased an item from a vendor to which an invoice discount was applied. When you posted a purchase invoice with Prices Including VAT selected on the invoice header, the contents of the Last Direct Cost field on the item card were different from when you posted the same invoice without Prices Including VAT selected. The difference was the amount of VAT which applied to the amount of the invoice discount amount.
This has been corrected.
Codeunit 90 Purch.-Post

Service System reference: NZ-962-512-PD5B
Internal Workbase reference: A1A9BA816E2FBC1FC1256BEC003B2919
A267) It Was Not Possible to Open a Purchase Quote or Blanket Order from The Purchase List
Error
You could not open a purchase quote or blanket order from the Purchase List form (53) using Shift+F5.
This has been corrected.
Form 53 Purchase List

Service System reference: HQ-193-466-WEX4
Internal Workbase reference: E16795F732A03FC6C1256BF200412810
A268) Wrong Caption Class in Purchase Prices
Error
When the vendor had the option of “Price Including VAT = Yes” in the Item Vendor Catalog, prices were excluding VAT. When zooming, however, the prices were shown with VAT but the caption was Direct Unit Cost Excl. VAT.
This has been corrected.

Service system reference: DE-28-479-CKVD
A269) Requisition Worksheet Did Not Take Relevant Data from Stockkeeping Units
Error
When you got a drop shipment that had an SKU on a requisition worksheet, the vendor number, vendor item number and direct cost were not taken from the SKU.
This has been corrected.
Service system reference: CH-145-568-HHEV
A270) Gap in Posted Number Series
Error
The invoice number changed each time an invoice was unsuccessfully posted. For example, if the user forgot to fill in the Vendor Invoice No. field, this led to unused invoice numbers.
This has been corrected.
Service system reference: SI-6-156-4BU8
A271) The Report Vendor - Order Detail Did Not Show Changed Currency Code
Error
Even if you placed a check mark in the Show Amount in LCY field on this report, the value did not get calculated in LCY; the currency sign disappeared but the value was the same.
This has been corrected.
Service system reference: AT-25-149-8D6S
A272) Overview of Purchase Orders
Error
When you looked at the overview of the purchase orders and made the field "completely received" visible, the purchase orders where all the items had been received were visible but where purchase orders had extended text on the order lines there was no indication that they were completely received.
This has been corrected.
Service system reference: BE-704-849-YL37
A273) Dimensions Not Defaulted Properly When Using Cross Reference Items
Error
If you entered an item into a purchase order by using the Cross Reference, it would not set up the dimensions properly and could result in an error when you posted it.
This has been corrected.
Service system reference: DE-197-482-5CB6
A274) Invoicing Problems with Certain Extended Text Items
Error
If you created an item with extended text (3 lines) and then created a purchase order with this item and you inserted another line with a G/L Account between the line with the item and the extended text, then you were unable to invoice (only receive).
This has been corrected.
Service system reference: DE-440-63-7HH4
A275) Requisition Worksheet Line on G/L Accounts
Error
When using a G/L Account in the Requisition Worksheet and entering a Due Date for the purchase order that was about to be created, the system looked for an item that had the G/L Account No. and the user received an error message that the item did not exist.
This has been corrected.
Service system reference: AU-812-629-C4A6
A276) No Extended Texts in Purchase Order
Error
When you created a purchase requisition and ran the Carry Out Action Message batch job, the purchase order line did not have any extended texts inserted. This was in spite of the fact that the item had extended texts, Automatic Ext. Texts was true, and all the fields on the Purchases tab of the extended text header were checkmarked.
This has been corrected.
Service system reference: GB-857-0-8F6D
A277) Error Message when Posting a Purchase Invoice
Error
When you used the Get Receipt Lines function on a Purchase Invoice, but not all the order lines were invoiced, the error message you got when you tried to post the remaining order lines from the invoice referred to the wrong Receipt No. and Receipt Line No.
This has been corrected.
Service system reference: SE-154-433-XBK2
A278) Sequence of the "Lead Time Calculation" and "Vendor No" Fields
Error
Because the vendor lead time overwrites the lead time calculation on the item card, the Vendor No. field needed to precede the Lead Time Calculation field.
This has been corrected.
Service system reference: DK-915-312-MD9P
A279) No Access to the Planning Flexibility Field on the Req Worksheet
Error
It was not possible to access the Planning Flexibility field on the Req Worksheet.
This has been corrected.
Form 99000851 Req. Worksheet

Service System reference: DK-31-864-RAMR
Internal Workbase reference: A410CFE9CFA2DF0AC1256B04003AF53D
A280) Vendor Item No. Was Not Copied to Req. Worksheet
Error
When a vendor number and vendor item number had been applied to an item, and when looking at a requisition line that had that number, once you changed the “Requisition system” field to purchase, some fields related to the vendor in question should have been filled in but were not.
This has been corrected.
A281) Sales Cross Reference
Error
When attempting to apply a cross reference on a sales or purchase line to a vendor or customer that had multiple cross references numbers applied, the correct item was retrieved but the cross-reference number on the line was changed to one of the others existing for that item.
This has been corrected.
A282) Wrong Unit of Measure in Purchase Order if Base Unit of Measure <> Purch. Unit of Measure
Error
When attempting to apply a cross reference on a sales or purchase line to a vendor or customer that had multiple cross reference numbers applied, the correct item was retrieved but the cross reference number on the line was changed to one of the other existing for that item.
This has been corrected
A283) Void in the Number Series of Posted Invoices
Error
When a sales order was deleted using “Delete invoiced sales orders” in the periodic activities menu, it was deleted but the “posting no.” of the sales order was missing in the posted invoices.

A posted invoice should have been created as it is when you manually delete the sales order.
This has been corrected
A284) Sales Qty. Code Shown Using the AssistButton on the Item Card
Error
On table 27, item card, there was an error in field 13, Sales Qty. Disc. Code. While viewing properties it showed that Table Relation was set to "Item" instead of "Item Sales Qty. Disc".
On the Item card you could pick an item with the AssistButton in the Sales Qty. Disc. Code field.
This is no longer an issue as a result of a redesign in pricing
A285) Name and Address Fields on the Sales Header
Error
If the user changed the name and address fields on the sales header, it had no effect in following:

- Purchase&Receivables/Purchase Order/Functions/Drop Shipment/Get Sales Order
- Purchase&Receivables/Requisition Worksheet/Functions/Carry out Action Message (Requisition lines coming out of sales orders for the same customer, same ship-to code, and the same vendor will be summarized in one purchase order, ignoring the name and address fields in the sales order.)
This has been corrected
A286) Wrong Direct Cost set on the Drop Shipment Purchase Line when created through a Requisition.
Error
When Item Sales Unit of Measure was different from Item Purch. Item Unit of Measure then the Direct Unit Cost on the Drop Shipment Purchase Line was wrong when created a Requistion Line.
This has been corrected.
Service system reference: NL-638-40-RGVQ

=== Inventory ===

==== Features ====

A287) Undo Quantity Posting
Feature
This feature allows the user to undo a mistakenly posted receipt or shipment.
This feature has been implemented.
A288) Reconciliation Traceability
Feature
This feature enables the balances in inventory and general ledger to be synchronized. Having the Adjust Cost - Item Entries batch job to insert – instead of modify – this is done by adjusting value entries.

When posting to G/L per entry, it is possible to establish a link between value entry and G/L entry. This information is stored in the value entry in the following fields: G/L Entry No. (Account) and G/L Entry No. (Bal. Account). On the G/L entry, it is stored in the Value Entry No. field. This traceability only works for actual cost – not expected cost.
This feature has been implemented.
A289) Assignment of Non-Inventoriable Cost
Feature
This feature enables the user to make a more precise profit calculation because it is now possible to assign non-inventoriable cost. An example could be the cost of transporting the goods from the company to the customer (freight-out). This cost can now be assigned to sales.

As a result, a new field has been introduced on the value entry: Cost Amount (Non-Invt.).

This feature has been implemented.
A290) Performance Optimization for Cost Posting and Adjustment
Feature
Several SIFT indices on the value entry have been shortened. As a result, the following fields have been introduced: Sales Amount (Expected), Sales Amount (Actual), Cost Amount (Expected), and Cost Amount (Actual). These fields replace Amount and Adjusted Cost.
This feature has been implemented.
Errors fixed
A291) Assigning an Item Category Code to a New Item Did Not Set the Correct Default Costing Method
Error
When assigning an Item Category code to a new item, the correct default costing method was not transferred to the item.
This has been corrected.
Table 27 Item.

Service System reference: DK-588-957-HGQQ
Internal Workbase reference: 22F9535743BD8D59C1256B760034776E
A292) Transfer Header Table 5740 Test Relation Properties Inconsistent with Sales and Purchase Header Test Relation Properties
Error
The properties of the Validate Table Relation and Test Table Relation fields 7 and 16 of the transfer header table 5740 were inconsistent with the same values for sales and purchase headers: they should all be “No”.
This has been corrected.
Table 5740 Transfer Header.

Service System reference: BE-529-383-BC94
Internal Workbase reference: A0FF20EBD58312B8C1256B650048B680
A293) Wrong Code in Form 353 Item Availability Lines
Error
Trigger ShowSchedNeed on Form 353 Item Availability Lines contained “ProdOrderLine.SETRANGE”, whereas it should have been “ProdOrderComp.SETRANGE”.
This has been corrected.
Form 353 Item Availability Lines

Service System reference: DE-251-667-7JMQ
Internal Workbase reference: 247C3A5A93558EBFC1256B970032021A
A294) Document Date Was Deleted if the BOM Was Exploded in Item Journals
Error
Some fields were missing on the exploded lines when exploding an Item Journal line:
"Document Date",
"External Document No.",
"Source Code",
"Reason Code",
And a link on the "Journal Batch Name".
This has been corrected.
Codeunit 246 Item Jnl.-Explode BOM

Service System reference: INT-219-980-3USL
Internal Workbase reference: D884B4E17AB16AA741256AAA004F5FD6
A295) Error in Transfer Statistics.
Error
The quantity in Transfer Statistics was doubled when the transfer order was shipped.
This has been corrected.
Form 5750 Transfer Statistics

Service System reference: INT-602-526-3V3A
Internal Workbase reference: C70B34CA99C8982CC1256B0900490B65
A296) Missing CaptionML in Form 99000918 Action Message Entries
Error
CaptionML = “Source Type” was missing on control 4 in Form 99000918 Action Message Entries.
This has been corrected.
From 99000918 Action Message Entries

Service System reference: DE-65-667-6C3J
Internal Workbase reference: E716A7E5E67F2C1EC1256B9000342B33
A297) Source Code Not Shown in Item Registers When Exploding BOM in Item Journal
Error
When an item with a BOM was exploded and posted in Item Journal, no source code was recorded in the Item Register.
This has been corrected.
Codeunit 246, Item Jnl-Explode BOM

Service System reference: INT-46-19-3UPE
Internal Workbase reference: D3847460C359ECD5C1256B020048DBE3
A298) Error Message When Attempting to Explode a BOM in Item Journal
Error
In certain circumstances, when an attempt was made to explode an item with a BOM in the Item Journal, the error message “There is not enough space to explode BOM” would appear.
This has been corrected.
Codeunit 246, Item Jnl-Explode BOM

Service System reference: DE-126-84-XALM
Internal Workbase reference: 9AC5A92E5CACFEFEC1256B7400375F78
A299) Inventory Levels Incorrectly Depicted on Item Card after Returning from SKU
Error
When returning from an SKU to the item card, the inventory level of that SKU was wrongly shown as the inventory level on the item card.
This has been corrected.
Form 5700 Stockkeeping Unit Card

Service System reference: N/A
Internal Workbase reference: 64A4607264D40D1CC1256B42004C1868
A300) Field Post Code on Table Locations Should Not Have TestTableRelation=Yes
Error
The TestTableRelation property in the Post Code field on table locations was wrongly set to Yes.
This has been corrected.
Table 14 Location.

Service System reference: NL-497-303-MBEJ
Internal Workbase reference: 0A12D85D463F061DC1256B4F0043D8A5
A301) Error In Availability Calculations
Error
The availability calculations can be found in different places in the application, but in some places they were not correct.
This has been corrected.
Form 5415 Item Avail. by Variant Lines
Report 705 Inventory Availability

Service System reference: DK-241-117-RAA4, NL-43-677-WLS9
Internal Workbase reference:
3C4D307689696567C1256B1E00429233
B5328F3C11CE8910C1256B61004DFAD6
A302) Availability Calculations Used Ending Date on Production Order Lines
Error
The availability calculations on the item availability forms used the ending date on the production order lines to calculate the scheduled receipt column instead of the due date.
This has been corrected.
Form 353 Item Availability Lines

Service System reference: INT-708-198-AEAM
Internal Workbase reference: 7B1BBE91BFDEBDE5C1256B640034CE44
A303) Editable Fields on Item Table
Error
Some flowfields on the item table were editable.
This has been corrected.
Table 27 Item

Service System reference: BE-691-891-BCBB
Internal Workbase reference: 4CBC2BB4562BD8B1C1256B88003A43C1
A304) Check Availability Form Caption
Error
The caption on the Check Availability form (342) was set to “Navision Attain”. The result was that the Help text for this form could not be found.
This has been corrected.
Form 342 Check Availability

Service System reference: N/A
Internal Workbase reference: 5A90873E8473C6E841256AB2002EED48
A305) Variants and Bins in the BOM Journal
Error
When a BOM journal line with a variant code defined was posted, the variant code was not transferred to the Item Ledger entry. The same situation applied to the Bin code.
This has been corrected.
Codeunit 32 BOM Jnl.-Post Line

Service System reference: CZ-580-70-FGH2, FR-979-65-ML9V
Internal Workbase reference: 0B28D2398C636AD3C1256B4C0030AC30
A306) Previewing the Post Inventory Cost to G/L batch before posting
Error
It was impossible to run a trial check on the inventory cost batch job before posting it to G/L.
This has been corrected.
Service system reference: DK-458-756-7B2Q
A307) Posting of Rounding Value Entries and Dimensions
Error
When posted, rounding value entries did not retain the dimensions of the source entries.
This has been corrected.
Service system reference: US-264-519-JKBL
A308) Credit Memo (Exact Cost Reversing) and Batch Jobs
Error
It was necessary to fill in the Appl. to Item Entry No. when using exact cost reversing.
This has been corrected.
Service system reference: DE-429-517-9LU5
A309) Posting Purchases with Item Charges Assigned
Error
The system returned an error when you posted a purchase with item charges assigned, even though locations were entered.
This has been corrected.
Service system reference: NL-936-423-HGRD
A310) Deadlock When Posting Orders, Adjusting Cost and Posting Inventory to G/L
Error
The system ended up deadlocked when Order, Adjustment Cost and Posting Inventory to G/L occurred at the same time.
This has been corrected.
Service system reference: SE-557-682-WD3S
A311) Standard Cost on the Item Ledger Different from the Item Card When You Used Adjust Item Costs/Prices
Error
The single-level cost on the item card was not updated when the cost price was updated through Adjust Item Costs/Prices.
This has been corrected.
Service system reference: DE-641-890-PM6J
A312) Incorrect Consideration of Unit of Measure in Production BOM Header When Using Fixed Scrap Quantity in Routing Line
Error
The Calc. Standard Cost function calculated incorrectly when the Unit of Measure in the BOM header was not the base and routing lines with fixed scrap quantity existed.
This has been corrected.
Service system reference: DE-421-364-4D6X
A313) Information Missing on Test Report for Phys. Inventory Journal
Error
No body text was printed for the above report.
This has been corrected.
Service system reference: AT-242-564-SBRK
A314) Incorrect Error Message When Attempting to Change Item Costing Method
Error
The program displayed an incorrectly formatted error message if you tried to change the costing method where this was not allowed.
This has been corrected.
Service system reference: DE-609-559-RR3A
A315) Incorrect Information Shown on Item Age Composition Reports
Error
The total quantity/value was shown in the wrong column.
This has been corrected.
Service system reference: MY-424-147-YEGG
A316) Incorrect Document Number on Posted Entries When Posting Charge (Item) from Credit Memo
Error
When posting a credit memo with Charge (Item) as the line type and assigned to posted shipment, the number of the posted credit memo was not the same as it was in the other ledger entries.
This has been corrected.
Service system reference: LV-787-733-5D9X
A317) Shipment Posted Twice
Error
The program created two positive item ledger entries when posting a credit memo that was created by means of using the Move Negative Lines function from the invoice of the already shipped negative sales line.
This has been corrected.
(By means of introducing an error warning if the user tries to move negative lines related to a shipment.)

Service system reference: DE-493-68-4K7Q
A318) It Was Impossible to Overrule the Average Costing Method by Using the Fixed Application
Error
Even when the fixed application was made between the entries, the program would still value the applied outbound entry by average instead of on the basis on the applied inbound entry.
This has been corrected.
Service system reference: SE-561-192-WGT9
A319) Calculate Inventory Value Function in the Revaluation Journal
Error
The Calculate Inventory Value batch job could not run in the request form if the costing method filter was set up for non-average costing method.
This has been corrected.
Service system reference: DE-981-148-7N6T
A320) Incorrect Location Filter for the Adjust Item Costs/Prices Batch Job
Error
Setting the filter on one location in the Adjust Item Costs/Prices field updated all SKUs for that item and not just for that one location.
This has been corrected.
Service system reference: US-427-876-VKZX
A321) Missing Permissions on Availability Forms
Error
It was impossible to drill down from the availability forms if the user license did not contain basic manufacturing.
This has been corrected.
Granule 4010 Basic Inventory in C/CAPS

Service system reference: GB-846-147-4DZR
Internal Workbase reference: 88EDA085A5F14ABAC1256B270037E00F
A322) Order Tracking Form Did Not Show the Demand Entity
Error
Form 99000822 Order Tracking did not show the demand entity when the "Show" button was clicked or a lookup was selected.
This has been corrected.
Service system reference: SE-87-916-4HNS
Internal Workbase reference: E0AF36CC78A431F9C1256B5F00486226
A323) Find Button Removed from the Order Tracking Form
Error
The Find button on Form 99000822 Order Tracking did not have any purpose and has been deleted.
This has been corrected.
Form 99000822 Order Tracking

Service system reference: AU-475-521-FW3E
Internal Workbase reference: E38F318B30531AA3C1256B880046EA2B
A324) Pick Reports for Partly Posted Transfer Orders Showed Fully Posted Quantities
Error
When viewing pick reports for partly posted transfer orders, the full quantity was shown instead of the partially complete quantity.
This has been corrected.
Codeunit 5704 Transfer Order
Codeunit 5705 Transfer Shipment

Service System reference: NL-628-836-AK8P
Internal Workbase reference: 43AAD479867349CAC1256B2F004BB855
A325) Impossible to Change Posting Date on Partly Posted Transfers without Reopening the Transfer Order
Error
After partially posting a transfer order, it was impossible to change the posting date on the transfer header without first reopening the transfer order.
This has been corrected.
Table 5740 Transfer Header

Service System reference: N/A (INTERNAL REPORT)
Internal Workbase reference: 8A4483A7006FC4A6C1256B290046FF9E
A326) When Changing Posting Date on a Transfer Order Header, Other Dates Were Affected
Error
Changing the posting date on the header of a transfer order wrongly changed the Shipment Date and Receipt Date fields on both the header and the lines.
This has been corrected.
Table 5740 Transfer Header

Service System reference: N/A (INTERNAL REPORT)
Internal Workbase reference: EAEFE53598227225C1256B29004D11F1
A327) Incorrect Warning when Clicking Prices Includes VAT on the Item Card
Error
If the user selected Prices Includes VAT on the item card and they had not filled in the VAT Bus. Post. Gr. (Price), an error message appeared saying the wrong text. You should, in fact, set up a VAT Posting Setup with blank VAT Bus. Post. Gr. and with the appropriate VAT%, but the program did not check if such a setup existed.
This has been corrected.
Table 27 Item

Service System reference: SE-860-441-6G7W
Internal Workbase reference: 183CED773BD9D4AFC1256BCE00328A09
A328) Missing Location Code Filter
Error
There was no Location Code filter on the Item Ledger Entries table when applying (Appl.-to Item Entry) a sales line with a specified location code to an outbound entry. This caused users to make mistakes by applying sales to entries in the wrong location.
This has been corrected.
Service system reference: HK-181-826-UNBK
A329) Impossible to Print Test Reports from Item Reclass. Journal and Phys. Inventory Journal
Error
Headers and bodies in sections for report 702 (Inventory Posting – Test) were not defined for the Item Reclass. and Phys. Inventory Journals.
This has been corrected.
Service system reference: SI-101-137-B9Z2
A330) Item Ledger Entry Created for Deleted Item
Error
It was possible to post a positive adjustment for an item that had been deleted.
This has been corrected.
Service system reference: DE-500-498-TCKW
A331) Item Availability by Location and drill down
Error
When you drilled down in the Item Availability by Location form, it did not always show all the source data.

This has been corrected.
Service system reference: GB-387-612-VKZX
A332) Error in Item Availability Lines Form
Error
The Inventory field on this form was always 0.

This has been corrected.
Service system reference: BE-672-671-BJHH
A333) Drilldown Uses Date Filter in Inventory Column
Error
A posting date was active on the Inventory column of the Item Availability form.

This has been corrected.
Service system reference: NL-743-870-6LGP
A334) Inventory Column Always Showed Zero Value
Error
In the Item Availability lines and Item Avail. by Variant Lines forms, the inventory column (which is defined as item "Net Change") always read zero, even if there was stock against the item.
This has been corrected.
Service system reference: GB-609-553-TLBF
A335) Height in Extended Text Lines Form
Error
The height in the Extended Text Lines form was 2860, but it should be 3300.

This has been corrected.
Service system reference: DE-143-380-3AXU
A336) Missing Table Relation
Error
There was a table relation missing in the "Item No." field on the Item Journal Line table (T83).
This has been corrected.
Service system reference: DK-253-809-4BGT
A337) Inventory – Availability Plan
Error
In this report, the Planned Releases field doubled the number it should show.
This has been corrected.
Service system reference: SE-679-453-6DW2
A338) Item Cross Reference Description Fills Used in Two Fields
Error
The item cross reference description filled in both the Description and the Description2 fields on a sales order line.
This has been corrected.
Service system reference: US-256-410-VNXJ
A339) Last Unit Cost Calc. Date Was Not Filled in for the Item
Error
When using Calc. Standard Cost for an item with standard costing method from the Assembly List, the last unit cost calc. date was not filled in.
This has been corrected.
Service system reference: DK-312-829-3C4U
A340) Misleading Caption in Report Inventory Valuation and Inventory Valuation – WIP
Error
In the Inventory Valuation and Inventory Valuation – WIP reports, the Balance to Starting Date column was named "As per <Starting Date>", while the actual balance shown was the balance before the Starting Date.
This has been corrected.
Service system reference: SE-170-715-NM2R
A341) Item Cross Reference Did Not Work Correctly With Bar Code As Type
Error
The cross-reference number disappeared when entering a sales line with a cross-reference type bar code.
This has been corrected.
Service System reference: DK-70-562-3B4P
A342) Item Category Code Was Not Transferred to Item Journal
Error
This has been corrected.
Service System reference: FR-578-117-3DCY
A343) Vendor Item No. Was Not Filled In Correctly When Using Drop Shipment
Error
When creating a drop shipment purchase order for an item with vendor item no., this number was added to the following lines.
This has been corrected.
Service System reference: US-888-30-YV8V
Issues
A344) The Item Tracking Solution Has Been Restructured
Issue
An objective for Attain 3.60 was to ensure the seamless integration of an optimized reservation structure (through full embedment) with order tracking, reservation and item tracking in the same engine.

The item tracking functionality has been stabilized through a total redesign of the underlying structure. The new structure is greatly simplified compared with the 3.10 solution and now uses the Item Ledger Entry as the primary carrier of item tracking.

As part of the change, integration of item tracking in planning, manufacturing and warehouse has been improved.

Service System references:
INT-306-881-8GAY
DE-670-299-ZLZQ
DE-675-224-EJ3J
DE-836-502-FKHS
LT-287-830-3AVN
GB-993-641-HDRR
AU-446-190-FABS
INT-871-302-8GBP
INT-903-65-3UYY
INT-245-531-3V37
DE-156-254-FDAU
DE-671-30-FHB9
DE-824-887-ZLG6
DE-158-991-ELYK
FR-803-936-KHN8
DK-669-231-4DSG
DK-842-582-VBJT
DE-251-256-BFEN
DK-432-653-QKAS
DK-142-465-UKAR
US-244-15-YKBY
DE-356-705-KCT8
DK-259-456-3HBB
US-452-810-VQQE
BE-283-238-MJB4
BE-710-981-AHDH
NL-82-826-3FCR
CH-56-142-FGHU
GB-454-88-PPG8
AU-380-725-X8AM
FR-690-967-NMEP
A345) Performance Improvement
Minor performance improvement. Reducing requests to Reservation Entry Table.
In response to this issue, a change has been implemented.
Codeunit 99000845 Reservation Management
A346) Performance
Issue
For SQL Server performance reasons, the property MaintainSIFTIndex is used on keys in order to reduce the cost of updating tables and to reduce locking on the SQL Server.
In response to this issue, a change has been implemented.
Table 246 Requisition Line
Table 5741 Transfer Line

=== Warehouse Management ===

==== Features ====

A347) Warehouse Management System (WMS)
Feature
Warehouse Management Systems (WMS) for Attain is developed as an integrated granule for the Attain application. It is a solution for the Navision customer that has a need for managing the inventory and distribution of items in a warehouse environment. It is especially developed for the warehouse that functions by using specific zones and bins. WMS provides functionality for more advanced warehouse operations than the functionality in the basic Warehouse Management (WM) solution released in NAV 3.10.

The new functionality that is introduced includes the setup and operation of separate zones and individual bins for each warehouse location. This enables features for the performance of directed picks and put-aways, as well as the implementation of automated data capture systems (ADCS).
This feature has been implemented.
A348) Automatic Data Capture Systems (ADCS)
Feature
Automatic Data Collection systems (ADCS) for Attain is the granule that provides the basic architecture for setting up the communication between handheld devices and the WMS application. The ADCS functionality supports the warehousing workflows by being enabled in put-away, movement, pick, and warehouse physical inventory documents. Online wireless Radio Frequency (RF) communication is supported. The architecture utilizes the Navision Application Server (NAS), introduces a Communication System Services (CSS) based on XML and XSLT formats, and a specific “plug-in” for each handheld device. For this release, a “plug-in” for the PDT 6100 radio frequency device from Symbol is provided.
This feature has been implemented.
Errors fixed
A349) Rights in Roles for the Warehouse Setup Table Incomplete
Error
No role (except for the SUPER) contained rights to insert, modify or delete from the table 5769 Warehouse Setup. The roles WM-PERIODIC, WM-POSTED PA/P, WM-R/PA/A/P/S, WM-R/PA/A/P/S, POST and WM-SETUP are created within the warehouse area.

This has been corrected.
Table 5769 Warehouse Setup

Service System reference: DK-0-595-5DN2 – only part 1); CH-885-970-UE9U - partially
Internal Workbase reference: 52623A44BFC59D94C1256B590042D241
A350) Error in Calculating Inventory Available When Components Were Reserved for a Production Order
Error
When you had a manufactured item and you reserved one of the components for that item, the system incorrectly calculated the inventory on hand for warehouse assignment for the picking of the components. It also showed an incorrect quantity to handle on the assignment document.
This has been corrected.
Codeunit 7311 Whse. Worksheet-Create

Service System reference: US-958-516-LQ3K
Internal Workbase reference: DB51CCDB3A4BE978C1256B5A00427D1B
A351) Picking Items Not in Stock
Error
It was possible to pick items and create pick documents for items that were not available in inventory.
This has been corrected.
Table 7326 Whse. Worksheet Line
Table 27 Item
Codeunit 7311 Whse. Worksheet-Create
Codeunit 7312 Create Pick

Service System reference: DK-403-968-BFL8
Internal Workbase reference: 13EC84DD90A259BEC1256B6800295D7A
A352) Missing Permissions in User Roles
Error
The Warehouse Management Setup table was not included in the ‘ALL’ role. The result was that the warehouse roles should be included in a user profile to enable the posting of a sales order.
This has been corrected.
Codeunit 101991 Create Permissions

Service System reference: DK-0-595-5DN2
Internal Workbase reference: 52623A44BFC59D94C1256B590042D241
A353) “W” for Work Date on Source Document Filter Card
Error
It was not possible to enter “w” for work date in the date fields of the source document filter card.
This has been corrected.
Form 5786 Source Document Filter Card
Table 5771 Warehouse Source Filter

Service System reference: DE-776-637-7H7K
Internal Workbase reference: 3E41DE924ADDAAAFC1256B87002DDBDB
A354) Post, Ship and Invoice from a Sales Order When Location is Set to Require Pick
Error
It was possible to edit the Qty. to Ship/Receive field on a sales or purchase order even if warehouse activity lines existed. Furthermore, in a partial shipment scenario the field was updated with the remaining quantity that you were able to post and ship without a system warning.
This has been corrected.
The quantity now returns to zero in partial scenarios and a warning is implemented in the Warehouse Management location, but it is possible to continue the process. This is not possible in the WMS location.

Codeunit 80 Sales-Post
Codeunit 90 Purch.-Post
Codeunit 5704 TransferOrder-Post Shipment
Codeunit 5705 TransferOrder-Post Receipt

Service System reference: NO-7-956-4CM3, INT-750-796-6GA7
Internal Workbase reference: 82B2D8EE93785B9FC1256BC7002AA239
A355) Pick Lines Were Not Split When a Pick Document Was Created for Items with Item Tracking Requirement
Error
While the put-away lines were split automatically when posting a receipt of an item with Item Tracking requirement, the pick lines were not split for these items. This situation meant that the split line function was used too much.
This has been corrected.
The following rule has been implemented: If warehouse serial number tracking is required for an item and no serial number information is entered at the Whse. Shipment or the Component or the Internal Pick or the Pick Worksheet Line, then the pick lines are created as if split with quantity 1.

Codeunit 7312 Create Pick

Internal Workbase reference: D1534D53C3EA3A7CC1256BC1004305F6
A356) ADCS/WMS, Action Type Sorting Method Was Missing on Warehouse Documents
Error
This sorting method was missing but was crucial for a proper organization of the activity lines for ADCS usage.

This has been corrected.

Table 5766 Warehouse Activity Header
Table 5767 Whse. Activity Line
Table 5772 Registered Whse. Activity Hdr.
Form 5770 Warehouse Put-away
Form 5795 Registered Put-away
Form 7315 Warehouse Movement
Form 7349 Registered Movement
Report 5754 Create Pick
Report 7305 Whse.-Source - Create Document
Report 7318 Whse.-Shipment - Create Pick
Code unit 7312 Create Pick
Code Unit 7313 Create Put-away

Internal Workbase reference: 68E40A7F69A7CB29C1256BDB0053392F
A357) For Certain Documents, the Quantity on the Inventory Did not Match the Quantity on the Bins
Error
For certain documents, the quantity on the inventory did not match the quantity on the bins. For example, when posting Service Invoice lines on a WMS location, a warehouse entry was not created, this was also the case for Job Journals and BOM journals.

This has been corrected

A stop for preventing the use of these additional documents/journals has been implemented.

TAB89 BOM Journal Line
TAB210: Job Journal Line
TAB5902 Service Invoice Line
COD31 BOM Jnl.-Check Line
COD201 Job Jnl.-Check Line
COD5907 ServInvLine-Post

Internal Workbase reference: C599D3729D35880BC1256BD8002B3877
A358) Mismatch of the Maximum and Minimum Qty Restrictions at the Bin
Error
When the default receiving bin was empty and the Max. Qty. for a specific item was set, the program did not prohibit the receiving of more than the maximum quantity allowed. Only when there was some of the item already in the bin would it prohibit more than the max. qty. There were also problems regarding no check being performed after quantities were corrected according to an error message.

This has been corrected

Table 7317 Whse. Receipt Line
Table 5767 Warehouse Activity Line
Table 7317 Warehouse Receipt Line
Form 5769 Whse. Receipt Subform
Form 5771 Whse. Put-away Subform
Form 5780 Whse. Pick Subform
Form 7316 Warehouse Movement Subform
Code unit 7302 WMS Management
Code unit 7307 Whse.-Activity-Register
Code unit 7312 Create Pick
Code unit 7313 Create Put-away

Internal Workbase reference: FB2F56460840D0C2C1256BE2003E5310; 0BA39220F2689A2AC1256BDB0054AE67; 78CF511E89F0C7FFC1256BE300444D92
A359) Cycle Counting on SKU Card Was Not Working
Error
Cycle Counting did not take the "Next Counting Period" field on SKU cards into account.

This has been corrected

REP790 Calculate Inventory
REP7390 Whse. Calculate Inventory

Internal Workbase reference: 991638DB89BC892EC1256BE30033096F
A360) Inconsistencies with the Break-Bulk Functionality
Error
When in a Warehouse Management location, error messages appeared that were formulated as if you were in a Warehouse Management Systems environment (Bins etc.). Certain scenarios were detected where you could have a duplication of items in the bin. Furthermore, under certain circumstances, the bin content was not deleted.

This has been corrected

Table 5767 Warehouse Activity Line
Codeunit 7307 Whse.-Activity-Register
Codeunit 7312 Create Pick

Internal Workbase reference: 950C69E89A9510E3C1256BB7003A0040; 7B7BC091C9569635C1256BDD00340CE1; 640ECF922B22CB30C1256BE6003E2114

A361) Integration Issues Within Whse. Physical Inventory Journal, Whse. Item Journal and the Whse. Adjustment Bin for Items with Item Tracking Policy
Error
Various inconsistencies were detected.

This has been corrected

COD 80 Sales-Post
COD 90 Purch.-Post
COD 7304 Whse. Jnl.-Register Batch
REP 790 Calculate Inventory
Table 7311 Warehouse Journal Line

Internal Workbase reference: 044978EB7B86235DC1256BF7003E5F60; 2D11107762DE0CFCC1256C00003F97DC; A3079FE90709012FC1256BF300503B1E; C4D3DD2A617ED0A3C1256BDC0041B726
A362) Inconsistencies with Various Sorting Methods
Error
Inconsistencies were detected when using various sorting methods: by bin ranking and by document. This applied on internal put-away or on internal pick, as well as at the movement worksheet.

This has been corrected

Table 5400 Bin
Table 7332 Whse. Internal Put-away Line
Table 7333 Whse. Internal Pick Header
Table 7334 Whse. Internal Pick Line
Table 7326 Whse. Worksheet Line
Form 7354 Whse. Internal Put-away
Form 7355 Internal Put-away Subform
Form 7358 Whse. Internal Pick Line
Form 7351 Movement Worksheet
Form 7345 Pick Worksheet
Form 7352 Put-away Worksheet

Internal Workbase reference: 4DDA299E2291AA00C1256BDC003DC062; F82EDA27D5A00116C1256BDC0049A38D; BF4F6B8107CF5C20C1256BDC004CCC17; 77324359AB0912DBC1256BDD003B73A0; AE2D3A65E6DCEA02C1256BDD002F5C1D
A363) GUI Issue
Error
Glue was missing from the Template menu button.

This has been corrected

Form 7314 Put-away Template List

Internal Workbase reference: 0807340FFF511518C1256BD7004CFA95
A364) Accessibility to Bin Content Depending on User Setup
Error
If you were not logged into the system as a user, you were barred access to the bin content table.

This has been corrected

Table 7302 Bin Content
Form 7374 Bin Contents

Internal Workbase reference: 3013D1DB47729A3FC1256BCE00334DFB
A365) Wrong Trigger of Error Message
Error
When at a WM location, you could receive WMS related or formulated messages.

This has been corrected

New error messages have also been implemented.

Table 7321 Warehouse Entry

Internal Workbase reference: 5CAAED8F6FF457BEC1256BC6003E3D7E
A366) Bin Creation Worksheet
Error
When using the Bin Creation worksheet, the parameters from the line above were not blanked out.

This has been corrected

Table 7338 Bin Creation Worksheet Line
Form 7371 Bin Content Creation Worksheet
Form 7372 Bin Creation Worksheet

Internal Workbase reference: C4D3DD2A617ED0A3C1256BDC0041B726
A367) Inconsistencies Using Warehouse Class Code
Error
The Whse. Class of the Inbound Production Bin, Outbound Production Bin and Open Shop Floor Bin could not be checked if items were placed there.

This has been corrected

Table 5400 Bin

Internal Workbase reference: 5CB27C0E35E479A4C1256BE5002CA02D
A368) Automatic Composing of Form Captions
Error
On certain forms, the caption was composed in a way that was not helpful to the multilanguage facility.

This has been corrected

Form 5774 Warehouse Activity List
Form 5785 Warehouse Activity Lines
Form 5797 Registered Whse. Activity List
Form 7364 Registered Whse. Act.-Lines

Service System reference: BE-602-602-RE55
Internal Workbase reference: 4C0AB2BFFAEDE1F8C1256BF000436DED
A369) Wrong Length of User ID Code Field
Error
The code length was 10 instead of 20.

This has been corrected

Table 7301 Warehouse Employee
Table 7319 Posted Whse. Receipt Line
Report 5754 Create Pick
Report 7305 Whse.-Source - Create Document
Report 7318 Whse.-Shipment - Create Pick
Form 7331 Posted Whse. Receipt Subform
Codeunit 7313 Create Put-away

Service System reference: DE-465-448-Y82M
Internal Workbase reference: CF1C86532E8260FFC1256BF4002E316A
A370) Bin Templates
Error
It was possible to assign a zone code to a location without the zone code being set up for that location. The same was possible for the max. cubage and max. height fields.

This has been corrected

Form 7367 Bin Templates

Internal Workbase reference: 95BCCEB384D3D585C1256BCE00422131
A371) The Shelf/Bin No. field Was Missing on the Internal Put-away Line
Error
The internal put-away was not functioning correctly for Warehouse Management locations.

This has been corrected

A new Shelf/Bin No. field has been added to the table 7332 "Whse. Internal Put-away Line", on the subform 7355 "Internal Put-away Subform", on the form 7361 “Whse. Internal Put-away Lines”.

Table 7331 Whse. Internal Put-away Header
Table 7332 Whse. Internal Put-away Line
Form 7355 Internal Put-away Subform
Form 7361 Whse. Internal Put-away Lines
Report 7305 Whse.-Source - Create Document
Codeunit 7311 Whse. Worksheet-Create

Internal Workbase reference: A04DF383E547A271C1256BF20028691C
A372) ADCS and Identifiers
Error
On the item card and the Item List window, the menu item Identifier should have been called Identifiers. The Item Identifiers window had a wrong key; the menu item did not have the LinkType=OnUpdate property defined; and the Item Identifiers window did not have the item information in the data caption – as it should have done. The Item Identifier Code field did not have the NotBlank=Yes property defined.

This has been corrected

Table 7704 Item Identifier
Form 30 Item Card
Form 31 Item List
Form7706 Item Identifiers
Form 7707 Item Identifiers List

Internal Workbase reference: B468B373EFC7471AC1256BEC004CBCF1
A373) ADCS and Hard Coded Error Messages
Error
The error messages were hard coded.

This has been corrected

Note: the miniform design is not fully multilanguage enabled.

Code unit 7702 Miniform Management
Code unit 7703 ADCS Get Field Value

Internal Workbase reference: 8FD1212648C41459C1256BEC004D1B3
A374) ADCS and Curser
Error
The curser was incorrectly placed when a field no. was already filled out.

This has been corrected

Table 7701 Miniform Line
Form 7700 Miniform

Internal Workbase reference: 5DB59E98DC91134EC1256BEC003E833D

=== Manufacturing ===

==== Errors fixed ====

A375) Deleting Items on Certified Production BOMs
Error
It was possible to delete an item even if it was used in a certified production BOM.
This has been corrected.
Table 27 Item

Service System reference: INT-431-567-3UUX
Internal Workbase reference: DFFE6B42A8B830EEC1256AFF0038AEA2
A376) Missing Multilanguage Enabling
Error
An option string in the Planning Buffer table (99000846) was not multilanguage enabled.
This has been corrected.
Table 99000846 Planning Buffer

Service System reference: NO-59-219-3FDG
Internal Workbase reference: 7E51F5BADBDC300FC1256B430046118C
A377) Variant Code Was Not Deleted When Item Number Was Changed
Error
When the item number was changed on a production BOM, the variant code was not reset. The situation was the same on production order lines and production order components.
This has been corrected.
Table 5406 Prod. Order Line
Table 5407 Prod. Order Component
Table 99000772 Production BOM Line

Service System reference: DK-571-680-HDGS
Internal Workbase reference: D5A49DC6BA061438C1256B2F0057769A
A378) Production Forecasts on In-transit Locations
Error
It was possible to enter production forecasts on in-transit locations.
This has been corrected.
Form 15 Location List
Form 99000919 Production Forecast

Service System reference: INT-93-423-3UZK
Internal Workbase reference: EB7D1E6A00EA25ECC1256AC4004E8707
A379) Wrong Error Message When a Production BOM Is Certified
Error
When a production BOM with a missing Routing Link code is certified, the error message was formatted incorrectly.
This has been corrected.
Codeunit 99000769 Production BOM-Check

Service System reference: DE-622-20-5C5L
Internal Workbase reference: 202CF99796CAD334C1256B6000340F5C
A380) Incorrect Option Sting
Error
In some tables, the option string for the Prod. Order Status filter contained an incorrect value.
This has been corrected.
Table 99000758 Machine Center

Service System reference: N/A
Internal Workbase reference: AB2C2423EC8BD89441256AAB00366019
A381) Inability to Change Currency Code on Sales Orders
Error
If a production order was planned from a sales order, it was impossible to change the currency code at a later date.
This has been corrected.
Table 36 Sales Header

Service System reference: DK-150-26-MDQ4
Internal Workbase reference: C22890F951463139C1256B180037AFBD
A382) Planning Flexibility Field Not Transferred to Purchase Orders
Error
When planning flexibility was set to none on the planning worksheet, this was not transferred to the purchase orders when the action messages were carried out.
This has been corrected.
Codeunit 333 Req. Wksh.-Make Order
Codeunit 99000813 Carry Out Action

Service System reference: DK-718-196-HF5J
Internal Workbase reference: F696F1D9FF0521B3C1256B270037FDEA
A383) Unable to Create a Project Production Order from a Sales Order
Error
It was impossible to create a project production order from a sales order with dimensions.
This has been corrected.
Codeunit 99000787 Create Prod. Order Lines
Codeunit 99000792 Create Prod. Order from Sale

Service System reference:
GB-91-522-MJWZ
DE-514-24-GDHD
NO-590-37-2KQ4
GB-730-574-KGPQ
Internal Workbase reference: E2FC763F029DF35EC1256BA6002D672A
A384) Permissions on Planning Availability Report (99001049)
Error
On the Planning Availability report, the Planning Buffer table was not used as a temporary table. This caused permission problems for some users.
This has been corrected.
Report 99001049 Planning Availability

Service System reference: DK-365-230-NGD8
Internal Workbase reference: 543685F192AE92B1C1256BB1004CE772
A385) Planning Worksheet Errors Not Corrected
Error
The errors corrected in earlier versions for send-ahead quantities on production orders were still present on the planning worksheet.
This has been corrected.
Codeunit 99000810 Calculate Planning Route Line

Service System reference: US-426-832-7TPC
Internal Workbase reference:
29A9DD714BEC538C41256AB70048EF87
70E084625A87A2ACC1256B6C003A32D4
86A30DDAF02ACFC4C1256B80003DD4CF
A386) Send-Ahead Quantity and Setup Time
Error
When send-ahead quantity was used in combination with a setup time on the routing, the preceding operation was scheduled incorrectly when scheduling backwards.
This has been corrected.
Table 5410 Prod. Order Capacity Need
Codeunit 99000773 Calculate Prod. Order
Codeunit 99000810 Calculate Planning Route Line

Service System reference: FR-128-188-LJN3
Internal Workbase reference: 24A136B4F95DF757C1256BB100747FF2
A387) Incorrect Ending Dates for Production Orders
Error
If a production order was refreshed without calculating the production order lines, the ending date was calculated incorrectly.
This has been corrected.
Report 99001025 Refresh Production Order

Service System reference: N/A
Internal Workbase reference: 2E9FAA089EAF9115C125674400524FF9
A388) Exchange Production BOM Item Did Not Re-certify
Error
When the Exchange Production BOM Item batch job changed more than one Production BOM, only the first version was certified automatically.
This has been corrected.
Report 99001043 Exchange Production BOM Item

Service System reference: INT-12-273-3UW3
Internal Workbase reference: 15CA6AEF9751A33B41256AAB0037E335
A389) Exchange Production BOM Item Batch Job and Versions
Error
The Exchange Production BOM Item batch job did not work when versions of production BOMs were used.
This has been corrected.
Report 99001043 Exchange Production BOM Item

Service System reference: DK-920-964-GGPH
Internal Workbase reference: A38C6C316B0E6562C1256B6D0046DD42
A390) No Requisition Lines Shown
Error
When the user drilled down from the planning worksheet to the item availability per period, then to the Item Availability Line list, and then to the requisition lines, an empty form was displayed.
This has been corrected.
Form 9900902 Item Availability Line List

Service System reference: CZ-695-908-UJHJ, GB-387-612-VKZX
Internal Workbase reference: 3558FAC679EFF623C1256B58004873B0
A391) The Detailed Calculation Report 99000756 Shows Incorrect Unit of Measure
Error
The Detailed Calculation report was incorrect when a “Unit of Measure” that differed from the “Base Unit of Measure” on the BOM line was used.
This has been corrected.
Service system reference: INT-302-413-8G4B
A392) Prod. Order Comp. Line No. Is Automatically Filled In
Error
If a consumption journal is entered manually for an item that is only defined once as a prod. order component, then the Prod. Order Comp. Line No. field is filled in automatically.
This has been corrected.
Service system reference: DK-360-577-R9UX
A393) Wrong Filters for the Application Entries Table in the Consumption Journal
Error
When trying to open the Applies-from Entries table in the consumption journal, the program opened the table containing the inbound entries rather than the outbound ones.

This has been corrected.
A394) Change Status on Project Orders
Error
When a production order was created as a project order from the sales order, the status of the production order could not be changed. This problem was caused by a check being made on the production order’s source no. as if it was an item number.
This has been corrected.
Table 5405 Production Order

Service System reference: GB-730-574-KGPQ
Internal Workbase reference: 2EE02AAF17790E24C1256B670045E86F
A395) Wrong Number Series Used When Production Orders Are Created from the Planning Worksheet
Error
When a production order was created from the planning worksheet, the wrong number series was used.
This has been corrected.
Codeunit 99000813 Carry Out Action

Service System reference: NL-342-315-MLT9, CZ-297-168-LG9W, DK-403-738-RDHF
Internal Workbase reference:
53685B72023855B2C1256B5A004A2A61
108859714BAF1B6FC1256B3700382B76
A396) Missing Permissions in User Roles
Error
Even when a user included all manufacturing roles, it was impossible to refresh a production order.
This has been corrected.
Codeunit 119102 Create Permissions Manf.

Service System reference: US-989-637-9QPG
Internal Workbase reference: DEBB1968CCA3F419C1256B52004D9F99
A397) Existing Transfer Orders Ignored during Planning
Error
When regenerative planning was calculated, existing transfer orders were ignored.
This has been corrected.
Table 99000853 Inventory Profile
Codeunit 99000813 Carry Out Action
Codeunit 99000854 Inventory Profile Offsetting

Service System reference: BE-964-869-WLDQ
Internal Workbase reference: A3ADDA02D84C1E97C1256B730039FF92
A398) Partial Receipts and Regenerative Planning
Error
If partial receipts were posted, the regenerative planning resulted in incorrect suggestions.

Codeunit 99000854 Inventory Profile Offsetting

Service System reference: DK-705-838-VDSG, NL-691-145-3DWQ
Internal Workbase reference:
995F837E966F395FC1256BB2003F36B6
D7363422F56B8BCCC1256BA00041808C
A399) Regenerative Planning on Location without Stockkeeping Units
Error
Without defining stockkeeping units, incorrect results for new items could result when regenerative planning was calculated for a different location.
This has been corrected.
Codeunit 99000854 Inventory Profile Offsetting

Service System reference: AT-715-499-9C6D, INT-117-695-3UYM
Internal Workbase reference: 9C095328B649225EC1256BA000453F72
A400) Regenerative Planning – Suggested Change in Quantity
Error
In some cases, regenerative planning erroneously suggested that a change in the current quantity for a replenishment order was needed.
This has been corrected.
Codeunit 99000854 Inventory Profile Offsetting

Service System reference: N/A
Internal Workbase reference: 703314F53661E07EC1256BA0004F759D
A401) Replan Batch Job Incorrectly Calculated Dates on Component Orders
Error
When the replan batch job was executed for All Levels, the component orders were incorrectly scheduled.
This has been corrected.
Table 5405 Production Order

Service System reference: US-595-460-2SJP
Internal Workbase reference: E00A3A3191E021B5C1256B5A00377552
A402) Error When Deleting a Work Center
Error
It was impossible to manually delete a work center.
This has been corrected.
Table 99000754 Work Center
A403) Posting Consumption of Components That Were Not on Inventory
Error
Under certain circumstances, it was possible to post consumption of components that were not on inventory. Posting of negative consumption was possible where all the items (manufactured and components) were using the Average costing method, had requisition system set up to Prod. Order, and a production order contained more than one line.
This has been corrected.
Service system reference: DE-612-897-NQU9
A404) Loss of Dimension When Using Calculate Regenerative Plan Function
Error
Under certain circumstances, when using the calculate regenerative plan, the program did not copy the Default dimension to the Planning Worksheet line.
This has been corrected.
Service system reference: FR-865-908-VF8R
A405) No Lookup in the Capacity Need Field
Error
The lookup function in the Capacity Need field of the Statistics window for the production order was not present.
This has been corrected.
Service system reference: US-419-548-ZSSF
A406) Obsolete Source Codes
Error
In the Trail Codes of the General Ledger setup, in the Source Code Setup and Source Code tables, the Post Prod. Order WIP and Post Prod. Order Recognition fields became obsolete.
This has been corrected.
Service system reference: SE-567-509-NKEE
A407) Wrong Calendar Rounding Precision in Work Center
Error
Due to the wrong value in the Calendar Rounding Precision field on the work center card, the capacity for the work center was not calculated correctly.

This has been corrected.
Service system reference: DE-890-114-NCYM
A408) Possible to Post Consumption of Components Not in Inventory
Error
When a component was set up to use automatic flushing (forward), the program posted consumption of this component even though there was not enough quantity in inventory.
This has been corrected.
Service system reference: DE-319-638-NAB7
A409) Impossible to Change Starting or Ending Dates on a Project Order
Error
The problem was that when (for planning reasons) the end and/or starting date of the production order line were changed manually, the new value would be overwritten by the old date. In other words, the manually entered date would not be saved.
This has been corrected.
A410) Item Availability by Location and Change Component Location
Error
If you looked at production order components, you could look up components by Location. When you selected a different location, you were asked if you wanted to change it. Answering “Yes” did not apply the change, however, a manual change was possible.
This has been corrected.
A411) Lookup on Item Availability by Variant Did Not Update the Production Order Component Line
Error
It was impossible to change the variant code on the production order component line by use of the "Avalibility by Variant" form.

This has been corrected.
A412) Location Code must be #### in Reservation Entry No.=2 Positive=Yes
Error
You received an error when attempting to carry out an action message for a requisition worksheet line for a special order that had an item with an order tracking policy of “tracking and action message”.
This has been corrected.
A413) Order Promising for an Additional Second Item
Error
If you had many sales lines in one order and you already had accepted capable to promise for one of these sales lines, then you first had to Carry out Action Message in the Requisition Worksheet before you could accept another capable to promise for any subsequent sales line.
This has been corrected.
A414) Order Promising: Wrong ATP Calculation
Error
Sometimes the ATP calculation suggested an Earliest Shipment Date even when there was no inventory available.
This error has been corrected.
A415) Where-Used Item List Contained an Irrelevant Column
Error
Form 99000782, Where-Used Item List contained an irrelevant column “Bill of Materials” referring to table 90 BOM/Assembly List Indicator. It would be relevant to replace this column with a column referring to “Production BOM No.”
This has been corrected.
Form 99000782 Where-Used Item List

Service System reference: N/A
Internal Workbase reference: 532598AC439023064125691A004E99F8

A416) Production Order Components Comments Disappeared or Were Moved
Error
When creating a Production Order for an item using a BOM with a newly added component with comments, these comments disappeared and comments for other components were moved.
This has been corrected.
Codeunit 99000773, Calculate Prod. Order

Service System reference: NO-731-869-3G25, N/A
Internal Workbase reference: E5A542C5CD917959C1256B520047103A and 53C9521F9DAC85F4412568F60045D4AB.

A417) Warning Not Issued When Qty. is Changed on a Sales Order With Associated Production Order
Error
When changing the Qty for a produced item on a Sales Order Line with a Production Order created for this item, no warning for the discrepancy between sales order Qty and associated Production Order Qty was issued.
This has been corrected.
Form 99000883, Check Prod. Order Status

Service System reference: AT-350-958-XM3V
Internal Workbase reference: 1E62606E760F7168C1256B9D00467419
A418) Confirmation Dialog Was Not Phrased As a Question
Error
A global text constant Text011 used in a confirmation dialogue was not phrased as a question.
This has been corrected.
Table 37, Sales Line. (Global text constant Text011)

Service System reference: N/A
Internal Workbase reference: 2D9EFE5EA97C270841256A140032774F
A419) Prod. Order Line Had Code on Wrong Trigger for Quantity (Base) Field
Error
Code that should have been placed on the “OnValidate()” trigger on the Quantity (Base) field was wrongly placed on the “OnLookup()” trigger.
This has been corrected.
Table 5406, Prod. Order Line

Service System reference: DE-947-195-QGUZ
Internal Workbase reference: F374C64814171B4CC1256BDC002F9BD7
A420) Obsolete Planning Lot Nos. Field Resent in Manufacturing Setup
Error
In NM 2.60, the planning lot nos. was used for planning between Production Orders – on the planning tab for production orders. From Attain 3.00, this field wasn’t there anymore. In NM 2.60, production orders were planned with the same part no. From Attain 3.00, this wasn’t possible anymore because the planning lot nos. were no longer present on the production orders. Thus, as the Planning Lot Nos. field was not used, it should have been removed from the Manufacturing setup.
This has been corrected.
Table 99000765, Manufacturing Setup.
Form 99000768, Manufacturing Setup.
Codeunit 119020, Create Manufacturing Setup. (Demodata)

Service System reference: INT-98-524-3UZ6
Internal Workbase reference: 1262FB76A67D0E76C1256B170050D55F
A421) Unable to Change Currency Code on a Sales Order with a Production Order Created by Planning
Error
It was impossible to change the currency code on a sales order when a production order was planned for the order.
This has been corrected.
Table 36, Sales Header.

Service System reference: DK-150-26-MDQ4
Internal Workbase reference: 4A38CDA9B1294B69C1256B6C004625C5
A422) Order Tracking in Purchase Order Lost When Transfer Was Used as Requisition System
Error
When using Transfer as Requisition System, Order Tracking on the Purchase Order was lost.
This has been corrected.
Code unit 99000883, Req. Line-Reserve

Service System reference: DE-294-319-TGHH
Internal Workbase reference: 8C777199F7DA111BC1256B1700550BE5

A423) Superfluous Variables and Filters Were Present in the Redefined Reorder Job
Error
Report 699, Calculate Plan – Req. Wksh. contained some now obsolete Variables and filters.
This has been corrected.
Report 699, Calculate Plan – Req. Wksh.

Service System reference: N/A
Internal Workbase reference: 458F1C69B7E4C3D4412569840044925A
A424) Unnecessary Code in Reports 699/99001019
Error
Reports 699, Calculate Plan – Req. Wksh. and 99001019, Calculate Plan – Plan. Wksh. contained unnecessary code.
This has been corrected.
Report 699, Calculate Plan – Req. Wksh.
Report 99001019, Calculate Plan – Plan. Wksh.

Service System reference: DE-240-256-GDEL
Internal Workbase reference: 90B513377B396F26C1256B9D003D86E1
A425) Reservation Against Purchase Line with a Job No.
Error
It was possible to reserve an item against a purchase line that contained a job no. Correspondingly, it was also possible to reserve an item that was set up for automatic reservations against a purchase line that contained a job no.
This has been corrected.
Codeunit 99000845, Reservation Management

Service System reference: DE-908-375-UHUB
Internal Workbase reference: 5B9C0E509D887B24C1256B1F00536906
A426) Order Promising Wrong ATP Calculation
Error
It was possible to for the ATP calculation to suggest an Earliest Shipment Date even when there was no inventory available.
This has been corrected.
Table 27 Item
Table 99000880 Order Promising Line
Codeunit 99000886 Capable to Promise
Codeunit 99000889 Availability Management

Service System reference: IT-482-958-KLCZ
Internal Workbase reference: C03BBD8D8058B8BCC1256BD70039A504
A427) Problems in Order Promising When Quantity Changed
Error
The CTP calculation was incorrect when the quantity on the order line was changed.
This has been corrected.
Table 27 Item
Table 99000880 Order Promising Line
Codeunit 99000886 Capable to Promise
Codeunit 99000889 Availability Management

Service System reference: INT-474-675-3UZY
Internal Workbase reference: 70492E090E97A703C1256B2700491BD6
A428) Sales Order Planning Created Incorrect Production Order Due Date
Error
Sales order planning used the work date instead of the shipment date for the production order due date.
This has been corrected.
Table 99000791 (NA 3.01) 5405 (NA 3.10) Production Order

Service System reference: US-994-454-UV9D
Internal Workbase reference: 0BF09D919C7640E2C1256B58004B66AC
A429) Information from Production Order Line Lost in Output Journal
Error
When a production order consisted of more than one line for the same item number, the variant and location codes were not transferred to the output journal.
This has been corrected.
Codeunit 5406 Output Jnl.-Expl. Route

Service System reference: HQ-106-230-JHXV
Internal Workbase reference: 444EEF5A07F6BDC7C1256BAB003D7F28
A430) Purchase Unit of Measure Not Transferred Correctly to the Requisition Worksheet
Error
When using the Calculate Plan function in the Requisition Worksheet, the Purch. Unit of Measure was incorrectly transferred from the item card to the requisition worksheet line.
This has been corrected.
Codeunit 99000845 Inventory Profile Offsetting

Service System reference: N/A
Internal Workbase reference: 154FC4C73B4CB7A3C1256BB7003D3A20
A431) Replan Function Did Not Create Production Orders for Subassemblies Correctly
Error
The Replan function on a production order that specified a location did not create additional production orders for subassemblies.
This has been corrected.
Report 99001026 Replan Production Order

Service System reference: DE-895-860-2FUE
Internal Workbase reference: 4B02BAB3284969AFC1256BD700302757
A432) Multiple Prod. Order Instead of Multi-line Prod. Order
Error
The function ‘Carry Out Action Message’ created one firm planned production order per MTO/multi-level planning line, instead of creating one multi-level/multi-line production order.
This has been corrected.
Codeunit 99000813 Carry Out Action

Service System reference: N/A
Internal Workbase reference: A903B1BA696CEAB2C1256BF80032765E
A433) Report 99000788 Had Redundant Code
Error
This has been corrected.
Service System reference: DE-594-121-3K4L
A434) Could Not Carry Out Action Message When Using Project Order
Error
If a project order was created from a sales order, and the shipment date later changed, the system was able to calculate a regenerative plan.
This has been corrected.
Service System reference: DE-554-841-NAV6
A435) Unable to Change Concurrent Capacity on Output Journal Line
Error
When you changed the value of concurrent capacity on the output journal line, an error message was created.
This has been corrected.
Service System reference: DK-795-634-ZBQV
Issues
A436) Performance Improvement When Planning Production Orders
Issue
To improve performance, the code has been changed to avoid unnecessary requests to the Calendar Entry table.
To improve performance, the code has been changed and extra filtering added to Calendar Entries by using the assumption that filtering on Starting Date-Time alone can imply a filter on Ending Date-Time, and vice versa, making better use of indexes.
To improve performance, the code has been changed and extra filtering added to Prod. Order Capacity Need by using the assumption that filtering on Starting Date-Time alone can imply a filter on Ending Date-Time, and vice versa, making better use of indexes.
Performance improved by reducing requests to Calendar Entry Table.
In response to this issue, a change has been implemented.
Codeunit 99000774 Calculate Routing Line
Codeunit 99000810 Calculate Planning Route Line

=== Cap. Reqts. Planning ===

==== Errors fixed ====

A437) Wrong Error Message When Changing Unit of Measure on Work Centers
Error
It is impossible to change the Unit of Measure on work centers that are currently scheduled. This error message was not formatted correctly.
This has been corrected.
Table 99000754 Work Center

Service System reference: CZ-934-365-8MX5
Internal Workbase reference: 776F24DFB2F260D5C1256B96003EBB96
A438) Scheduling of Production Order Lines Using the Same Routing
Error
If two production order lines used the same routing, changes in the date or time for the one line affected the other.
This has been corrected.
Codeunit 99000773 Calculate Prod. Order

Service System reference: DK-216-441-NBRN
Internal Workbase reference: E54BC0603B1A6BD0C1256B040035F969
A439) Allocated Capacity for Production Orders
Error
When the capacity allocated to a certain operation of a production order was looked up from the production order routing, the proper allocations were not always shown.
This has been corrected.
Form 99000817 Prod. Order Routing

Service System reference: DK-878-958-XGA9, SE-310-821-KCNF
Internal Workbase reference:
95F7419BFC06C038C1256B5900487565
0BF4B8A273D0C357C1256B670039642B
A440) Expected Capacity Cost in Production Order Statistics
Error
The expected capacity cost for production orders was not calculated correctly in all cases.
This has been corrected.
Codeunit 99000774 Calculate Routing Line
Codeunit 99000810 Calculate Planning Route Line

Service System reference: CZ-376-249-VHR2
Internal Workbase reference: 68B3A60517E63430C1256B61003065A0
A441) Recalculation of Allocated Capacity When Rescheduling Production Orders
Error
When a production order was rescheduled, the allocated capacity was recalculated. This recalculation allocated capacity for the total output quantity, even though some capacity consumption was already posted.
This has been corrected.
Now the remaining allocated capacity for runtime is just rescheduled – the quantity stays the same. However, the allocated capacity for the setup is recreated.

Codeunit 22 Item Jnl.-Post Line
Codeunit 99000774 Calculate Routing Line

Service System reference: NL-473-753-TG86
Internal Workbase reference: EF34AE2DDD83242CC1256B61004AB7A2
A442) Expected Capacity Need for Production Orders
Error
If a production order was made from the planning worksheet, the expected capacity need on the production order statistics was zero.
This has been corrected.
Table 99000830 Planning Routing Line
Codeunit 99000810 Calculate Planning Route Line
Codeunit 99000830 Carry Out Action

Service System reference: CZ-107-624-LJVL
Internal Workbase reference: 7A9F6AF37EFEC333C1256B61004B89A1
A443) Multiple Lines on Production Orders
Error
If a production order had more than one line and the lines used the same routing in different versions, it was impossible to insert new operations.
This has been corrected.
Codeunit 99000772 Prod. Order Route Management

Service System reference: LT-815-303-YKSS
Internal Workbase reference: 12E281BC605C03A9C1256B99002A9FFC
A444) Manually Created Production Order Lines
Error
If a production order lines was created manually, the Unit Cost Calculation field was not initialized properly, but was by default set to ‘Time’.
This has been corrected.
Table 5409 Prod. Order Routing Line

Service System reference: N/A
Internal Workbase reference: 0EA983FF5EF694F0C1256B6E003C293A
A445) Manufacturing Information Lost on Purchase Lines for Subcontracting
Error
If the user changed the Buy-from Vendor No. on a purchase order, the manufacturing-related information was lost on purchase lines for subcontracting.
This has been corrected.
A446) Error Message When Trying to Run the Work Center or Machine Center Tables
Error
An error message was given if the above tables were run from the object designer.
This has been corrected.
Service system reference: US-707-110-6P4W
A447) Queue Time on Production Orders from the Planning Worksheet
Error
When production orders were created from the planning worksheet, queue time on the work centers was ignored.
This has been corrected.
Codeunit 99000810 Calculate Planning Route Line

Service System reference: DE-351-599-TMJR
Internal Workbase reference: F30DCDF8E98DD063C1256B6800305EDF
Issues
A448) Lookup of Allocated Capacity from the Planning Routing
Issue
It was impossible to lookup the related allocated capacity from the planning routing form.
This has now been implemented.
Form 99000863 Planning Routing

Service System reference: N/A
Internal Workbase reference: CD705C5C41D63B2EC1256BB500498C95
A449) Performance Improvement When Calculating Work Center Calendar
Issue
To improve the performance on the Navision Server and SQL Server when calculating the work center calendar for work centers with the field Consolidated Calendar set, a better key will be used for reading.
In response to this issue, a change has been implemented.
Report 99001046 Calculate Work Center Calendar
A450) Performance Improvement When Calculating Machine and Work Center Calendar
Issue
To improve the performance on the Navision Server and SQL Server, the code has been changed to minimize requests to the Calendar Absence Entry table for Machine and Work Centers with no absence registrations in the specified period.
In response to this issue, a change has been implemented.
Codeunit 99000755 CalendarManagement

=== Resources ===

==== Errors fixed ====

A451) Resource Capacity Settings Assigned Incorrect Resource Group
Error
The resource group was assigned incorrectly when setting resource capacity on resources.
This has been corrected.
Form 6013 Resource Capacity Settings

Service System reference: DE-983-316-QGPA
Internal Workbase reference: 1369E019191B6F98C1256BC800295E21

=== Commerce Portal ===

==== Errors fixed ====

A452) The Existence of a Web Site Record Causes Concurrent Posting of Two Sales/Purchase Orders to Fall in a Deadlock
Error
When posting a sales document, four changes can be reflected in the Commerce Portal replication tables in the Commerce Server databases:
1) Deletion of the Sales Order
2) Creation of the Sales Shipment Header
3) Creation of the Sales Invoice Header
4) Creation of a Sales Credit Memo

All of these actions must happen after the Sales Line table has been locked, so the callings depending on the existence of a Web Site record need to be properly placed. The modified code in Codeunit 80 - Sales-Post looks like (The lines in bold have been removed from earlier in the procedure and reintroduced as described):

<PRE>
IF NOT RECORDLEVELLOCKING THEN BEGIN
...
SalesLine.LOCKTABLE(TRUE,TRUE);
...
END;
IF Ship THEN BEGIN
...
IF WebSite.FIND('-') THEN
SynchMgt.InsertSalesShipHeader(SalesShptHeader);
END;
IF Invoice THEN BEGIN
...
IF WebSite.FIND('-') THEN
SynchMgt.InsertSalesInvoiceHeader(SalesInvHeader);
END;
</PRE>

When posting a purchase document, 3 changes can be reflected in the Commerce Portal replication tables in the Commerce Server databases:
1) Deletion of the Purchase Order
2) Creation of the Purchase Receipt Header
3) Creation of the Purchase Invoice Header

All of these actions must happen after the Purchase Line table has been locked, so the callings depending on the existence of a Web Site record have been properly placed. The modified code in Codeunit 90 - Purchase-Post looks like (The lines in bold have been moved from earlier in the procedure and reintroduced as described):

<PRE>
IF NOT RECORDLEVELLOCKING THEN BEGIN
...
PurchLine.LOCKTABLE(TRUE,TRUE);
...
END;
IF Receive THEN BEGIN
...
IF WebSite.FIND('-') THEN
SynchMgt.InsertPurchaseRcptHeader(PurchRcptHeader);
END;
IF Invoice THEN BEGIN
...
IF WebSite.FIND('-') THEN
SynchMgt.InsertPurchaseInvHeader(PurchInvHeader);
END;
</PRE>

This has been corrected.
A453) Triggering a Full Synchronization Causes the Application Server to Run in an Endless Loop
Error
When the size of the database is not big enough for the DB Manager to cache the deletion of records in the SynchMessage Queue Table the Application Server will fail to synchronize the full contents of this table and the changes will be rolled back. This means that none of its records will be deleted, and therefore the next time it tries to synchronize it will find the same contents. This behavior was repeated over and over.
This has been corrected.
A COMMIT needs to be used when the ATAS takes records from the SynchMessage Queue table in Attain and puts it in Windows Message Queues, so the records become effectively deleted after being taken and not at the very end.

It should be introduced as indicated in bold:

Codeunit 6208 - Synchronization

<PRE>
LOCAL PROCEDURE PutSynchMessage@10();
...
IF SynchMessageQueue.FIND('-') THEN
REPEAT
XMLDocEncode.Synchronization(SynchMessageQueue,XMLDocOut);
IF QueueHandler.SendToLabel(NASMgt.GetSynchOutQueueLabel,XMLDocOut,5,0,NASMgt.GetHK
EYLOCALMACHINESynch,TRUE) THEN
BEGIN
IF NASMgt.GetLogSynchronization THEN
MsgLogHeader.InsertLogEntry(XMLDocOut,1,'SYNCHRONIZATION');
END
ELSE
ERROR(Text005);
COMMIT;
UNTIL SynchMessageQueue.NEXT = 0;
</PRE>

A454) Handling of picture extensions
Error
The picture extension was not sent from Attain to the website.
This has been corrected.

In Table 6212 - Page Property, the creation of Compiled Properties and Compiled Multilanguage Properties must include the extension of the picture file when required
(notice that this is only noticeable in the Compiled properties and therefore in the Commerce Server DB, not in the Attain Properties).

In PROCEDURE InsertCompiledProperties a local variable of type Picture (6215) has been added and the code has been modified like this:



In LOCAL PROCEDURE SetValue
A Local Variable of type Picture (6215) must be added

The Code should be modified like this:



=== Issues ===

A455) Renaming of Objects
Issue
The naming of some objects was not consistent with that used Navision Attain. Consequently, the following objects have been renamed:

Table 6203 Web Portal User Role
Field No. Field Name
3 Web Portal Role Code
4 Web Portal Role Name

Table 6227 Web Portal Role

Table 6228 Web Portal Permission

Table 6231 Web Portal Role Permission

Field No. Field Name
1 Web Portal Role Code
2 Web Portal Perm. No.
3 Web Portal Perm. Name
4 Web Portal Perm. Description

Form 6219 Web Portal User Roles
Form 6236 Web Portal Roles
Form 6237 Web Portal Permission List
Form 6238 Web Portal Role Permissions

Codeunit 6228 Web Portal Permission-Create
Codeunit 102213 Create Web Portal Roles
Codeunit 102214 Create Web Portal User Roles

This has been implemented.

=== Commerce Gateway ===

==== Features ====

A456) Sales and Purchase Documents Includes Multiple Lines for One Item Number
Feature
In the base application it is perfectly possible to have several lines associated to a purchase or sales document referring to the same item. This is desirable when making a transaction from different locations, indicating different variants and the like.

In the Commerce Gateway, given the handling of Common Item Nos. this was not possible.
This feature has been implemented
A457) Sales and Purchase Documents Have Different Currency Codes than Defined in the Source Documents
Feature
Up to and including Navision Attain 3.10, incoming purchase and sales documents were required to have either the default currency for the company or to have the same currency code as the document that initiated the transfer through BizTalk Server.
By using a Currency Mapping table, several currencies can be used in one business transaction; the currency code included in the incoming document is defined in this table.
This feature has been implemented
A458) Serial and Lot No. Information Is Transferred Via Commerce Gateway
Feature
As opposed to Commerce Gateway 2.65, where serial and lot no. information was carried directly on sales and purchase lines, Navision Attain 3.60 handles it in separated but related tables.
This tables are now included in the document exchange functionality provided by the Commerce Gateway, so sales and purchase documents are sent together with the their respective reservation entries when they have serial or lot no. data.
This feature has been implemented
Errors fixed
A459) Option and Integer Type Fields Not Encoded as Integers
Error
Option and integer type fields in the BizTalk reservation entries were not encoded as integers.
The following fields must be treated as integers instead of strings when encoding a CG XML document:

5 Reservation Status
10 Source Type
11 Source Subtype
32 Binding
34 Planning Flexibility
99008501 Biztalk Document Direction

Use the FormatInteger directive when introducing the fields in an XML document.

Field 31 Action Message Adjustment is a FlowField, and therefore cannot be assigned

Objects updated:

COD99008517 - XML Document Create
COD99008518 - XML Document Transform
All Document Definitions
All Maps
This has been corrected.
Internal Workbase reference 0BE88BFEBB6ED044C1256BDD005353E6
A460) Currency Codes Not Properly Transferred For Inbound Documents
Error
When accepting an inbound business document, with a currency other than blank (the default of the system), the program would attempt to find a currency exchange rate, independent of the currency mappings for the incoming value.

In the following code units:
99008501 Purchase Quote-Accept
99008502 Sales Order-Accept
99008503 Purchase Order Cnfmn.-Accept
99008504 Purchase Invoice-Accept
99008505 Purchase Receipt-Accept
This has been corrected.
Several changes have been implemented:
1) In the validate procedures, the InboundDocument parameter always gets assigned the mapped currency for the partner. This works independent of whether a reference quote or order was found. This parameter is always passed by reference, so the assigned values remain active for as long as the code unit lives and not only when the validate procedure is active.
2) In the create and update procedures, the currency code of the base documents is always taken from the InboundDocument, which already got the mapped value.
3) When quantities need to be validated, a currency exchange rate for the currency code in process is found, unless the currency for the order is the default of the system.

Internal Workbase reference E50B14E0C062FADFC1256BF9004E877C
A461) Reservation Entries Item Nos. Not Handled Properly
Error
The reservations were created on the basis of the internal item no. for the vendor. Usage of item vendor nos. or common item nos. can now be handled in the following code units:

99008500 Request for Sales Quote-Accept
99008501 Purchase Quote-Accept
99008502 Sales Order-Accept
99008503 Purchase Order Cnfmn.-Accept
99008504 Purchase Invoice-Accept
99008506 Purchase Credit Memo-Accept

This has been corrected.
There is now a variable (ItemNo), which receives the proper value for the item no. depending on the agreement with the partner (common, internal or vendor item no.)
This value is used to issue the creation of reservation entries.

Internal Workbase reference 829B98E7C5DE2033C1256BD0004CCD0A
A462) Amount fields on Open Sales/Purchase Document have a value of 0 when being sent through the Commerce Gateway
Error
Amount fields and discounts are calculated only when an order is released. When Commerce Gateway transfers data from open documents to the buffer outbound tables, a value of 0 in the amount and discount fields was 0, which was of no use to a partner.
This has been corrected.
Internal Workbase reference A3B45917E18BB242C1256BF500460D49
A463) All Objects in Commerce Gateway Updated to use XML 3.0
Error
The objects was using XML 2.0.
This has been corrected.
Internal Workbase reference 2C084BE008E99B7641256A1100525673
A464) Inbound Sales Orders Cannot Be Automatically Accepted
Error
When the type field in the sales line to be accepted was validated, a form was called as a part of the validation process. When using the application server, this is a prohibited action, so a GUIALLOWED verification must be executed before the validation process.

This has been corrected.
Internal Workbase reference BFA24DB450A54F61C1256BDD0054BDD0
A465) Not Possible to Send A Product Catalog to Several Partners
Error
Two things were necessary for this issue to be solved:
1) The COD99008517 was missing CLEAR - XML Document-Create
2) In COD99008514 - XML Document-Send, running the procedure SendXMLDocument, the encoding must proceed on the first unprocessed document.

When an outbound document with a status different from “Processing” is scanned, the same document being sent several times (to the same partner).
This has been corrected.
A MESSAGE will appear for every partner the document has been sent to. Microsoft Navision Attain can continue to operate while the MESSAGE is appearing.

Internal Workbase reference 368EC9C345B84A13C1256ADA003A9175
A466) An Inbound Biztalk Document can Disappear Completely
Error
If a document contains a DocumenteTypeCode that the program cannot handle, it exits the function. The program must issue an ERROR saying that the document cannot be handled. It is unknown and ends up in the retry queue in the Biztalk server and a record is placed in the event log.
This has been corrected.
Internal Workbase reference 92C5C87994E9C696C1256AF400313150
A467) Order Copy Function in Sales and Purchase Documents Copies BizTalk Status Fields
Error
If an order was copied from another order which had already been sent to the BizTalk server, the corresponding BizTalk fields, for example, BizTalk purchase order, were also copied. Therefore, the newly generated order could not be sent by Commerce Gateway.
This has been corrected.
To solve this problem, two functions have been added to code unit 6620: copy document mgt.:
• ClearSalesBizTalkFields
• ClearPurchBizTalkFields

Which are called respectively from functions:
• CopySalesDoc
• CopyPurchDoc

All values of the fields in the range 990085XX have been reset.

Internal Workbase reference 23BF1F4F40E62CBBC1256B980044C08A
A468) Inbound Product Catalog Lines Cannot Be Accepted
Error
In General Ledger, when item import destination was set to “Both” or “Item Vendor Catalog”, the accept of an item product catalog failed.

This was a pricing issue in general caused by two main problems:
1) Keys in table 99 - Item Vendor have been changed.
2) Prices are no longer carried in the Item Vendor table but in the Purchase Price table.
This has been corrected.
To solve this problem, code unit 99008530, Product Catalog Line-Accept, has been updated with the proper keys, and a creation of Purchase Price records when necessary is implemented.

Internal Workbase reference A3EA72761C4CE1C2C1256BF7002A230A
A469) Accept Fails When Creating Item Vendor/Purchase Price Information
Error
In the Purchase Catalog line, accept fails when trying to create Item Vendor/Purchase Price information.

When the Item Import Destination is set to either “Item Vendor Catalog” or “Both” in the Product Catalog tab on the Partner Setup form, the acceptance of product catalog lines failed because it made the wrong call to update the purchase price record. The program attempted to insert the record and then modify some fields in the primary key.
This has been corrected.
Internal Workbase reference B0F57E828A2786A1C1256BFB00327E08
A470) The Currency Code Field in the Biztalk Currency Map Table Must Be Unique and Allowed to Be Blank
Error
In Microsoft Navision Attain, it is possible to create a currency map with a blank currency code, but not possible to change an existing one into blank.

This has been corrected.

The Not Blank property has been set to false as default in the table definition, and the validation code for the field now takes care of rejecting a value that already exists in the table for the Partner
This has been corrected.
Internal Workbase reference 9A85B39621F47A79C1256BF7002B4210
A471) Location Codes for Business Documents Were Assigned To Base Documents
Error
Location codes received in inbound documents, were assigned to base documents. This should not be so, as location codes are company dependent, and are not necessarily the same for two partners.

This has been corrected.

The location code is allowed to stay in the inbound buffer tables as it might be valuable information for the recipient. When accepting the documents, the values are not transferred.

The validation of location codes has been removed from the following code units
99008500 Request for Sales Quote-Accept
99008501 Purchase Quote-Accept
99008502 Sales Order-Accept
99008503 Purchase Order Cnfmn.-Accept
99008504 Purchase Invoice-Accept
99008506 Purchase Credit Memo-Accept
This has been corrected.
Internal Workbase reference F5FC4FEEB9A7AF81C1256BF7002CB134
Issues
A472) Naming of Objects According to Product and Component Names
Issue
Table 99008512 BizTalk Management Setup
Fields
29 Rqst. Srv. IP Address
30 Rqst. Srv. Port No.
31 Rqst. Srv. Transport Type
Appln. Srv. Port No.
This has been implemented

=== Resources ===

==== Errors fixed ====

A473) Resource Group Number Not Set in Job Ledger Entries
Error
When posting a sales invoice and specifying both the resource number and the job number, the resource group number did not appear on the job ledger entry.
This has been corrected.
Codeunit 202 Job Jnl.-Post Line

Service System reference: AU-409-468-Z2PV
Internal Workbase reference: E16F1443A5A617B4C1256B75003ED598

=== Jobs ===

==== Errors fixed ====

A474) Wrong Caption in The Job - Actual to Budget Report (1209)
Error
If a job journal line was made that was not related to a budget, and the Job - Actual to Budget report (1209) was previewed, in the section "Phases that cannot be related to the budget", there were two labels with the caption Budgeted Total Price.
This has been corrected.
Report 1209 Job - Actual to Budget

Service System reference: GB-400-629-TEN9
Internal Workbase reference: AD148427FA8947DAC1256B5000406771


== Development Environment and Database Changes ==

=== Navision Attain Database Server ===

==== Features ====

P1) Login Type Field in Session Table
Feature
The Login Type field has been updated and contains two option values: Database and Windows.
This feature has been implemented.
P2) Server Name Change
Feature
Microsoft Navision Attain Database Server is the new name for what used to be called Navision Server.
This feature has been implemented.
P3) Options to Control the Client Monitor
Feature
A new Option tab has been added to the Client Monitor Form.
See the Application Designer’s Guide for detailed information.
This feature has been implemented.
P4) 128GB Database
Feature
It is now possible to increase the database size to 128GB provided your license permits it. The standard database size is 64GB.

This feature has been implemented.
Errors fixed
P5) Error 1355 When Backing up a Database
Error
While restoring a backup an error 1355 in module 19 could occur.
This was caused by an error in the implementation of Multilanguage.
This has been corrected.
Temporary Workaround: Change your computer settings to English before restoring.

Internal Workbase reference: C32465C5277F2AC4C1256BD0003F275F
P6) Multiple Instances of Hotcopy Crashed a Server
Running two instances of hotcopy with two separate Navision Attain Servers crashed one of the servers.
This has been corrected.
Internal Workbase reference: EBC41BC7C7D49B0CC1256BCD00455DAA
P7) Error 1391 in Module 19
Error
This error could occur when (within the same Navision Attain program) changing records in a form (even through codeunits, dataport, reports etc.), and opening the Table Designer, redesigning a table used by the form (directly or indirectly). This error stopped the server/database engine.
This has been corrected.
These issues have been known for a while, and were addressed with the “SafeGuard” introduced in 3.01.B

Internal Workbase reference: 02F33F4CFFD61666C1256BF0003A6FEF

=== MS SQL Server Option ===

==== Features ====

P8) Login Type Field in Session Table
Feature
The Login Type field has been updated and contains two option values: Database and Windows.
This feature has been implemented.
P9) Per Database Licensing
Feature
It is now possible to store a license file per database. This feature helps ASP businesses by allowing multiple license files to be stored on one SQL Server.
Activating this feature can be done in the New/Alter Database window. This feature requires the new granule: 2,020 Per Database license.
See the manual “Installation and System Management: Microsoft SQL Server Option” for more information about this feature.
This feature has been implemented.
P10) Options to Control the Client Monitor
Feature
A new Option tab has been added to the Client Monitor Form. SQL Server System table options can now be set directly from user interface.
See the Application Designer’s Guide for detailed information.
This feature has been implemented.
P11) Identifier Conversion
Feature
This feature allows you to have characters in the names of SQL Server objects (tables, columns, constraints) in the database replaced with the underscore character. The Remove Characters field contains a list of the characters that are converted to underscores. This feature can be found in the New/Alter Database window.
See the manual “Installation and System Management: Microsoft SQL Server Option” for more information about this feature.
This feature has been implemented.
P12) Database Virtual Table Extended
Feature
The virtual Database table now contains these fields:
• Database Name
• Creator
• Created
• Replication Type
• My Database

Keys: Database Name, Creator, Created
This feature has been implemented.
P13) New Fields and Keys for Session Table
Feature
New fields and keys have been added to the Session table:

Keys available:
• Connection ID
• User ID
• Login Date,Login Time
• Application Name
• Host Name
• Physical I/O
• Blocked,Blocking User ID
• Blocked,Blocking Host Name

See the Application Designer’s Guide for details.
This feature has been implemented.
P14) New Error Message for Deadlock
Feature
The deadlock error message has been improved.

This feature has been implemented.
Errors fixed
P15) Empty Object Record BLOB Handling Was Missing
Error
Unable to delete a table description, if adding a record to the object table created it.
This has been corrected.
Internal Workbase reference: 13ED429723D8DB43C1256BEA0033137B
P16) Performance Problem Gathering Scrollbar Statistics
Error
The determination of the vertical scrollbar size and position in tablular forms could cause performance problems
This has been corrected.
For the SQL platform a query is used with less overhead for obtaining an execution plan, and for both server platforms a timeout will not cause additional server requests to obtain scrollbar information when navigating the table window.

Internal Workbase reference: A980EA2E462ECFFBC1256BD6002C763C
P17) BLOB Data Was Not Always Modified as Expected
Error
On the SQL platform, when modifying data in BLOB fields (for example with IMPORT) and VALIDATEing afterwards, the data modification could be lost.
This has been corrected.
Internal Workbase reference: 9218B338D346EE98C1256BB90053A0CD
P18) Disabled Find Feature in the Microsoft SQL Server option for Navision Attain
Error
The Use the Best Key check box in Find dialogs was disabled.
This has been corrected.
Internal Workbase reference: 4C90E1BE93FBDDFDC1256BE300325E0E
P19) There Was a 30 Character Limit to User IDs
Error
When the User table had the User ID field increased beyond 30 characters, and an ID was entered into the table beyond this size, various error messages were given when trying to login with the ID.
This has been corrected.
The limit is now defined by SQL Server, currently 128 characters.

Internal Workbase reference: 978DB6DCD4D5AB4EC1256BF300481D8C
P20) Code Fields With Variant SQL Data Type: Extended Behavior
Error
A Previous limitation for Code fields assigned as a Variant SQL Data Type existed. This limitation was that variables of that type could not be converted back to either a Varchar or Integer data type.
This has been corrected.
It is now possible, in table re-design, to change the data type from Variant to Varchar. It is not possible to change from Variant to Integer, but it is still possible to change from Varchar to Integer.

Internal Workbase reference: 96D56271E69C2973C1256BF300472526
P21) ODBC Error When Using Filter on SQL Option
Error
When setting a filter on a database field of type Text or Code, it was possible to apply a filter value longer than the defined max. length.
Applying the value 0123456789012345678901 to a Code20 caused the error:

The following ODBC error occurred:

Error: [Microsoft][ODBC SQL Server Driver]String data, right truncation
State ID:22001
This has been corrected.
A better error message is now displayed.
Internal Workbase reference: D2F7D3F36676B0C0C1256BC80020C2E7
P22) Bad Performance Using Form With 'Marked Only' Records
Error
For example using 'Applied Entries':
In the old implementation SQL Server was asked to perform a "FIND(=<)". This did not make any sense, as the server had no knowledge of the "filter" contained in the marked-only list.
This has been corrected.
SQL Server will now do a correct "FIND(=)".
Internal Workbase reference: 59B5AD7BAA4D04ECC1256BF3004A0265
Issues
P23) Limitations When Converting FinSQL from Navision Financials to Navision Attain 3.60
Issue
Converting a SQL database from Navision Attain (3.01.x, 3.10.x) to 3.60 is possible.
Converting a SQL database from any Navision Financials version directly to 3.60 is NOT possible.

See the Upgrade Toolkit for detailed information.

=== Development Environment ===

==== Features ====

P24) New Function Called COPYSTREAM
Feature
If you wanted to copy binary data from an InStream object to an OutStream object, you had to copy byte by byte using a CHAR data type as the buffer. Although this worked, this was slow.
This feature has been implemented.
Now when you want to copy data from an InStream to an OutStream object, you can use the new variable function COPYSTREAM. For more details, see the C/SIDE Reference Guide.

Internal workbase reference ID: E50A64F6EBCAD482C1256B740055D811
P25) Assigning IStream Interfaces
Feature
When you were assigned an IStream interface from one Automation server to another, you had always to declare an InStream or OutStream intermediate datatype. For example:
InStr:= InMsg.GetStream();
MSDOM.Load(InStr);
OutStr:= OutMsg.GetStream();
MSDOM.Save(OutStr);
This feature has been implemented.
Now when you want to assign an IStream interface from one Automation server to another, you don't have to declare anymore an intermediate InStream or OutStream datatype anymore. For example:
MSDOM.Load(InMsg.GetStream());
MSDOM.Save(OutMsg.GetStream());
is now allowed.

Internal Workbase reference: 1106D7CF231EB71DC1256B75002DC007
P26) SOCKET Bus Adapter
Feature
If you wanted to communicate between two applications you had the option of using the named pipe bus adapter, the Microsoft-message Queue bus adapter or third party components. This did not allow extensive ways of interaction.
This feature has been implemented.
When you want to communicate between two applications, you have now the option of using standard socket communications, which allows much broader options of contact. For more details, see the Development Guide for Communication Components.

Internal Workbase reference: E50A64F6EBCAD482C1256B740055D811
P27) GUID Data Type
Feature
The new GUID data type is used for the global identification of objects, programs, records and so on. The globally unique identifier (GUID) data type is a binary 16 byte data type, and can be logically grouped into the following:

4byte-2byte-2byte-2byte-6byte.

The standard textual representation of which is

{12345678-1234-1234-1234-1234567890AB}.

The GUID data type is useful when you want to uniquely identify some data so that it can be exchanged with external applications. For example, if you want to transfer an item catalog to an external application, you add a GUID field to the record in the table and use this as the primary reference when you communicate with the external application.
This feature has been implemented.
Internal Workbase reference: B2572C8B19850915C1256BBA004D0537
P28) Icons and Bitmaps Updated for XP-Look
Feature
Some of the used icons/bitmaps have been updated for XP.

This is a short list of icons/bitmaps, which have been changed or added to the application:
1. Redesign of 5 bitmaps used within applications forms: AL bitmap nos. 6, 7, 20, 21, 34.
2. Redesign of 4 icons used in the window’s title bar, (caption on forms, print windows, batch job windows and the designer window).
3. Redesign of 5 icons used in the Navision Attain Object Designer form, on buttons and in the table for Tables, Forms, Reports, Dataports and Codeunits.
4. Redesign of 6 bitmaps used in the Navision Attain Object Designer toolbar.
This is the bitmaps for Toolbar, Color, Font, Field Menu, C/AL Symbol Menu and C/AL code.
5. Redesign of 3 bitmaps in the Print Preview window (for Toggle zoom, Show one page and Show more than one page side by side).
6. New AL bitmaps.
Bitmaps with nos. 35-44 can now be used from AL-code. The bitmaps are mainly added for the new Main Menu.

Note: All changes are for both Window XP Theme and Windows Classic.
This feature has been implemented.
Internal Workbase reference:
C4B1F3899716773CC1256BBA004D2968
376020CDD1500EBEC1256B560030B864
9D14228E7A8BF523C1256BA3002386BD
P29) New Datatypes: RECORDREF, FIELDREF, KEYREF and RECORDID
Feature
Four new Datatypes have been introduced in C/SIDE - 3 for accessing tables, fields and keys (RECORDREF, FIELDREF and KEYREF) - one reference to a record in the database (RECORDID). Read more about it in the online Help.
This feature has been implemented.
Internal Workbase reference: 401453569A95AC44C1256BBA004D9500

P30) VARIANT Size Reduced
Feature
This is a change to C/SIDE functionality. The maximum length of a string within a VARIANT data type has been reduced from about 10k to about 3k. Also, a VARIANT can no longer contain a variable of type FILE. This has been done to handle some memory allocation problems.
This feature has been implemented.
Internal Workbase reference: E7A1861E8801EC79C1256B900036214F
P31) Assign a Short Cut Key to the Show All Function
Feature
We have implemented that a short-cut key (Ctrl+Shift+F7) for the "Show All" filter function.
This feature has been implemented.
Internal Workbase reference: C9DDCFB42C1DA21FC1256B9C00288671
P32) Debugger
Feature
In addition to the list of new features, this new debugger differs from the old one by being a separate program that is executed from the application.

New Features compared with the old debugger:
- Callstack
- Watch window
- Data types on variables
- Stop debugging
- Search functionality in the code
- The possibility of debugging the Navision Attain Application Server.
- New short-cut keys for activating/deactivating the debugger (Ctrl+Shift+F11) and for activating/deactivating "Breakpoint on Triggers option" (Ctrl+Shift+F12).

For more information see the Application Designer’s Guide.
This feature has been implemented.
P33) New Data Type: DateTime
Feature
This new data type represents a point in time as a combined date and time (01-01-01 23:59:59).
For information about this data type, see the Application Designer’s Guide.
This feature has been implemented.
P34) Customizable Formatting For DateTime Data Type
Feature
DataTime is one of the new data types supported by the application. Now it supports the format customization. This note describes customizable formatting for DateTime.

DateTime data type supports four predefined or “standard” formats and also supports the custom build formats the same way as this feature exists for other data types like for example Date or Time data types.

Here are examples and short descriptions for DateTime standard formats:

Standard Format 0 (Standard display format (output)): 01-02-02 10:20
Date part formatted according to client regional settings for date followed by Time part separated by space. Time part displays only hours and minutes and formatted according to the client regional settings for Time formatting.

Standard Format 1 (Standard display format (edit)): 01-02-02 10:20:15,357
Date part formatted according to client regional settings for date followed by Time part separated by space. Time value consists all time components including seconds and milliseconds. Milliseconds are separated form the other time parts (formatted according the client regional settings for Time format) by decimal separator (according to the client regional settings for decimal separator).

Standard Format 2 (like Standard Format 0): 01-02-02 10:20
Date part formatted according to client regional settings for date followed by Time part separated by space. Time part displays only hours and minutes and formatted according to the client regional settings for Time formatting.

Standard Format 3: 01-02-02 10:20:15
Date part formatted according to client regional settings for date followed by Time part separated by space. Time part displays hours, minutes and seconds. Milliseconds are not displayed.

Customized formats for DateTime can be created using the Format property. Use the following Field Names to create customized formats for DateTime:
Day, Month, Month Text, Quarter, Year, Year4, Week, Week Year, Week Year4, Weekday, Weekday Text, Hours24, Hours12, Minutes, Seconds, Thousands, AM/PM, Second dec.

This feature has been implemented.
P35) New Data Type: BigInt
Feature
This new data type is a 64-bit integer data type.
For information about this data type, see the Application Designer’s Guide.
This feature has been implemented.
P36) New Data Type: Duration
Feature
This new data type represents the difference between two points in time, in milliseconds. The value can be negative.
For information about this data type, see the Application Designer’s Guide.
This feature has been implemented.
P37) AutoIncrement Property
Feature
This new field property applies to fields of the Integer and BigInteger data type.
If this property is enabled, the server will automatically assign a new value to the field when a new record is inserted. The assigned value will be incremented by one for each insert.
See C/SIDE Reference Guide for detailed information.
This feature has been implemented.
P38) Open Company
Feature
In the Open Company window, the user now sees only the companies to which he has access rights
This feature has been implemented.
Internal Workbase reference ID: A008B04C03B437EBC1256BD500265F4F
P39) Name Change
Feature
The product name ‘Navision Attain’ have been changed to ‘Microsoft Navision Attain’ in the following places:
• Window title bars
• Message box title bars
• Menu items in the Menu Help
This feature has been implemented.
Internal Workbase reference ID: D120EEB366871E7FC1256BF8002C4B54
Errors fixed
P40) SendWaitForReply(0) in MSMQ Bus Adapter
Error
The Navision Microsoft-Message Queue Bus Adapter was not waiting until the InMessage was received, as documented, when using OutMessage.SendWaitForReply(0). It would wait to send the OutMessage and would then return immediately.
This has been corrected.
When using OutMessage.SendWaitForReply(0) for the Navision MS-Message Queue Bus Adapter, the function will not return until the InMessage is received.

Internal Workbase reference: 8A02F043C42F2F2CC1256B72002F6CF3
P41) InMessage IStream Interface in MSMQ Bus Adapter
Error
In some situations, the IStream interface of the InMessage object from the Navision MS-Message Queue Bus Adapter would crash the hosting system.
This has been corrected.
The InMessage IStream interface for the Navision MS-Message Queue Bus Adapter has been rewritten to prevent exceptions.

Internal Workbase reference: 8A02F043C42F2F2CC1256B72002F6CF3
P42) InStream.EOS Function Generated an Error Message
Error
In some situations, the InStream.EOS function returned an error message: "You are using and invalid data type for this function".
This has been corrected.
InStream.EOS function should not prompt this Error message anymore.

Internal Workbase reference: 5FFDF4C66514701DC1256B82004DC2EA
P43) Uncompiled Tables Could Cause Navision Attain to Terminate Abnormally
Error
When an uncompiled table was edited in the object designer, pressing F6 (field lookup) would cause Navision Attain to terminate. An error message was shown explaining that the table must be compiled first. But immediately, Navision Attain would close without further warning.
This has been corrected.
The same error message is still shown, but the user is left in the dialog box where the attempt to do the lookup was made.

Internal Workbase reference:
41F298DD72158FA6C1256B9D001A6599
48C0FFE722B9D91EC1256B6E004F394D
P44) View Menu Item Could Cause Uncontrolled Shutdown of Navision Attain
Error
Opening menu items when editing local variables in the C/Al editor would cause unhandled exception in Navision Attain. The error occured when the C/Al Local Variable Window was subsequently closed.
This has been corrected.
The bug has been fixed. It is now possible to continue working. However, the trigger that was selected before the menu Designer Window was opened is no longer selected, when returning from the C/Al Local Window. This happens as the object designer has lost focus when the Designer Window was opened.

Internal Workbase reference: 7F0E2E021B1579CCC1256B6F0037361B
P45) NTimer "Milliseconds" Misspelled
Error
On the event Timer, the parameter "MilliSecounds" was misspelled.
This has been corrected.
It is now spelled “Milliseconds”.
Internal Workbase reference: DFC139DAF810FE42C1256BA400433E5B
P46) Navision Timer Enabled Always Return False(no)
Error
The Enabled function on Navision Timer always returned false(no) even when the timer was actually enabled.
This has been corrected.
Internal Workbase reference: DFC139DAF810FE42C1256BA400433E5B
P47) FILE Data Type Is No Longer Supported Anymore By Variant Data Type
Error
Because of the FILE data type, VARIANT data type consumed lot of memory, This, we stop supporting FILE data types within the VARIANT data type.
This feature has been corrected.
FILE data type cannot longer be coerced to VARIANT data types as, an error message will appear at runtime when trying to do so.

Internal Workbase reference: A4149AE52BC1A807C1256B90003ABE3D
P48) Rectangle Shape Controls Didn’t Display at Runtime
Error
While it was possible to design a rectangular shape control, it was not possible to display it at runtime.
This has been corrected.
Internal Workbase reference: 9ED3B202781E6650C1256B7300223931
P49) Glue Error on Form Designer's Field Menu Window
Error
The buttons on the Form Designer's Field Menu Window were not justified according to the GUI standards.
This has been corrected.
Internal Workbase reference: E48A93E60B1E85C4C1256B7200528AED
P50) CurrFieldNo Varianble Not Always Updated
Error

The CurrFieldNo, system defined variable was not always updated when running code on a table field.
This has been corrected.

Now the CurrFieldNo, will be updated each time code runs on a table field.

Internal Workbase reference: 2945CEA410AEB584C1256B72006E9168
P51) Yellow Tool Tip Box Using 99% CPU
Error
Sometimes when, Navision Attain displayed the Tool Tip the fin.exe file will use almost all the CPU power of the computer.
This has been corrected.
The over load on the CPU is corrected.

Internal Workbase reference: EA0B2C7D913352CC412569C20032F808
P52) Default Value of CallFieldValidate Property Has Changed
Error
Prior to Navision Attain 3.10, the default value for the CallFieldValidate property of dataport fields was <No>.
In version 3.10, the default value has changed to <Yes>. This had the following consequences:

1. Many existing dataport objects would break.
2. Many dataport objects would appear to work, but would no longer perform the actions they used to perform. Data would be corrupted and the errors could be detected too late. This is because many of the Validate triggers fill in values of fields, which in the past the user could assume would be left blank.
This has been corrected.
We have made the following change to the CallFieldValidate property:

When the FileFormat dataport property is set to 'UPXML', the default value of the CallFieldValidate property is 'Yes'.
When the default value of the FileFormat property is 'Variable', it means that the default value of the CallFieldValidate property is 'No'.

This change ensures that both User Portal and Navision Attain dataports work correctly.

Internal Workbase reference: 0EB7746A79B2BCEAC1256B9B00331608
P53) Invisible Dialog Boxes
Error
Sometimes the Open Database and License Information dialog boxes were invisible to the user. The dialog boxes exist in the Windows menu and it's possible to enter data into the fields (for example to logon), but they were not displayed on the screen.
This has been corrected.
The dialogs will now always be visible when user has requested the dialogs.

Internal Workbase reference: E17B4DA3E239DC6FC1256B350038D369
P54) GETFILTER Function Limited to a Maximum of 250 Characters
Error
While it was possible to define a string as a filter with length greater then 250 characters, the GETFILTER function only returned a string of length of at most 250 characters.
This has been corrected.
Internal Workbase reference: EEE85587F1EB7BAAC1256B97002831A8
P55) Dateformula to Dataport
Error
It was not possible to add a Date Formula field to Dataport
This has been corrected.
Internal workbase reference ID: 32916728AE10873A41256AA900473E79
P56) C/AL Function TESTFIELD Gives Incorrect Error Message With DateFormula Data Type
Error
When used with the DateFormula Data type, the TESTFIELD C/AL functions issued a wrong error message. Instead of starting that the DateFormula should be specified, the error message informed that the DateFormula value could not be entered here.
This has been corrected.
The correct error message that the DateFormula value should be specified is now issued.

Internal Workbase reference: 9A154C142036D5B8C1256B510050AD70
P57) Hover Effect on Buttons with No Border
Error
Buttons, with no border had no hover effect. Among others, this affected the Main Menu Window, which is built up of buttons with no border. As a consequence, the Main Menu did not have any hover effect.
This has been corrected.
A hyperlink hover effect (underlining text on hot buttons) has been implemented for buttons with text and no border. The implementation at the same time has introduced the same hover effect on option buttons and check boxes when running Windows Classic.

Internal Workbase reference: C5E75ED36EA248A5C1256B4300527879
P58) Toolbar Dialog Box Looks Bad When Maximized
Error
When the Toolbar dialog box was maximized, this resulted in an additional frame being drawn on the dialog. Furthermore, the toolbar options dialog box could be instantiated more than once, resulting in multiple toolbar options dialog being opened at the same time.
This has been corrected.
The toolbar options dialog box can no longer be maximized. Nor can it be instantiated more than once. It always appears on top to clearly distinguish it from other windows of the application.

Internal Workbase reference: 0DC9D05E8F9D131A4125676100423EE7
P59) Bitmaps Not Drawn Correctly When Using Large Fonts
Error
When using large fonts (>96 dpi) a number of bitmaps where not drawn correctly or wrong bitmaps were drawn. Among others, this includes the toolbar when running XP Windows, About Navision Attain Box, splash screen, and Main Menu Window.
This has been corrected.
Internal Workbase reference: 9C9F74F63EF4D2BDC1256B7D005138F1
P60) Error in .STX File Could Result in Crash of Navision Attain
Error
It was not possible to display error messages related to C/Al CHAR data type, for example, if the sort table entry in the .STX file contained two identical characters, the resulting error message, showing which character was a duplicate would cause Navision Attain to crash.
This has been corrected.
Internal Workbase reference: 40D407C0DDB2AABCC1256B97006125EA
P61) Language Module Import/Export
Error
It was not possible to import or export the complete language module when the Navision Attain license did not contain read/write permissions for all the objects involved.
This has been corrected.
It is now possible to import and export the complete language module regardless of the permissions the user has.

Internal Workbase reference: D295FC06FA812F20C1256B670053FED2
P62) Navision Attain Icon for Microsoft Management Console Snap-Ins
Error
The new Navision Attain icon was missing for the Microsoft Management Console snap-ins.
This has been corrected.
The new bitmap for Navision Attain is now used. The following files have changed:

nasmnasm_16.bmp
nasmnasm_32.bmp
ndsmNDSMSnapIn_16.bmp
ndsmNDSMSnapIn_32.bmp

Internal Workbase reference: EE52062A05E166C3C1256B5E00460612
P63) Option String Search Limitation
Error
When Navision Attain searched in an Option String it searched the Name List and not the Caption list, and this couldn’t successfully search if Navision Attain ran in language other than American English (W1).
This has been corrected.
This bug is now fixed so it will search in the Caption list.

Internal Workbase reference: D2CEF3A18AEB38E9C1256B99004317E8
P64) Navision Attain Crashed Occasionally When Debugger Reached a "Break On Error"
Error
When debugger reached a "Break On Error" and you have a local variable of the REORD data type, Navision Attain crashed when it tried to access the Record variable.
This has been corrected.
This bug is much too extensive to fix in this version and we have to implement a temporary solution that simply does not access the Record variable if it's "Break On Error", a local variable and the data type is Record.

Internal Workbase reference:
8E14D9296092FEC4C1256B48002D22A0
38E223BA782420DB41256A68002DAB6E
P65) Wrong XP Font in Frames within a Form
Error
The frame text painting uses the theme API DrawThemeText function. This function needs a wide string (LPWSTR).
In the text drawing of the frame(ThemePaintFrame:rawThemeText) the OEM2Wide function was called to make the transformation from LPSTR to LPWSTR. This function called the OEMToAnsi function prior to calling the MultiByteToWideChar function. This caused the problem.
This has been corrected.
The ThemePaintFrame:rawThemeText function has been changed now to call the MultiByteToWideChar directly.

Internal Workbase reference: 47D72AD568FBCE5EC1256BAE0032D893
P66) Report: Calculation of Page Breaks and Transfooter Problems
Error
If you had indented data items in a report, size of a section would always be subtracted from the space free of a page, even though the SHOWOUTPUT property was set to False in the OnPreSection trigger.
This could lead to strange page breaks. It could also cause that the last line on a page was not added to the TransFooter's total.
This has been corrected.
Internal Workbase reference:
EFAC2E318FFD4AE441256855002DAE1B
7D9FFA640E12A589412568B7002E65A5
B10139770D1547C3C1256BBB0031F1EE
P67) Multi-line Column Headings Use Too Much Space in Windows XP
Error
When a column contained a multi-line column header the heading text did not fit properly and the header was too tall. This applied only to the Windows XP operating system.
This has been corrected.
Internal Workbase reference: 0A58C085802CB542C1256BBC001E2E4F
P68) Object Designer Entry in .STX File Could Be Translated.
Error
The translation code (represented as “x” below) for the .STX file entry

00089-01504-030-x: Object &Designer

was erroneously specified as “2”, which meant that the entry could be translated during localization.
This has been corrected.
The translation code has been changed to “0”, which means that “Object &Designer” should not be translated during localization.

Internal Workbase reference: 4C7386D904AC652CC1256BF0004F942A
P69) Using the Windows Menu Item Could Cause Client to Crash.
Error
When used under stressed conditions – typically when using shortcut keys to frequently move from one window to another – using the Windows menu item to access the individual windows caused Navision Attain to crash.
This has been corrected.
Internal Workbase reference: CBBE557647264CDEC1256BD80046FCDA
P70) Unnecessary and NON-Operational Popup Menu in the Status Bar.
Error
When right-clicking fields in the status bar, the menu Cut|Copy|Paste|Clear appeared. However, this menu had no effect.
This has been corrected.
Internal Workbase reference: 135C7388E615CEF6C1256BDC0022727B
P71) Missing Lock Test on InProcess COM Events.
Error
C/AL code on InProcess COM events was executed even though there was a system lock. The system lock could be Test Database Expand or a message.
This has been corrected.
Now InProcess COM events respect a system lock.

Internal Workbase reference: B741CFB6C05ADC35C1256BDF001DB807
P72) Cannot Import Codeunit as Text.
Error
Using an automation variable and setting the property WithEvents=Yes could sometimes break the export to a .txt file containing the variable.
This has been corrected.
The export to .txt files has been changed so that the use of automation variables and their events is supported better.

Internal Workbase reference: 9A03E58FC55447FBC1256BD700365330
P73) Automation to MS Project 2000 Makes fin.exe Crash.
Error
Unable to import MS Project file.
This has been corrected.
A memory bug has been fixed. MS Project files can now be imported.

Internal Workbase reference: 66CFD267C718B53DC1256BCE00445A81
P74) Printer Selection on ATAS Does Not Work.
Error
When running Navision Attain Application Server, the printer selection trigger in Codeunit 1 is not called.
This has been corrected.
Internal Workbase reference: 8F857A97D37B5D97C1256BE5003F11CC
P75) Memory Leak When Running Report.RUN in a Loop.
Error
When running Report.RUN in a loop, you get a memory leak.
This has been corrected.
Internal Workbase reference: 46561FF5E5864B9FC1256B05003701F0
P76) Last Used Filters Overrule Record Parameters in Reports.
Error
If filters are parsed through the record parameter to a report, they are only applied if the filters were empty the last time the report was generated.
The problem is visible in request form, which now “remember” the previously used filters instead of applying the filters from the current record.
This has been corrected.
The Filter functionality now works as it did prior to Navision Attain 3.60 Beta2.

Internal Workbase reference: 7EB6E507BC97C62BC1256BD4002A1F95
P77) Error when Generating Hyperlinks to Reports.
Error
In Navision Attain 3.60Beta2, there is a problem with hyperlinks to reports in the following menu commands:
• Send Link by e-mail
• Sent Shortcut to desktop
• Copy Link
… and in the C/AL functions concerning URLs on reports
This has been corrected.
The hyperlink functionality now works as it did prior to Navision Attain 3.60 Beta2

Internal Workbase reference: FBCC18820897F31CC1256BD400436F0C
P78) An Error in a Report Makes the Client Crash.
Error
If you execute a report through a report variable, an error in the report will crash the client.
This has been corrected.
Internal Workbase reference: 7DFFA5B31A2D2A37C1256BED00469151
P79) Strange Performance of the Field Menu in the Object Designer.
Error
If the Field Menu was opened in the Section Designer, and focus was then switched to another object in design mode, the Field Menu was not usable for the new object. If you clicked one of the fields, the Field Menu would switch to show the fields in the Section Designer.
This has been corrected.
Internal Workbase reference: 9E5FB8700B49D089C1256B5E0038155C
Issues
P80) Hidden Flowfields on Tabular Forms Are Not Calculated
Issue
If a flowfield on a tabular form is hidden the field it is not calculated. This affects C/AL code on the form that assumes the field has been calculated automatically by C/SIDE.
This behavior was introduced in Navision Attain 3.10. but failed to appear in documentation for that version.

This has been implemented.

=== Commerce Portal ===

==== Features ====

P81) Customer Card Added to Sales Representative Role
Feature
A customer card feature has been added to support the most common tasks needed by a sales representative working in the field.

The customer card enables the sales representative to create, look up and maintain information on his/hers customers. The information displayed, is based on the fields displayed on the General, Invoicing, and Commerce Portal tab on the customer card in Navision Attain.
The Sales Representative can look up comments, statistics and contacts related to a customer. Furthermore, the sales history of the customer can be reviewed.

New role permissions have been added in Navision Attain. These are used to maintain the user rights for these features. The new permissions are numbered 101xx, (previous permissions are numbered 100xx)
This feature has been implemented
P82) Contact Card Added to Sales Representative Role
Feature
A contact card feature has been added to support the most common tasks needed by a sales representative working in the field.

The contact card enables the sales representative to create, look up, and maintain information on his/her contacts. The information displayed is based on the fields displayed on the General tab, Communication tab on the contact card in Navision Attain.
The sales representative can look up to-dos, interactions, comments and order history related to a contact.

New role permissions have been added in Navision Attain. These are used to maintain the user rights for these features. The new permissions are numbered 101xx, (previous permissions are numbered 100xx).
This feature has been implemented.
P83) Maintain Credit Limit
Feature
A sales representative can edit the credit limit of a customer from the website. A special permission has been created for this feature.
This feature has been implemented
Errors fixed
P84) Anonymous Users Cannot Change Language
Error
An anonymous user was not able to change language even though the links to change language were visible to the user.
The ASP page userinfo.asp has been modified so anonymous users can now change language.
This has been corrected

Internal Workbase reference: 212F00A96C8A6083C1256B57004CC71A
P85) Maintenance of Order and Ship To Address Always Selects First One
Error
If you maintain ship/order to address, and several customers or vendors have the same ship/order to code, Navision Attain will select the first ship/order to address when maintaining from the Web site. Customer no. and vendor no. must be added to the WHERE clause for addresses.
This has been corrected

Internal Workbase reference: 9CF3D5EC83ED4123C1256B730032DD65
P86) Using Readonly Attribute for Select - Option Command Not Possible
Error
Because it's only possible to use readonly attribute for INPUT commands in HTML code, a workaround for the SELECT commands is now available.

bEditData containing the Readonly value doesn't have any meaning for SELECT command, instead the following code for the table row containing SELECT command must be used:

<%
if bEditData = "readonly" then
display_roles = "style='display:none'"
end if
%>
<tr <% = display_roles %> >
This has been corrected

Internal Workbase reference: DCA052D205ED963BC1256B800050C431
P87) Erroneous Redirect After Saving Item For Later
Error
On product card, moving an item to the save for later basket, you will be redirected to the regular basket. This is not correct, redirection should have been to the saved shopping cart.
This has been corrected

Internal Workbase reference: 6B97D83A0DBC36D841256A9D00545BE1
P88) Hardcoded Value in Delinfo.asp
Error
In the shipment information page (delinfo.asp) a hard coded value (n/a) is used to indicate that a unit has not been specified. The hard coded value has been removed and no value is displayed when a unit not specified in Navision Attain.
This has been corrected

Internal Workbase reference: 7966AC9CFD9E811FC1256B02004AB88F
P89) Names of Catalog Changed
Error
NCP Catalog has been renamed Cronus Catalog. It contains the same items as before. Test Catalog has been renamed Cronus Furniture Catalog. It now only contains furniture.
This has been corrected
Internal Workbase reference: 4D0FF90663E3E4CBC1256B1B004F2A6F
P90) The Basket Frame Not Updated
Error
Having reordered an item, the basketframe is not updated.
This has been corrected
Internal Workbase reference: B1A2F46A97C86035C1256B220058D5A5
P91) Order And VAT Amount Changed to 0,00 on Update
Error
The order amount and VAT amount changed to 0.00 when the delivery date were updated. When the site was refreshed, the amount would change back to what it should be.
This has been corrected
Internal Workbase reference: E7B4771EEAB7E6F3C1256B180033AEA4
P92) No Keys Set In Code Unit 6203
Error
Several places in code unit 6203, the function SETRANGE on the contact table is often used without setting the right keys. Without the right key, a timeout occurs every time a new sales document is created from the Web site.
This has been corrected
Internal Workbase reference: D4D1270A3E86BE04C1256BB300227EED
P93) Commerce Portal Synchronization Fails
Error
In code unit 86 in the OnRun trigger, a call to CP synchronization is made without a check to the Web site. This causes a customer license without Commerce Portal granule to fail the synchronization.
This has been corrected
Internal Workbase reference:94474379906CD18FC1256BC20030FF16
2.5 Commerce Gateway
Features
P94) Simplified Hosting Developed
Feature
The design of the Commerce Gateway Request Server is changed and the code language changed from VB to C#. The new design is based on a communication architecture where XML documents are sent to Commerce Gateway Request Server via Socket communication: TCP/IP. This bypasses any previous security constraints that were present using the Com+ approach.

Socket communication does not have to comply with the Microsoft security context.

The previous version of the AIC supported Named pipes as the communication protocol. In order to have unified communication architecture in the solution, this has also been changed to sockets communication.

This feature has been implemented.
2.6 User Portal
Errors fixed
P95) User Portal Limitation When Using Automation Components
Error
Some Automation components could not be created when invoked through User Portal dataports.
This has been corrected.
It is now possible to create the same Automation components through User Portal dataports as it is when they are invoked from the Navision Attain client.

Internal Workbase reference: 94AEB4D05403AB59C1256B8300415FDB

=== Navision Attain Application Server ===

Features
P96) Reports on Navision Attain Application Server
Feature
Navision Attain Application Server is now able to run reports and does like the Navision Attain Client. However, there are the following differences:
• It does not have page setup.
• It does not have print preview.
• It will fail if you try to run a report with the request form.
• It will ignore the status dialog box.

Navision Attain Application Server can:
• Print a report.
• Run a batch report.
• Save a report as HTML.
• Save a report as XML.
This feature has been implemented.
Internal Workbase reference: 074D1AD3B661BDC4C1256BBA004DC00C
Errors Fixed
P97) Not Possible to Connect to a Database Server Running on AIX Using Windows Authentication
Error
It was not possible to connect to a database server running on an AIX machine from ATAS or UPAS. This was due to the fact that both ATAS and UPAS required Windows authentication to connect to the database server.
This has been corrected.
It is now possible to make a client connection using Windows authentication on a database server that runs on AIX. The user will be authenticated on the client that connects to the database server. In the case of UPAS/ATAS, it will be the client machine that runs UPAS/ATAS. All groups that have a security identifier that belongs to the so-called Well Known Security Identifier group, or Alias Security Identifier group, will not be used for authentication even though they might be added as users on the client machine.

Internal Workbase reference: 5E74BB409CFF3913C1256BE5001E18F0
P98) Missing Error Message When “Request Form” on Report is Expected.
Error
When a report is called from C/AL with the parameter “Request Form” = True (the default value), the report is (as expected) not generated. However, no error message is logged
This has been corrected.
Internal Workbase reference: 6C72AE8B5503C105C1256BD1003A39DF

== Installation ==

=== Installation Program ===

==== Features ====

I1) Commerce Gateway Request Server Installation Developed
Feature
The Commerce Gateway Request Server is installed on the same server as your Microsoft BizTalk Server. Navision Attain Application Server connects to the Commerce Gateway Request Server to send and receive electronic business documents and an installation program has been developed to install it.

This feature has been implemented

=== Errors fixed ===

I2) Miscellaneous Errors When Uninstalling Commerce Gateway Related Systems
Error
Numerous errors could occur when uninstalling or modifying Commerce Gateway systems. The delivery method for the Commerce Gateway COM+ proxies could not be installed cleanly. Commerce Gateway Request Server and developments in the Navision Attain Application Server have replaced these COM+ proxies, and the errors no longer arise.

This removes the COM+ related errors from the Navision Attain Application Server and also makes every Navision Attain client a Commerce Gateway enabled client.
This has been corrected
Internal Workbase reference:
3FAD0FF06A5F9C3DC1256B51002724FA
96E12971CAA3F49DC1256B7A004EBD65
I3) Commerce Gateway.dll Not Registered Correctly
Error
Registry information denoting that the commercegateway.dll is in fact also a lightweight application integration component (AIC) was not given when installing previous versions of Commerce Gateway for the Navision Attain Application Server. The Commerce Gateway Request Server Installation program now performs registration of the commercegateway.dll file and the file is now installed and registered correctly.
This has been corrected

Internal Workbase reference: CCF3A92217127EA8C1256B840073DEB8
I4) Uninstalling Commerce Portal
Error
If multiple Commerce Portal synchronization services were implemented by creating multiple registry entries, uninstalling would fail because the uninstallation program only expected a single entry.

The uninstallation program now can cope with multiple entries and deletes them accordingly.

This has been corrected

Internal Workbase reference: 0F3924EC6E432FF441256A7D0035D6D5
I5) Message Queue Restarting ATAS
Error
The job queue and reply queue have been moved to be installed by the Navision Attain Application Server installation program and error queue and synch queue have been moved to be installed by the Commerce Portal Web Integration Components installation program.

This has been corrected

Internal Workbase reference: 49E8A9A2CF8EAC9DC1256BB300394202
I6) Problems Related to Microsoft Data Access Components Installation
Error
When Navision Attain was installed Microsoft Data Access Components was automatically installed, but on some computers this could initiate problems
This has been corrected.
It is now possible to skip installation of MDAC when installing the Navision Attain client or Navision Attain Application Server or forcing the installation.
Internal Workbase reference: 50B3A948B8627897C1256B7C0045C99D

== Tools ==

=== C/ODBC ===

==== Features ====

T1) Regional Decimal Symbol unaware C/ODBC application like Access97 can't retrieve correct decimal value from Database.
Feature
A new option called "Use Regional Decimal Symbol" has been added at C/ODBC data source Option setup dialog.
The default installation will set this option default to "No", which makes the driver only return '.' as the decimal separator

The Access97 users and other Microsoft Office 97 users should to be aware to set the Option to "Yes" so C/ODBC will replace the '.' with the Regional Decimal symbol which set up from Regional settings.

It is emphasized that this option should is not recommended to be used with newer application since according to ODBC specification, the Decimal symbol should always be '.', the ODBC application (e.g. Microsoft Access 2000) should be the one the format in the way it wants. For instance replace '.' with ','. Newer applications are products like Microsoft office 2000 and newer.

The Option is available in the when setting up the data source. From the C/ODBC setup window choose "Options..." and in the C/ODBC Options window you will find the "Use Regional Decimal Symbol" option.
This feature has been implemented.
Internal Workbase reference: FE8E297DE2D81437C1256BD40041D827
Errors
T2) C/ODBC wasn't able to filter on some dates
Error
It wasn't possible to filter on some dates. You would get an ISAM error or error 142-1 in STX file.


This has been corrected.
We will now use the same date format as in C/SIDE.

Internal Workbase reference: E7E8A65810917609C1256BFB00390934
T3) C/ODBC doesn't support fields of type 'Date Formula'
Error
DateFormula data type was not supported in the SQL Where clause (Filter level support)

This has been corrected.

DateFormula data type is now supported; i. e. SQL statement can be executed like:
select * from CODBCTestTable where fDateFormula = '2D+2W'

Internal Workbase reference: 6EA31B9782B6509D41256A000030B97B
T4) C/ODBC filter length error
Error
C/ODBC handle the filter length of <Text> or <Code> data type incorrect. The filter length was set to 1 less than the designed length.

This has been corrected.
The filter length has set to the same length as designed for <Text> and <Code>.
Internal Workbase reference: DC3CC15BADE7112BC1256BD40024DBE1
Issues
T5) C/ODBC Samples Removed from Product CD.
Issue
C/ODBC samples are no longer provided.

=== C/FRONT ===

==== Errors fixed ====

T6) SetNavisionPath did not have any effect
Error
C/Front always used the latest installed path to the Navision client.

This has been corrected.

SetNaviPath allows the C/Front user to set the path which contains the files: fin.exe, ndbcs.dll, fin.etx and fin.stx.

If the user doesn't call SetNaviPath or call it with NULL argument, the Program Path will be set to the value that read from Registry. So if the user have multiple install of Attain and doesn't supply correct argument for SetNaviPath(...), the path will be set as the latest Attain path.

Internal Workbase reference: C748469A64F618AA41256A86004DDEF1

=== Upgrade Toolkit ===

==== Errors fixed ====

T7) Upgrade Tool Did Not Fill Sales Shipment Line Table
Error
The Upgrade Toolkit manual did not specify that the Bill-to Customer No. field on the Sales Shipment Line table got updated during the upgrade.
This has been corrected.
Service system reference: NL-893-605-FGN5
T8) "Return Qty to Receive Must Equal the quantity" Error Message After Upgrading
Error
Some fields were not correctly initialized during upgrade.
This has been corrected.
Service System reference: AU-545-252-N358
T9) Report Selection Was Incorrect After Upgrading
Error
After upgrading, the report selection was incorrect.
This has been corrected.
Service System referenc AU-94-645-RTSH

== Documentation ==

=== Manuals ===

==== Features ====

D1) Application Designer’s Guide
Feature
Information about the Monitor, Session and Database virtual tables has been updated.
Information about identifiers and data types has been updated.
Information about the new data types has been added.
D2) Installation & System Management: Microsoft SQL Server Option
Feature
Information about identifier conversion and per database licensing has been added.
Information about installing MDAC has been added.
D3) Installation & System Management: Navision Attain Database Server
Feature
Information about the recommended way to increase the size of a working database has been added.
Information about the maximum database size has been updated.
Information about setting up database files has been updated.
New name Navision Attain Database Server has been implemented.
Reference to RAID 5 has been removed.
D4) C/SIDE Reference Guide
Feature
Information about the new data types, properties and the functions they use has been added.
Errors fixed

D5) Error in Upgrade 3.01 and 3.10 and Comments
Error
In Step 9 of the manual (w1w1upgr.pdf - Upgtk folder on the product CD), it was stated that you must import the Upgrade3.10.2.fob file. Inside this file, there was a codeunit: 104057 Upgrade 3.10 Step 2 Comments. This codeunit had to be run in Step 16, but there was nothing on the trigger OnRun. For that reason, this codeunit would never upgrade the Sales Comment Line & Purch. Comment Line tables.
This has been corrected.
Service system reference: ES-237-448-NN2Z

=== On-line Help ===

==== Features ====

D6) Navision Attain Online Help
Feature
The Help topics for the New/Alter database windows has been updated.
Server name change has been implemented.

=== HTML Pages ===

==== Features ====
D7) HTML Pages replaced by DemoShield

Feature
The HTML Pages are no longer used but have been replaced by a DemoShield ‘browser’.

The ‘HTML’ folder as well as the index.htm file has been removed from the Product CD. A new startcd.exe and ‘Bin’ folder have been added to run the DemoShield browser.
This feature has been implemented.

Источник http://wiki.dynamicsbook.com/index.php?tit...ion_Attain_3.60
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Опции темы Поиск в этой теме
Поиск в этой теме:

Расширенный поиск
Опции просмотра

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 00:31.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.