The purchase advance letter line is not deleted when you delete the purchase advance letter in the Czech version of Microsoft Dynamics NAV 5.0 Service Pack 1 with Feature Pack 1 installed

Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:

• The Modify permission for the object that you will be changing.

• The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.

Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, follow these steps:

1. Add a local variable in the OnDelete trigger in the Sales Advance Letter Hearder table (26585), and then specify the variable as follows:

   • Name: SalesHeader

   • DataType: Record

   • Subtype: Sales Header

   
   

2. Add a local variable in the OnDelete trigger in the Sales Advance Letter Hearder table (26585), and then specify the variable as follows:

   • Name: AdvLetterHeader2

   • DataType: Record

   • Subtype: Sales Advance Letter Header

3. Add a local variable in the OnDelete trigger in the Sales Advance Letter Hearder table (26585), and then specify the variable as follows:

   • Name: ReleaseSalesDoc

   • DataType: Codeunit

   • Subtype: Release Sales Document

4. Change the code in the OnDelete trigger in the Sales Advance Letter Hearder table (26585) as follows:
   Existing code

   DimMgt.DeleteDocDim(DATABASE::"Sales Advance Letter Header",0,"No.",0);
   
   DeleteLetterLines;

   ...
   

   Replacement code

   //Add the following lines.AdvLetterHeader2.SETRANGE("Order No.","Order No.");
   AdvLetterHeader2.SETFILTER("No.",'<>%1',"No.");
   IF AdvLetterHeader2.ISEMPTY THEN 
   IF SalesHeader.GET(SalesHeader."Document Type"::Order,"Order No.") THEN 
   ReleaseSalesDoc.Reopen(SalesHeader); 
   //End of the lines.
   
   DimMgt.DeleteDocDim(DATABASE::"Sales Advance Letter Header",0,"No.",0);
   
   DeleteLetterLines;
   ...

5. Add a local variable in the OnDelete trigger in the Purch. Advance Letter Hearder table (26587), and then specify the variable as follows:

   • Name: PurchHeader

   • DataType: Record

   • Subtype: Purchase Header

6. Add a local variable in the OnDelete trigger in the Purch. Advance Letter Hearder table (26587), and then specify the variable as follows:

   • Name: AdvLetterHeader2

   • DataType: Record

   • Subtype: Purch. Advance Letter Header

7. Add a local variable in the OnDelete trigger in the Purch. Advance Letter Hearder table (26587), and then specify the variable as follows:

   • Name: ReleasePurchDoc

   • DataType: Codeunit

   • Subtype: Release Purchase Document

8. Change the code in the OnDelete trigger in the Purch. Advance Letter Hearder table (26587) as follows:
   Existing code

   DimMgt.DeleteDocDim(DATABASE::"Purch. Advance Letter Header",0,"No.",0);
   
   DeleteLetterLines;...

   Replacement code

   //Add the following lines.AdvLetterHeader2.SETRANGE("Order No.","Order No."); 
   AdvLetterHeader2.SETFILTER("No.",'<>%1',"No."); 
   IF AdvLetterHeader2.ISEMPTY THEN 
   IF PurchHeader.GET(PurchHeader."Document Type"::Order,"Order No.") THEN 
   ReleasePurchDoc.Reopen(PurchHeader); 
   //End of the lines.
   
   DimMgt.DeleteDocDim(DATABASE::"Purch. Advance Letter Header",0,"No.",0);
   
   DeleteLetterLines;
   ...

9. Change the LetterLine local variable in the DeleteLetterLines function in the Purch. Advance Letter Hearder table (26587) as follows:

   • Name: LetterLine

   • DataType: Record

   • Subtype: Purch. Advance Letter Line