Rapidly Published articles provide information directly from within the Microsoft support organization. The information that is contained herein is created in response to emerging or unique topics, or is intended to supplement other Knowledge Base information.
Microsoft Business Solutions-Navision 4.0 and Microsoft Navision 4.0 are now part of Microsoft Dynamics NAV 4.0. All references to Microsoft Business Solutions-Navision or to Microsoft Navision 4.0 relate to Microsoft Dynamics NAV.
This article applies to Microsoft Dynamics NAV 5.0 for the Spanish (es) language locale.
Symptoms
When you create bills that contain dimensions by posting a cartera bill group directly instead of by posting a journal in the Spanish version of Microsoft Dynamics NAV, the Journal Line Dimension table (356) is unexpectedly populated.
This problem occurs in the following products:
-
The Spanish version of Microsoft Dynamics NAV 2009
-
The Spanish version of Microsoft Dynamics NAV 5.0
-
The Spanish version of Microsoft Dynamics NAV 4.0
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 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 apply this hotfix, follow these steps:
-
Change the code in the InsertGenJournalLine trigger in the Post Payment Order report (7000080) as follows:
Existing code...
ELSE BEGIN
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine,JnlLineDim);
END;
...Replacement code
...
ELSE BEGIN
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine,JnlLineDim);
// Add the following line.
JnlLineDim.DELETEALL;
END;
... -
Change the code in the PostedDoc - OnPostDataItem trigger in the Settle Docs. in Posted PO report (7000082) as follows:
Existing code...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
IF PostedPmtOrd.GET(GenJnlLine."Document No.") THEN
...Replacement code
...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
// Add the following line.
JnlLineDim.DELETEALL;
IF PostedPmtOrd.GET(GenJnlLine."Document No.") THEN
... -
Change the code in the PostedDoc - OnPostDataItem trigger in the Partial Settl.- Receivable report (7000084) as follows:
Existing code...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
UNTIL GenJnlLine.NEXT = 0;
CustLedgEntry.GET(PostedDoc."Entry No.");
...Replacement code
...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
// Add the following line.
JnlLineDim.DELETEALL;
UNTIL GenJnlLine.NEXT = 0;
CustLedgEntry.GET(PostedDoc."Entry No.");
... -
Change the code in the PostedDoc - OnPostDataItem trigger in the Partial Settl. – Payable report (7000085) as follows:
Existing code...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
UNTIL GenJnlLine.NEXT = 0;
VendLedgEntry.GET(PostedDoc."Entry No.");
...Replacement code
...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
// Add the following line.
JnlLineDim.DELETEALL;
UNTIL GenJnlLine.NEXT = 0;
VendLedgEntry.GET(PostedDoc."Entry No.");
... -
Change the code in the PostedDoc - OnPostDataItem trigger in the Settle Docs. in Post. Bill Gr. report (7000098) as follows:
Existing code...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
IF PostedBillGr.GET(GenJnlLine."Document No.") THEN
DocPost.CloseBillGroupIfEmpty(PostedBillGr,PostingDate);
UNTIL GenJnlLine.NEXT = 0;
Window.CLOSE;
...Replacement code
...
IF GenJnlLine.FIND('-') THEN
REPEAT
GenJnlLine2 := GenJnlLine;
GenJnlPostLine.SetFromSettlement(TRUE);
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine2."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine2."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine2."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine2,JnlLineDim);
// Add the following line.
JnlLineDim.DELETEALL;
IF PostedBillGr.GET(GenJnlLine."Document No.") THEN
DocPost.CloseBillGroupIfEmpty(PostedBillGr,PostingDate);
UNTIL GenJnlLine.NEXT = 0;
Window.CLOSE;
... -
Change the code in the InsertGenJournalLine trigger in the Post Bill Group report (7000099) as follows:
Existing code...
IF CurrReport.USEREQUESTFORM THEN
INSERT
ELSE BEGIN
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine,JnlLineDim);
END;
END;
...Replacement code
...
IF CurrReport.USEREQUESTFORM THEN
INSERT
ELSE BEGIN
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine."Journal Batch Name");
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine."Line No.");
GenJnlPostLine.RunWithCheck(GenJnlLine,JnlLineDim);
// Add the following line.
JnlLineDim.DELETEALL;
END;
END;
... -
Change the code in the Code trigger in the Gen. Jnl.-Post Batch codeunit (13) as follows:
Existing code...
IF GenJnlLine3.FINDSET(TRUE,FALSE) THEN
REPEAT
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine3."Line No.");
JnlLineDim.DELETEALL;
GenJnlLine3.DELETE;
...Replacement code
...
IF GenJnlLine3.FINDSET(TRUE,FALSE) THEN
REPEAT
// Add the following lines.
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",GenJnlLine3."Journal Template Name");
JnlLineDim.SETRANGE("Journal Batch Name",GenJnlLine3."Journal Batch Name");
// End of the added lines.
JnlLineDim.SETRANGE("Journal Line No.",GenJnlLine3."Line No.");
JnlLineDim.DELETEALL;
GenJnlLine3.DELETE;
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Spanish version of Microsoft Dynamics NAV 2009 Service Pack 1
-
The Spanish version of Microsoft Dynamics NAV 2009
-
The Spanish version of Microsoft Dynamics NAV 5.0 Service Pack 1
-
The Spanish version of Microsoft Dynamics NAV 4.0 Service pack 3
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.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.
THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
