Import Model to AX2012

Hi,

I have two different AOS for AX2012 at my end.

i.e. AOS1 and AOS2.

I have developed a job “TestJob” on AOS1 and the same job “TestJob” on AOS2. But “TestJob” contains the different implements on both the AOS.

Now i have exported the Model using Powershell cmdlet utility from AOS1 and trying to install the model on AOS2 using the INSTALL command.

After successful importing the layer it prompts me to do below things.

  1. restart AOS service

  2. run scripts (which are they i dont know. please suggest)

  3. compile and synchronize the application

So, my question is, it is compulsory to execute above 3 steps on everytime i importing a model ? (If yes then it is very time cumbersome process if i have only a single line change in a single file)

please suggest me the proper way to import the model into a model store.

Thanks in advance.

That is exactly how model are to be used. There is a lot of detail on the msdn page.

http://msdn.microsoft.com/en-us/library/hh335184.aspx

If you want to just put a job in. You may use the xpo method but you have to understand that this is not a proper deployment method. You have to be careful with object ids when moving objects.

Hi munib,

Thanks for your quick reply.

I have already gone through the link provided by you. But that resource is not clearing my confusion regarding to compile and synchronize the application everytime i import the Model in AX.

Can you please give some brief on the same?

Thanks again.

This is not something that can be explained in brief.

Option 1 xpo:

XPO is an export and import from the AOT. This does not take the ids with it. It is generated on import. You generally (I used this word loosly) can get away with compiling the object you imported etc.

This is not a proper release procedure. It is a quick fix for a particular problem and generally done between dev and test environments. Not recommended for production.

Option 2 model:

This is an export and import using the commands. This moves the specific model. This can be used to release into production. Full compile, sycn, CIL compile is required - this can take time. Ids are generated when model is imported. If the object already exists, id is not regenerated.

Option 3 model store:

Model store export and import using the commands. This moves the whole application over. Since you are moving everything, no compile is required.You have to be careful as this takes the ids from the exported environment. You could have data loss.

That is the short of a long story.

Hi munib,

This is what i actually want.

Your explanation is well understood.

Thank you for your support.