Hello Jazib I guess you would need to run through the layer structure and the design philosophy of AX once more. The SYS layer is ofcourse delivered by MS and EmplTable belongs here. So when you install AX out of the cd you get a virgin EmplTable. Now you use your development environment and make changes to the EmplTable and also the methods associated to it. You add maybe new classes to AX. Changes in AX are made in your layer. I assume that you are a VAR. So the changes will be reflected in your layer. Now once you have done all the changes you need to, you deliver the axvar.aod file to your deployment team. They take it along to the customer site and install Ax out of the box. Then add the axvar.aod file to the application folder. Launch AX and then follow the rest of the steps to finish the deployment. Say you are delivering this module on version 3.0. Now version 4.0 is the planned upgrade path for the customer, after say 6 months. Brief Steps to achieve before your customer can go to version 4.0 1. Create a development environment for version 4. Open the CD and install AX4.0 2. Upgrade the DB AX3.0 using the steps given. 3. Now normally you should be ok here in case you have added fields to the AX3.0 Empl Table and they are distinct from the new fields if any added by MS in AX4. 4. Now the next bit comes wherein the axvar.aod is still code compatible with ax3.0 5. Create an upgrade project and diff out the code that has changed. 6. Study impact on your module/customization. 7. 3 possible things can happen, You reappend your code at the correct spot where you would need it. You remove your code as it is not needed becos MS has added this code themselves. You retain your code as is. 8. Once this has been achieved, we go back to the customer and repeat the same steps at the customer. Only we do it quickly as you have a new application folder (AX4.0) to use and the only steps to execute at the customer is the database upgrade at the time of going live. Ok this was in short a lifecycle of your modifications from 1 version to another. Hope this helps. Thanks Rajesh Guidelines on Changes Types of changes 1. New Fields in EmplTable You should be OK with this as long as You use a specific naming convention to identify your fields. This way you can 99.9% sure that when a service pack is released or a new version comes out MS hasnt shipped the EmplTable with a new field and it has the same name as you have used. The same applies to EDT (Extended Data Types) as well. 2. Code Changes Make sure your code is clearly demarked by comments (a bad best practise - but helps initially to maintain the code since AX is evolving and change is something we have to live with ). 3. New Labels Best to use existing labels in Axapta. But if you do need to create new labels then ofcourse you have your own label file which you will deliver to the deployment team along with What do you do when you receive a new version of AX ? The end goal is to deliver to your customer a new VAR layer file axvar.aod and any label file that goes with it with your new labels. There can also be some preupgrade or post upgrade scripting that you might want to do to keep the data consistent with your module. It could also be a patch layer file that you would deliver in case of a patch/service pack release.
----- Original Message ---- From: jazib.abdulah <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, May 8, 2008 7:13:31 AM Subject: [development-axapta] What are the implications of making changes into a table like EmplTable Hi everybody I have to develop a small module for Axapta which requires me to make some changes in EmplTable like adding some new fields and methods. But what are the implications of making these changes especially from the following point of view.How upgrades and future releases in Axapta will affect my changes?? If another module like HR is also making some changes into the EmplTable than how my changes and changes from another module will effect at the end? Thanks a lot in advance ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ [Non-text portions of this message have been removed]
