wiki.dynamicsbook: Changes Made in Navision Attain 3.01B

[Blog bot]

Summary: Uploaded



== Overview ==

This document describes the changes between Navision Attain 3.01.A and Navision Attain 3.01.B.

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

== Application Changes ==

=== General Changes ===

==== Issues ====

'''A1) OrderManagement'''
Issue
An object was not used, which caused some confusion. The object has been deleted.
In response to this issue, a change has been implemented.

'''A2) Calculate Planning Route Line'''
Issue
In the Calculate Planning Route Line (99000810) codeunit, important loops for the manufacturing planning batch job changed the values in the current key in the body of the loop, thereby forcing the client to ask for a new set of records on SQL Server when the next statement in the loop was executed. This has been corrected.

In the Calculate Planning Route Line (99000810) codeunit, important loops for the manufacturing planning batch job read more calendar entries than was needed to calculate the ending and starting times in routing lines. This has been changed.
In response to this issue, a change has been implemented.

'''A3) WHILE FIND loops.'''
Issue
There were several loops written in a way that gave non-optimal performance on SQL Server:

<PRE>
WHILE FIND('-/+/>/<')/NEXT <> 0 DO
</PRE>

These loops have been rewritten using the normal pattern, which is optimized for SQL Server:

<PRE>
IF FIND('-') THEN
REPEAT
UNTIL NEXT = 0;
</PRE>

In response to this issue, a change has been implemented.
*Table 36 Sales Header
*Table 38 Purchase Header
*Table 5744 Transfer Shipment Header
*Table 5746 Transfer Receipt Header
*Table 5772 Posted Whse. Activity Header
*Form 498 Reservation
*Codeunit 86 Sales-Quote to Order
*Codeunit 96 Purch.-Quote to Order
*Codeunit 363 PostSalesLines-Delete
*Codeunit 364 PostPurchLines-Delete
*Codeunit 5895 Inventory Adjustment
*Codeunit 99000845 Reservation Management

'''A4) Key usage in the Carry Out Action Msg. - Plan. batch job'''
Issue
To increase performance, SETCURRENTKEY has been added in 3 places of Report 99001020 Carry Out Action Msg. - Plan.
In response to this issue, a change has been implemented.

'''A5) Keys in the Default Dimension table'''
Issue
The key ”Value Posting” has been deleted and it is no longer used.

The old key(s) was not able to filter records from the table efficiently, so the more records in this table, the worse the performance would be when using this key.
In response to this issue, a change has been implemented.
*Table 352 Default Dimension
*Codeunit 408 DimensionManagement

'''A6) Keys in the Warehouse Request table'''
Issue
1. The key ”Type, Location Code, Source Type, Source Subtype, Source No.” was not efficient when filtering warehouse requests for a sales order (or purchase order) on SQL Server. New keys ” Source Type, Source Subtype, Source No.” and ”Source Type, Source No.” have been added, and in some places of the code we now refer to the new key, for example when deleting warehouse requests for a sales order during posting.

The old key(s) was not able to filter records from the table efficiently, so the more records in this table, the worse the performance would be when using this key.

2. When a warehouse request was deleted, no proper key was selected for deleting warehouse activity lines.
In response to this issue, a change has been implemented.
*Table 5765 Warehouse Request
*Codeunit 80 Sales-Post
*Codeunit 90 Purch.-Post
*Codeunit 5771 Whse.-Sales Release
*Codeunit 5772 Whse.-Purch. Release
*Codeunit 5773 Whse.-Transfer Release

'''A7) Keys in the Sales Line and Purchase Line tables'''
Issue
The following keys in table 37 Sales Line and table 39 Purchase Line were not efficient when filtering sales and purchase lines for both Orders and Return Orders in the same query on SQL Server:
*Table 37 Sales Line:
**Document Type, Type, No., Variant Code, Drop Shipment, Location Code, Bin Code, Shipment Date
*Table 39 Purchase Line
**Document Type, Type, No., Variant Code, Drop Shipment, Location Code, Bin Code, Expected Receipt Date

The following new efficient keys have been added to table 37 Sales Line and table 39 Purchase Line, and in some places of the code we now refer to the new keys (when Document Type is not filtered to a single specific value):
*Table 37 Sales Line:
**Type, No., Variant Code, Drop Shipment, Location Code, Bin Code, Document Type, Shipment Date
*Table 39 Purchase Line
**Type, No., Variant Code, Drop Shipment, Location Code, Bin Code, Document Type, Expected Receipt Date
In response to this issue, a change has been implemented.
*Table 37 Sales Line
*Table 39 Purchase Line
*Table 27 Item
*Table 156 Resource
*Codeunit 5790 Available to Promise
*Codeunit 99000854 Inventory Profile Offsetting

'''A8) Keys in the Prod. Order Line and Prod. Order Component tables'''
Issue
The following keys in table 5406 Prod. Order Line and table 5407 Prod. Order Component were not efficient when filtering production order lines and components on different statuses of production orders:
*Table 5406 Prod. Order Line:
**Status, Item No., Variant Code, Location Code, Bin Code, Ending Date
**Status, Item No., Variant Code, Location Code, Bin Code, Due Date
*Table 5407 Prod. Order Component:
**Status, Item No., Variant Code, Location Code, Bin Code, Due Date

The MaintainSIFTIndex property has been set to No for these keys, because it is not efficient to calculate sums with these keys on SQL Server when the Status field is not filtered to one specific value.

The following new efficient keys have been added to table 5406 Prod. Order Line and table 5407 Prod. Order Component, and in some places of the code we now refer to the new keys (when Status is used for a range or OR-filters):
*Table 5406 Prod. Order Line:
**Item No., Variant Code, Location Code, Bin Code, Status, Ending Date
**Item No., Variant Code, Location Code, Bin Code, Status, Due Date
*Table 5407 Prod. Order Component:
**Item No., Variant Code, Location Code, Bin Code, Status, Due Date

The following keys were deleted from table the 5406 Prod. Order Line and table 5407 Prod. Order Component, because other keys on these tables can serve the same purpose:
*Table 5406 Prod. Order Line:
**Item No.
*Table 5407 Prod. Order Component:
**Status, Item No., Variant Code, Location Code, Bin Code, Due Date
In response to this issue, a change has been implemented.
*Table 5406 Prod. Order Line
*Table 5407 Prod. Order Component
*Table 27 Item
*Form 353 Item Availability Lines
*Form 515 Item Avail. by Location Lines
*Form 5415 Item Avail. by Variant Lines
*Form 99000902 Item Availability Line List
*Report 99000766 Prod. Order - Picking List
*Report 99000788 Prod. Order - Shortage List
*Codeunit 5790 Available to Promise
*Codeunit 99000854 Inventory Profile Offsetting

'''A9) Keys in the Prod. Order Component table'''
Issue
The following key in table 5407 Prod. Order Component was not efficient when filtering production components with different flushing method on SQL-server:
*Flushing Method, Routing Link Code
This key was replaced with the following new efficient key, and in all the places of the code we now refer to the new key:
*Status, Prod. Order No., Routing Link Code, Flushing Method
In response to this issue, a change has been implemented.
*Table 5407 Prod. Order Component
*Codeunit 99000781 Output Jnl.-Post Line
*Codeunit 99000788 Prod. Order Status Management

'''A10) Keys in the Prod. Order Capacity Need table'''
Issue
The following keys in table 99000793 Prod. Order Capacity Need were not efficient when filtering on production order status on SQL-server:
*Status, Type, No., Starting Date-Time, Ending Date-Time, Active
*Status, Type, No., Ending Date-Time, Starting Date-Time, Active
These keys were replaced with the following new efficient keys, and in all the places in the code we now refer to the new keys:
*Type, No., Starting Date-Time, Ending Date-Time, Active
*Type, No., Ending Date-Time, Starting Date-Time, Active
In response to this issue, a change has been implemented.
*Table 99000793 Prod. Order Capacity Need
*Form 99000817 Prod. Order Routing
*Form 99000890 Machine Center Load Lines
*Codeunit 99000774 Calculate Routing Line
*Codeunit 99000810 Calculate Planning Route Line

'''A11) Keys in the Reservation Entry table'''
Issue
The following key in Table 337 Reservation Entry was not efficient when filtering reservation entries with different reservation statuses on SQL-server:
o Reservation Status, Item No., Variant Code, Location Code, Bin Code, Source Type, Source Subtype, Expected Receipt Date
The following new efficient key has been added to Table 337, and in some places of the code we now refer to the new key (when Reservation Status is used for a range or OR-filters):
o Item No., Variant Code, Location Code, Bin Code, Source Type, Source Subtype, Reservation Status, Expected Receipt Date
In response to this issue, a change has been implemented.
*Table 337 Reservation Entry
*Table 27 Item
*Codeunit 99000845 Reservation Management

=== General Ledger ===

==== Errors fixed ====

'''A12) Close Income Statement - Database Inconsistency'''
Error
When posting the final entry on retained earnings account, the Gen. Journal Line was initialized wrongly, dependent on the previous (i.e. last) G/L entry.
This has been corrected.
*Report 94

Internal Workbase reference: 08B6F852A32D73E2C1256AB8004AE835

'''A13) Inconsistency with Line Discount'''
Error
An inconsistency error occurred when posting small line- and invoice discount amounts in additional currency.
This has been corrected.
*Codeunit 80
*Codeunit 90

Internal Workbase reference: F9C75B5623A1120EC1256AB7003D2534

'''A14) Dimensions were Deleted when Posting Only One Line in General Journals'''
Error
When making several journal lines with dimensions and filtering on the document number so that only one line was posted, the dimensions on the other journal lines disappeared.
This has been corrected.
*Codeunit 13
*Codeunit 23
*Codeunit 33
*Codeunit 203
*Codeunit 213
*Codeunit 5633
*Codeunit 5653
*Codeunit 99000763
*Codeunit 99000782
*Codeunit 99000803

Internal Workbase reference: A83748C492A186A7C1256ABD004DAFE5

'''A15) Pmt. Disc. Given/Rcd. was not shown when Using Adjust for Payment Discount'''
Error
The Pmt. Disc Given and Pmt Disc. Rcd. fields were not filled out on Customer and Vendor Ledger Entries if the program was set up to use the Adjust for Payment Discount feature.
This has been corrected
*Codeunit 12

Internal Workbase reference: F4273E7D8CA7CD7941256AAE003344DD

'''A16) Error Message "Acc Schedule Name 'ANALYSIS' does not exist"'''
Error
If the Account Schedule report (95) was previewed with Acc. Schedule Name ‘ANALYSIS’ and the company was closed down and a new company was made, an error message would appear when trying to get into Account Schedules.
This has been corrected
*Form 104

Internal Workbase reference: E6590D96F8629AEA41256A810037E38E

'''A17) "Currency Factor" Value Not Assigned in Codeunits 80 and 90'''
Error
The error message “Currency Factor must not be 0” appeared, when trying to post a Sales or Purchase Order where the Bal. Account No. field on the header contained a value.
This has been corrected
*Codeunit 80
*Codeunit 90

Internal Workbase reference: F73AF475BFEC8FF541256A7800427E37

'''A18) Concurrency Problem in REP95 Date Compress VAT Ledger Entries'''
Error
An optimistic concurrency problem was sometimes occurring when running Date Compress VAT ledger entries and other Date Compress batch jobs on a SQL database.
This has been corrected
*Report 95
*Report 98
*Report 198
*Report 398
*Report 798
*Report 898
*Report 1198
*Report 1298
*Report 1498
*Report 5696
*Report 5697
*Report 5698

Internal Workbase reference: 716674F40952B7BE41256A690051065A

'''A19) Incorrect Rounding of VAT Entries when ACY Amount Rounding Precision was <> LCY Rounding Precision.'''
Error
If an Additional Reporting Currency (ACY) was set up with amount rounding precision < the LCY, VAT entries would be rounded differently than GL entries, when you used Reverse Charge VAT.
This has been corrected
*Codeunit 12

Internal Workbase reference: 285112669DC96C0041256AA90034AF77

'''A20) Error in General Journals'''
Error
The error appeared when the table 81 Gen. Journal Line validated the "Account No." and the "Bal. Account No."
When the "Account No", "Bal. Account No.” and General Journal Batch had the same Bank Account with the same currency and you wanted to create a new line, an error message appeared.
This has been corrected
*Table 81

Internal Workbase reference: 598718F327170396C1256AD8004032D8

==== Issues ====

=== Sales & Receivables ===

==== Errors fixed ====

'''A21) UOM on Sales Order and Order Promising'''
Error
If the different UOMs on the Item were not the same, the Order Promising would mess up the Unavailable Quantity.
This has been corrected
Correcting different Qty. fields so there is a clear line between Qty. and Qty. (base).

*Codeunit 99000889 AvailabilityManagement

Internal Workbase reference: EE21EC6E329118AB41256A78005296A9
Internal Workbase reference: 7D56951A51DE9DEC41256A7800491B3B

'''A22) Permission and Sales Order'''
Error
Missing permission when making a sales order line.
This has been corrected
*Codeunit 99000832 Sales Line-Reserve

Internal Workbase reference: 28C4DC00FDB6B7A6412569F100343A10

'''A23) The Menu Item Ret. Order - Credit Memo Does Not Work Correctly'''
Error
If you posted a credit memo from the Sales Return Order, you could not see the credit memo from the menu item Ret. Order - Credit Memo.
This has been corrected.
*Table 114 Sales Cr.Memo Header
*Form 6630 Sales Return Order

Internal Workbase reference: 11E7019D3AB47FDB41256AB5005135A8

'''A24) External Document No. was Displayed Twice on the Posted Return Receipt form (6660)'''
Error
External Document No. was displayed twice on Posted Return Receipt form (6660).
This has been corrected.
*Form 6660 Posted Return Receipt

Internal Workbase reference: BFBC0F2260BCA3F341256AAA00582E6D

'''A25) Error Message after Stock-out Warning'''
Error
If the location code on a sales line was changed immediately after a stock-out warning, a system error message was displayed.
This has been corrected
*Table 37 Item

Internal Workbase reference: 40D75E57A630697E41256A67004AC7F3

'''A26) Special Orders and Nonstock Items'''
Error
When a special order was created for a non-stock item, it was impossible to view purchase orders for this item.
This has been corrected
*Form 42 Sales Order
*Form 46 Sales Order Subform

Internal Workbase reference: 81839F5BBC3D4B0641256AA900481051

'''A27) Substitute with a Non-stock Item'''
Error
When an item on a sales order was substituted with a non-stock item, an error message was displayed.
This has been corrected
*Table 5715 Item Substitution
*Codeunit 5701 Item Subst.
*Codeunit 5703 Nonstock Item Management

Internal Workbase reference: 12FC2B9FFF1DC48841256AA9004D6C45

'''A28) Barcode Cross-references'''
Error
It was impossible to set up barcodes as cross-references on sales and purchase orders.
This has been corrected
*Table 37 Sales Line
*Table 39 Purchase Line
*Codeunit 5702 Dist. Integration

Internal Workbase reference: A5BA7414AF9D3BBE41256AAA0042A79D

'''A29) Make Sales Orders from Sales Quotes'''
Error
When a sales order was made from a sales quote, an error message was displayed in certain situations.
This has been corrected
*Codeunit 5790 Available to Promise

Internal Workbase reference: CF63A15D3AA8E5EBC1256ABF004D4445

=== Relationship Management ===

==== Errors fixed ====

'''A30) The Bill-to Customer No. Field on a Sales Quote was Not Updated when Creating a Contact as a Customer.'''
Error
A sales quote can be assigned to an opportunity before the related contact is created as a customer. When the contact was eventually created as a customer, the Bill-to Customer No. field on the sales quote was not updated. Only the Sell-to Customer No. field was updated.
This error has been corrected.
Now both the Bill-to Customer No. and the Sell-to Customer No. fields are updated.
*Table 5092

'''A31) The Create Interaction Wizard Failed When Attachments were Stored in Disk Files.'''
Error
The Create Interaction wizard failed when Disk File was selected in the Attachment Storage Type field. Any changes made to a Microsoft Word document in the Create Interaction wizard were ignored when sending and logging the interaction. This resulted in contacts receiving e-mails without the added information.
This error has been corrected.
*Table 5062
*Codeunit 5054

=== Purchases & Payables ===

==== Errors fixed ====

'''A32) Permission and Purchase Order'''
Error
Missing permission when receiving a purchase order.
This has been corrected
*Codeunit 6513 Item Tracking Mgt. Purch. Line

Internal Workbase reference: 53ACAD0381D7904A41256AB8003DF857

'''A33) The Menu Item Ret. Order - Credit Memo did not Work Correctly'''
Error
If you posted a credit memo from the Purchase Return Order, you could not see the credit memo from the menu item Ret. Order - Credit Memo.
This has been corrected.
*Table 124 Purch. Cr. Memo Hdr.
*Form 6640 Purchase Return Order

Internal Workbase reference: 11E7019D3AB47FDB41256AB5005135A8

'''A34) Property RunFormLink was Incorrectly set in the Purchase Return Form (6640)'''
Error
The property RunFormLink was incorrectly set in the Purchase Return form (6640).
This has been corrected.
*Form 6640 Purchase Return Order

Internal Workbase reference: 2E6128652537530F41256AA8002DA74F

=== Inventory ===

==== Errors fixed ====

'''A35) Get Item Ledger Entries report (594) gave Incorrect Results'''
Error
A filter was set incorrectly in the code of the above-mentioned report.
This has been corrected.
*Report 594 Get Item Ledger Entries

Internal Workbase reference: EEEEBED62F18FC92C1256AB700495953

'''A36) Deletion of an Item Variant failed to delete Item Variant Translation'''
Error
When an item variant was deleted, the item variant translation was not deleted.
This has been corrected.
*Table 5401 Item Variant
*Form 30 Item Card
*Form 5700 Stockkeeping Unit Card

Internal Workbase reference: 7D83CFC9AF4FA48F41256AAA00509DA9

==== Manufacturing ====

=== Errors fixed ===

'''A37) Deleting an Item and the Effect on the Prod. BOM.'''
Error
It was possible to delete an item that was part of the certified Production BOM .
This has been corrected
If an item is part of a Production BOM, then it is impossible to delete it.

*Table 27 Item

Internal Workbase reference: F6673D27311CFDDD41256AAA005C5CA4

'''A38) Item Unit of Measure and Finished Prod Order Ledger Entries'''
Error
The UOM in the Ledger Entries for Finish Production Orders, was copied from the parent item and not from the component. This meant that if the two UOM were not the same, the filter would be set to filter on the UOM for the Parent Item.
This has been corrected
Changed the filter for Field 90 in Tab99000817 to filter on "No." instead of "Item No."

Table 99000817 Fnshd Prod. Order Ledg. Entry
Internal Workbase reference: 806324EFFC55D87541256AA900283B9B

'''A39) Default Safety Lead Time and Refresh on Production Order'''
Error
The production order used the Default Safety Lead Time on the Manufacturing Setup, even though a Safety Lead Time was specified on the Item card.
This has been corrected
*Table 99000791 Production Order

Internal Workbase reference: ADE27256A7C18B0641256A650045EB0C

'''A40) Changing a BOM Exchange Production BOM Item'''
Error
When you used the function to change one item for another, you could create a new version and certify it, but the system just certified the last BOM version.
This has been corrected
*Report 99001043 Exchange Production BOM Item
Internal Workbase reference: 230654D1EA7F4BFD41256AA000313E0A

'''A41) Net Change Planning and Sales Order Shipment Date'''
Error
A changed shipment date on a sales order header was not respected in net change planning. However, if shipment date was only changed in the sales order line, it worked.
This has been corrected
*Table 36 Sales Header

Internal Workbase reference: 416C45468DC8F12E41256A8D002CDFF0

'''A42) Lookup in table 99000826 and table 99000827'''
Error
When using the Lookup button on table 99000826 and 99000827, an error message was displayed.
This has been corrected
*Tables 99000826 and 990008227 are not used anymore, but were not deleted in Navision Attain.

*Tables 99000825 and table 99000827 are deleted.

Internal Workbase reference: FF4ACE365C9B31E241256AAA004EEEC9

'''A43) Unused Table'''
Error
Invt. Value Tracking Entry table (99000845) is no longer used and must be removed from the application.
This has been corrected.
*Table 99000845 Invt. Value Tracking Entry
*Codeunit 119102

Internal Workbase reference: C6311766279F26C7C1256AB8004F482B

=== Cap. Reqts. Planning ===

==== Errors fixed ====

'''A44) Parallel routing and inserting of a new Prod. Order Routing Line.'''
Error
It was not possible to insert a new Prod. Order Routing Line when using parallel routing.
This has been corrected
Table 99000792 Prod. Order Routing Line

Internal Workbase reference: 568462DF896E7C0D412567E700344AA6

'''A45) Error when Using a Continual Shop Calendar'''
Error
Problem: When creating a (firm) planned production order with a continual shop calendar, the field "Starting date-time" in the Routing of the PO was not filled out when refreshing forward. It worked fine when refreshing backward.
This has been corrected
Codeunit 99000774 Calculate Routing Line

Internal Workbase reference: A42DF3FDB92A454F412569ED0040D664

=== Resources ===

==== Errors fixed ====

'''A46) Resource - Price List report (1115) gave Incorrect Results'''
Error
A filter was set incorrectly in the code of the above-mentioned report.
This has been corrected.
Report 1115 Resource - Price List

Internal Workbase reference: EEEEBED62F18FC92C1256AB700495953

== Development Environment and Database Changes ==

=== Navision Server ===

==== Features ====

'''P1) HotCopy Program Available on Unix'''
Feature
The HotCopy program is now available on AIX, HP-UX and Reliant Unix.

'''P2) HotCopy Database Test Functionality'''
Feature
A new argument called dbtest has been added to the HotCopy program. This argument must take one of 3 values: minimum, normal or maximum. The values refer to the following:

minimum : test blobs and primary keys
normal : minimum plus test secondary keys
maximum : normal plus test relationship between primary and secondary keys plus test
field relationships between tables.

The test is performed before the backup is started. If errors occur during testing, the backup is not guaranteed to be consistently backed up. Note that on Unix, version field relationships between tables cannot be performed.
Read more about HotCopy in the “Installation & System Management: Navision Server” manual.
Errors fixed

'''P3) Memory Fault in HotCopy'''
Error
Applying the HotCopy program on a database with two files sometimes resulted in a core dump. This happened if the primary file of the database was used as the first argument of the source parameter, and some nondatabase file as the second argument of the source parameter.
This has been corrected.
Internal Workbase reference: D4B13817252DFCFDC1256ADB00373A4E

'''P4) Safeguard against Corruption of Database'''
Error
In some rare cases, redesigning the database led to corruption of the database. This was caused by a problem in database space allocation.
This has been corrected.
A safeguard mechanism to check for database space allocation problems has been implemented. Transactions that are compromised will be aborted before they lead to corruption of the database.
Internal Workbase reference: 053EA6989CC8AFFEC1256AB00054235E

=== MS SQL Server Option ===

==== Errors fixed ====

'''P5) User Permission Change'''
Error
Users without permission to read a particular table received an error when trying to do so, even if the table was empty. This was different from the way the security system was implemented on Navision Server.
This has been corrected.
The implementation of user permissions has been changed so that all users can now read from an empty table that they don't have permission to. They can only read from the table if it is empty and nothing can be read from it.
Internal Workbase reference: FCF432E4085394C641256AA900309079

'''P6) Client Consumed Too Much Memory for Cursor Cache, Resulting in Poor Performance'''
Error
When opening a database on a client machine with little physical memory, poor performance could have occurred due to use of the memory swap file on the client machine.
This has been corrected.
When opening a database, the available physical memory on the client machine is now used to determine the amount of memory the Attain client program will consume.

The usage is divided internally, depending on available physical memory:

{| class="wikitable" border="1" cellpadding="10" cellspacing="0"
! Usage
! Memory
|-
|Low
|< 100MB
|-
|Medium
|< 224MB
|-
|High
|> 224MB
|}

This means that low specification clients will occupy a relatively low footprint. More capable clients will allow more resources to be used, which will utilize the various performance optimizations built into the product.

There is an upper limit to all of these resources. Continuing to add client memory will not correspondingly improve performance.
Internal Workbase reference: C786C8B90608CA11C1256AD9004A79D4

'''P7) Incorrect Collation Used When Creating a Database'''
Error
Trying to open a database without specifically choosing a collation caused the database to be successfully created with the SQL server’s code page. If discrepancies between the client machine’s and the SQL server’s code pages existed, the database could not be opened due to code page compatibility checking.
This has been corrected.
Now, Navision Attain will choose a collation for a newly created database that is compatible with the client local settings.
Internal Workbase reference: 0965AA9F5BFC6BE741256AA0003A1FF2

'''P8) SIFT Triggers Were Not Updated Properly During Database Conversion from Navision Financials 2.60 to Attain 3.01'''
Error
If the Company name contained a period, the following error message occurred when updating tables with SIFT triggers: "The <table name> table does not exist any longer."
This has been corrected.
Internal Workbase reference: 3985BA90E8056763C1256ADE0040CEA6

'''P9) Setting MaintainSIFTIndex = NO Could Fail to Update SIFT Trigger and SIFT Tables'''
Error
If the last index with SumIndexFields on a table had the property MaintainSIFTIndex changed from YES to NO, the SIFT trigger on the base table was not updated properly and the associated SIFT table was not deleted.
This has been corrected
Internal Workbase reference: 479DABE6FA03C7F1C1256AE9002CCDF8

'''P10) The LinkedObject Table Property Failed to Check for SumIndexFields'''
Error
It was possible to set the table property LinkedObject to YES even if the table had SumIndexFields.
This has been corrected
C/SIDE now checks that there are no indexes with SumIndexFields (and the MaintainSIFTIndex property set to YES) before allowing the LinkedObject property to be changed to YES.
Internal Workbase reference: 0011242F5BB0A280C1256AE8002A7DC4

'''P11) Wrong Error Message when Changing SQL Data Type of a Code Field'''
Error
When changing the SQL Data Type of a code field to a value, which was incompatible with the existing data in the table, an incorrect error message was displayed.
This has been corrected
The proper (SQL Server) error message is now displayed.
Internal Workbase reference: 40599BE47654DB89C1256AE800310D6D

=== Development Environment ===

==== Features ====

'''P10) Field Caption in C/AL Symbol Menu'''
Feature
In the C/AL Symbol Menu window, it is now possible to see both the field name and the field caption in the current application language.

'''P13) Field Caption in the Zoom Window'''
Feature
In the Zoom window, it is now possible to see both the field name field and the field caption in the current application language.

'''P14) Object Caption in the Table List and the Form List'''
Feature
In the Table List window and the Form List window, it is now possible to see both the object name and the object caption in the current application language.

'''P15) Field Caption in the Field Menu'''
Feature
In the Field Menu window, it is now possible to see both the field name and the field caption in the current application language.

'''P16) Field Caption in the Field List'''
Feature
In the Field List window, it is now possible to see both the field name and the field caption in the current application language.

'''P17) Object Caption in the Object List'''
Feature
In the Object List window, it is now possible to see both the object name and the object caption in the current application language.

'''P18) Field Captions in Form and Report Wizards'''
Feature
In the wizards for Forms and for Reports, you now see the caption of the fields in the Available Fields list.

'''P19) Object Caption in the Object Designer'''
Feature
It is now possible to see the object captions in the Object Designer. (Note: this field will be hidden by default.)

==== Errors fixed ====

'''P20) CfrontMayUsePermission Property Not Working'''
Error
The CfrontMayUsePermission property for codeunits did not exist in Navision Attain 3.01 A.
This has been corrected.
Internal Workbase reference: D1ED9D63174F9BE5C1256AC000396C8A

'''P21) Hyperlinking to E-Mail Was Slow'''
Error
The function Send – E-Mail by Link on a customer card in Navision Attain 3.01 A had unacceptable performance.
This has been corrected.
Internal Workbase reference: 634F5A6FFD8D7B43C1256ACA0032B5A7

'''P22) Sealed Stx files'''
Error
You were able to run a fin.stx file in a subfolder without it being sealed.
This has been corrected.
Now, it is possible to seal the files in all language subfolders and subsequently check them.
However, in case of failure, the present implementation does not reveal which of the fin.stx files have been corrupted. It only indicates that there is a checksum error in the fin.stx file.

Internal Workbase reference: 3F0BBC298B382BCD41256A09003B8E25

'''P23) Stx File Does Not Contain Version Information'''
Error
Sealing the fin.stx file often created confusion in the NTRs because when a checksum error message was given, it wasn’t clear if this was due to an incorrect level of fin.stx file.
This has been corrected.
Now, the information in the first effective line in the fin.stx file is checked against the present version number of the fin.exe.
For example, if we are working with version W1 3.01.B, this must match the version of the present fin.exe file. The ID for the version line is 11111-11110. Hence, the first line in the fin.stx file must be something like 11111-11110-060-0: W1 3.01.B

Sealing will not continue if this is not satisfied.

Internal Workbase reference: A3EF956900C9CA6D41256ABE0036C64D

'''P24) Rec.BLOB Crashes C/AL Editor'''
Error
If you declared a record type variable and referenced a BLOB field from that table in the C/AL code, the client crashed as soon as you attempted to use it.
This has been corrected.
Using BLOB fields in the editor occasionally crashed the client. This internal crash occurred when searching for information about the BLOB field that had to be written in the status line of the editor.

This search has been changed; only the type and field no. are written in the status line.

Internal Workbase reference: 2DA93D99D1241A3241256A94005B4311

'''P25) Cut and Paste of TableBox reset controls Xpos and Ypos to -220'''
Error
When cutting and pasting a TableBox containing existing controls, and those existing controls had XPos or YPos equal to zero, this resulted in negative XPos and YPos in all controls. The object was usable unless it was exported as text and imported again.
This has been corrected.
Internal Workbase reference: A5B369F9CF10A4D941256A94003930FB

'''P26) Navision Crashed if a Local Record was InStreamed or Outstreamed'''
Error
When a local record was declared and used together with InStream or OutStream, Navision Attain crashed.
This has been corrected.
Internal Workbase reference: F1186EAAF443F82E41256AA2003319BF

'''P27) Internet Explorer 5.0 Needed for Installation'''
Error
If you did not have Internet Explorer 5.0 installed, you would get an incomprehensible error message.
This has been corrected.
Now the Installation program checks if Internet Explorer 5.0 is installed. If it is not installed, a meaningful error message appears in the beginning of the installation process.

Internal Workbase reference: 370A8A37E7C6F2BA412569FF0045F605

== Tools ==

=== Upgrade Toolkit ===

==== Errors fixed ====

'''T1) Sales Return Receipts and Purchase Return Shipments were not updated correctly'''
Error
Because of object renumbering, the Sales Return Receipt and the Purchase Return Shipment must be moved to the renumbered tables. This did not happen – instead the Sales Return Receipt and the Purchase Return Shipment were just deleted.
This has been corrected.
Internal Workbase reference: 0CD108F755040C05C1256AD8004AE130

== Documentation ==

=== Manuals ===

==== Features ====

'''D1) Installation & System Management: Navision Server'''
The HotCopy program description has been updated in the manual.

'''D2) Application Designer's Guide'''
This manual has been partially redesigned: most of the information previously found in the Appendixes has been moved into the body of the manual.
More SQL Option specific information has been added, including a description of how SIFT has been implemented in the SQL Server Option.
A description of the new index-hinting feature has also been added.

'''D3) Application Designer's Guide'''
Chapters 6, 7, 10, 12 and 18 have been updated with information about new multilanguage features.

==== Issues ====

'''D4) Upgrade Toolkit Manual Updated'''
Chapter 3 "Upgrading to Multilanguage" has structural changes that make it easier to follow the instructions as a continuing process. It contains a new section describing which databases to use and how they must be opened.

Chapter 4 "Customizing the New Database" now contains references to Navision Developer's Toolkit. All references to Merge Tool have been deleted.

The section Remove IDs has been moved from chapter 3 to chapter 4.

These changes were also released in hotfix number 1 for Navision Attain 3.01.A

== Changes Made in Hotfix 1 for Navision Attain 3.01.B ==

This document describes the changes between Navision Attain 3.01.B and Hotfix 1 for Navision Attain 3.01.B.

==== Errors fixed ====

'''Optimistic Concurrency Error when doing an “Empty” MODIFY'''
Error
If a record was retrieved from the database after a MODIFY command that has not changed any field values, the record would be stamped with an incorrect (old) version stamp.
This could generate an optimistic concurrency error (“Another user has modified this <Rec>…”) in subsequent transactions.

Example:

<PRE>
Rec.GET(...);
Rec.MODIFY; // No actual modifications
Rec.GET(...);
COMMIT;
...
Rec.MODIFY;
</PRE>

The last MODIFY statement would generate an optimistic concurrency error.
This has been corrected.
*Ndbcs.dll

== Changes Made in Hotfix 2 for Navision Attain 3.01.B ==

This document describes the changes between Hotfix 1 for Navision Attain 3.01.B and Hotfix 2 for Navision Attain 3.01.B.

==== Errors fixed ====
Navision Attain Client and Navision Server Failed When Started with Nettype=netb
Error
If the NetBIOS net type was selected, the Navision Attain Client and the Navision Server will display the error message “Error 182 in module 1” and fail to start.
This has been corrected.
Internal Workbase reference: 1A7EA81BB8647C57C1256B040050F7CC
*Nc_netb.dll

=== MS SQL Server Option ===

==== Errors fixed ====

'''SIFT Sums were Wrong when a Date Field was the Last Field in the Composite Key'''
Error
If the composite key of a SIFT index had a date field at the end, the SIFT sums based on that index were incorrect.
A SIFT index is a key with SumIndexFields, and the composite key for an index is defined as the fields of the secondary key plus those fields from the primary key that are not already part of the secondary key.
The error only happened when the MaintainSIFTIndex key property was set to Yes.
This has been corrected.
The fix will not fix errors in existing tables. Existing tables with date fields at the end of the composite index will need to be rebuilt by toggling the value of the MaintainSIFTIndex property.
There are no such tables in the base application.

Internal Workbase reference: C1E14E4BADE3AE3BC1256AF4003D7BB8
*Ndbcs.dll

=== Development Environment ===

==== Errors fixed ====

'''Lookup Could be Very Slow'''
Error
When performing a lookup in filtered sets, for example from the Balance field of the G/L Account, displaying the lookup form could be very slow.
The problem was caused by the system trying to position the form on or “close to” the record that was displayed the last time the form was used.
This has been corrected.
Internal Workbase reference: 5F77C6E63F07E391C1256B0B0059632E

*Fin.exe
*FinSQL.exe

'''Using Lookup to set values in Filters'''
Error
When selecting values from a Lookup form into a filter field, any existing text in the field would be replaced by the last selection.
This would make it impossible to use a Lookup form to enter a filter string like ‘10000..50000’ in a request form, because the ‘10000..’ part would be replaced by the last selected value ‘50000’.

Entering the filter string using the keyboard worked.
This has been corrected.
The new rules for executing trigger code are identical to the rules in NF2.60.
The current design in C/SIDE does not allow the OnValidate trigger to be executed automatically when using lookup, so validation code should be called explicitly if needed.

Internal Workbase reference: D06BB3E8C0385CF3C1256B0A00420486

*Fin.exe
*FinSQL.exe


== Changes Made in Hotfix 3 for Navision Attain 3.01.B ==

This document describes the changes between Hot Fix 2 for Navision Attain 3.01.B and Hot Fix 3 for Navision Attain 3.01.B.

==== Features ====

==== Errors fixed ====

'''Object Caption Overflow'''
Error
Forms showing object names could give text overflow errors. For example, this included form 358 Objects. From now on, only the first 30 characters of object names will be shown in these forms. You must delete the contents of table 377 and 378 before importing the new objects, and rerun the steps for importing object captions into Attain 3.01 (see the upgrade toolkit manual).
This has been corrected.
*Table 377
*Dataport 1

==== Issues ====

=== Inventory ===

==== Features ====

==== Errors fixed ====

'''Missing Permissions and Incorrect Update of Value Entry and Item Application Entry in Codeunit 32 BOM Jnl.-Post Line'''
Error
When posting a BOM item with a costing method different from Standard through a BOM Journal, the cost of the BOM item was not updated correctly on the Value Entry and Item Application Entry. But as the permissions for modifying Value Entry and Item Application Entry were missing, this could never occur using a customer license file.
This has been corrected.
*Codeunit 32

Internal Workbase references:
5FFB27D4D76338ECC1256B030041F7EE
4C37E61270F3D64CC1256B030043EF86
69B5B99DEAFB9EE6C1256B1E003F7A46

'''The Adjust Cost – Item Entries Batch Job Could End Up in a Never-Ending Loop'''
Error
If an inbound entry was applied to both a consumption entry and a not completely invoiced sales entry, then the Adjust Cost – Item Entries batch job could end up in a never-ending loop.
This has been corrected.
*Codeunit 5895

Internal Workbase references: 236C576654BF6350C1256B1000527789

Источник http://wiki.dynamicsbook.com/index.php?tit...on_Attain_3.01B