Search This Blog

Monday, September 12, 2011

Installation of Object ID's in AX2012

Installation-specific IDs What can you do? Microsoft Dynamics AX 2009 Microsoft Dynamics AX 2012 Why is this important?
Object IDs such as table IDs, field IDs, and class IDs are now installation specific. With this change, you no longer need to worry about conflicting object IDs in different installations. Objects IDs were assigned when a model element was created. When a new model element is saved, imported, or installed, a unique ID is assigned to the model element at that installation site.
For example, when a new class is added by a developer and saved to the model store, the class will be assigned a class ID. But when the same class is imported to another installation at a customer site, the class ID may be different to the ID assigned in the first installation site.
The new object IDs assigned for Microsoft Dynamics AX 2012 installations are greater than the previous object ID range and will not conflict with any of the earlier versions of Microsoft Dynamics AX.
In an upgrade scenario, object IDs are preserved because they are automatically assigned to the new LegacyId property on the application objects.
With installation-specific IDs, conflicts are avoided because an ID is not assigned until installation time.
Because the assignment of the object IDs is handled at the installation site, the Team Server is no longer required to manage IDs. Team Server is no longer installed, and version control setup is no longer dependent on Team Server

No comments:

Post a Comment

Thanks for visiting my blog,
I will reply for your comment within 48 hours.