The "Delete Invoiced Sales Orders" report (299) and the "Delete Invoiced Purch. Orders" report (499) do not clear linked fields as expected in Microsoft Dynamics NAV 2009

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

Symptoms

Assume that you create a link between a sales order and a purchase order by using the Get Sales Order function in Microsoft Dynamics NAV 2009. You invoice the sales order. In this situation, when you run the "Delete Invoiced Sales Orders" report (299) to delete the sales order, the linked fields are not cleared in the purchase order. Therefore, you cannot delete the purchase order. 
Additionally, if you invoice the purchase order, and then you run the "Delete Invoiced Purch. Orders" report (499) to delete the purchase order, the linked fields in the sales order are also not cleared.
This problem occurs in the following products:

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009 Service Pack 1

Resolution

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 2009 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 the problem, follow these steps:

  1. Change the code in the Data Item Number 1 in the Delete Invoiced Sales Orders report (299) as follows:
    Existing code

    ...
    IF SalesOrderLine.HASLINKS THEN
    SalesOrderLine.DELETELINKS;
    SalesOrderLine.DELETE();
    END ELSE
    AllLinesDeleted := FALSE;
    UNTIL SalesOrderLine.NEXT = 0;

    IF AllLinesDeleted THEN BEGIN
    SalesPost.DeleteHeader(
    "Sales Header",SalesShptHeader,SalesInvHeader,SalesCrMemoHeader,ReturnRcptHeader,
    ...

    Replacement code

    ...
    IF SalesOrderLine.HASLINKS THEN
    SalesOrderLine.DELETELINKS;
    SalesOrderLine.DELETE();
    END ELSE
    AllLinesDeleted := FALSE;

    // Add the following line.
    UpdateAssPurchOrder;

    UNTIL SalesOrderLine.NEXT = 0;

    IF AllLinesDeleted THEN BEGIN
    SalesPost.DeleteHeader(
    "Sales Header",SalesShptHeader,SalesInvHeader,SalesCrMemoHeader,ReturnRcptHeader,
    ...
  2. Change the code in the UpdateAssPurchOrder function in the Delete Invoiced Sales Orders report (299) as follows:
    Existing code

    WhseRequest@1008 : Record 5765;
    SalesPost@1005 : Codeunit 80;
    Window@1004 : Dialog;
    AllLinesDeleted@1006 : Boolean;

    BEGIN
    END.
    }
    RDLDATA
    {

    Replacement code

    WhseRequest@1008 : Record 5765;
    SalesPost@1005 : Codeunit 80;
    Window@1004 : Dialog;
    AllLinesDeleted@1006 : Boolean;

    // Add the following lines.
    LOCAL PROCEDURE UpdateAssPurchOrder@1001();VARPurchLine@1001 : Record 39;
    BEGIN
    IF NOT SalesOrderLine."Special Order" THEN
    EXIT;
    WITH PurchLine DO BEGIN
    RESET;
    SETRANGE("Special Order Sales No.",SalesOrderLine."Document No.");
    SETRANGE("Special Order Sales Line No.",SalesOrderLine."Line No.");
    SETRANGE("Purchasing Code",SalesOrderLine."Purchasing Code");
    IF FINDFIRST THEN BEGIN
    "Special Order Sales No." := '';
    "Special Order Sales Line No." := 0;
    END;
    MODIFY;
    END;
    END;

    BEGIN
    END.
    }
    RDLDATA
    {
  3. Change the code in the Data Item Number 1 in the Delete Invoiced Purch. Orders report (499) as follows:
    Existing code

    ...
    PurchLine.DELETELINKS;

    PurchLine.DELETE;
    END ELSE
    AllLinesDeleted := FALSE;
    UNTIL PurchLine.NEXT = 0;

    IF AllLinesDeleted THEN BEGIN
    PurchPost.DeleteHeader(
    "Purchase Header",PurchRcptHeader,PurchInvHeader,PurchCrMemoHeader,
    ...

    Replacement code

    ...
    PurchLine.DELETELINKS;

    PurchLine.DELETE;
    END ELSE
    AllLinesDeleted := FALSE;

    // Add the following line.
    UpdateAssSalesOrder;

    UNTIL PurchLine.NEXT = 0;

    IF AllLinesDeleted THEN BEGIN
    PurchPost.DeleteHeader(
    "Purchase Header",PurchRcptHeader,PurchInvHeader,PurchCrMemoHeader,
    ...
  4. Change the code in the UpdateAssPurchOrder function in the Delete Invoiced Purch. Orders report (499) as follows:
    Existing code

    WhseRequest@1007 : Record 5765;
    PurchPost@1012 : Codeunit 90;
    Window@1004 : Dialog;
    AllLinesDeleted@1006 : Boolean;

    BEGIN
    END.
    }
    RDLDATA
    {

    Replacement code

    WhseRequest@1007 : Record 5765;
    PurchPost@1012 : Codeunit 90;
    Window@1004 : Dialog;
    AllLinesDeleted@1006 : Boolean;

    // Add the following lines.
    LOCAL PROCEDURE UpdateAssSalesOrder@1001();
    VAR
    SaleLine@1001 : Record 37;
    BEGIN
    IF NOT PurchLine."Special Order" THEN
    EXIT;
    WITH SaleLine DO BEGIN
    RESET;
    SETRANGE("Special Order Purchase No.",PurchLine."Document No.");
    SETRANGE("Special Order Purch. Line No.",PurchLine."Line No.");
    SETRANGE("Purchasing Code",PurchLine."Purchasing Code");
    IF FINDFIRST THEN BEGIN
    "Special Order Purchase No." := '';
    "Special Order Purch. Line No." := 0;
    END;
    MODIFY;
    END;
    END;

    BEGIN
    END.
    }
    RDLDATA
    {

Prerequisites

You must have one of the following products installed to apply this hotfix:

  • Microsoft Dynamics NAV 2009 R2

  • Microsoft Dynamics NAV 2009 Service Pack 1

Removal information

You cannot remove this hotfix.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×