Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
In the old days (not using any version control) it was our responsibilty to export and import with id values to keep the object id the same. Now with version control, i was wondering if this rule doesn't apply anymore?
Is the id i get on my system (through the id server) the same that the object will get when creating an version release?
Team Server and version control have nothing to do with it. ID is allocated in the DEV (by ID server or AOS) and is never changed by itself.
How do you install your application to other environments, like TEST or LIVE, is out of control of the version control system (although you could have a build system based on a version control system). You don't have to, but you should, keep all IDs the same. So you need to install whole layers or .xpos with IDs - the situation is identical if you use VCS or not.
It is highly recommended to deploy complete layers.
[ Goshoom.NET Dev Blog ]
Not sure if I understand right way; but you can still running in Id conflict if you work with XPO deployment even your environments are using VCS. Maybe I missunderstand - if so, please tell.
ID server controls ID allocation on the DEV server only - and it is still your responisibility to keep the same IDs on all other environments, i.e. to release whole layers or to export modifications with IDs.
thanks for your reply. Is the created ID the same over all developers. So in Detail:
Developer A creates a new Table and gets ID 4711 for that. He is doing some urgent thing and exports the Table to the production system (for example with id value). At the end of the month a clean build is created. Will the id of the table remain the same? Or will we have any issues here?
The Ids are the same for all users.
Thanks all for the info. The reason for my question is... i was told to ever export and import with id values to keep the systems in sync. That was before using any version control. Now somebody told me that we shouldn't do this, because every developer has other ids. But it seems wrong and we should continue the rule to always export and import with id values.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13