Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

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 for the Spanish (es) language locale.

Symptoms

When you run the Make 347 Declaration report in the Spanish version of Microsoft Dynamics NAV, special characters are not converted to regular characters.

Note All special characters will be converted to regular characters. The characters of á, é, í, ó, ú, ä, ë, ï, ö, ø and ü should be converted to the characters of a, e, i, o and u. Other characters, such as ’, ”, &, $, ( and ), should be converted to spaces. Character ñ should be converted to ASCII 209 and character Ç should be converted to ASCII 199. Any other character that differs from a character from a to z and from A to Z should be converted to a blank. Additionally, a minus sign (-) should be converted to a blank.

This problem occurs in the following products:

  • 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

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:

  1. Change the code in the Data Item Number 2 object in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    GLEntry3@1100000 : Record 17;
    BEGIN
    VATRegNo347 := PADSTR(COPYSTR(DELCHR("VAT Registration No.",'=','.-/'),1,9),9,' ');

    // Delete the following lines.
    Name347 := PADSTR(Name,40,' ');
    Name347 := CONVERTSTR(UPPERCASE(Name347),'µ•ÔÖÞàãé륚()"&ï',Text1100003);
    // End of the lines.

    PostCode347 := PADSTR(StatementNo("Post Code"),5,' ');
    CountryCity := COPYSTR(PostCode347,1,2)+ ' ';
    IF Customer."Country Code" <> '' THEN BEGIN
    ...

    Replacement code

    ...
    GLEntry3@1100000 : Record 17;
    BEGIN
    VATRegNo347 := PADSTR(COPYSTR(DELCHR("VAT Registration No.",'=','.-/'),1,9),9,' ');

    // Add the following line.
    Name347 := PADSTR(FormatTextName(Name),40,' ');
    // End of the line.

    PostCode347 := PADSTR(StatementNo("Post Code"),5,' ');
    CountryCity := COPYSTR(PostCode347,1,2)+ ' ';
    IF Customer."Country Code" <> '' THEN BEGIN
    ...
  2. Change the code in the Data Item Number 2 Sections object in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    ELSE
    CashAmtText := PADSTR('',15,'0');
    OutText :=

    // Delete the following line.
    '2347' + FiscalYear + VATRegNo + VATRegNo347 + PADSTR('',9,' ') +UPPERCASE(Name347) + Text1100002 +
    // End of the line.
    .
    COPYSTR(PostCode347,1,2) + PADSTR('',3,' ') + Text1100008 + CONVERTSTR(AmountText,' ','0') + PADSTR('',2,' ') +
    CashAmtText + PADSTR('',15,'0') + PADSTR('', 371, ' ');
    ...

    Replacement code

    ...
    ELSE
    CashAmtText := PADSTR('',15,'0');
    OutText :=

    // Add the following line.
    '2347' + FiscalYear + UPPERCASE(VATRegNo) + UPPERCASE(VATRegNo347) + PADSTR('',9,' ') +UPPERCASE(Name347) + Text1100002 +
    // End of the line.

    COPYSTR(PostCode347,1,2) + PADSTR('',3,' ') + Text1100008 + CONVERTSTR(AmountText,' ','0') + PADSTR('',2,' ') +
    CashAmtText + PADSTR('',15,'0') + PADSTR('', 371, ' ');
    ...
  3. Change the code in the Data Item Number 5 object in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    OnAfterGetRecord=BEGIN
    VATRegNo347 := PADSTR(COPYSTR(DELCHR("VAT Registration No.",'=','.-/'),1,9),9,' ');

    // Delete the following lines.
    Name347 := PADSTR(Name,40,' ');
    Name347 := CONVERTSTR(UPPERCASE(Name347),'µ•ÔÖÞàãé륚()"&ï',Text1100003);
    // End of the lines.

    PostCode347 := PADSTR(StatementNo("Post Code"),5,' ');
    CountryCity := COPYSTR(PostCode347,1,2)+ ' ';
    IF Vendor."Country Code"<>'' THEN BEGIN
    ...

    Replacement code

    ...
    OnAfterGetRecord=BEGIN
    VATRegNo347 := PADSTR(COPYSTR(DELCHR("VAT Registration No.",'=','.-/'),1,9),9,' ');

    // Add the following line.
    Name347 := PADSTR(FormatTextName(Name),40,' ');
    // End of the line.

    PostCode347 := PADSTR(StatementNo("Post Code"),5,' ');
    CountryCity := COPYSTR(PostCode347,1,2)+ ' ';
    IF Vendor."Country Code"<>'' THEN BEGIN
    ...
  4. Change the code in the Data Item Number 5 Sections object in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    CLEAR(OutText);
    AmountText := AmtEuro(PurchasesAmt);
    OutText :=

    // Delete the following line.
    '2347' + FiscalYear + VATRegNo + VATRegNo347 + PADSTR('',9,' ') +UPPERCASE(Name347) + Text1100002 +
    // End of the line.

    COPYSTR(PostCode347,1,2) + PADSTR('',3,' ') + Text1100011 + CONVERTSTR(AmountText,' ','0') + PADSTR('',2,' ') +
    PADSTR('',15,'0') + PADSTR('',15,'0') + PADSTR('', 371, ' ');
    ...

    Replacement code

    ...
    CLEAR(OutText);
    AmountText := AmtEuro(PurchasesAmt);
    OutText :=

    // Add the following line.
    '2347' + FiscalYear + UPPERCASE(VATRegNo) + UPPERCASE(VATRegNo347) + PADSTR('',9,' ') +UPPERCASE(Name347) + Text1100002 +
    // End of the line.

    COPYSTR(PostCode347,1,2) + PADSTR('',3,' ') + Text1100011 + CONVERTSTR(AmountText,' ','0') + PADSTR('',2,' ') +
    PADSTR('',15,'0') + PADSTR('',15,'0') + PADSTR('', 371, ' ');
    ...
  5. Change the code of the global variables in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    CODE
    {
    VAR

    // Delete the following lines.
    Text1100001@1100058 : TextConst 'ENU="AAEEIIOOUUÑU ";ESP="AAEEIIOOUUÑU "';
    Text1100002@1100059 : TextConst 'ENU=D;ESP=D';
    Text1100003@1100060 : TextConst 'ENU="AAEEIIOOUUÑU ";ESP="AAEEIIOOUUÑU "';
    Text1100004@1100061 : TextConst 'ENU=<Integer>;ESP=<Integer>';
    Text1100005@1100062 : TextConst 'ENU="AAEEIIOOUU¥U ";ESP="AAEEIIOOUU¥U "';
    // End of the lines.

    Text1100006@1100063 : TextConst 'ENU=Postal Code is missing in customer''s card %1;ESP=Falta el c¢digo postal en la ficha del cliente %1';
    Text1100008@1100065 : TextConst 'ENU=B;ESP=B';
    Text1100009@1100066 : TextConst 'ENU=Postal Code is missing in vendor''s card %1;ESP=Falta el c¢digo postal en la ficha del proveedor %1';
    ...

    Replacement code

    ...
    CODE
    {
    VAR

    // Add the following lines.
    Text1100002@1100059 : TextConst 'ENU=D;ESP=D';
    Text1100004@1100061 : TextConst 'ENU=<Integer>;ESP=<Integer>';
    // End of the lines.

    Text1100006@1100063 : TextConst 'ENU=Postal Code is missing in customer''s card %1;ESP=Falta el c¢digo postal en la ficha del cliente %1';
    Text1100008@1100065 : TextConst 'ENU=B;ESP=B';
    Text1100009@1100066 : TextConst 'ENU=Postal Code is missing in vendor''s card %1;ESP=Falta el c¢digo postal en la ficha del proveedor %1';
    ...
  6. Change the code in the CreateFileHeader function in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    CLEAR(OutText);

    OutText :=

    // Delete the following lines.
    '1347' + FiscalYear + VATRegNo +
    PADSTR(CONVERTSTR(UPPERCASE(CompanyInfo.Name),'µ•ÔÖÞàãé륚€()"&ï','AAEEIIOOUUÑUÇ '),40,' ');
    // End of the lines.

    IF DeclarationMediaType = DeclarationMediaType :: Telematic THEN
    DeclrationMT := 'T'
    ...

    Replacement code

    ...
    CLEAR(OutText);

    OutText :=

    // Add the following lines.
    '1347' + FiscalYear + UPPERCASE(VATRegNo) +
    PADSTR(FormatTextName(CompanyInfo.Name),40,' ');
    // End of the lines.

    IF DeclarationMediaType = DeclarationMediaType :: Telematic THEN
    DeclrationMT := 'T'
    ...
  7. Change the code in the CreateFileHeader function in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    OutText := OutText + DeclrationMT;
    OutText := OutText + ContactTelephone;

    // Delete the following line.
    OutText := OutText + PADSTR(CONVERTSTR(UPPERCASE(ContactName),'µ•ÔÖÞàãé륚€()"&ï','AAEEIIOOUUÑUÇ '),40,' ');
    // End of the line.
    ...

    Replacement code

    ...
    OutText := OutText + DeclrationMT;
    OutText := OutText + ContactTelephone;

    // Add the following line.
    OutText := OutText + PADSTR(FormatTextName(ContactName),40,' ');
    // End of the line.
    ...
  8. Change the code in the Documentation object in the Make 347 Declaration report (10707) as follows:
    Existing code

    ...
    NoOfAcc := j - 1;
    END;

    BEGIN
    END.
    }
    }
    ...

    Replacement code

    ...
    NoOfAcc := j - 1;
    END;

    // Add the following lines.
    PROCEDURE FormatTextName@1100006(NameString@1100000 : Text[50]) Result@1100001 : Text[50];
    VAR
    TempString@1100002 : Text[50];
    TempString1@1100003 : Text[1];
    BEGIN
    CLEAR(Result);

    TempString := CONVERTSTR(UPPERCASE(NameString),'•µ¶ÇŽÔÒÓÞÖ×Øãàâå™ëéêší¥€§¦','AAAAAEEEEIIIIOOOOOUUUUYOÑÇ ');
    IF (STRLEN(TempString) > 0) THEN
    REPEAT
    TempString1 := COPYSTR(TempString,1,1);
    IF TempString1 IN ['A'..'Z','0'..'9','Ñ','Ç'] THEN
    Result := Result + TempString1
    ELSE
    Result := Result + ' ';
    TempString := DELSTR(TempString,1,1);
    UNTIL STRLEN(TempString) = 0;

    EXIT(Result);
    END;
    // End of the lines.

    BEGIN
    END.
    }
    }
    ...

Prerequisites

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

  • 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.

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.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×