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. "Please specify a filter for the Liquidity Date field in the Liquidity Analysis View Entry table" error message when you run the Export to Excel function in the "Liq. Analysis by Dimension" dialog box in the Swiss version of Microsoft Dynamics NAV 5.0 SP1

"Please specify a filter for the Liquidity Date field in the Liquidity Analysis View Entry table" error message when you run the Export to Excel function in the "Liq. Analysis by Dimension" dialog box in the Swiss version of Microsoft Dynamics NAV 5.0 SP1

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the following countries and language locales.
  • French (Switzerland) (fr-ch)
  • German (Switzerland) (gr-ch)
  • Italian (Switzerland) (it-ch)

↑ Back to the top

Symptoms

When you run the Export to Excel function in the Liq. Analysis by Dimension dialog box that has a date filter specified in the Swiss version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1), you receive the following error message:
Please specify a filter for the Liquidity Date field in the Liquidity Analysis View Entry table.
For information about entering filters, see the online Help.

↑ 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 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 SetCommonFilters function in the "Liq. Analysis by Dimensions" form (5055285) as follows: 
    Existing code
    ...
    SETFILTER("Liquidity No.",LiquidityFilter);
    IF LiqAccFilter <> '' THEN
    SETFILTER("Liquidity Account No.",LiqAccFilter);
    // dach0002.begin
    // SETFILTER("Liquidity Date",DateFilter2);

    // Delete the following lines.
    IF DateFilter = '' THEN
    SETFILTER("Liquidity Date",DateFilter);
    // End of the lines.

    // dach0002.end
    IF Dim1Filter <> '' THEN
    SETFILTER("Dimension 1 Value Code",Dim1Filter);
    IF Dim2Filter <> '' THEN
    SETFILTER("Dimension 2 Value Code",Dim2Filter);
    ...
    Replacement code
    ...
    SETFILTER("Liquidity No.",LiquidityFilter);
    IF LiqAccFilter <> '' THEN
    SETFILTER("Liquidity Account No.",LiqAccFilter);
    // dach0002.begin
    // SETFILTER("Liquidity Date",DateFilter2);

    // Add the following lines.
    IF DateFilter = '' THEN
    SETFILTER("Liquidity Date",DateFilter);
    // End of the lines.

    // dach0002.end
    IF Dim1Filter <> '' THEN
    SETFILTER("Dimension 1 Value Code",Dim1Filter);
    IF Dim2Filter <> '' THEN
    SETFILTER("Dimension 2 Value Code",Dim2Filter);
    ...
  2. Change the code in the CreateFile function in the Export Liquidity Analysis View codeunit (5055267) as follows:
    Existing code 1
    ...
    Line[1] := CONVERTSTR(Line[1],CharsNavision,CharsWindows);
    TextFile.WRITE(Line[1]);
    StartDate := "Liquidity Date";
    IF (DateFilter <> '') THEN BEGIN
    MaxDate := GETRANGEMAX("Liquidity Date");

    // Delete the following line.
    SETFILTER("Liquidity Date",'<=%1',MaxDate);

    END;
    SETFILTER("Liquidity No.",LiquidityFilter);
    IF FIND('-') THEN
    REPEAT
    IF ("Liquidity Date" = NORMALDATE("Liquidity Date")) THEN BEGIN
    ...
    Replacement code 1
    ...
    Line[1] := CONVERTSTR(Line[1],CharsNavision,CharsWindows);
    TextFile.WRITE(Line[1]);
    StartDate := "Liquidity Date";
    IF (DateFilter <> '') THEN BEGIN
    MaxDate := GETRANGEMAX("Liquidity Date");

    // Add the following line.
    SETFILTER("Liquidity Date",'%1..%2',GETRANGEMIN("Liquidity Date"),MaxDate);

    END;
    SETFILTER("Liquidity No.",LiquidityFilter);
    IF FIND('-') THEN
    REPEAT
    IF ("Liquidity Date" = NORMALDATE("Liquidity Date")) THEN BEGIN
    ...
    Existing code 2
    ...
    CharsNavision,CharsWindows);
    TextFile.WRITE(Tab + Tab + Tab + Tab + Line[1] + Line2);
    END;
    UNTIL TempDimValue2.NEXT = 0;
    END;

    // Delete the following lines.
    WeekNo := DATE2DWY(StartDate,2);
    Year := DATE2DWY(StartDate,3);
    StartDate := DWY2DATE(1,WeekNo,Year);
    // End of the lines.

    Line2 := '';
    FOR i := 1 TO NoOfColumns DO
    Line2 := Line2 + Tab;

    WHILE StartDate <= EndDate DO BEGIN
    ...
    Replacement code 2
    ...
    CharsNavision,CharsWindows);
    TextFile.WRITE(Tab + Tab + Tab + Tab + Line[1] + Line2);
    END;
    UNTIL TempDimValue2.NEXT = 0;
    END;

    // Add the following lines.
    WeekNo := DATE2DMY(StartDate,2);
    Year := DATE2DMY(StartDate,3);
    StartDate := DMY2DATE(1,WeekNo,Year);
    // End of the lines.

    Line2 := '';
    FOR i := 1 TO NoOfColumns DO
    Line2 := Line2 + Tab;

    WHILE StartDate <= EndDate DO BEGIN
    ...
Note This resolution is valid for all the versions of Microsoft Dynamics NAV 5.0 Service Pack 1 that contain the Liquidity module.

Prerequisites

You must have the Swiss version of Microsoft Dynamics NAV 5.0 Service Pack 1 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: kbmbscodefix, kberrmsg, kbnoloc, kbsurveynew, kbmbsquickpub, kbmbspartner, kb, kbqfe, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2664516
Revision : 1
Created on : 1/7/2017
Published on : 1/31/2012
Exists online : False
Views : 241