wiki.dynamicsbook: Changes Made in Navision Attain 301

[Blog bot]

Summary: /* Fixed Assets */



== Overview ==

This document describes the changes between Navision Solutions 3.00 and Navision Attain 3.01.

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 ===

==== Features ====

'''A1) Main Menu'''
Feature
The main menu has been changed because of the new company colors and the new product name.
Table 389 has been deleted since it was only used in the main menu for Solutions 3.00.
The two bitmap files:

*logowatermark ID 29.bmp
*watermark ID 33.bmp

installed along with the Attain Client are thus no longer used, but has been left for reasons of backward compatibility.
Implemented

*''Form 330 Main Menu''
*''Form 332 General Ledger Menu''
*''Form 333 Sales & Receivables Menu''
*''Form 334 Purchases & Payables Menu''
*''Form 335 Inventory Menu''
*''Form 336 Resource Menu''
*''Form 337 Job Menu''
*''Form 5000 Relationship Management Menu''
*''Form 5224 Human Resource Menu''
*''Form 5606 FA Menu''
*''Form 5765 Warehouse Mgt. Menu''
*''Form 5959 Service Menu''
*''Form 99001048 Cap. Reqts. Planning Menu''
*''Form 99001049 Manufacturing Menu''

==== Errors fixed ====
'''A2) Error in the Demo Data for Customers 41231215, 41497647 & 41597832.'''
Error
A wrong Gen. Bus. Posting group for the customers resulted in an error when the "VAT- VIES Declaration Tax Auth" report was printed. The reason was that the Gen. Bus. Posting group was EU instead of Export. CH isn't an EU country and hasn't an EU country code in the country code table.
However, a lot of VAT entries with the wrong Gen. Bus. Posting group still exists.
This has been corrected
*''Codeunit 101004''

'''A3) Optimistic Concurrency Error on SQL Server when Posting Sales and Purchase Orders'''
Error
In Navision Solutions 3.00 there is an error regarding the Release document function.
If "Sales & Receivables Setup"."Calc. Inv. Discount" or "Purchases & Payables Setup"."Calc. Inv. Discount" is set to "Yes", then the Release function fails when posting orders, resulting in an error message saying "Another user has modified...".
The error only occurs when using SQL Server.
This has been corrected:
*''Codeunit 414 Release Sales Documents''
*''Codeunit 415 Release Purchase Documents''

'''A4) Multi language correction for dimensions'''
Error
Some dimension forms referred to the Object table without using the Object Translation table.
This has been corrected:
*''Form 544 Ledger Entry Dimensions''
*''Form 545 Journal Line Dimensions''
*''Form 546 Document Dimensions''
*''Form 547 Posted Document Dimensions''

'''A5) Spelling Mistake in the Demo Data'''
Error
An item in the Demo Data was called “2000-S SIDNEY”. This has been changed to “2000-S SYDNEY”.
Project Workbase ID: 9686478CF5E1084441256A1C0035B4B2
This has been corrected
*''Codeunit 101030''

==== Issues ====

=== General Ledger ===

==== Features ====

'''A6) Confirm Message if the Customer/Vendor has a Bill-to Customer No./Pay-to Vendor No.'''
Feature
When filling out journal lines, a confirmation message will now appear when the user enters a customer/vendor no. in the Account no. or Bal. Account No. fields and the customer or vendor has a bill-to customer no./ pay-to customer no.
Implemented
*Table 81 Gen. Journal Line

==== Errors fixed ====

'''A7) Missing Extended Permissions in Report 94 Close Income Statement'''
Error
On report 94 Close Income Statement, no extended permission was given for modify on G/L Entry, which is necessary for modification of Close Income Statement ID field.
This has been corrected
*Report 94 Close Income Statement

'''A8) Wrong VAT Rounding Type in Table 81 Gen. Journal Line'''
Error
VAT rounding direction was not taken into consideration in table 81 Gen. Journal Line.
This has been corrected
*''Table 81 Gen. Journal Line''

'''A9) Wrong Date Filtering on Form 475 VAT Statement Preview'''
Error
A previous change to report 12 VAT Statement regarding use of start and end dates instead of date filter caused form 475 VAT Statement Preview Line to show wrong numbers because filters were not set correctly.
This has been corrected
*''Form 475 VAT Statement Preview Line''
*''Report 12 VAT Statement''

'''A10) Dimensions not Copied in the Copy Budget Batch Job'''
Error
When dimensions were defined in the copy budget batch job, this was not taken into consideration in the actual copy.
This has been corrected
*''Report 96 Copy G/L Budget''

'''A11) Division by Zero in Table 37 and Table 39'''
Error
When entering a sales order where invoice discount = line amount and using prices including VAT, a 'division by zero' error occurred in the statistics window.
This has been corrected
*''Table 37 Sales Line''
*''Table 39 Purchase Line''

'''A12) When Date Compressing the G/L Budget Entries an Error Occurred'''
Error
An error message would appear, saying that you had to retain the dimensions and even though you selected all the dimensions in the Retain Dimensions field, the same error message would continue to come.
This has been corrected
*''Report 97 Date Compr. G/L Budget Entries''

'''A13) Error in Report 715 "Price List"'''
Error
Report 715 did not take the currency's "Unit-Amount Decimal Places" into consideration.
This has been corrected
*''Report 715 Price List''

'''A14) Inconsistency when Applying'''
Error
The program gave an inconsistency error when an Invoice was applied to a payment when the payment was in the same currency as the Additional Reporting Currency and the Appln. Rounding Precision was set to 0.01 for that currency.
This has been corrected
*''Codeunit 12''

==== Issues ====

=== Fixed Assets ===

==== Features ====

==== Errors fixed ====

'''A15) Wrong Modify in Table 5600'''
Error
There was a wrong modify in the OnValidate trigger of the Description field in table 5600.
This is corrected
*''Table 5600''

==== Issues ====

=== Sales & Receivables ===
Features

Errors fixed
A16) Deletion of Several Order Promising Lines
It was not possible to delete more than one Order Promising Line at a time.
Project Workbase ID: 624114BAE18DE6BB41256A4500534A59
This has been corrected
Sales Order form (42)
Order Promising Lines form (99000959)
Capable to Promise codeunit (99000886)
AvailabilityManagement codeunit (99000889)
A17) Lead Times Are Used Inconsistently on Sales and Purchase Order
Lead Times can be found on the Item Card as well as on the Stockkeeping Unit Card, the Item Vendor Card and the Vendor Card. These Lead Times should be prioritized and used consistently in Sales Orders and Purchase Orders.
Project Workbase ID: C392DD109B3FB9BD41256A3900323D05
This has been corrected.
Item table (27)
A18) Incorrect Name of Menu Item
On the Posted Sales Shipment form, the Menu Item “Tracking” should be named “Order Tracking” like in all other forms.
Project Workbase ID: 4AE0E2213CE3F00141256A6700325E36
This has been corrected.
Posted Sales Shipment form (130)
Issues
A19) Sales Returns
Issue
The Sales Returns functionality has been redesigned to ensure the appropriate quality level.
1.5 Relationship Management
Features
A20) Name Change
The name of the Business Interaction Management application area has been changed into Relationship Management. This is implemented in the application, the online help and the training material.
A21) Button "Show Doc."
Feature
Renamed to "Show". Show will now "show" either an Attachment or a Document, depending on what is available.
Internal Reference No. IS00904.
Implemented
Form 5076
A22) Close Opportunity Code Filter on Opportunity Matrix
Feature
It’s now also possible to filter on “Close Opportunity Code” in the opportunity matrix.
Internal Reference No. IS01008.
Implemented
Form 5131
Table 13
Table 5050
Table 5071
Table 5093
Table 5102
A23) Disable Sales Cycle Stage Filter Field if Sales Cycle Filter = ''
Feature
Instead of having “Sales Cycle Stage Filter” Editable=No, is it now marked Enabled=no.
Internal Reference No. IS01053
Implemented
Form 5131
A24) Offer to Reset No. of Criteria Actions
Feature
We now ask if the user wants to Reset No. of Criteria Actions (If No. of Segment lines = 0).
Internal Reference No. IS01118.
Implemented
Table 5076
Table 5077
A25) “Go Back” Extended with Confirmation Message
Feature
A confirmation message is issued to avoid loosing a lot of setup by accident.
Internal Reference No. IS01119.
Implemented
Form 5091
A26) Jump from Segment Wizard to the “Add Contacts” function
Feature
In the Segment Wizard it is now possible to add additional criteria by activating the “Add Contacts” function from the Segment Wizard.
Internal Reference No. IS00934.
Implemented
Form 5113
Table 5096
A27) Lookup Sales Quote from Opportunity Wizard
Feature
In the Update Opportunity Wizard and the Close Opportunity Wizard it is now possible to look up the Sales Quote for the Opportunity.
Internal Reference No. IS00958.
Implemented
Form 5128
Form 5129
A28) Default Field Values in Wizard’s
Feature
On To-Do Wizard, Opportunity Wizard and Assign Activity Wizard more default fields are now filled out and it is possible to change the default values.
Internal Reference No. IS01002.
Implemented
Form 5146
Table 5065
Table 5080
Table 5092
Errors fixed
A29) Assign Activity Wizard Face-lift
Error
Inconsistencies have been removed.
Internal Reference No. IS01003.
This has been corrected
Form 5146
A30) Error Message in Mail Wizard
Error
The Mail Wizard is now giving the user a more precise error description.
Internal Reference No. IS01007.
This has been corrected
Codeunit 397
Form 5148

A31) Import Attachment in Interaction Wizard
Error
Bug fixed in Interaction Wizard. If the user chooses to cancel on Import of the attachment all buttons in the Interaction Wizard were disabled. Now we move on to the next page in the Wizard.
Internal Reference No. IS01100.
This has been corrected
Form 5077
A32) Wrong Field Order in Wizard
Error
Changed field order in Create Opportunity Wizard on page one. Priority and Description have switched places.
Internal Reference No. IS01116.
This has been corrected
Form 5126
A33) Fixed Checkboxes in Wizards
Error
It is now possible to toggle checkmarks in Wizards by clicking on the caption.
Internal Reference No. IS01131.
This has been corrected
Form 5077
Form 5097
Form 5147
Form 5148
A34) Incorrect Calculation in Classification
Error
When classifying with a “Contact Class. Field” using the method “Percentage of Contacts” or “Percentage of Value” it used both companies and persons in the calculation of the total value, even though the “Profile Questionnaire Header” specified companies only.
Internal Reference No. IS01138.
This has been corrected
Report 5199
A35) Localization Problems with the Contact List
Error
To remove the risk of localized versions not indenting the persons properly, it has been made language independent to check if a certain key is used.
Internal Reference No. IS01139.
This has been corrected
Form 5052
A36) Improved Word 2000 Stability
Error
Problems with MS Word integration have been fixed.
Internal Reference No. IS01140.
This has been corrected
NSAppHandler.dll
A37) Could Show Misleading Statistics on Interaction Template
Error
If an Interaction Template got a new Interaction Group assigned, only new Interaction Log Entries would be shown in the statistics. Now it’s not using the Interaction Group in links from Interaction Templates, and thereby showing all the Interaction Log Entries with the same Interaction Template Code.
Internal Reference No. IS01033
This has been corrected
Form 5075
Table 5064
Table 5065
A38) Show “Right” Record when Drilling Down into the Interaction Log Entry List and the To-do List
Error
When drilling down into the Interaction Log Entry List the record is not the one showed in the Flow-Field
Internal Reference No. IS01121.
This has been corrected
Form 5050
Form 5105
Form 5116
Table 5065
Table 5080
A39) Typos in Demo Data
Error
The demo data contained spelling errors in a URL definition and in a Contact name.
This has been corrected
Create Web Source 5059 codeunit (101559)
Create Contact 5050 codeunit (101550)
Issues
A40) Optimized Key Usage
Issue
Table keys has changed because a new optimized key usage is now available in min/max FlowFields
Internal Reference No. IS01135
Implemented
Table 5065
Table 5080
Report 5051
Report 5053

=== Purchases & Payables ===
Features

Errors fixed
A41) Default Dimensions on Requisition Journal Line
The Default Dimensions were not copied for Requisition journal lines.
Project Workbase ID: E1833A6A80D8978641256A47004B7A52
This has been corrected.
Requisition Line Table (246)
A42) Cost Shares of Purchase Credit Memos
The calculated cost shares of the Purchase Credit Memo were not the exact reverse of the related Purchase Order.
Project Workbase ID: FE2ABB98501DD97941256A3B004C2E3F
This has been corrected.
Issues

=== Inventory ===
Features

Errors fixed
A43) Nonstock Items With Same Vendor Item Number
Error
It was possible to define a nonstock item with an already used Vendor Item Number. The error message was shown very late.
Project Workbase ID: 7FF37DFEC553657C41256A46004CCA7D
This has been corrected.
Nonstock Item table (5718)
A44) Description of Nonstock Items
Error
It was not possible to enter a description of a nonstock item after use.
Project Workbase ID: 0885F13D0C11981541256A4D004D25E0
This has been corrected.
A45) Change of Ship-to Code When Using Nonstock Items
It was not possible to change the Ship-to code when a nonstock item was used at a Sales Line.
Project Workbase ID: 5EF7722D0841AE5741256A4D004C2368
This has been corrected
Sales Header table (36)
A46) Misplaced Labels on Out-of-Stock Warning
Error
The labels for Earliest Availability Date and Total Quantity were swapped.
Project Workbase ID: 06924AE27E5BBC9C41256A4C003222BD
This has been corrected.
Check Availability Form (342)
A47) Incorrect Expected Cost Total on Inventory Valuation Report
Error
The Inventory Valuation Report did not calculate the correct Expected Cost Total.
Project Workbase ID: 23B39C8BE200C93341256A4800288FB2
This has been corrected.
Inventory Valuation report (1001)
A48) Add Lines to Transfer Orders
Error
It was not possible to add new lines to a Transfer Order where a shipment was posted.
Project Workbase ID: DC4048AAE15BD4FC41256A5D00468A15
This has been corrected.
Transfer Line table (5741)
A49) Warehouse Handling Time not Used Consistently on Transfer Order
Error
Inbound and Outbound Whse. Handling Time were not copied to the Transfer Order Header.
Project Workbase ID: EC7F04DB55D6CC9141256A68003B4308
This has been corrected.
Transfer header (5740)
Transfer line table (5741)
Transfer Route table (5742)
Transfer Order form (5740)
Transfer Order Subform form (5741)
A50) Posting Date on Transfer Order Header was not Used
Error
The Posting Date on the Transfer Order Header was not used for the posted Item Ledger Entries.
Project Workbase ID: 321E08410AE2884041256A4D00458F98
This has been corrected.
TransferOrder-Post Shipment codeunit 5704
TransferOrder-Post Receipt codeunit 5705
A51) Missing Permissions in the Adjust Cost – Item Entries Batch Job
Error
Due to missing permissions it was not possible to run the Adjust Cost – Item Entries batch job with a user license.
Project Workbase ID: EEA6BB4C6F519CFA41256A680029DA04
This has been corrected.
Inventory Adjustment codeunit (5895)
A52) Stack Overflow in Adjust Cost - Item Entries Batch Job
Error
A stack overflow could happen in the Adjust Cost – Item Entries batch job.
Project Workbase ID: 6899EB561C68084041256A50004BB9BF
This has been corrected.
A53) Average Cost Calculation
Error
In some case the average cost could incorrectly be calculated to zero.
Project Workbase ID: 2DF43A3C0EB8CD1F41256A1B005232A1
This has been corrected.
A54) Deletion of Revaluation Journal Lines After Posting
Error
Not all Revaluation Journal Lines were deleted when the journal was posted.
Project Workbase ID: E5B306F85C32517541256A2B00336D3C
This has been corrected.
Issues
A55) Un-editable Fields at the Item Card
When a requisition system was selected (purchase or production), some other fields became un-editable.
For instance, the Vendor No. became not editable when Production had been selected. This was less fortunate because even if the item would normally be produced, it could for practical reasons be useful to maintain the possibility to buy it elsewhere.
Project Workbase ID: 7F28A59916BF51FA41256A450059033F
In response to this issue, changes have been made.
Item Card form (30)

=== Warehouse Management ===
Features

Errors fixed
A56) Not Possible to Post Orders With a User License
Error
It was not possible to post Sales, Purchase or Transfer Orders with a User License if Warehouse Management was not included.
Project Workbase ID: 017B46BC358B709441256A6700358765
This has been corrected.
Release Sales Document codeunit (414)
Release Purchase Document codeunit (415)
Release Transfer Document codeunit (5708)
A57) Change of Prod. Order Component Lines
Error
It was possible to change or delete Prod. Order Component Lines even after Warehouse Activity Lines had been created for these.
Project Workbase ID: 807C8DE94E2B023A41256A21002ECEF7
This has been corrected.
Prod. Order Component table (5407)
Whse. Validate Source Line Codeunit (5777)
A58) Due Date on Warehouse Activity Lines
The Due Date on the Warehouse Activity Line was not copied when the assignment was made from a Purchase Credit Memo.
Project Workbase ID: 072D5F1D3ADFDACD41256A45004999E0
This has been corrected.
Whse. Activity Create codeunit (5750)
A59) Error Message When Post Pick and Ship
In some cases an error message in the Post Pick and Ship batch job could hide messages about successfully created lines.
Project Workbase ID: 376E9CB95343F52441256A46003BC3B3
This has been corrected.
Whse.-Post Pick (Yes/No) codeunit (5758)
Whse.-Post Pick codeunit (5766)
A60) Production Orders In The Source Document Selection List
Error
A Production Order could be found both as Firm Planned and as Released in the Source Document Selection List after release of the Production Order.
Project Workbase ID: E746EBD81BC0B1DA41256A450052C310
This has been corrected.
Prod. Order Component table (5407)
A61) Deletion of Transfer Lines
Error
It was possible to delete Transfer Lines even after a related assign document was created.
Project Workbase ID: 6314DD35F73B447A41256A4800343C82
This has been corrected.
Whse. Validate Source Line codeunit (5777)
Transfer Line table (5741)
A62) Login Management Not Used Consistently in Create Picks
Error
The new Login Management had not been implemented in the Create Pick batch job.
Project Workbase ID: D622697A1DA27BB341256A5B003E240F
This has been corrected.
Create Pick batch job (5754)
A63) Deletion of Warehouse Pick Documents
Error
When a Warehouse Pick Document was deleted, not all related Warehouse Assignments were deleted.
Project Workbase ID: D499E000263650CF41256A3E0025F492
This has been corrected.
A64) Filters on Warehouse Ship Lines Window
Error
When a filter was used in the Warehouse Ship Lines Window and the window was closed and reopened, the filter was removed from the field, but still active.
Project Workbase ID: 42F33DD9C6BB9CC641256A4D00340242
This has been corrected.
Warehouse Ship Lines form (5781)
Issues
A65) Quantity Handled Added to All Warehouse Management Forms
Issue
Quantity Handled was not shown on the all Warehouse Management forms.
Project Workbase ID: 382CD4627435185D41256A0700656F84
In response to this issue, changes have been made.
A66) Shipment Date on Whse. Source Filter
Issue
The Shipment Date was missing at the Sales Tab of the Whse. Source Filter.
Project Workbase ID: CE7064528EDB82CA41256A1B00424090
In response to this issue, changes have been made.
A67) Cross-Dock Functionality Moved to the Put-Away Window
Issue
To have a better foundation for future development, the Cross-Doc functionality has been moved from the Receipt to the Put-Away window.
In response to this issue, changes have been made.

=== Manufacturing ===
Features

Errors fixed
A68) Cost Amount Value on a Production Order Ledger Entry
Error
This amount was calculated incorrectly, which caused errors in the Production Order Statistics.
Project Workbase ID: 88C27D39A6E4DF8C41256A540028A82E
This has been corrected.
Consump. Jnl.-Post Line codeunit (99000802)
A69) Default Safety Lead Time
Error
The Default Safety Lead Time was not a date field.
Project Workbase ID: AC76BA2F352890C941256A54004BA57E
This has been corrected.
Manufacturing Setup table (99000765)
Planning-Get Parameters codeunit (99000855)
Issues
A70) Reorder Point vs. Safety Stock problems
Issue
When a Safety stock had been defined, the planning should reduce the suggested order qty. when the Reorder policy had been defined to Max. Qty.
Project Workbase ID: 5882E95F395046DA41256A7A0056296A
This has been corrected.
Inventory profile offsetting Codeunit (99000854)

=== Cap. Reqts. Planning ===
Features

Errors fixed
A71) The Capacity Cost or Subcontracted Cost in Production Order Statistics
Error
The Capacity Cost or Subcontracted Cost in Production Order Statistics showed zero even when a routing was defined.
Project Workbase ID: F0936DC237F6B2B641256A550023D556
This has been corrected
A72) Refresh of a Simulated Production Order
Error
In some cases when using capacity constrained resources, the refresh of a simulated production order could take very long time.
Project Workbase ID: E6AA2612361E9D8641256A38005AC37F
This has been corrected
Calculate Routing Line codeunit (99000774)
A73) Deletion of a Prod. Order Routing Line
Error
When a Prod. Order Routing Line was deleted, the Next Operation No. of the previous line and the Previous Operation No. of the next line were not updated.
Project Workbase ID: 076AC7B2F4ABE3EA412568F50043A9C4
This has been corrected
The system will inform the user if any of the remaining lines are pointing at the deleted operation. The user will then have to assess whether the value in Previous/Next should be changed.

Prod. Order Routing Line table (99000792)
Prod. Order Routing form (F99000817)
Issues


== Development Environment and Database Changes ==

=== Navision Server ===
Features
P1) Server Based Backup: “HotCopy” Introduced
Feature
A program to create fast backups of a running Navision Server database has been introduced. Read more about the new program in the “Installation & system Management: Navision Server” manual.
For Attain 3.01, the HotCopy feature is available for the Navision Server running on Windows only.
Errors fixed

Issues

=== MS SQL Server Option ===
Features
P2) SQL Server 2000 Default Collation
Feature
When installing SQL Server 2000 it is no longer necessary to use a SQL Collation for the default server collation: a Windows Collation can be used if desired. Navision Attain will not generate an error message when it detects a server Windows Collation. However, it is still only possible to create databases with either a SQL Collation or Binary Windows Collation. It is also necessary that the code page for the database collation match the client computer OEM or ANSI System code page, as with previous releases.

It is important to ensure that the database collation is set to that required by the system administrator when creating a database, using the Collation tab in the New Database window.
P3) Client Monitor - Additional Parameters
Feature
To help trouble-shooting and performance analysis when running against SQL Server, new parameter entries that can be configured dynamically have been added to the Client Monitor. These include status information for caching and SQL statements, along with execution plans.

In a future version of Attain the configuration will be possible from within Attain in the user interface. Currently this has to be done outside of Attain, using the Enterprise Manager or Query Analyzer tools. The [$ndo$dbproperty] table in the database being analyzed contains a new integer column named 'diagnostics' (provided that the database has been opened and converted with an Attain 3.01 client). The value of this column determines the parameters and their values used in the Client Monitor. This value is determined by adding together the following combination of flags:

Flag Parameter Behavior
0 (default) SQL Statement displayed with actual filter values (can be copied into Query Analyzer and executed, providing the statement has not been truncated).
SQL Status displays 'Cached' when data has been read from a client cache, instead of making a server call.
Statistics 'Server Time', 'Reads' and 'Records Read' (i.e. the number of records fetched to the client for the operation) are collected.
1 SQL Statement is not displayed.
2 SQL Statement uses '?' placeholders instead of filter values.
4 Statistics 'Server Time', 'Reads' and 'Records Read' are collected.
8 SQL Plan is displayed (for most statements), as a collapsed tree with the format:

Plan Step(Object)[n,p];... Here, node n has parent p.

E.g.: Computer Scalar[2,1];Clustered Index Seek(User$0)[4,2]
This defines the tree:

1 -- Root
2 -- Computer Scalar
4 -- Clustered Index Seek(User$0)
16 SQL Status is not displayed.
32 SQL Status displays additional information; internal statement ID; re-use status; prepared status; cursor type; hints; transaction type.

For example, to remove statistics but display execution plans; add flag 4 to flag 8 to give a diagnostics value of 12. Update the table using Enterprise Manager or using a statement in Query Analyzer such as:

UPDATE [$ndo$dbproperty] SET [diagnostics] = 12

The value takes effect the next time the database is opened.

Notes:

Collecting server statistics is time-consuming, so enabling statistics with flag 4 is not recommended when performing benchmarking, in order to give the most accurate value for the 'Elapsed Time (ms)' parameter.

Similarly, displaying the execution plans is extremely time consuming and should not be done when benchmarking. This parameter is useful when trouble-shooting problematic application areas to determine if a SQL statement is a bottle-neck, and can be valuable to users not able to run the SQL Profiler tool (note that executing a SQL statement in Query Analyzer to use its graphical execution plan does not necessarily give the same plan or statistics as when it is executed from Attain, due to cursor type differences; the SQL Profiler or Client Monitor SQL Plan parameter give the most accurate plan).

The diagnostic flag 32 is useful for understanding which properties of a SQL statement are being used for an operation. It is also possible to see how frequently statements are being re-used or re-created. The unique ID can be used to cross reference re-used statements to determine the original SQL statement entry.
P4) Index Hinting Feature Added
Feature
It is now possible to force the SQL Server to use a particular index when execution queries for FIND(‘-‘), FIND(‘+’), FIND(‘=’) and GET statements. This can be utilized as a workaround when the SQL Server’s Query Optimizer picks the wrong index for a query.

Index hinting can avoid situations where the SQL Server query optimizer is choosing an index access method that performs many page reads, giving rise to long running queries (response times of seconds or several minutes). The selection of an alternative index, had it been chosen instead, can give instant 'correct' query executions (response times of milliseconds). The problem usually occurs only for particular tables and indexes, containing certain data spreads and index statistics.

It is possible to direct Navision Attain to use index hinting for such problematic queries, in the rare situations in which it is necessary. When using index hinting, Navision Attain adds commands to the SQL queries sent to the server that will by-pass the normal decision-making of the SQL Server's Query Optimizer and force the server to choose a particular index access method. The feature should be used only after all other possibilities have been exhausted and failed (e.g. updating statistics, optimizing indexes or re-organizing column order in indexes).

The procedure is as follows:

In the database create a table, owned by dbo:

CREATE TABLE [$ndo$dbconfig] (config VARCHAR(512) Not Null)

(There can be additional columns in this table if required. The length of the config column should be large enough to contain the necessary configuration values explained below, but need not be 512)

There is one record in this table for each index hint required.
The index hint syntax is:

IndexHint=<Yes,No>;Company=<company name>;Table=<table name>;Key=<keyfield1,keyfield2,...>; Search Method=<search method list>;Index=<index id>

Each parameter keyword can be localized in the stx file, in the "Driver configuration parameters" section.
• If IndexHint=No, the entry is ignored.
• All keywords must be present or the entry is ignored.
• If a given keyword value cannot be matched the entry is ignored.
• The values for the company, table, key fields and search method can be surrounded by double-quotes, to delimit names containing spaces, commas etc.
• The table name corresponds to that supplied as the name in the Object Designer (not the Caption name).
• The key must contain all key fields that match the required key in the Keys window in the Table Designer.
• The search method contains a list of search methods used in FIND statements, that must be one of '-', '+', '=', or '!' (for the C/AL GET function).
• The index id corresponds to a SQL Server index for the table: 0 represents the primary key; all other ids follow the number included in the index name for all secondary keys. Use the following SQL Server command sp_helpindex to get information about the index id associated with indexes on a given table; In the example the Item Ledger Entry table:

sp_helpindex 'CRONUS Ltd_$Item Ledger Entry'

When Navision Attain executes a query, it checks if the query is for the company, table, current key and search method listed in one of the IndexHint entries. If so, it will hint the index for the supplied index id in that entry.

• If the company is not supplied, then the entry will match all companies.
• If the search method is not supplied then the entry will match all search methods.
• If the index id is not supplied, then the index hinted will be the one corresponding to the supplied key. This is probably the desired behavior in most cases.
• If the company/table/fields are renamed, or the table's keys redesigned, the entries must be manually modified as appropriate.


Examples

To add an index hint to the table, execute the following statement in Query Analyzer.

<PRE>
Insert [$ndo$dbconfig] values
('IndexHint=Yes;Company="CRONUS Ltd.";Table="Item Ledger Entry";Key="Item No.","Variant Code";Search Method="-+";Index=3')
</PRE>

Example 1

<PRE>
IndexHint=Yes;Company="CRONUS Ltd.";Table="Item Ledger Entry";Key="Item No.","Variant Code";Search Method="-+";Index=3
</PRE>

This will hint the use of the [$3]index of the [CRONUS Ltd_$Item Ledger Entry] table for FIND('-') and FIND('+') statements when the "Item No.","Variant Code" key is set as the current key for the "Item Ledger Entry" table in the "CRONUS Ltd." company.


Example 2

<PRE>
IndexHint=No;Company="CRONUS Ltd.";Table="Item Ledger Entry";Key="Item No.","Variant Code";Search Method="-+";Index=3
</PRE>

The entry is disabled.


Example 3

<PRE>
IndexHint=Yes;Company="CRONUS Ltd.";Table="Item Ledger Entry";Key="Item No.","Variant Code";Search Method="-+";Index=
</PRE>

This will hint the use of the "Item No.","Variant Code" index of the [CRONUS Ltd_$Item Ledger Entry] table for FIND('-') and FIND('+') statements when the "Item No.","Variant Code" key is set as the current key for the "Item Ledger Entry" table in the "CRONUS Ltd." company.
This is probably the most frequent use of the index hinting feature.


Example 4

<PRE>
IndexHint=Yes;Company=;Table="Item Ledger Entry";Key="Item No.","Variant Code";Search Method="-+";Index=2
</PRE>

This would apply a hint when this table is queried for all companies (including a non-company table of this name).


Example 5

<PRE>
IndexHint=Yes;Company="CRONUS Ltd.";Table="Item Ledger Entry";Key="Item No.","Variant Code";Search Method=;Index=3
</PRE>

This would apply a hint for all search methods.
Errors fixed

Issues
P5) Performance Improvements
Issue
Several performance improvements are included in this release when running against SQL Server. These are due to extended client-side data caching, and the issuing of SQL statements with optimal attributes or execution plans, whenever possible. The benefits are primarily for read operations, but since batch jobs and modification transactions are also very read-intensive, these areas are also improved depending on the application code.
The Client Monitor tool has new parameters when running against SQL Server that can aid in trouble-shooting and benchmarking. Details of these parameters can be found in section 2.2 of this document.

=== Development Environment ===

Features
P6) Exist FlowField can be Reversed
Feature
The sign for Exist FlowFields can be reversed to obtain a Not Exist function.
For example: A FlowField can be defined to indicate that there are no comments for a customer record.
Errors fixed
P7) Error in Report Section Designer
Error
The height of a section dramatically increased if you changed the caption of the associated parent control.
This has been corrected.
Internal Workbase reference: DAF3645337CF4BF641256A5C002663C3
P8) Compiler Crashed Navision Solutions 3.00
Error
If you tried to address a nonexistent option variable in a report using code like:
OptionVar := OptionVar::nonexist;
where nonexist didn’t exist, the compiler would correctly issue an error message but would fail to clean up its internal memory structure paving the way for a subsequent crash.
This has been corrected.
Internal Workbase reference: C37DD25142EB39FA41256A64003F1830
P9) Pressing <Esc> in a Dialog Window Produced Error Message
Error
Pressing the Escape button when a dialog window was active would close the dialog window and produce the error message:
"The dialog window is not open."
This has been corrected.
Internal Workbase reference: 84B1C725588B2B664125698F00536516
P10) Not able to Load the STX File from the DAN Language Folder
Error
When loading the Danish language folder (DAN) it was not possible to read the STX file from this folder.
This has been corrected.
Internal Workbase reference: EA8797B0C9F2216241256A68004D9B5
P11) Controls not Visible in Report Section Designer
Error
The controls added to a section weren’t visible before the section designer had been closed and reopened.
This has been corrected.
Internal Workbase reference: 421887398897D03841256A5C002BF925
P12) C/AL Messages not Displayed after a Run-Time Error
Error
If a Codeunit.RUN command gave an error, a previously issued C/AL message would not be displayed, as in the following example:

<PRE>
MESSAGE(‘Hello World’);
CodeUnit.RUN; // Fails with an ERROR(...) statement
</PRE>

The ‘Hello World’ message would never be displayed.
This has been corrected.
Internal Workbase reference: 142973C1601E63AF41256A5E004B420C
P13) Table Filter Failed when Viewing Marked Only
Error
If a Marked Only filter had been applied, pressing Ctrl-F7 to open the table filter dialog would produce an error message.
This has been corrected.
Internal Workbase reference: 0D314D2824E7629B41256A720026DCE9
P14) Adding Fields with AutoFormatType/Expr to a Request Form Crashed Navision Solutions
The program crashed when fields that had the properties AutoformatType and /or AutoformatExpr defined were added to a request form.
This has been corrected.
Internal Workbase reference: ABBE7E7F814D141941256A87004C4926
Issues
P15) Min/Max FlowFields no Longer Require Special Keys to be Defined
Issue
In previous versions, C/SIDE required that a key existed starting with the field that a Min/Max FlowField was calculated upon.
Special keys are no longer required in order to calculate Min/Max FlowFields.

== Tools ==

=== C/ODBC ===

Features
T1) C/ODBC Supports Multilanguage
Feature
C/ODBC has been multilanguage-enabled.
T2) C/ODBC Supports Closing Date
Feature
C/ODBC includes a feature for using Closing Dates.
Errors fixed

Issues

=== Communication Component and Bus Adapters ===

Features

Errors fixed
T3) VARIANT_BOOL was Missing in CommunicationComponent2
Error
The Communication Component2 functions OutMessage.Send and InMessage.ExpectReply did not return BOOLeans in C/AL.
This has been corrected.
Internal Workbase reference: EC18F773CF0B479A41256A480028B72E
T4) CommunicationComponent (with Events) could not be Imported in Text Format
Error
An object using the CommunicationComponent, with WithEvents=yes, could not be imported if the object had been saved in text format.
This has been corrected.
Internal Workbase reference: 5CD03C0AB13D44A341256A5E002BDA06
T5) CommunicationComponent with Named Pipe Bus Adapter Crashed
Error
The Named Pipe bus adapter was not checking if a valid IStream was used.
This has been corrected.
Internal Workbase reference: 208518591CD9DEA841256A330024B47C
Issues


== Documentation ==
Features
D1) A Description of the HotCopy Program has been Added
Feature
A description of the new server based backup program called HotCopy has been added to the Installation and System Management: Navision Server manual, section 5.6.
Errors fixed

Issues
D2) Application Designer's Guide
Issue
The manual has been updated with the new product name.
Appendix I now includes more information about how to work in a multilanguage-enabled environment.
D3) Upgrade Toolkit
Issue
The manual has been updated with the new product name.
The description of the multilanguage part of the upgrade is now more comprehensive.
D4) C/ODBC Guide
Issue
The manual has been updated with the new product name and now includes information about multilanguage and closing date support.
Section 2.1 Installation does not include screenshots.
D5) Multilanguage Folder Removed from Localization CD
Issue
All relevant information from the documents previously found in the Multilanguage Folder has been transferred to the manuals Application Designer's Guide and Upgrade Toolkit.

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