Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. An error occurs when you run the Calculate Counting Period function in the "Phsy. Inventory Journal" dialog box in the RoleTailored client in Microsoft Dynamics NAV 2009

An error occurs when you run the Calculate Counting Period function in the "Phsy. Inventory Journal" dialog box in the RoleTailored client in Microsoft Dynamics NAV 2009

View products that this article applies to.

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

↑ Back to the top

Symptoms

When you run the Calculate Counting Period function that has dimensions selected in the Phsy. Inventory Journal dialog box in the RoleTailored client (RTC) in Microsoft Dynamics NAV 2009, you receive the following error message:
Another user has modified the selected dimensions for the Retain Dimensions field after you retrieved it from the database. Enter your changes again in the Dimension Selection window by clicking the Assist Button on the Retain Dimensions field.

↑ Back to the top

Cause

This problem occurs because the request page does not have the SaveValues property. Therefore, the request page cannot save any dimension values that are previously used. However, the classic client and the RTC in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1) or a later version have the SaveValues property.

↑ Back to the top

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.

↑ Back to the top



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 CreatePhysInvtItemJnl function in the "Phys. Invt. Count.-Management" codeunit (7380) as follows: 
    Existing code
    ...
    IF PhysInvtCountRep.GetRequest(
    PostingDate,DocNo,SortingMethod,PrintDoc,PrintDocPerItem,ZeroQty,PrintQtyCalculated)
    THEN BEGIN
    Window.OPEN(Text000,TempPhysInvtItemSel."Item No.");
    REPEAT
    Window.UPDATE;
    CalcQtyOnHand.InitializeRequest(PostingDate,DocNo,ZeroQty);
    CalcQtyOnHand.SetItemJnlLine(ItemJnlLine);
    CalcQtyOnHand.InitializePhysInvtCount(
    TempPhysInvtItemSel."Phys Invt Counting Period Code",
    TempPhysInvtItemSel."Phys Invt Counting Period Type");
    ...
    Replacement code
    ...
    IF PhysInvtCountRep.GetRequest(
    PostingDate,DocNo,SortingMethod,PrintDoc,PrintDocPerItem,ZeroQty,PrintQtyCalculated)
    THEN BEGIN
    Window.OPEN(Text000,TempPhysInvtItemSel."Item No.");
    REPEAT
    Window.UPDATE;

    // Add the following line.
    CalcQtyOnHand.SetSkipDim(TRUE); 

    CalcQtyOnHand.InitializeRequest(PostingDate,DocNo,ZeroQty);
    CalcQtyOnHand.SetItemJnlLine(ItemJnlLine);
    CalcQtyOnHand.InitializePhysInvtCount(
    TempPhysInvtItemSel."Phys Invt Counting Period Code",
    TempPhysInvtItemSel."Phys Invt Counting Period Type");
    ...
  2. Change the code in the Calculate Inventory report (790) as follows: 
    Existing code
    ...
    PROPERTIES
    {
    ProcessingOnly=Yes;
    OnPreReport=BEGIN

    // Delete the following line.
    DimSelectionBuf.CompareDimText(3,REPORT::"Calculate Inventory",'',ColumnDim,Text003);

    ZeroQtySave := ZeroQty;
    END;

    }
    ...
    Replacement code
    ...
    PROPERTIES
    {
    ProcessingOnly=Yes;
    OnPreReport=BEGIN

    // Add the following lines.
    IF SkipDim THEN
    ColumnDim := ''
    ELSE
    DimSelectionBuf.CompareDimText(3,REPORT::"Calculate Inventory",'',ColumnDim,Text003);
    // End of the lines.

    ZeroQtySave := ZeroQty;
    END;

    }
    ...
  3. Change the code in the Item - OnPreDataItem trigger in the Calculate Inventory report (790) as follows:
    Existing code
    ...
    IF NOT HideValidationDialog THEN
    Window.OPEN(Text002,Item."No.");

    // Delete the following line.
    SelectedDim.GetSelectedDim(USERID,3,REPORT::"Calculate Inventory",'',TempSelectedDim);

    END;

    OnAfterGetRecord=BEGIN
    IF NOT HideValidationDialog THEN
    Window.UPDATE;
    END;

    ReqFilterFields=No.,Location Filter,Bin Filter;
    ...
    Replacement code
    ...
    IF NOT HideValidationDialog THEN
    Window.OPEN(Text002,Item."No.");

    // Add the following lines.
    IF NOT SkipDim THEN
    SelectedDim.GetSelectedDim(USERID,3,REPORT::"Calculate Inventory",'',TempSelectedDim);
    // End of the lines.

    END;

    OnAfterGetRecord=BEGIN
    IF NOT HideValidationDialog THEN
    Window.UPDATE;
    END;

    ReqFilterFields=No.,Location Filter,Bin Filter;
    ...
  4. Change the code in the Global Variables in the Calculate Inventory report (790) as follows:
    Existing code
    ...
    HideValidationDialog@1028 : Boolean;
    AdjustPosQty@1036 : Boolean;
    ItemTrackingSplit@1006 : Boolean;
    ColumnDim@1027 : Text[250];
    PosQty@1031 : Decimal;
    NegQty@1032 : Decimal;
    Text004@1025 : TextConst 'ENU=You must not filter on dimensions if you calculate locations with %1 is %2.';
    ...
    Replacement code
    ...
    HideValidationDialog@1028 : Boolean;
    AdjustPosQty@1036 : Boolean;
    ItemTrackingSplit@1006 : Boolean;

    // Add the following line.
    SkipDim@1037 : Boolean;

    ColumnDim@1027 : Text[250];
    PosQty@1031 : Decimal;
    NegQty@1032 : Decimal;
    Text004@1025 : TextConst 'ENU=You must not filter on dimensions if you calculate locations with %1 is %2.';
    ...
  5. Change the code in the InitializeRequest function in the Calculate Inventory report (790) as follows:
    Existing code
    ...
    PostingDate := NewPostingDate;
    NextDocNo := DocNo;
    ZeroQty := ItemsNotOnInvt;
    ColumnDim := DimSelectionBuf.GetDimSelectionText(3,REPORT::"Calculate Inventory",'');
    ...
    Replacement code
    ...
    PostingDate := NewPostingDate;
    NextDocNo := DocNo;
    ZeroQty := ItemsNotOnInvt;

    // Add the following lines.
    IF NOT SkipDim THEN
    ColumnDim := DimSelectionBuf.GetDimSelectionText(3,REPORT::"Calculate Inventory",'');
    // End of the lines.
    ...
  6. Add a new SetSkipDim function in the in the Calculate Inventory report (790) as follows: 
    PROCEDURE SetSkipDim@8(NewSkipDim@1000 : Boolean);
    BEGIN
    SkipDim := NewSkipDim;
    END;
You may also upgrade from Microsoft Dynamics NAV 2009 to Microsoft Dynamics NAV 2009 SP1 or Microsoft Dynamics NAV 2009 R2 to resolve this problem.

Prerequisites

You must have Microsoft Dynamics NAV 2009 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

↑ Back to the top

Status

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

↑ Back to the top

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.

↑ Back to the top

Keywords: kberrmsg, kbmbscodefix, kbnoloc, kbsurveynew, kbqfe, kbmbspartner, kbmbsquickpub, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2620233
Revision : 1
Created on : 1/7/2017
Published on : 11/18/2011
Exists online : False
Views : 233