== Overview ==
This file contains information about how to upgrade from Navision Financials W1 1.30 to Navision Financials W1 2.00, and other miscellaneous information concerning this release.
This document was originally written and published by Navision Software A/S and
released as part of the Navision CD for that product. The original text has been
preserved, and has only been edited for formatting. The original document can be
found at the end of this document, under external links.
== Change Log ==
=== Development Environment ===
Print preview had blank areas when scrolling the preview of a Report that contained Shapes. This has been corrected.
Since version 1.30 it has not been possible to use Char as SourceExpr for a TextBox. This has been corrected.
A disabled (Enabled=No) MenuItem could be invoked via it's ShortCutKey.
This has been corrected.
In version 1.30, TableBox updating was faulty in certain scenarios.
This has been corrected.
Closing a maximized Form with a TableBox that contained a focus rectangle drew a "bad" focus rectangle. This has been corrected.
Specifying 0 for RowHeight or MatrixColumnWidth properties in the Property Sheet generated a 'Division by Zero' error and halted the program. This has been corrected.
Access keys on the tabs in the C/AL variable editors have been removed.
When filters were set on FlowFields, the functions Rec.COUNT, Rec.DELETEALL and Rec.NEXT disregarded them unless one of the functions Rec.GETFILTERS, Rec.MODIFYALL, Rec.GET, Rec.FIND, Rec.CALCFIELDS, Rec.CALCSUMS was called after setting filters on FlowFields and before calling Rec.COUNT, Rec.DELETEALL or Rec.NEXT. This has been corrected.
"Error 1213 in module 19" could appear instead of the following message: "Another user has modified the record for this <xxx> since you retrieved it from..." This has been corrected.
Unified login failed when special characters such as Г¶ and Г¤ were used in the user name. This has been corrected.
The error message: "The transaction cannot be completed because it will cause inconsistencies in the <TableName> table." sometimes occurred even though no tables were marked as potentially inconsistent by the rec.CONSISTENT function. This has been corrected.
The password for a user was no longer valid after the UserID for that user was renamed. This has been corrected. NOTE: It is now necessary to enter the password for the UserID being renamed.
When a table was imported in Navision Financials format, the system always had to rebuild the existing keys in the database. This is no longer the case.
If AssistEdit was clicked in a text box in order to enter a file name on a dataport request form, and the text box has a source expression such as CurrDataport.Filename, a general protection fault occurred. This has been corrected.
If either the function CurrDataport.Skip or CurrDataport.Break were called from within the triggers OnInitDataport, OnPreDataport or OnPostDataport, a general protection fault occurred. Because it does not make sense to call CurrDataport.Skip or CurrDataport.Break from within these Triggers, such calls will now be ignored.
When the client ran under Windows 95, printing or previewing a report could cause a general protection fault. The problem occurred when certain printer drivers, typically matrix printers, were used. This has been corrected.
The Find and Replace dialogs could not handle strings longer than 80 characters. This has now been changed so that strings of up to 250 characters can be used. The maximum length for a string in Navision Financials is 250 characters.
Controls on the request options form of a report or dataport sometimes had strange names in the Symbol menu. This has now been corrected.
In the filter dialog of a report or dataport request form, if you entered a new name in the "Field" column in an existing line, the previous field disappeared, but any filter on that field remained. The result was that the actual filter could not be seen. The only way to fix the problem was either to put all the fields on the form and then remove the filter, or to delete the ZUP file. This has now been corrected so that all fields that have filters are shown if you reopen the report or dataport.
In the filter dialog of a report or dataport request form, if you had a filter on marked records, you could use the lookup, drop-down or AssistEdit button on the filter, even though the "Marked" filter was read only. However, using a button produced an error and the request form was closed. This has now been corrected, so it isn't possible to use the lookup, drop-down or AssistEdit button on a "Marked" filter.
The "Marked" filter is created by clicking the lookup button on the form, marking some records on the lookup form and clicking View->Marked Only on the menu. When you close the lookup form, a line saying Marked=Yes appears in the filter.
In certain situations, the contents of a lookup form looked strange the second time the user used the lookup function from a report or dataport request form. The error occurred if one of the fields on the lookup form showed the result of a function, and the function was placed on the table that was looked up. This has been corrected.
When Navision Financials objects were modified in a multiuser environment, it was possible to overwrite the work of another user because of the object cache. Now when an object is modified, it is always loaded from the database, even if the object was already in the object cache.
The following scenario produced the error: User A loads object 1 in order to run it and closes it again. This saves a version of object 1 in user A's cache. User B loads object 1 for design purposes and saves it. This changes the object in the database. User A loads object 1 for design purposes and gets the old version from user A's cache. When user A saves the object, the changes made by user B are overwritten.
The C/AL function RANDOM() returned values in the range [0..n] instead of in the range [1..n], as was stated in the documentation. This has been corrected.
Time calculations that passed midnight caused an error of 1 ms. This has been corrected.
If a server running under Windows NT had a large cache, a situation could arise in which new users could not log on to the server. This has been corrected.
When the C/AL function ERROR()was used, tables locked by the code calling the ERROR() function were not unlocked. This has been corrected.
Error texts taken from the Windows NT and Windows 95 operating systems did not show special characters correctly. This has been corrected.
If you called the C/AL function ERROR from a trigger from which it is not allowed to write to the database, the system gave two messages. Only the first message was relevant. The second message, "You cannot make any changes in the database from this trigger," was redundant.
This has been corrected.
It was not possible to print Shapes with ShapeStyle=HorzLine or ShapeStyle=VertLine when BorderWidth=HairLine.
Nor was it possible to print Shapes with ShapeStyle=HorzLine when BorderWidth=1pt. This has been corrected.
If you made multiple backups without reading from the database in between them, all of the backups were taken of the same version of the database. Now the system selects the latest version each time a backup is started.
C/SIDE did not pick the first matching option when a user partially entered an option value. This has been corrected.
It is now possible to copy the contents of non-editable text boxes to the clipboard.
The Find dialog now contains a 'Find as You Type' option. The Find dialog is automatically opened in 'Find as You Type' mode, when the user starts typing in a non-editable text or code field.
The Find, Replace, Filter, Sort, and Zoom dialogs now open outside the active form.
It is now possible to search by pressing the first letter in table boxes where the Find dialog does not apply - the Find dialog still only works on database tables. Examples include the Show Columns dialog, the Zoom dialog, the Field Menu, the Properties window, and the C/AL Symbol Menu.
The Replace dialog now has a 'Replace Whole Field' option.
The contents of check boxes, option buttons, indicators, and picture boxes can now be formatted as text and copied to the clipboard using the Edit|Copy menu item. For BLOBs in picture boxes, a 'Yes' or 'No' is copied depending on whether the BLOB contains data or not.
The Print Setup dialog has been removed.
The properties Orientation, PaperSize, PaperSource, and DeviceFontName has been added to reports.
The Left-, Top-, Right-, and BottomMargin properties now serve as defaults for the margin settings in the Page setup dialog.
It is now possible to choose a printer from the Page Setup dialog using a 'Printer...' button.
Previously, the status line did not always display that there was a filter on the current view even though there was. This has been corrected.
When C/AL code was called from a form with a subform, the subform link was updated and the current record was set to the first. This has been corrected, so that the current record doesn't change.
Local characters like <nowiki>''</nowiki> or <nowiki>'''</nowiki> were not transferred correctly in certain lookup scenarios. This has been corrected.
Resizing the columns of a matrix box could lead to very strange situations, where the non-matrix part was hidden. This has been corrected.
In version 1.20, the NextControl algorithm was altered for matrix boxes, so that pressing Enter in the last column moves to the first matrix column of the next record. Unfortunately, this change unintentionally meant that the NextControl property on the inmatrix control was ignored. This has now been corrected, so that NextControl on the inmatrix control works as it did before version 1.20.
The local versions of the startup, about and logo bitmaps 0 and 17 have been removed.
Splitting and merging long lines in the C/AL editor could result in a General Protection fault. This has been corrected.
On a menu button, it was possible to create two menu items with the same ID. This caused problems for the translation tool because there were two texts with the same ID.
Now, when an object is compiled, the system checks that the ID's are unique.
We now support arrays of OCX and Automation variables. An array is created by setting the Dimensions property of the variable > 1. For an array of OCX variables, an element is created the first time it is used. For an array of Automation variables, each element must be created explicitly by calling CREATE(ServerArray[Element]). The compiler does not accept this syntax: CREATE(ServerArray). The NewServer parameter can be used independently on each element as it is created. You can CLEAR either the whole array by calling CLEAR(ServerArray) or an individual element by calling CLEAR(ServerArray[Element]).
It is now possible to assign a VARIANT to an object. For example, an Automation server might return a VARIANT that can be either a string or an object. Previously, this would have caused a compile-time error.
We now support the USERDEFAULT "metadatatype" (except structs). The most important aspect is the ability to use Enums (which are used extensively in Microsoft Outlook). You cannot use the symbolic name - you must use the constant value. For example, use "-4711" and not "appColorWhite".
The algorithms for generating syntax strings for the Symbol Menu have been revised extensively. Previously, there were a number of errors and inconsistencies. Most importantly, data types of properties are now displayed.
All syntax strings pasted from the Symbol Menu into the C/AL Editor were reduced to 3 characters. This has been corrected. Now, strings with less than 132 characters are pasted into the C/AL Editor, while longer strings are not.
The AssistEdit button in the Subtype field of an Automation variable in the C/AL Locals menu now appears correctly.
The algorithms for handling the Subtype field of an Automation variable have been changed. This means that a number of errors and inconsistencies have disappeared.
It is now possible to invoke Help for an interface of an Automation server from the Symbol Menu.
It is now possible to invoke Help for an interface of an Automation server from the Automation Objects list.
It is now possible to invoke Help for an automation server from the Automation Servers list.
There is now a run-time type check when one Automation object is assigned to another.
Memory leak problems with OCX/Automation member calls involving the Date, Boolean and Currency data types have been corrected.
New data types: support for ByRef variables and VARIANT. Most simple data types (except Byte) are now converted to the corresponding C/SIDE data types.
There is now stronger compile-time and run-time type checking.
"OCX : Properties with more than one parameter do not work and can cause a GP error." This problem has been solved.
"OCX : When compiling an object with an unknown OCX, an internal error 7 module 35 is produced." This problem has been solved.
The list of OCXs in the Custom Control List that is opened by clicking the AssistButton in the Subtype field of an OCX variable is now sorted alphabetically on the user-friendly name of the control.
Methods and properties of an OCX control are now shown with the correct (COM) data types in the C/AL Symbol Menu.
The OCX interface now supports a wider range of data types. See the C/SIDE online Help for the OCX data type for details.
The OCX interface now supports calling methods with VAR (ByRef) parameters.
If the syntax string of an OCX is > 132 characters, it will not be pasted into the C/AL Editor from the Symbol Menu. Previously, an error would occur in this situation.
Version 2.0 includes support for controlling Automation servers from C/AL. See the documentation for details.
Navision Financials now supports the Microsoft IntelliMouse. See the "Office 97 Compatible" Help topic for details.
Navision Financials now supports context-sensitive (pop-up) menus. This is the menu that appears when you right-click the mouse. See the "Office 97 Compatible" help topic for details.
Shortcut keys are now localized to be compatible with the shortcut keys used by the local version of Microsoft Office 97.
Temporary tables may now have more than one key. Only the keys in use are maintained.
The new properties AutoFormatType and AutoFormatExpr have been added to fields and TextBoxes.
=== Application Changes ===
Sales Tax and VAT have been collected
Some new features have been added to the Item card.
It was possible to create inconsistent records in the Gen. Jnl. Allocation table, which made it impossible to use the recurring general journal. This has now been corrected.
The Combine Shipments (295) report could not make more than 1 invoice. This has now been corrected.
Previously, when the Adjust Exchange Rates (595) report was run several times, without anything else being done in between, the report would still make an adjustment the 2nd time, 3rd time, and so on. A rounding problem concerning the bank account balances in foreign currency could cause the report to continuously move an amount equal in size to the minimum unit in the company's currency (1 cent, for example) back and forth between the relevant G/L accounts.
Previously, a format change in Last Used No. in the No. Series Line table could be rejected. This has now been corrected.
Previously, it was possible to rename a Bank Account, Customer ... by entering a new number in the No. field, even though the program was told not to allow manual numbers in the table. This has now been corrected.
The ApplicationManagement (1) codeunit has been changed, so that when "?" is entered in a text field, the program no longer replaces it with the first record in the standard text table.
The table relations on the Customer Posting Group fields in the Issued Reminder Header (297) and Issued Fin. Charge Memo Header (304) tables have been corrected.
It was not possible to post an invoice on which Invoice Rounding had taken place. If the amount rounded on the invoice was converted to LCY, it was then rounded to 0.00. It's now possible again to post an invoice or order with a zero amount on a sales line with Type=Account.
When Location Mandatory is set in the Inventory Setup table, the program now also checks that the New Location Code field in an Item Journal Line is filled in when the Entry Type on the line is Transfer.
Whenever a general journal is posted and one of the journal lines has a check mark in the Correction field, the Gen. Jnl.-Post Batch (13) codeunit now checks that there is a check mark in the Force Doc. Balance field on the general journal template and that all the lines for this document (date, type, no.) have a check mark in the Correction field.
Due to an error it was not possible to use Suggest Vendor Payments and post the entries created. This has been corrected.
A new problem was introduced by Service Pack 1 for W1 1.30. The Shipping No. Series and Posting No. Series fields were not filled in when an order (invoice etc.) was entered using the AssistButton to fill in the No. field.
The header in the the Reminder (117) and Finance Charge Memo (118) reports was only printed on page 2. This has been corrected.
If you deleted a customer (table 18) or a vendor (table 23), the bank accounts (tables 287 and 288) was not deleted. This has been corrected.
The system now checks that the Gen. Journal Line fields "Check Printed" and "Posting No. Series" are not filled in at the same time.
When changing the customer/vendor no. on a sales/purchase order (invoice...) that contained manually created lines with text only, the user received an error message. This has now been corrected.
In W1 1.30, the Quote (204), Order Confirmation (205), Purchase - Quote (404) and Order (405) reports did not include all the lines when printing more than 1 quote. This has now been corrected.
The description FlowFields in the No. Series Relationship (310) table have been extended to include 50 characters so they match the length in the No. Series table.
Functionality for reservation of inventory items has been implemented. The reservation can be managed automatically or manually. With reservation of inventory items, it is possible to ensure and maintain timely delivery of items to customers. In a sales document, the quantity can be reserved for delivery to a particular customer on a certain date. This means that the same items cannot be sold to or reserved for another customer.
The document type field in the Sales Header table (36), Sales Line table (37), Purchase Header table (38) and the Purchase Line table (39) has been given a new option Blanket Order. The Blanket Order No. field (97) and the Blanket Order Line No. field (98) have been added to the Sales Line table (37) and the Purchase Line table (39).
Account Schedules has been improved and will allow the user to define the format of account schedules. In particular, it will be possible to adjust the number, type and position of columns. A user may wish to see the percentage of a balance compared to a budget and it is easy to create a new column to view such data. It is also possible to make simple calculations and view results in different ways, for example, as percentage values.
A matrix window for viewing Customer / Item Discount Groups coherence has been implemented and the field Discount Group has been changed from integer to code.
The Customer Discount Group table (340) and the Item Discount Group table (341) are new tables.
The Customer Discount Groups form (512), the Item Discount Groups form (513) and the Customer/Item Discount Overview form (514) are new forms.
The Cust./Item Disc. Gr. field has been changed from integer to code 10 in the Customer table (18), the Item/Cust. Disc. Gr. field has been changed from integer to code 10 in the Item table (27) and the Customer Disc. Group field and Item Discount Group field have been changed from integer to code 10 in the Cust./Item Discount ( 20). On the Customer Card form (21), the size of the Cust./Item Disc. Gr. field has been changed and lookup made possible. A menu item for accessing Customer/Item Discount Overview has been added. On the Item Card form (30), the size of the Cust./Item Disc. Gr. field has been changed and lookup made possible. A menu item for accessing Customer/Item Discount Overview has been added.
Matrix windows for viewing Items by Location and Item Availability have been implemented.
Menu items have been added to the Sales Quote form (41), Sales Order form (42), Sales Invoice form (43) and the Item form (30). On the Item Availability form (157), the field Inventory has been added. The Items by Location form (491) and the Item Availability by Location form (492) have been created.
An option for automatically calculating invoice discounts has been implemented.
A new Calc. Inv. Discount field has been added to the Sales & Receivables Setup table (311) and the Purchases & Payables Setup table (312).
Changes have been made on the Sales & Receivables Setup form (459), Purchases & Payables Setup form (460), the Sales Invoice form (43), Sales Invoice Lines form (47), Sales Quote form (41) , Sales Quote Lines form (95), Sales Order form( 42), Sales Order Lines form (46), Sales Credit Memo form ( 44), Sales Cr. Memo Lines form (96), Purchase Quote form( 49), Purchase Quote Lines form( 97), Purchase Order form ( 50), Purchase Order Lines form (54), Purchase Invoice form (51), Purch. Invoice Lines form (55), Purchase Credit Memo form (52), and the Purch. Cr. Memo Lines form (98).
Changes have been made in the codeunit Sales-Post (80), codeunit Purch.-Post (90).Codeunit Test Report-Print(228), codeunit Document-Print(229).
When the user chose to apply to in a journal in Sales & Receivables, Purchases & Payables, or General Ledger the system gave Applies-to ID to all three journal lines. If the user then deleted the line from a General Journal Line, the Applies-to ID from the Apply Customer Entries /Apply Vendor Entries window was not deleted.
This error has been corrected by changing the Gen. Journal Line table (81).
When the user wanted to calculate an invoice discount manually in Sales & Receivables, a dialog box appeared. If the user did this in Purchases & Payables, the dialog box did not appear.
This has been corrected by changing the Purchase Order Lines form (54), the Purch. Invoice Lines form (55), the Purchase Quote Lines form (97) and the Purch. Cr. Memo Lines form (98).
The top frame on the Bank Acc. Reconciliation form (379) has been changed to tab control.
When the user chose to apply a payment to one or more open debit entries from Sales & Receivables, or to apply a payment to one or more open credit entries from Purchases & Payables, the system gave Applies-to ID to General Journal Line. If the user delete the Applies-to ID from Apply Customer Entries, the Applies-to ID will not be deleted from General Journal Line.
This error has been corrected by changing the Gen. Jnl.-Apply codeunit (225).
It is now possible to apply an invoice or credit memo to several entries, but the functionality is available as a default only for the credit memo. To use the functionality from the invoice, the menu item Apply Entries must be added to the Function button.
An Applies to ID field has been added to in the Sales Header table (36) and the Purchase Header table (38).
Changes have been made in the Apply Customer Entries form (232), Apply Vendor Entries form (233) Sales Credit Memo form (44) and the Purchase Credit Memo form (52).
Changes have been made in the Sales-Post codeunit (80), Purch.-Post codeunit (90), Cust. Entry-SetAppl.ID codeunit (101) and the Vend. Entry-SetAppl.ID codeunit (111).
A new Sales Header Apply codeunit (401) and Purchase Header Apply codeunit (402) has been made.
The field Description has been added to the G/L Budget Entries form (120).
It is now impossible to create Budget Entries without a Budget Name. A TESTFIELD on the G/L Budget Entry Table (96) has been made, and a TESTFIELD has been added to the On Insert trigger.
A field for User ID has been added to the G/L Budget Entry Table (96) and the Job Budget Entry Table (211). This field will be updated through the trigger On Insert, where the line "User ID" := USERID is added.
In the Customer (18), Vendor (23), Sales Header (36) and Purchase Header (38) tables, there is a Payment Method field pointing to a code field in the Payment Method table. For consistency, these fields have been renamed Payment Method Code.
At present, there is no way to see the BOM entries. The menu button on the BOM Registers form (267) has been extended with an option for showing the BOM Ledger Entries form 430)
A Currency card form (495) and Finance Charge Terms card form (494) has been implemented.
For consistency Reconciliation has been added as a Menu Item in G/L Journal Batch List form (251).
The field External Document No. has been added to the Applied Vendor Entries form (61) and the Applied Item Entries form (63).
On the Item Availability form (353), the Quantity on Hand field has been renamed to Inventory and now the field will react to the date filters; i.e. by pressing the Balance at Date button the column shows quantity on hand at date.
Confidential Information in Human Resources
In Human Resources, comments about confidential information are stored in the general comments table, and are thus accessible to everybody. Therefore a Human Resource Confidential Comment Line table (5219) has been made.
When making a sales line and using Appl.-to ID or Serial No., the unit cost was copied from the item card, but should have been taken from the specific item ledger entry. This has been corrected.
In the Sales Line table (37), the function SelectItemEntry has been extended with a line of code, which copies the Unit Cost field in the Item Ledger Entry table (32) to the Unit Cost (LCY) field on the Sales Line.
Comments on Quotes were inherited by Orders, comments on orders were inherited by posted shipments, but were not inherited by invoices. This has been changed so comments will be inherited by all descendants.
The existing copy function has been changed in the Sales Post codeunit (80), the Blanket Sales Order to Order codeunit (84), Purch. Post codeunit (90) and the Blanket Purch. Order to Order codeunit (94). Both the Sales & Receivbles setup form (459) and table (311), and the Purchases & Payables setup form (460) and table (312) have been extended to include three new option fields for Copy Comments.
When the user tried to import a company into a consolidation company from a file using the Import Consolidated from File report (92), it could only be done if the company was created manually in the database. This should not be necessary since the company is already in the Business Unit table (table 220). This has been corrected.
In the Business Unit table (220), the Company Name field has been given the properties Validate Table Relation and Test Table Relation has been set to NO.
When a lookup was made for a G/L Account in the G/L Account table (15), the Chart of Accounts form (16) showing amounts was displayed. Instead, the G/L Account List form (18) should be used as the lookup form. This has been corrected.
When entering blocked BOM-items in a BOM journal, no warning was given. The Post function tested for this and displayed a warning. Now, a warning has been implemented to be given when entering blocked BOM's. On the BOM Journal Line table (89), the function CheckItemAvailable has been changed accordingly.
It was not possible to explode BOMs in the Item Journal, as it can be done in the Sales Order form (42). The functionality and menu item from the Sales Order form (42) has been copied to the Item Journal form (40).
The Fixed Asset - Book Value 01 report (5605) was given the headline Fixed Asset - Book Value 01 %3 instead of Fixed Asset - Book Value 01 (Budget Report). This has been corrected.
To ease localization, the local variable FieldErrorText has been changed from a type Text30 to Text50 in the FA Insert G/L Account codeunit (5601).
The calculation of Custom 1 depreciation was not correct if the starting dates for calculating "Depreciation" and "Custom 1" were different. The Calculate Custom 1 Depr. codeunit (5612) has been changed to correct this.
Lines in the FA Reclass. Journals were rounded according to the content of the Use Rounding in Periodic Depr. field on the Depreciation Book Card form (5611). This did not work properly when the fixed asset was 100% reclassified. This has been corrected in the FA Reclass. Transfer Line codeunit (5612), so now the lines are always rounded using the standard rounding.
If the Bal. Account Type was Fixed Asset, the post processing code for Bal. Account No. was not triggered. This could result in the contents of the Department Code field and the Project Code field being wrong. This has been corrected in the Gen. Journal Line table (81).
A miscalculation of VAT% in FA occurred in the Purchase Order line when posting acquisition costs from a purchase invoice. This happened if the asset did not have a link to the Default Depr. Book, or if the Default Depr. Book field in the FA-Setup was not filled in. This has been corrected by inserting a VALIDATE in the GetFaPostingGroup function in the Purchase Line table (39).
In the reports Post Job Recognition to G/L (1213) and Post Job WIP Value to G/L (1214) the posting specification lines were not placed under the correct Job No. This has been corrected.
It is now possible to have different base currencies with different amount rounding precision in different companies in the same database.
Customs Exch. Rate has been removed from the Currency table.
Customers and vendors may now use any number of currencies. It is now possible to apply amounts in different currencies.
The Exchange Rate field has been removed from the Currency table (4). Rates are now entered as two amounts on the Currency Exchange Rate table (330) - the fields determine the ratio. Every line has a Starting Date field, allowing former exchange rates to be saved in the table. In addition, the posting date on each transaction determines the default exchange rate on, for example, journal lines.
Foreign currency amounts are now displayed with the correct number of decimals for the particular currency.
Resources can now be priced in any number of currencies.
All conversions of amounts between EMU currencies now use the triangulation method.
An additional reporting currency has been introduced so it is possible to report to national authorities in a currency other than the base currency.
When you set Calc. Inv. Discounts to "Yes" in the Sales & Receivable setup and you posted a sales invoice, the No. Series Line table was locked for too long. In order to optimize performance, changes have been made in the Sales-Post codeunit (80) and the Purch.-Post codeunit (90).
If you specified the "LIFO" costing method for an item, you were not able to post an item transfer journal line for this item. This problem has been solved by changing the Item Jnl.-Post Line Codeunit (22).
The message that appears when you start the demo company has been changed from a message that you must answer "Yes" or "No" to, to a message that can only be confirmed (by clicking "OK").This is because it makes no sense to use the demo company with dates before 1-1-99 because no exchange rates have been setup for dates before 1-1-99. Changes have been made to the ApplicationManagement codeunit (1).
The number of repeated reads of Inventory Setup, General Ledger Setup and General Posting Setup has been reduced in the codeunits 22, 32, 80 and 90 in order to improve posting performance.
It was impossible to delete a general journal line if the value in the Remaining Amount field was less than the value in the Pmt. Disc. Possible field. The Gen. Journal Line table (81) has been corrected.
After a shipment and an invoice had been made, it was possible to change
the Type field or the No. field and reset the Quantity Shipped and Quantity Invoiced fields.
Now it is not possible to change the fields when the contents of the Quantity Shipped field is different from 0. Corrections have been made to the Sales Line table (37) and the Purchase Line table (39).
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
|Опции темы||Поиск в этой теме|