Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Syntax error in a 'Translation Import' The text is too long
jw65
Member Posts: 18
A funny thing occurred when I was doing some translations for a report. In NAV 2013 Text Constant names can be more than 30 characters long, which for example is the case in the finnish localization of report 206 Sales - Invoice. It looks like this isn't implemented for the translation files. If I export the translation file for the report I cannot import the file back in (even without any modifications to the exported file). I get the error message:
The text constant name has a name that is larger than 30 chars, but the exported translation file indicates the field as "L30".
Anyway I was able to continues my work by just removing the sections with larger text constant names in the text file. Just wondering if this is a bug or if I'm doing something wrong.
There is a syntax error in a 'Translation Import'. The text is too long
The text constant name has a name that is larger than 30 chars, but the exported translation file indicates the field as "L30".
Anyway I was able to continues my work by just removing the sections with larger text constant names in the text file. Just wondering if this is a bug or if I'm doing something wrong.
0
Comments
Never stop learning
Van Vugt's dynamiXs
Dutch Dynamics Community
Tried the following:
1.- Created new table with text constant Text35_8901234567890123456789012345 (so length of name is 35 chars)
2.- Create translate export
Result: T88888-Q1000000002-P2818-L30:Text35_8901234567890123456789012345
[note: indeed L30!]
3.- Changed translate export
Result: T88888-Q1000000002-P2818-L35:Text35_8901234567890123456789012345
4.- Imported changed translate export
Result: dialog saying that Development Environment stopped working (even though is did not crash) / import did not succeed
5.- Export to and re-import new table object from .fob
Result: no problem
6.- Export to and re-import new table object from .txt
Result: no problem
7.- Tried to create the same table in NAV 2009 R2
Result: when trying to compile this new table I am getting the error message I had expected before (when compiling table in NAV 2013):
Microsoft Dynamics NAV Classic
The value entered in the Name field of the Data Item cannot exceed 30 characters.
OK, what does this say to me: NAV 2013 does not behave OK.
You should not be able to create a text constant name longer then 30 chars. (Or the translate export/import funtionality should be changed).
I suggest you report this bug to MS.
Never stop learning
Van Vugt's dynamiXs
Dutch Dynamics Community
I guess we need a fix only for the import/export translation, since also variable names now have a limit of 128 characters.
http://mibuso.com/blogs/zenandtheartofc ... ble-names/
On the positive side: longer variable names, text constant names and function names also seem to imply longer event names (see below), which should solve some issues we used to have with automation events whose names started with the same string (which led to duplicate names when truncated). :-)
Jan Hoek
Product Developer
Mprise Products B.V.