This article applies to Microsoft Dynamics NAV for the Spanish (es) language locale.

Symptoms

When you run the Navigate function in the Cartera module in the Spanish version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1), you
experience the following issues:

  • When you run the Navigate function for posted bill groups in the Receivables module or for posted payment orders in the Payables module, the related form is not popped up as expected.

  • Assume that you are prompted to run the Navigate function for a payment order in the Payables module. When you try to click Related to Payment Order after you click Related to Document, you receive the following error message:

    There are no posted records with this combination of document number and posting date.

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

  1. Change the code in the controls in the Payment Orders form (7000050) as follow:
    Existing code

    ...
    OnPush=VAR

    Option@1100001 : Integer;

    BEGIN

    //Delete the following lines.
    Option := STRMENU(Text1100000);

    CASE Option OF

    0:EXIT;

    1:CurrForm.Docs.FORM.Navigate;

    2:BEGIN

    Navigate.SetDoc("Posting Date","No.");

    Navigate.RUN;

    END;

    END;
    //End of the lines.

    END;

    }

    }
    ...

    Replacement code

    ...
    OnPush=VAR

    Option@1100001 : Integer;

    BEGIN

    //Add the following line.
    CurrForm.Docs.FORM.Navigate;

    END;

    }

    }
    ...
  2. Change the code in the NavigatePostedDoc function in the CarteraManagement codeunit (7000000) as follows:
    Existing code 1

    ...
    Type::Receivable:

    BEGIN

    IF NOT CustLedgEntry.GET("Entry No.") THEN

    //Delete the following lines.
    Navigate.SetDoc(CustLedgEntry."Posting Date",CustLedgEntry."Document No.");

    EXIT;
    //End of the lines.

    END;

    Type::Payable:

    BEGIN
    ...

    Replacement code 1

    ...
    Type::Receivable:

    BEGIN

    IF NOT CustLedgEntry.GET("Entry No.") THEN

    //Add the following lines.
    EXIT;

    Navigate.SetDoc(CustLedgEntry."Posting Date",CustLedgEntry."Document No.");
    //End of the lines.

    END;

    Type::Payable:

    BEGIN
    ...

    Existing code 2

    ...
    Type::Payable:

    BEGIN

    IF NOT VendLedgEntry.GET("Entry No.") THEN

    //Delete the following lines.
    Navigate.SetDoc(VendLedgEntry."Posting Date",VendLedgEntry."Document No.");

    EXIT;
    //End of the lines.

    END;

    END;

    Navigate.RUN;
    ...

    Replacement code 2

    ...
    Type::Payable:

    BEGIN

    IF NOT VendLedgEntry.GET("Entry No.") THEN

    //Add the following lines.
    EXIT;

    Navigate.SetDoc(VendLedgEntry."Posting Date",VendLedgEntry."Document No.");
    //End of the lines.

    END;

    END;

    Navigate.RUN;
    ...
  3. Change the code in the NavigateClosedDoc function in the CarteraManagement codeunit (7000000) as follows:
    Existing code 1

    ...
    Type::Receivable:

    BEGIN

    IF NOT CustLedgEntry.GET("Entry No.") THEN

    //Delete the following lines.
    Navigate.SetDoc(CustLedgEntry."Posting Date",CustLedgEntry."Document No.");

    EXIT;
    //End of the lines.

    END;

    Type::Payable:

    BEGIN
    ...

    Replacement code 1

    ...
    Type::Receivable:

    BEGIN

    IF NOT CustLedgEntry.GET("Entry No.") THEN

    //Add the following lines.
    EXIT;

    Navigate.SetDoc(CustLedgEntry."Posting Date",CustLedgEntry."Document No.");
    //End of the lines.

    END;

    Type::Payable:

    BEGIN
    ...

    Existing code 2

    ...
    Type::Payable:

    BEGIN

    IF NOT VendLedgEntry.GET("Entry No.") THEN

    //Delete the following lines.
    Navigate.SetDoc(VendLedgEntry."Posting Date",VendLedgEntry."Document No.");

    EXIT;
    //End of the lines.

    END;

    END;

    Navigate.RUN;
    ...

    Replacement code 2

    ...
    Type::Payable:

    BEGIN

    IF NOT VendLedgEntry.GET("Entry No.") THEN

    //Add the following lines.
    EXIT;

    Navigate.SetDoc(VendLedgEntry."Posting Date",VendLedgEntry."Document No.");
    //End of the lines.

    END;

    END;

    Navigate.RUN;
    ...

Prerequisites

You must have the Spanish version of Microsoft Dynamics NAV 2009 Service Pack 1 installed to apply this hotfix.

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?

Thank you for your feedback!

×