Dimensions that are added in an Excel worksheet are not assigned to the records after you import the Excel worksheet in Microsoft Dynamics NAV 2013

Applies to: Dynamics NAV 2013

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

Symptoms


Assume that you use the Dimensions as Columns column in the Configuration worksheet to fill shortcut dimensions in master data tables by using Microsoft Excel in RapidStart Services for Microsoft Dynamics NAV 2013. In this situation, when you import an Excel worksheet and apply the imported data, the dimensions that are added in the Excel worksheet are not assigned to the records as expected.

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 2013 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. However, 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 ApplyConfigLines function in the codeunit 8611 as follows:
    Existing code
    ...
    PROCEDURE ApplyConfigLines@17(VAR ConfigLine@1003 : Record 8622);
    VAR
    ConfigPackage@1000 : Record 8623;
    ConfigPackageTable@1002 : Record 8613;
    ConfigMgt@1004 : Codeunit 8616;
    Filter@1001 : Text;
    BEGIN
    ConfigLine.FINDFIRST;
    ConfigPackage.GET(ConfigLine."Package Code");
    ConfigPackageTable.SETRANGE("Package Code",ConfigLine."Package Code");

    // Delete the following line.
    Filter := ConfigMgt.MakeTableFilter(ConfigLine);

    IF Filter = '' THEN
    ...
    Replacement code
    ...
    PROCEDURE ApplyConfigLines@17(VAR ConfigLine@1003 : Record 8622);
    VAR
    ConfigPackage@1000 : Record 8623;
    ConfigPackageTable@1002 : Record 8613;
    ConfigMgt@1004 : Codeunit 8616;
    Filter@1001 : Text;
    BEGIN
    ConfigLine.FINDFIRST;
    ConfigPackage.GET(ConfigLine."Package Code");
    ConfigPackageTable.SETRANGE("Package Code",ConfigLine."Package Code");

    // Add the following line.
    Filter := ConfigMgt.MakeTableFilter(ConfigLine,FALSE);

    IF Filter = '' THEN
    ...
  2. Change the code in the MakeTableFilter function in codeunit 8616 as follows:
    Existing code
    ...
    PROCEDURE MakeTableFilter@14(VAR ConfigLine@1000 : Record 8622) Filter : Text;
    BEGIN
    Filter := '';
    IF ConfigLine.FINDSET THEN
    REPEAT
    ConfigLine.CheckBlocked;
    IF (ConfigLine."Table ID" > 0) AND (ConfigLine.Status <= ConfigLine.Status::"In Progress") THEN
    Filter += FORMAT(ConfigLine."Table ID") + '|';
    UNTIL ConfigLine.NEXT = 0;
    IF Filter <> '' THEN
    Filter := COPYSTR(Filter,1,STRLEN(Filter) - 1);

    EXIT(Filter);
    END;
    ...
    Replacement code
    ...
    PROCEDURE MakeTableFilter@14(VAR ConfigLine@1000 : Record 8622;Export@1002 : Boolean) Filter : Text;
    VAR
    AddDimTables@1001 : Boolean;
    BEGIN
    Filter := '';
    IF ConfigLine.FINDSET THEN
    REPEAT
    ConfigLine.CheckBlocked;
    IF (ConfigLine."Table ID" > 0) AND (ConfigLine.Status <= ConfigLine.Status::"In Progress") THEN
    Filter += FORMAT(ConfigLine."Table ID") + '|';
    AddDimTables := AddDimTables OR ConfigLine."Dimensions as Columns";
    UNTIL ConfigLine.NEXT = 0;
    IF AddDimTables AND NOT Export THEN
    Filter += STRSUBSTNO('%1|%2|',DATABASE::"Dimension Value",DATABASE::"Default Dimension");
    IF Filter <> '' THEN
    Filter := COPYSTR(Filter,1,STRLEN(Filter) - 1);

    EXIT(Filter);
    END;
    ...
  3. Change the code in the ExportExcelFromConfig function in codeunit 8618 as follows:
    Existing code
    ...
    PROCEDURE ExportExcelFromConfig@19(VAR ConfigLine@1006 : Record 8622);
    VAR
    ConfigPackageTable@1005 : Record 8613;
    ConfigMgt@1000 : Codeunit 8616;
    FileMgt@1004 : Codeunit 419;
    XLSDataFile@1001 : Text;
    Filter@1003 : Text;
    BEGIN
    XLSDataFile := FileMgt.SaveFileDialog(Text030,'.xlsx','');
    IF XLSDataFile = '' THEN
    EXIT;

    ConfigLine.FINDFIRST;
    ConfigPackageTable.SETRANGE("Package Code",ConfigLine."Package Code");

    // Delete the following line.
    Filter := ConfigMgt.MakeTableFilter(ConfigLine);

    IF Filter <> '' THEN
    ConfigPackageTable.SETFILTER("Table ID",Filter);
    ...
    Replacement code
    ...
    PROCEDURE ExportExcelFromConfig@19(VAR ConfigLine@1006 : Record 8622);
    VAR
    ConfigPackageTable@1005 : Record 8613;
    ConfigMgt@1000 : Codeunit 8616;
    FileMgt@1004 : Codeunit 419;
    XLSDataFile@1001 : Text;
    Filter@1003 : Text;
    BEGIN
    XLSDataFile := FileMgt.SaveFileDialog(Text030,'.xlsx','');
    IF XLSDataFile = '' THEN
    EXIT;

    ConfigLine.FINDFIRST;
    ConfigPackageTable.SETRANGE("Package Code",ConfigLine."Package Code");

    // Add the following line.
    Filter := ConfigMgt.MakeTableFilter(ConfigLine,TRUE);

    IF Filter <> '' THEN
    ConfigPackageTable.SETFILTER("Table ID",Filter);
    ...
To import the Excel worksheet correctly, follow these steps after you apply the code fix:
  1. On the Configuration Worksheet page, add a table that can have shortcut dimensions assigned to it, for example, the G/L Account table (15).
  2. Click Actions, and then click Assign Package.
  3. Create new package, fill in the Code value and the Description value, and then click OK to assign the package to the worksheet line.
  4. On the worksheet line, enable the Dimensions as Columns setting.
  5. In the confirmation dialog box, click OK.
  6. Click Export to Template.
  7. Add a new account at the bottom of the list.

    Note Make sure that you define a number for it.
  8. Define dimensions for the customer in the Dimension columns. They are displayed as the last columns on the spreadsheet.
  9. Save the Excel worksheet, and then import it back to the Configuration Worksheet page by using the Import from Template action on the ribbon.
  10. Click Apply Data.
After you do this, the account that you added in the Excel worksheet is added in Microsoft Dynamics NAV. You can see that the account has shortcut dimensions that you assigned to it in the Excel worksheet.

Note Step 7 is an important step to define the key because the shortcut dimensions will not be created if the key is left blank and assigned automatically by using the No. Series value.

Prerequisites

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

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.