The structure of txt file export from Nav through Translate!
cunny
Member Posts: 129
Hi all,
Could anybody please explain me the structure of txt file export from NAV using Obeject Desginer--Tools--Translate--Export? I have figure out some meanings of that but I am not sure!
F5-C40-P8672-M41-P8629-A1033-L999:Card
Does it mean that:
FormID-ControlID-?-MenuButtonID-?-AlanguageID-?:Description
Thanks,
Could anybody please explain me the structure of txt file export from NAV using Obeject Desginer--Tools--Translate--Export? I have figure out some meanings of that but I am not sure!
F5-C40-P8672-M41-P8629-A1033-L999:Card
Does it mean that:
FormID-ControlID-?-MenuButtonID-?-AlanguageID-?:Description
Thanks,
0
Comments
-
Pnnnn means "Property id", Lnnn means "Max Length of nnn".
The (localized) name for a "Property id" can be looked up in fin.stx as follows:
For property id "P8672":
Step 1) Convert to hex: 8672 decimal = 21E0 hex
Step 2) Convert hex bytes back to decimal: 0x21 = 33, 0xE0 = 224
Step 3) Look for a line in fin.stx that begins with 00033-00224...
00033-00224-030-0: Menu
Likewise for property id "P8629", you will find
00033-00181-030-0: CaptionML1 -
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 328 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions