Moving a whole project from USR layer to BUS layer

jdeme
Member Posts: 12
Hello everyone and happy new year!
I have a few questions regarding the movement of projects from one layer to another.
The issue is as follows: When we started developing in axapta we took the USR layer so until today we are still developing in that layer. Now comes the issue that all the development we've done should be moved to the BUS layer so that it can be correctly implemented at the customer. The problem is that references between the project items will be lost as when they are moved to the BUS layer they are assigned new IDs (belonging to the layer's range of IDs).
Does anyone have any suggestions as how to resolve this issue? Any ideas will be greately appreciated!
Joanna
I have a few questions regarding the movement of projects from one layer to another.
The issue is as follows: When we started developing in axapta we took the USR layer so until today we are still developing in that layer. Now comes the issue that all the development we've done should be moved to the BUS layer so that it can be correctly implemented at the customer. The problem is that references between the project items will be lost as when they are moved to the BUS layer they are assigned new IDs (belonging to the layer's range of IDs).
Does anyone have any suggestions as how to resolve this issue? Any ideas will be greately appreciated!
Joanna
jdeme
0
Comments
-
I just might have an idea:
1) Stop the AOS and make a backup of your application folder
2) Change all the corresponding files in the application folder from USR to BUS (aod, index files, etc.)
3) Delete the axapd.aoi file
4) Start up the AOS and connect with a client
Your application object indexes will be rebuilt, but I do not think that IDs will be affected. Also I do not have any information if the layer file contains itself any relation, or only the filename determines it, but it is worth a try.
If something goes wrong, you can restore the previous state by stopping the AOS and copying the backup to it's original place.
Please inform me about the results.
Another note is that you should avoid using fixed IDs, instead of you have functions like tablename2id(), fieldname2id() and the reversed forms too.0 -
Hi Icelanderwill,
I am not sure what you mean in your second point where you say -
Change all the corresponding files in the application folder from USR to BUS (aod, index files, etc.)
I hope you did not mean renaming the files physically.
Joanna -
One option you can consider is exporting from USR layer and importing them into BUS layer. If you want to retain the IDs, try importing them with this command - "-internal=importexportID" in your config utility. First please test this in your test environment.
Regards,Harish Mohanbabu
Long way to go before I sleep..0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 320 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