5,901
Hi all,
Can you please let me know, i have created a new legal entity for Japan. Shall i create a new model for Japan like "JAP" MODEL for development ? So, i think in future it's easy to us to export and import model in to ( UAT, TEST and PROD ).
Please suggest me.
Thanks!
About using your own model, the most important purpose is to prevent clashes and conflicts in deployments and upgrades.
Let's assume that two companies provide code to one system / one customer. If both used "VAR Model" you would not be able to install the code from both companies - at least not without a lot of manual work.
Also, you can't change the version number of MS owned standard models, so you can't version your code appropriately.
Also, you cant sign models that you didn't create yourself.
Within your project, most likely you will not have any issues in using the VAR Model. But why not do it right, and avoid all the issues (also in the future) that you will face because not following the guidelines.
You can check for example book "Inside Microsoft Dynamics AX2012" from Microsoft: https://books.google.ch/books?id=yQ0bBAAAQBAJ&pg=PA731&lpg=PA731&source=bl&ots=QNFshjppIr&sig=ACfU3U0bTJksQaZyFaEMoFwulDWZi6aiqQ&hl=en&sa=X&ved=2ahUKEwiM4eznqYPqAhXCyYUKHURRClMQ6AEwBXoECAoQAQ#v=onepage&q&f=false
I think you should discuss with your team how the code delivery process has been until now. I'm almost 100% sure that there already is some process, which you can use as it is, or adjust it. Could you please describe the current code delivery process for this customer? Until that, I can't provide any additional suggestions (except the ones in this message).
But yes, you are right that in my process you deliver all customizations to test system. That's how you should normally do: deliver a model with all your customizations, not only the latest changes.
For example, let's assume that your test system already has customizations A, B and C.
Now you develop customization D in your dev system. Your model delivery will contain customizations A, B, C and D.
If you don't want to deliver everything from your dev system, you need another system for collecting the delivery contents (in my description I called it "Delivery system".). Then you put there all the code that you want to deploy, export model from that system and import it to test system.
You can check Microsoft's whitepaper "Deploying customizations across AX2012 environments": www.microsoft.com/.../confirmation.aspx
sure, i will...
two things only
1. you said "no development should ever be done on the default models" why ?
2. ypu suggest me to use the "Var model"for Japan development. then i need to follow as you suggested above 1-3 points for import in TEST or Prod.
in fouth point -- " (4) Export your model (in your case VarModel) and import it to test system"
if i do that then it will impacts all legal entities customizations not only Japan legal entity becuase everything is there in one model "Varmodel". here i am confused.
kindly elaborate me please
No, I meant that no development should ever be done on the default models. Instead you should have a model like [CustomerName] and develop there. Anyway it's a different discussion. About your JAP customizations, my suggestion is to use the same model that is used for other customizations in this project.
But latest when you upgrade to D365, you need to start using a dedicated (non-default) model for all the developments.
When you export a model, it always contains all code in that model. By the way, you should definetely not use VarModel for any development, instead all code should be in some custom model.
If you don't have TFS, I suggest following process for delivering your code:
1) Export the customizations from dev system as XPO
2) Import them in a delivery system
3) Perform a full build in delivery system
4) Export your model (in your case VarModel) and import it to test system
Some people also import xpos directly to test but that's not the recommended approach.
I assume that there is already some code deployment process in this project. So please check if that process can be used, or if it needs to be adjusted. You should discuss this with the person who is responsible for the code delivery process.
thanks Nikoloas,
As i know, we are not using TFS version control in AX 2012
i saw in the application having already 5 legal entities for US,China , Japan. and all are in to the one model (VarModel) only.
So, for Japan custamization , i am also doing in VarModel only.
Could you please let me know when i am going to EXPORT model from DEV for Japan customaization then how i will identified the Japan customization only from Var model ? because other country customization is also there in same model ( Var model ).
Please give me more shed on this.
thnaks!
I would not create more than one custom model per project.
Here's why:
1) If you use TFS version control in AX2012, one object can exist only on one model per layer. For example, if you would add some customization to SalesTable and it would be in JAP model, then you would not be able to add any customization in SalesTable on another model (on the same layer)
2) When you update to D365FO (support for AX2012 is ending in a few years) one object can exist only in one model
But technically you can create as many models as you like. I just don't see much value in them, instead they just make things more complicated.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
