The linked Value entries for some G/L entries are not displayed as expected after you upgrade the Czech version of Microsoft Dynamics NAV 4.0 SP3 to the Czech version of Microsoft Dynamics NAV 5.0 SP1

This article applies to Microsoft Dynamics NAV for the Czech (cz) language locale.

Assume that you upgrade the Czech version of Microsoft Dynamics NAV 4.0 Service Pack 3 (SP3) to the Czech version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1). When you review a Value entry in version 5.0, you can select Entry – General Ledger to follow the related General Ledger entries. However, when you review a Value entry from before upgrade, you notice that some related G/L entries are missing.

The upgrade toolkit does not transfer all relationships between Value entries and G/L entries in the Czech database.

Symptoms

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.

Resolution



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 UpdateGLEntry function in Upgrade 5.00 Step 1 codeunit (104045) as follows:
    Existing code

    ...
    IF FINDSET(TRUE) THEN

    REPEAT

    StateIndicator.Update;


    IF GLEntry."Value Entry No." <> 0 THEN BEGIN

    GLEntry."Value Entry No." := 0;

    GLEntry.MODIFY;


    END;

    UNTIL NEXT = 0;

    TimeLog.TimeLogInsert(TimeLog,TABLENAME,FALSE);
    ...

    Replacement code

    ...
    IF FINDSET(TRUE) THEN

    REPEAT

    StateIndicator.Update;


    IF "Value Entry No." <> 0 THEN BEGIN

    InsertTempGLItemLedgRelation("Entry No.","Value Entry No.");

    "Value Entry No." := 0;

    MODIFY;


    END;

    UNTIL NEXT = 0;

    TimeLog.TimeLogInsert(TimeLog,TABLENAME,FALSE);
    ...
  2. Change the code in the UpdateValueEntry function in Upgrade 5.00 Step 1 codeunit (104045) as follows:
    Existing code

    ...
    REPEAT

    StateIndicator.Update;

    ModifyEntry := FALSE;


    IF "G/L Entry No. (Account)" <> 0 THEN BEGIN

    InsertTempGLItemLedgRelation("G/L Entry No. (Account)","Entry No.");

    ModifyEntry := TRUE;

    END;

    IF "G/L Entry No. (Bal. Account)" <> 0 THEN BEGIN

    InsertTempGLItemLedgRelation("G/L Entry No. (Bal. Account)","Entry No.");

    ModifyEntry := TRUE;

    END;

    IF "G/L Entry No. (Interim Acc.)" <> 0 THEN BEGIN

    InsertTempGLItemLedgRelation("G/L Entry No. (Interim Acc.)","Entry No.");

    ModifyEntry := TRUE;

    END;

    IF "G/L Entry No. (Int. Bal. Acc.)" <> 0 THEN BEGIN

    InsertTempGLItemLedgRelation("G/L Entry No. (Int. Bal. Acc.)","Entry No.");


    ModifyEntry := TRUE;

    END;
    ...

    Replacement code

    ...
    REPEAT

    StateIndicator.Update;

    ModifyEntry := FALSE;


    IF ("G/L Entry No. (Account)" <> 0) OR

    ("G/L Entry No. (Bal. Account)" <> 0) OR

    ("G/L Entry No. (Interim Acc.)" <> 0) OR

    ("G/L Entry No. (Int. Bal. Acc.)" <> 0)

    THEN BEGIN

    "G/L Entry No. (Account)" := 0;

    "G/L Entry No. (Bal. Account)" := 0;

    "G/L Entry No. (Interim Acc.)" := 0;

    "G/L Entry No. (Int. Bal. Acc.)" := 0;


    ModifyEntry := TRUE;

    END;
    ...
  3. Change the code in the InsertTempGLItemLedgRelation function in Upgrade 5.00 Step 1 codeunit (104045) as follows:
    Existing code

    ...
    END;

    END;


    LOCAL PROCEDURE InsertTempGLItemLedgRelation@3(VAR GLEntryNo@1000 : Integer;ValueEntryNo@1001 : Integer) : Boolean;


    VAR

    TempGLItemLedgRelation@1002 : Record 104050;

    BEGIN
    ...

    Replacement code

    ...
    END;

    END;


    LOCAL PROCEDURE InsertTempGLItemLedgRelation@3(GLEntryNo@1000 : Integer;ValueEntryNo@1001 : Integer) : Boolean;


    VAR

    TempGLItemLedgRelation@1002 : Record 104050;

    BEGIN
    ...
  4. Change the code in the InsertTempGLItemLedgRelation function in Upgrade 5.00 Step 1 codeunit (104045) as follows:
    Existing code

    ...
    TempGLItemLedgRelation."G/L Entry No." := GLEntryNo;

    TempGLItemLedgRelation."Value Entry No." := ValueEntryNo;

    IF TempGLItemLedgRelation.INSERT THEN;

    // Delete the following line.
    GLEntryNo := 0;
    // End of the deleted line.

    END;
    ...

    Replacement code

    ...
    TempGLItemLedgRelation."G/L Entry No." := GLEntryNo;

    TempGLItemLedgRelation."Value Entry No." := ValueEntryNo;

    IF TempGLItemLedgRelation.INSERT THEN;

    END;
    ...


Prerequisites

You must have the Czech version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1) installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

VSTF Dynamics NAVSE bug number: 208170

References

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

Status

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?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×