Hi Guys,

 

It’s my understanding that AX 2009 is constructed in such a way that Brazil, China and/or India cannot be on the same instance of AX as Russia and/or Poland as they have mutually exclusive GLS layers.  We’re nearing the stage where we will hit this conflict and so are looking into how to manage this.

 

Would anyone be able to point me to any documentation/blogs about this issue?  I’m hoping to find out more about the functional and technical implications and possible solutions.  I understand that AX 2012 does not have this issue, but would like to see what options we have in 2009 before making this decision.

 

Thanks in advance,

 

JB

 

 

If you want to know more about what I’m looking into, please see below:

·         What are the functional impacts (so we can decide if the functionality introduced by the GLS layer is relevant to our requirements / can implement some countries without their GLS layer if our requirements aren't affected by this)?

·         Is it possible to maintain one custom code base (i.e. in the VAR layer) for both instances, but using a different GLS layer in each?

·         If the above is not simple, is it achievable by putting more code in the VAR layer to map the two GLS layer’s functionality to one common layer (i.e. so it behaves as if classes in both GLS layers implemented the same interface), perhaps then using the VAP layer for custom code and the USR layer for patches (since all code will be developed by our partner so we don't require this layer for our own purposes)?

·         Is there any information on code management with multiple GLS layers?

·         Is there a description of why this issue exists (from a technical point of view) so I can get a better idea of exactly what the cause of this issue is (i.e. what bit of the architecture causes a conflict for multiple countries / how come this couldn't be resolved by MS in AX 2009)?