Localization Merge with Same Field ID's & Developer License
Sandeep_Rana
Member Posts: 2
Hello Friends,
Can somebody tell me how we can Merge the Localization(Taxation) Functionality with the same Field ID's in W1 Database, with the Developer License.
For e.g if we have one localised functionality mapped with the help of filed ID's 16001,16002,16003,etc. in some localised database and we want to merge/Import that functionality in the same Field ID's 16001,16002,16003,etc. with Developer License.
Waiting for Reply.....
Thanks,
Sandeep Rana
Can somebody tell me how we can Merge the Localization(Taxation) Functionality with the same Field ID's in W1 Database, with the Developer License.
For e.g if we have one localised functionality mapped with the help of filed ID's 16001,16002,16003,etc. in some localised database and we want to merge/Import that functionality in the same Field ID's 16001,16002,16003,etc. with Developer License.
Waiting for Reply.....
Thanks,
Sandeep Rana
A Beginner,
Sandeep Rana.
Sandeep Rana.
0
Comments
-
Official localizations does not have field range 50000..99999 and customization can't have range ..50000|99999.. (excluding add-ons)
I don't know how can you get this problem...maybe you're trying to copy the taxation fields to a custom table? (in custom tables you can define whatever number of field you want).
Basically, you have to move fields from one number to another...but this gets more complicated to explain...it depends from case to case...be more specific, please0 -
You will have to move the fields to different IDs and make sure all objects are updated accordingly. A good way is to put them in something like the 60,000 range but with a "similar" ID.
So 16000 = 60000, 16001 = 60001, etc.
It's not much fun to maintain, so for the sake of developers that come after you, please comment your objects and code
0 -
Sandeep, you have two separate issues to address here. The one pointed out by the replies above is not about merging, its about the user license.
So if you in fact already have an Indian license with permissions to these table number then you CAN use the 16,0xx number range to merge.
The second issue is merging. This is simple, but quite time consuming.
A developer license can not merge or create tables in the 16,0xx range, BUT you can merge them.
To do this you need to do the following.
Create a database with the Indian objects. Find the tables in the 16,0xx range, and also existing tables with fields in the 16,0xx range. In these tables you need to delete ALL code, ALL Functions, ALL Globals and ALL locals. Now export these blank tables.
Now open your W1 database, and import the Indian table objects. All objects that clash you set the option to MERGE new into existing. One that don't clash set to CREATE.
Navision will now import the new tables numbers and field numbers, BUT without code. But now you can use Beyond Compare to merge the C/AL code variables etc.
Be very carefull doing this, and start with just one table to learn how it all works, because if you do it wrong you can seriously mess things up.David Singleton0
Categories
- All Categories
- 75 General
- 75 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
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions

