This article applies to Microsoft Dynamics NAV for the Netherlands (nl) language locale.

Symptoms

Assume that you set a global dimension in a bank account in the Dutch version of Microsoft Dynamics NAV. When you create a Telebank proposal that uses the bank account, the global dimension is not transferred to the Telebank proposal. This problem occurs in the following products:

  • The Dutch version of Microsoft Dynamics NAV 2009 R2

  • The Dutch version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

  • The Dutch version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)

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. Add a new local variable in the OnInsert trigger in the Proposal Line table (11000000), and then specify the variable as follows:

    • Name: FDBR

    • DataType: Record

    • Subtype: Gen. Journal Line

  2. Add a new local variable in the OnInsert trigger in the Proposal Line table (11000000), and then specify the variable as follows:

    • Name: TableID

    • DataType: ARRAY [10] OF Integer

  3. Add a new local variable in the OnInsert trigger in the Proposal Line table (11000000), and then specify the variable as follows:

    • Name: No

    • DataType: ARRAY [10] OF Code

    • Length: 20

  4. Change the code in the OnInsert trigger in the Proposal Line table (11000000) as follows: Existing code

    ...InitRecord;DimManagement.InsertJnlLineDim(DATABASE::"Proposal Line","Our Bank No.",'',"Line No.",0,"Shortcut Dimension 1 Code","Shortcut Dimension 2 Code");...

    Replacement code

    ...InitRecord;DimManagement.InsertJnlLineDim(DATABASE::"Proposal Line","Our Bank No.",'',"Line No.",0,"Shortcut Dimension 1 Code","Shortcut Dimension 2 Code");// Add the following lines.TableID[1] := DimManagement.TypeToTableID1(FDBR."Account Type"::"Bank Account"); No[1] := "Our Bank No."; "Shortcut Dimension 1 Code" := ''; "Shortcut Dimension 2 Code" := ''; DimManagement.GetDefaultDim( TableID,No,'',"Shortcut Dimension 1 Code","Shortcut Dimension 2 Code"); DimManagement.InsertJnlLineDim(DATABASE::"Proposal Line", "Our Bank No.",'',0,0, "Shortcut Dimension 1 Code","Shortcut Dimension 2 Code"); // End of the lines....
  5. Add a new local variable in the OnDelete trigger in the Proposal Line table (11000000), and then specify the variable as follows:

    • Name: ProposalLine

    • DataType: Record

    • Subtype: Proposal Line

  6. Change the code in the OnDelete trigger in the Proposal Line table (11000000) as follows: Existing code

    ...DetailFilter("Detail line",Rec);"Detail line".DELETEALL(FALSE);DimManagement.DeleteJnlLineDim(DATABASE::"Proposal Line","Our Bank No.",'',"Line No.",0);...

    Replacement code

    ...DetailFilter("Detail line",Rec);"Detail line".DELETEALL(FALSE);DimManagement.DeleteJnlLineDim(DATABASE::"Proposal Line","Our Bank No.",'',"Line No.",0);// Add the following lines.ProposalLine.SETFILTER("Line No.",'<>%1',"Line No.");ProposalLine.SETFILTER("Our Bank No.","Our Bank No."); IF ProposalLine.ISEMPTY THEN DimManagement.DeleteJnlLineDim(DATABASE::"Proposal Line", "Our Bank No.",'',0,0); // End of the lines....
  7. Add a new local variable in the CreatePaymentHistoryLine function in the Process Proposal Lines codeunit (11000000), and then specify the variable as follows:

    • Name: FromBankJnlDim

    • DataType: Record

    • Subtype: Journal Line Dimension

  8. Add a new local variable in the CreatePaymentHistoryLine function in the Process Proposal Lines codeunit (11000000), and then specify the variable as follows:

    • Name: ToBankJnlDim

    • DataType: Record

    • Subtype: Journal Line Dimension

  9. Change the code in the CreatePaymentHistoryLine function in the Process Proposal Lines codeunit (11000000) as follows: Existing code

    ...DimManagement.CopyJnlLineDimToOtherJnlLnDim(FromJnlDim, ToJnlDim);PaymentHistLine."Global Dimension 1 Code" := Propline."Shortcut Dimension 1 Code";...

    Replacement code

    ...DimManagement.CopyJnlLineDimToOtherJnlLnDim(FromJnlDim, ToJnlDim);// Add the following lines.DimManagement.DeleteJnlLineDim(DATABASE::"Payment History", PaymHist."Our Bank",PaymHist."Run No.",0,0); FromBankJnlDim.SETRANGE("Table ID",DATABASE::"Proposal Line");FromBankJnlDim.SETRANGE("Journal Template Name",Propline."Our Bank No."); FromBankJnlDim.SETRANGE("Journal Line No.",0);ToBankJnlDim."Table ID" := DATABASE::"Payment History";ToBankJnlDim."Journal Template Name" := PaymHist."Our Bank";ToBankJnlDim."Journal Batch Name" := PaymHist."Run No.";ToBankJnlDim."Journal Line No." := 0;DimManagement.CopyJnlLineDimToOtherJnlLnDim(FromBankJnlDim,ToBankJnlDim);// End of the lines.PaymentHistLine."Global Dimension 1 Code" := Propline."Shortcut Dimension 1 Code";...

Prerequisites

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

  • The Dutch version of Microsoft Dynamics NAV 2009 R2

  • The Dutch version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

  • The Dutch version of Microsoft Dynamics NAVĀ 5.0 Service Pack 1 (SP1)

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?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.