Changes Made in Navision Financials 1.30
From Dynamics
3.0 LOG
=
3.1 Development Environment
P1. NEW New installation program.
P2. NEW It is now possible to use the Microsoft Systems Management Server to install the Navision Financials client.
P3. NEW MAPI Support. It is now possible to use File, Send to send electronic mail. When you send information from a report, the output is attached in HTML format and can be viewed by the receiver using an internet browser.
P4. CHANGED Because we have added a Send menu item to the File menu, it has been necessary to change the access keys for some of the menu items in the W1 version.
P5. NEW C/SIDE now uses the system settings for the tooltip and status bar font.
P6. NEW Improved implementation of the C/AL HYPERLINK function: a) Invokes any default browser (tested with MS Internet Explorer and Netscape
Navigator).
b) Reuses an already-open default browser. c) Works in Windows 95, Windows NT 4.0 and later versions.
P7. NEW Design tools now use small captions.
P8. NEW It is no longer possible to size the height of a tablebox heading so that no rows are visible.
P9. NEW The Navision Financials client and server both comply with the "Designed for Microsoft BackOffice" logo requirements.
P10. NEW Navision Financials complies with the "Designed for Windows NT and Windows 95" logo requirements.
P11. Setting the FILENAME of a dataport with USEREQFORM set to "No" produced an error when that dataport was run from C/AL. This has been corrected.
P12. Certain C/AL code in the OnBeforeEvaluate trigger of a dataport field would lead to a stack overflow. An example of such code is: Text := PADSTR(,50-STRLEN(Text),'0')+Text; This has been corrected.
P13. Attempting to import or export dataports containing lines of more than 600 characters resulted in only the first line being imported or exported. This has been corrected.
P14. With a demonstration license (or any other license with access to the form, report, or dataport designers), it was possible to modify records in any table, including G/L entries, posted invoices, and so on. This has been corrected.
P15. C/AL produced a General Protection (GP) fault when you tried to run an uncompiled object twice from the same owning object. Now an error message appears, and the owning object is closed properly the first time you attempt to run the uncompiled object.
P16. The following C/AL code would lead to a GP fault: CLEAR(file); file.OPEN(path); This has been corrected.
P17. The following C/AL code would lead to a GP fault, when len > 250: FORMAT(var,len); This has been corrected.
P18. The Navision Financials client now reports a more specific error if you try to run it on a computer (running Windows NT) that is simultaneously running the Navision Financials server as a service.
P19. Using a field of type #1### in the C/AL functions CONFIRM, ERROR, or MESSAGE without specifying a parameter for the #1### field would cause Navision Financials to close. This has been corrected.
P20. Certain format strings passed as the third parameter to the C/AL function FORMAT or set as the field property Format would not evaluate properly and would sometimes cause Navision Financials to crash. This has been corrected.
P21. The C/AL function DMY2DATE did not properly check the range of parameters. This has been corrected.
P22. The UNIX versions of the Navision Financials server would report an incomprehensible error if the UNIX kernel needed reconfiguration. This has been corrected.
P23. Trying to copy controls that cannot be created on a report from a form and then paste them to a report would generate a GP fault. Now only valid report controls can be inserted into report sections - any other control types that have been copied to the clipboard are simply left out when the copy is pasted. Controls within container controls are also left out. This means, for example, that if you try to paste a tab control to a report section, neither the tab control nor the controls on the tabs will be copied to the section. If you want to copy the controls on a tab to a report section, select and copy only the controls inside the tab - not the entire tab control.
IDE CHANGES TO 1.30 BETA 2
P24. ERROR In some situations, typing too quickly would cause characters to be lost - especially when inserting records. This has been corrected.
P25. ERROR The Navision Financials GUI is now robust when Windows is running low on resources. In such situations, previous versions would sometimes generate a GP fault (or on rare occasions, lock up Windows). This problem was particularly related to Windows 3.x.
P26. ERROR Progress indicators from the database were displayed below C/AL dialogs. This has been corrected.
P27. ERROR C/SIDE now properly detects a Rec.MODIFY in the OnValidate trigger and sets xRec accordingly.
P28. ERROR In some situations - for example, when focus switched between a subform and its main form - the control triggers OnActivate and OnDeactivate and the form triggers OnActivateForm and OnDectivateForm would be issued too many times or in an odd order. This has been significantly improved.
P29. ERROR In a table box without multiple new lines, clicking on a check box column in an empty row would change the value of the last non-empty row. This has been corrected so that a click in an empty row only sets the focus to the last non- empty row.
P30. ERROR Inserting a new section in the Report Designer did not cancel the selection of controls. This has been corrected.
P31. ERROR If you tried to run a form, report or dataport from the OnCloseForm trigger on a form, the program stopped with a GP fault. The fault also occurred if you tried to access a variable of one of these types for the first time in the OnCloseForm trigger. This has been corrected.
P32. NEW In a lookup from a filter, the record is now initialized with single filter values. (A single filter is a filter that is not a range.) This means, for example, that if you specify a single filter on a report data item in the DataItemTableView property, the values from the filter will be transferred to the record of the lookup table. This will allow the lookup form to show only the records that are included by the filter.
P33. ERROR If an error occurred in the OnNewRecord trigger on a form, an internal error could result (the form did not close). Now in all form and control triggers, when an error should cause the form to close, the form does close.
P34. ERROR Changing the license file from one that did not include access to C/OCX to a license file that did include it did not actually give the user access to C/OCX. This has been corrected.
P35. ERROR C/SIDE did not update the Work Date field in the status bar when you changed the work date with C/AL. This has been corrected.
P36. ERROR The contents of the SourceTableView property on a form was not respected when the form was run from within the Form Designer (CTRL-R). This has been corrected.
P37. ERROR When the request form was closed with Cancel, Esc or Close, the setup was not saved. This has been corrected.
P38. ERROR Ellipsis dots have been added to the File, Database, Options menu item.
P39. ERROR In a form, if you tried to edit a text box showing a variable of the type Record, the program stopped with an error. At compile-time, the program now checks that a text box has a valid data type. Valid data types for text boxes are: Integer, Text, Code, Decimal, Option, Boolean, Date, Time, Binary and BLOB.
P40. ERROR When an object was exported to a text file, the program did not ask for user confirmation before existing files were overwritten. This has been corrected.
P41. ERROR If you modified an existing code unit in the designer by deleting a property, and you then tried to close the designer, the designer would close without asking whether you wanted to save the changes. This has been corrected.
P42. ERROR A user could gain access to the C/AL Code window even without the proper license. This has been corrected.
P43. ERROR If AssistEdit was used in a text box with ID=1 on the request options form of a dataport, the Common Dialog for import/export file appeared. This could cause a GP fault if the type of the variable used for the text box was not Text. There is now a type-check so that only variables of the type Text can be used.
P44. ERROR There is now a Compile Check on SourceExpr in dataport fields to ensure that SourceExpr has a valid data type.
P45. ERROR If a dataport had the property Import=Yes, the Save-dialog was used instead of the Open-dialog. Now the dedicated Common dialog is used, so that the Save- dialog is used with export and the Open-dialog is used with import.
P46. CHANGED Temporary files are now by default placed where the operating system places temporary files.
P47. CHANGED The default century has been changed from 1980-2079 to 1920-2019. This means that 10.10.50 is 10.10.1950 instead of 10.10.2050.
P48. ERROR The C/AL function DMY2DATE accepted dates in which Day and Month had invalid values. This has been corrected.
P49. ERROR The C/AL functions CONFIRM/MESSAGE could bring the system down if the expected
- 1### fields were not specified in the function call.
P50. CHANGED The C/SERVER now runs with a higher priority on Windows NT because otherwise it might not run on a computer that was also running Microsoft SQL server.
P51. CHANGED The performance of the VXFS file system has been improved on SINIX and HP-UX servers.
P52. CHANGED Disk writes to the database will now alternate with disk reads when a completed transaction has been residing in memory (not committed to disk) for more than 60 seconds.
P53. CHANGED The commit cache process is now monitored each time a transaction is committed, to ensure that the commit cache process is not starved for resources (CPU, memory and disk I/O).
P54. ERROR If the panic error variable was set, C/SERVER generated a GP fault when a client connected to the server. The panic error variable is set if the operating system returns an unexpected error, for example, or if some unexpected error is detected. This has been corrected.
P55. CHANGED The scheduling priorities for C/SERVER and the commit cache have been increased to 15 (the same as for MS-SQL Server, for example). This is done to avoid starvation of C/SERVER and the commit cache, when they run on a computer that also runs MS-SQL Server, for example.
P56. CHANGED The maximum startup time for "slaves" (used by commit cache) has been increased to 200 seconds (it was previously 10 seconds). This prevents "Error 1312 in module 19" from occurring.
P57. ERROR "Error 1355 in module 19" occurred when the CPU stack became full, which prevented Navision Financials from closing. This has been corrected.
P58. CHANGED The filter parameter in error messages and in the monitor table has now been extended to display filters for all filter groups.
P59. CHANGED The default size for the object cache is now 2000 KB (it was previously 1000 KB).
P60. ERROR When the C/SERVER lost the connection to a client while a server dialog was displayed, the event log could be filled with hundreds of messages. This has been corrected.
P61. ERROR A GP fault could occur when a filter of a Text or Code field was assigned a value longer than the defined field length. In a client/server installation, the GP fault occurred on the server. This has been corrected.
P62. NEW When an OCX exception error is provoked, the text contents of the exception are displayed.
P63. NEW You can only see the AboutBox for a OCX control if you have a design time license for that control.
P64. NEW C/OCX now supports licensed OCX controls.
P65. NEW The property "Version" on OCX controls has been removed. The type library version is now chosen from the registry.
P66. ERROR The C/AL function CLEAR did not work on OCX variables. It is now possible to "clear" an OCX variable.
P67. ERROR The Symbol Menu did not show properties implemented as functions under the Properties category, but showed them instead under the Functions category. OCX properties implemented as functions now appear as one property (each) under the Properties category on the Symbol Menu.
P68. ERROR All OCX internal methods ("addref","release", and so on) were shown in the Symbol Menu. These methods have now been removed from the Symbol Menu.
P69. ERROR It was not possible to import OCX controls with a name longer than 38 characters. This has been corrected.
P70. ERROR When a property was implemented as two functions, it was only possible to call one of them. This has been corrected.
P71. ERROR Using a 250-character text as a BSTR argument provoked an internal error. This has been corrected.
P72. ERROR A method or a property that returned LVal (S32) did not always return the right value. This has been corrected.
P73. ERROR When an OCX method or property returned a BSTR, it did not return the right value. This has been corrected. The BSTR must always be in UNICODE.
IDE CHANGES TO 1.30 BETA 3
P74. ERROR Navision Financials would generate a GP fault if the disk containing the temporary directory was full. It now properly reports: "There is no more available space on the disk/diskette."
P75. ERROR The temporary files related to the Meta Font were not put in the directory specified by the TempFilePath option. This has now been corrected.
P76. CHANGE The Print Progress dialog now uses two full lines of text for displaying the printer name.
P77. CHANGE Drop-down lists are now closed immediately when the user starts typing.
P78. ERROR Executing a dataport several times in succession in a loop - for example, from a codeunit - resulted in poor performance. Performance in this situation has been improved.
3.2 Application Changes
A1. When the Implement Item Price Change batch job (793) was used for correcting prices, the General Business Posting Group was not set. This has been corrected with a new field in the Item Price Change table (40).
A2. The decimal places in the Qty. (Calculated) and Qty. (Phys. Inventory) fields in the Item Journal Line table (83) and Phys. Inventory Ledger Entry table (281) have been changed from 2:2 to 0:5.
A3. In the batch job Calculate Quantity on Hand (790), the number of locations per item was limited. This has been changed. A new table, Quantity on Hand Buffer (307), has been created to make this possible.
A4. The caption on tables 222 and 224 and on forms 300, 301, 368 and 369 has been changed from: <Cust. No.> <Address .Name> <Address.Code> to: <Cust. No.> <Cust. Name> <Address.Code> <Address .Name>.
A5. All DateFormula fields and variables have been given type Code[20]. Controls have been adjusted accordingly.
A6. An error message has been added to the journal posting functions to tell the user that the length of a batch name is limited. The error message has been added to the following codeunits:
Codeunit 13 Gen. Jnl.-Post Batch Codeunit 23 Item Jnl.-Post Batch Codeunit 33 BOM Jnl.-Post Batch Codeunit 203 Job Jnl.-Post Batch Codeunit 213 Res. Jnl.-Post Batch
A7. When entries were deleted from tables 7, 15, 27 and 56, the related extended text was not deleted. This has been corrected.
A8. NEW New functionality for managing numbering across all application areas has been implemented. The main features are:
Longer document numbers. All base tables can be numbered automatically. Subsequent number series that each start on a certain date. Multiple number series available for numbering items in the same table. Report that shows whether document numbers have been entered in the order of their posting dates. The same number series can be used in different application areas. Empty documents are created to document gaps in number series. Both temporary and final document numbers can be used. Reports for auditing purposes are available.
A9. When the Post Batch function on purchase invoices (or orders) was run, there was the option of replacing the posting date. If this option was used, the posting routine would not only change the posting date but also run the trigger code for the Posting Date field and thereby change the Document Date. This has been changed in codeunit Purch.-Post (90) so that the Document Date is no longer replaced.
A10. In the Bank Acc. Reconciliation Line table (274), a field called Check No. has been added to the Reconciliation Line.
A11. When checks were printed using the One Check per Vendor function from lines with Applies-to ID <> , the Check report caused an error message to appear that was difficult to understand. This message has been changed.
When checks were printed using the One Check per Vendor function, the Description on the Bank Account Ledger Entry window was the name of the bank account. The Description now contains the account type and account number. A new test has been added and the description calculation has been changed.
A12. When Costing Method was set to Standard on the Item card, the Indirect Cost % was automatically set to zero. But it was possible to change the Indirect Cost % field again later. This has been changed so that the UpdateUnitCost function will be activated with the validation of Indirect Cost % and will automatically set Indirect Cost % to zero.
A13. The batch job Adjust Item Costs/Prices (794) had an empty header section. This section was not needed, so it has been deleted.
A14. In tables 256, 258, 259, 260 and 263 and in forms 308, 309, 310 and 317 the name of the Text field has been changed to Description.
A15. A new function has been added in the G/L Account table (15). This function opens the G/L Account and checks if the Account Type is "Posting." If it is not, an error message appears. This function is performed when data is entered and when entries are posted.
The function also checks if the Blocked field has been activated.
This new function also checks if Direct Posting has been activated.
The new function is activated on all editable fields/controls with TableRelation to the G/L Account table (15).
A16. In the Customer - Detail Trial Bal. report (104), the name of the Include All Customers with a Balance field has been changed to Include Customers That Have a Balance Only.
In Vendor - Detail Trial Balance report (304) the name of the Include Vendors with Balances field has been changed to Include Vendors That Have a Balance Only.
In Bank Acc. - Detail Trial Bal. report (1404) the caption "Include all bank accounts that have a balance" has been changed to "Include Bank Accounts That Have a Balance Only."
A17. In the General Journal - Test report (2), the error message "Navision Financials cannot find the %1 currency" has been changed to "The currency %1 cannot be found."
In the Delete Invoiced Sales Orders batch job (299), the message "Processing Sales Orders#1##########" has been changed to "Processing sale orders."
In the Delete Invoiced Purch. Orders (499) The message "Processing Purch Orders#1##########" has been changed to "Processing purch. orders."
A18. The text "Credit Memo" on the menu button on the Sales Header was too long to be seen. It has been changed from "Credit Memo" to "Cr. Memo" in forms 44, 52, 134, 140.
A19. In the batch jobs Import Consolidation from DB (90) and Import Consolidation from File (92), the C/AL code has been modified so that it allows the Description field on the general journal line to contain only the permitted number of characters. If the description is too long for the field, the description will consist of only the first 30 characters (max. length) and the rest will be truncated.
A20. The following changes have been made because of GUI Guide regulations:
On the G/L Registers form (116), the tablebox has been moved, the buttons have been moved and the width of the form has been changed to 13530.
On the Posted Purchase Credit Memo form (140), the Applies-to Doc. Type and Applies-to Doc. No. fields have been moved to the Invoicing tab. The form has been changed to 8800 in height.
On the Resource Journal form (207), the distance to the left edge of the form has been changed from 1.1 mm to 2.2 mm. On the Resource Capacity form (213,) the Prices button has been changed from 23.1 mm to 22 mm in width. On forms 289, 290 and 311, the height is now the same as the height of the G/L Journal form (39).
A21. In the Contact table (5002), the name of the Job Responsibility field (14) has been changed to Job Responsibility Code.
A22. In codeunits 22, 201, 202, 211 and 212, a validity check during posting on the General Posting Setup has been included. The same validity check has been implemented in the test reports 702,1102 and 1202.
A23. The existing Accounting Setup window has been split up and distributed to the various application areas, and the Accounting Setup window has been renamed General Ledger Setup.
A24. In codeunit 80 and 90 "bal. Account" has been changed to "bal. account" in the status indicator window that shows posting progress.
A25. Non-editable journal batch forms (General Journal Batch List, and so on) have been deleted. The buttons from the non-editable journal batch forms have been moved to the editable journal batch forms (General Journal Batches, and so on) on forms 252, 263, 266, 273, 277, 294, 321 and 328.
The modify button has been removed from all non-editable journal template forms (Item Journal Template List, and so on).
Template menu buttons with batch menu items have been added to the journal template forms (General Journal Templates, and so on). It is therefore now possible to set up both templates and batches from the setup in the main menu. This is also the only way to edit batches without being in lookup-mode.
The special non-editable forms for Source Code and Reason Code have been deleted.
A26. In batch jobs Import Consolidation from DB (90) and Import Consolidation from File (92), the field for amount size has been expanded from 13 bytes to 20 bytes equal to 9,999,999,999,999.99.
A27. The General Journal - Test report(2) and codeunit Gen. Jnl.-Post Batch (13) have been changed so that "Force Doc. No. Balance" now means that lines in the general journal must balance per Document Type and per Document No. (previously, they only had to balance per Document No.).
The name of the Force Doc. No. Balance field, in the Gen. Journal Template table(80), has been changed to Force Doc. Balance in order to reflect the change.
A28. The following changes have been made because the same access key must not be used twice on the same menu:
On the General Ledger menu form (332): Bank Account Ledger changed to Bank &Account Ledger and Delete Check Ledger changed to Delete Check &Ledger
On the Job menu form (337): Job Budget Entries changed to Job &Budget Entries.
A29. In the Gen. Journal Line table (81), when Bal. Account Type is changed, nothing happens to the Balance field and therefore it appears that everything is still in balance, but it is not. This has been changed so OnValidate for Bal. Account Type and Account Type will activate Validate for Bal. Account No. and Account No. instead of just blanking it.
A30. In the Contact Management Setup table (5007), the name of the Follow-up Date Formula field has been changed to Follow-up Date Calculation.
A31. The Gen. Bus. Posting Gr. (Price) field was missing in the Item Price Change table (40). The field has been added. The field is needed when Prices Incl. VAT is used. The field will be used in the batch jobs Implement Item Price Change (793), Suggest Item Price Chg. (Item) (791) and Suggest Item Price Chg.(Price) (792)
A32. The "Division by Zero" error in the batch jobs Suggest Item Price Chg. (Item) (791) and Suggest Item Price Chg.(Price) (792) has been fixed, and a function has been added that tests if the "exchange rate" is different than zero.
A33. The codeunit BOM Calculate Cost (54) finds the resource cost price in the Resource table, but in other situations, the cost price is returned by activating codeunit Resource - Find Cost (220). This can result in a difference in the total BOM cost price as compared to the Item card and the invoice.
In the codeunit BOM Calculate Cost (54), the function UpdateUnitCost has been changed so that Resource Unit Cost will be retrieved by codeunit 220.
A34. The wrong key has been used on the Item Card/Item/Where-Used List. According to the filter, it should be Type, No. On the Item Card form (30) and the Item List form (31), the property RunFormView on the menu item Where-Used List has been changed to SORTING(Type,No.).
A35. The batch job Adjust Item Costs/Prices (794) adjusted the Average Cost even though the Costing Method was set equal to Average and there were item ledger entries. This could cause incorrect inventory values. This has been corrected.
The Adjust Item Cost/Prices batch job has been changed to use the same controls as when the fields are changed manually. Tests have also been added to the batch job.
In addition, it will no longer be possible to enter a negative value in the Adjustment Factor field on the request form.
A36. If Profit was set equal to Price-Cost on the item card, and Unit Price and Cost Price (calculated according to Costing Method) were entered, the Profit % field was not cleared/set to 0, if Unit Price was set equal to 0. This has been changed so that the Profit % field will now be set to 0 in the Item table (27) and in the Resource table (156).
A37. Clicking the command button "Alloc. to Dates" on the Job Budget form (212) opened the Job Quantity Allocated form (215). The default setting was always on the first record. This has been changed so it is now on the actual record in the Job Budget form. This change has been carried out by setting the property RunFormOnRec to Yes on the command button "Alloc. to Dates".
A38.
In the batch jobs Post Job Recognition to G/L (1213) and Post Job WIP Value to
G/L (1214), changes have been made to the C/AL code in order to make sure that
the maximum length of the Description field will not exceed the length of the
Description field in the general journal line.
A39. In order to increase the information on the Order Address List form, the Address and Address 2 fields have been added to the forms Ship-to Address List (301) and Order Address List (369). Visible has been set to No.
A40. When a Credit Memo is open (Remaining Amount <> 0), it will now be included in the Suggest Vendor Payment batch job. The Option tab on the request form has been changed so that it will be possible to use vendor priority in the batch job even if the amount available is 0. This is activated by placing a check mark in a new field on the request form.
Use Applies-to ID has been changed to One Line per Vendor. To make it possible to post payments of credit memos, the method of checking the general journal line has been changed so that if Applies-to Doc. Type and Applies-to Doc. No. are used to apply the credit memo, credit memos payments can be posted.
The Suggest Vendor Payment batch job (393) has been changed so that open credit memos and open payments will be included in the payments in the journal line. There is now a new field in which you can place a check mark to activate the variable UsePriority.
A new table, Vendor Ledg. Entry To Pay (317), has been created. The table is used as a temporary table in the Suggest Vendor Payment report (393).
The codeunit Gen. Jnl.-Check Line (11) has been changed so that it is in accordance with the method of checking described above.
A41. The batch job Make Orders (493) changed the lines in the requisition worksheet when creating orders and the following message used to appear: "The worksheet has been posted. The purchase orders have been created." The first sentence has been deleted because the worksheet is never "posted."
A42. When One Line per Vendor is activated in the batch job Suggest Vendor Payments (393) and One Check per Vendor and Document No. is activated in the Check report (1401), the error message that appears has been improved.
A43. The Inventory - Sales Back Orders report (718) prints item descriptions from the sales line Description field. In order to avoid affecting the description of this item in the report, if a user changes the description on a sales line, the SourceExpr on the control in the SalesLine Footer(2) has been changed from "Description" to "Item.Description."
A44. In the Resource table (156) MODIFYALL, is used instead of the previously used code in order to improve performance when the Resource Group No. is changed on a resource. The window with the progress indicator has been removed.
A45. Limitations on which fields on the Sales/Purchase Headers can and cannot be changed have been implemented. The test of the fields for sales headers is similar to the test of the fields for purchase headers and to the test of the fields for quotes, orders, invoices and credit memos.
A46. Document type has been added to the caption of the Sales List form (45) and the Purchase List form (53), so it now is possible to see whether the list forms for sales and purchases show quotes, orders, invoices or credit memos.
A47. The field names on Sales/ Purchase headers have been changed in order to make them more consistent. In purchase tables (38, 120, 122, 124), "Pay-to" has been added to the Name field, the Address field, and so on. In sales tables (36, 110, 112, 114), "Sell-to" has been added to the Name field, the Address field, and so on.
The following forms, reports and codeunits are affected: Forms 41, 42, 43, 44, 45, 49, 50, 51, 52, 53, 130, 132, 134, 136, 138, 140, 142, 143, 144, 145, 146, 147. Reports 708, 709. Codeunit 365.
A48. The name of the "Create Combined Shipment" batch job (295) has been changed to "Combine Shipments."
A49. In the tables Sales Line (37) and Purchase Line (39), the property has been changed to Editable=No in the Attached to Line No field. This has been corrected because it was possible to change the Attached-to Line No. manually when the field was put on a form.
A50. Use of the Grace Period field in the Finance Charge Terms table (5) has been changed. Grace Period is now used only for the first Finance Charge Memo and not also in between subsequent Finance Charge Memos.
On the Reminder form (434), in the Reminder Level field (28) the property has been changed to Editable=No. Two new batch jobs, Update Reminder Text (187) and Update Finance Charge Text (186), have been added in order to improve upon the previously manual method of updating beginning and ending text. On the Option tab in the batch job Update Reminder Text, users must specify from which level they want the text to be updated.
A51. In CodeUnits Sales-Quote to Order (83) and Purch.-Quote to Order (93), C/AL code has been changed so date fields will not be changed when the Make Order function on a Quote is used.
A52. On the Reminder Lines form (435), the property has been changed to Editable=Yes on the Reminder Level control.
A53. In codeunits Reminder-Issue (393) and FinChrgMemo-Issue (395), a "Nothing to issue" test has been added that is used when reminders and finance charge memos are issued. The test checks that Interest Amount, Additional Fee or Remaining Amount are different than zero.
A54. In the Issued Reminder Header table (297), when the AssistButton was used in the Reminder Terms Code field, the Finance Charge Terms window appeared. This has been corrected so that the Reminder Terms window now appears.
A55. On the Purchase Order form (50) on the Invoicing tab, the information in the Pay-to Vendor No. field was used in the Order report (405), but on the printed order the text was "Bill-from Vendor No." This inconsistency has been corrected. The Order report (405) has been changed as follows:
Bill-from Address -> Payment Details Bill-from Vendor No. -> Vendor No.
A56. Demonstration data has been changed in the various application areas to reflect new and changed functionality.
A57. In the Batch Post Sales Orders (296) on the Option tab, two fields have been renamed:
Ship on Next Post -> Ship Invoice on Next Post -> Invoice
In the Batch Post Purchase Orders (496) on the Option tab two fields have been renamed:
Receive on Next Post -> Receive Invoice on Next Post -> Invoice
A58. On the two batch jobs Create Reminders (188) and Suggest Reminder Lines (189), the name of the Only Entries with Overdue Balances field has been changed to Only Entries with Overdue Amounts.
A59. The name of the codeunit PuchJnlManagement (330) has been changed to ReqJnlManagement.
A60. The batch job Post Recognition to G/L. (1213) has been changed to Post Job Recognition to G/L.
A61. Several things have been changed in relation to the Gen. Jnl. Allocation table (221), the Allocations form (284) and the Recurring General Journal form (283): A61.1 The non-editable Allocation List form (285) has been deleted. A61.2 When drill down is used from the Allocated Amt. (LCY) field in the Recurring General Journal form, the (editable) Allocations form is now shown. A61.3 The name of the Allocation Amt. (LCY) field in the Gen. Jnl. Allocation table (221) has been changed to Amount because everything in this table is related to LCY (that is, Amount as well as VAT Amount). LCY was also misleading because there are no fields without LCY. A61.4 A new FlowField, Account Name, has been added to the Gen. Jnl. Allocation table (221). The new field is used on the Allocations form (284). A61.5 A DataCaption has been added to the Allocations form (284) to make it look more like the journal forms. A61.6 The code to update allocations has been modified so that if Allocation Quantity is specified, this - instead of Allocation % - is used to control the exact value in the Amount field. A61.7 The codeunit Allocation-CalcVAT (360) has been deleted, and the code has been moved to the Gen. Jnl. Allocation table (221).
A62. A change has been made in the Gen. Journal Line table (81) and it is now checked that Direct Posting to a G/L Account is TRUE only when the validation code for the Account No. and Bal. Account No. is run directly from a general journal form.
A63. Different amounts were used in the Intrastat Journal depending on whether the item was bought for use on a job. If it was an ordinary purchase, the cost amount was used, but if the purchase was related to a Job, the Total Price from the Job Ledger Entry was used. This has been changed so Total Cost will now be used when the Type is Usage and Total Price will be used when the Type is Sale. C/AL code has been corrected in the batch job Get Item Ledger Entries (594).
A64. A problem with the lookup function in Batch Name in journal forms has been corrected.
A65. On a Sales Line, Purchase Line, Reminder Line or Finance Charge Memo Line you can post using the type Account (G/L). When the line is posted, the System-Created Entry field on the G/L entry will now be set to "No."
When posting from a General Journal Line when the Account No. or the Bal. Account No. is a Bank Account, "System-Created Entry" will be set to "Yes" on the G/L entry.
A66. The Direct Posting field has been added on the report Chart of Accounts (1) and the form Chart of Accounts (16).
A67. In the Sales Header table (36) the name of the Ship on Next Post field has been changed to Ship and the name of the Invoice on Next Post field has been changed to Invoice. In the Purchase Header table (38) the name of the Receive on Next Post field has been changed to Receive and the name of the Invoice on Next Post field has been changed to Invoice.
A68. If you change Reason Code in a batch, this will now automatically change the Reason Code field in the attached journal lines.
A69. In the batch job Create Recurring Activity, (5087) incorrect input of values was handled differently depending on where the incorrect input was entered. This has now been changed so incorrect values are always handled consistently, which means that you can accept the message and try again.
A70. Terminology change in Report 1209 Job - Actual to Budget "can not" has been changed to "cannot."
A71. The purpose of the Direct Posting field in the G/L Account table (15) has been expanded. Now the Direct Posting field will be checked when entries are posted directly to G/L accounts from the Sales and Receivables and Purchases and Payables application areas. When entries are posted on a closing date, however, the Direct Posting field is not checked. This change affects tables 37, 39, 81 and codeunit 12.
A72.NEW The Fixed Assets application area has been implemented.
A73. The Purch.-Calc.Discount codeunit (71) has been divided into two objects on the same way that Sales-Calc. Discount (60) is divided. As a result, it is now possible to activate the function without the dialog.
A74. The Document No. incrementing functionality in the general journals has been corrected. Previously, it was possible for the document number on the last number not to be incremented when it should have been. The change has been implemented in forms 39, 253, 254, 255, 256 and 286.
A75. Now, when entries are posted to a bank account in a general journal, the bank account's G/L account is included in the Reconciliation form (345) and in the General Journal - Test report (2).
A76. The reports 204, 205, 404 and 405 have been changed so order lines will be generated in the same way as they are generated on invoice lines. In other words, calculated as Amount excl. VAT (Total) + Invoice Discount.
A77. In forms 79, 98, 242 and 5007 where the content of tables is shown with only one record the code has been corrected.
A78. When selecting Post and Print in journals, the codeunit had not set the correct filter at the end of the function. This has been corrected in codeunits 232, 242, 252, 272 and 282.
A80. The batch jobs Copy Sales Document (292) and Copy Purchase Document (492) replace the codeunits Sales-Copy Lines (62), Purch.-Copy Lines (72), Sales-Invoice to Credit Memo (380) and Purch-Invoice to Credit Memo (381). The replacement has been done in order to use the new functionality for numbering of journals and documents.
APP CHANGES TO 1.30 BETA 2
A81. On the Prospect - Profile report (5000) the label "Territory Code" has been changed to be not bold in order to conform with the GUI Guide.
A82. The Activity Due form (5022) opened with "Today" as "Due Date". It should be opened with "Work Date" as "Due Date", as explained in the manual "Contact Management", so TODAY has been changed to WORKDATE in the OnOpen trigger in the form.
A83. On forms 40, 201, 207, 253, 255 and 256, the field External Document No. has been added as a hidden field.
A84. It should not be possible to post documents when the Gen. Bus. Posting Group field for the customer/vendor is blank. So now codeunits 80 and 90 check that there is a value in the Gen. Bus. Posting Group field for customer/vendor, when a Sell-to Customer No./Buy-from Vendor No. is entered on a sales/purchase header.
A85. Preparation for Mail Integration to Microsoft Exchange A button with a new bitmap has been placed on all card forms with the field E-Mail. The following forms have been modified in this way: Form 1 Company Information Form 21 Customer Card Form 26 Vendor Card Form 300 Ship-to Address Form 368 Order Address Form 370 Bank Account Card Form 423 Customer Bank Account Card Form 425 Vendor Bank Account Card Form 5001 Prospect Card Form 5004 Contact Card Form 5200 Employee Card Form 5203 Alternative Address Card The button activates a new codeunit, Mail (397).
A86. In several objects, activation of the TESTFIELD function on boolean fields has been corrected so that messages of the form "Open must not be No." are avoided.
A87. An optimization (for speed) in the Transfer Extended Text codeunit (378) caused sales and purchase forms to be not always updated correctly. This has been corrected.
A88. The comment line tables and forms have been modified so that when the first new line is entered in a comment for a record (G/L Account, Bank Account, Customer, ...), the program suggests the work date in the Date field. The DelayedInsert=Yes property has been set on comment forms where it was not set already.
The following forms have been modified: Table 43 Purch. Comment Line Table 44 Sales Comment Line Table 97 Comment Line Table 299 Reminder Comment Line Table 306 Fin. Charge Comment Line Table 5006 Cont. Mgt. Comment Line Table 5208 Human Resource Comment Line Form 66 Purch. Comment Sheet Form 67 Sales Comment Sheet Form 124 Comment Sheet Form 442 Reminder Comment Sheet Form 454 Fin. Charge Comment Sheet Form 5011 Contact Mgt. Comment Sheet Form 5222 Human Resource Comment Sheet
A89. If you import prospects with the help of the Import/Export Prospects dataport (5000), you can update the data for the existing prospects and contacts. This should only be possible if the field "Allow External Update" is set to Yes. The program mistakenly allowed updates no matter what the field was set to. This has been corrected.
A90. In tables like the Gen. Journal Template table (80), where a change in the Source Code field made it necessary for the program to modify the Source Code field in related general journal lines, the code has been modified. Now the Gen. Journal Template record is modified as part of the same transaction as one in which the lines are modified.
A91. The special code to update the subform in the Reminder (434) and Finance Charge Memo (446) (as well as some code in the related Reminder Lines (435) and Finance Charge Memo Lines (447) forms) has been removed because C/SIDE now handles validation code involving transactions better.
A92. Caption was not set on the Phys. Inventory Journal (392). This has been corrected.
A93. The totals were wrong on the Status report (706). This has been corrected.
A94. In the Sales Order (42) and Purchase Order (50) forms, the Shipments/Receipts and Invoices menu items have been changed so that they open list forms, which now contain buttons.
A95. When G/L accounts are created with the account type Posting, the Direct Posting field will by default be set to Yes. Other account types will be set to No.
A96. The drill-down function has been removed from forms Misc. Articles Overview (5228) and Confidential Info. Overview (5229).
A97. In the Post Inventory Cost to G/L report (1002), an error message has been improved.
A98. Errors in lookup code for the journal batch name have been corrected. Corrections have been made in codeunits 240, 250, 270, 280.
A99. The label "Journal Template Name" was too short in Inventory Posting - Test report (702). It has been made longer.
A100. The menu item Compress Entries, on the Job Quantity Allocated form (215), was not removed when the report object was changed. This has been corrected. The menu item is deleted. Now the Date Compress Job Budget Entries report can be activated from the main menu: Job, Periodic Activities, Data Compression, Job Budget Entries.
A101. The Date Compress Job Ledger report (1298) did not summarize Total Price. This has been corrected. Total Price is now handled in the same way as Total Cost.
A102. If you bought the Requisition Management granule and did not have access to the Alternative Vendors granule, you got an error caused by the code in the Requisition Line table (246). This has been corrected in the Requisition Line table.
A103. When you chose Planning, Resource Availability on the Resource Allocated per Job form (221) or Planning, Resource Group Availability on the Res. Gr. Allocated per Job form (228), the record that opened in the Resource Availability form was not always the one on which the filter had been set in form 221 or 228. This has been corrected.
A104. In sales lines it is now possible to change "Allow Invoice Disc." when the Type field is blank and the No. field contains a standard text code.
A105. If an item description is translated in the Item Translation table, the description will be inserted in a sales line in a language corresponding to the language code of the customer.
A106. The Reminder (117), Reminder - Test (122), Finance Charge Memo (118) and Finance Charge Memo - Test (123) reports have been changed, so that now all text lines (in a reminder/finance charge memo) that are separated from the other lines by a blank line will be printed after the totals.
A107. It is now possible to insert sales quotes in the report selections.
A108. In the Req. Worksheet Templates form (293), the field "Request Worksheet Names" has been changed to "Req. Worksheet Names".
A109. The LookupFormID and DrillDownFormID properties have been set on the Misc. Article Information table (5214). The Serial No. field has been added to the Misc. Article Information form (5219) and the Employee - Misc. Article Info. Report (5202).
APP CHANGES TO 1.30 BETA 3
A110. Common address and fax number fields have been added to the Union table (5209), so all ordinary address fields are now included.
A111. An error message has been corrected in the BOM Journal - Test (802) report.
A112. The Document-Print codeunit (229) has been changed so that when you print a quote or an order, the printing is done modally. In this way, all the information - in particular, the No. Printed field - in the quote or order form is updated after printing.
A113. In Sales & Receivables, Setup, Report Selection, it is now possible to insert sales quotes.
A114. In the Prospect Profile report (5000), the Comment field was not long enough. It has now been expanded so that the full comment text can be printed.
A115. When the Import/Export Prospect dataport (5000) was activated, the Picture field was superfluous, and the field could not be in the dataport in C/SIDE version 1.30. The field has now been deleted.
A116. Two new fields, Currency Code and Exchange Rate, have been added to the Requisition Line table (246). The fields have been added to the Req. Worksheet form (291) and the Recurring Req. Worksheet form (296). The new fields are filled in when the item on the line is from a vendor using foreign currency.
A117. The value of the Currency Code field is checked in the Req. Wksh.- Make Order codeunit (333).
A118. A table relation to the Vendor table has been added to the Vendor No. field in the Requisition Line table (246) so that the Search Name function (and other common functions) can be used in this field.
A119. The field validation code in the Requisition Line table (246), as well as in the Purchase Line table (39), has been corrected so that no matter what currency is specified in the Item Vendor table (99), the program will translate the Direct Unit Cost to the required currency on the line.
