I
just tried to find some major MorphX development features that have been added or changed in in
Microsoft Dynamics AX 2009 when compared with AX 2012. I observed changes in the following concepts of AX :
1.Models
and the Model Store
2.Object
IDs
3.The
AxUtil Command Line Utility and PowerShell Cmdlets
4.Development
Workspace
5.Some
Layers Have Been Renamed
6.Installation-specific
Ids
|
Sr No.
|
Microsoft
Dynamics AX 2009
|
Microsoft
Dynamics AX 2012
|
Why
is this important?
|
|
1.
Models and the Model Store
|
The
model store did not
exist
in Microsoft
Dynamics
AX 2009.
Application
model data was stored in .aod files. You can load .aod files
during version upgrade. You can also load .aod files by using the
Tools
menu.
|
The
following model features are new:
1.
A model is a set of model elements in a specific
layer.
2.
Each layer consists of one or more models. One of
the
models is generated by the system. For example,
VAR
Model is the model that is generated for the VAR
layer.
3.
Each element in a layer must belong to only one
model.
4.
Models can be exported to a file artifact that is
called
a model file. Model files have an .axmodel
extension.
A model file is like an .aod file from earlier
versions,
but the names and numbers are not limited.
Models
in the model store can be exported to model
files
and imported from model files. Model files can
be
signed, and the signature is verified when the
model
files are installed.
5.
Model files replace
.aod files as
installation
artifacts.
6.
Models in the SQL Server–based model store
replace
.aod files that were used at run time.
7.
Development is performed in the current model in
any
given layer. All development work, such as
creating
a new class, becomes part of the current
model
in the current layer. You can change the
current
model by clicking the name of the current
model
on the status bar, similarly to the way that you
change
the current company.
8.Any
element that is created in the current layer can
easily
be moved to another model in the same layer.
9.
The Application Object Tree (AOT) shows you
which
model a particular element belongs to, in
addition
to the layer tags.
10.
The additional folder capabilities for version control have been
renamed models, and the capabilities have been extended. When you
add an element to version control, the element is added to the
version-controlled model.
11.
You can generate a MorphX project that contains all of the
application objects in the model. A new Model
management submenu
on the Tools
menu
contains many tools that you can use to work with
models
and the model store.
12.
The new SysModel* system tables provide a view of the metadata
that is associated with models. These tables enable you to use
model metadata in select
statements
in your X++ code. For example, you can use the
SysModelElementLabel table to retrieve the string value for the
label that is associated with a particular model element.
|
Storing
models in SQL
Server
increases quality,
reliability,and
performance.In
addition,
you can use
the
tools that are
available
in SQL Server
forbackupand
administration
|
|
2.
Object ID's
|
Object
IDs were 16 bits long
|
Object
IDs are 32 bits long
|
Changing
the length of
object
IDs from 16 bits to 32 bits exponentially increases the number of
object IDs that are available.
|
|
3.
The AxUtil Command-Line
Utility and PowerShe ll Cmdlets
|
The
feature was not available
|
AxUtil
is
a command-line utility that you can use to import and export
.axmodel files into the SQL Server model store. You can also use
AxUtil to delete one or models, create new empty models, and list
all models in a layer. All of the capabilities of AxUtil are also
exposed as PowerShell CmdLets.
|
Users
can use these tools to work with models from outside the
development environment. Therefore there are more options for
scripting deployment processes.
|
|
4.Development
Workspace
|
Development
occurred directly in the Application Workspace.
|
The
Developer Workspace contains all of the tools that a developer
must have to create and customize a Microsoft Dynamics AX
application.
Changes
that you save in the Development Workspace are always synchronized
with the Application Workspace. You can still open application
elements in the AOT. You can also open an Application Workspace
from the Development
Workspace
to view your customizations. You can open Microsoft Dynamics AX
directly from a write Development Workspace by using the Ax32.exe
command-line flag.
|
The
new Development Workspace provides a morestreamlined environment
for writing code. The menus have also been customized to make it
easier to find the tools and commands that you use when you code.
|
|
5.
Layers
|
Old
layer names:
USP
USR
CUP
CUS
VAP
VAR
BUP
BUS
SL3
SL2
SL1
HFX
GLP
GLS
SYP
SYS
|
New layer names:
USP
USR
CUP
CUS
VAP
VAR
ISP
ISV
SLP
SLN
FPP
FPK
GLP
GLS
SYP
SYS
|
The
new layer names more accurately describe the usage of the layers
|
|
6.
Installati on
|
Objects
IDs were assigned when a model was created.
|
When
a new model element is saved, imported, or element 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 is assigned a class ID. However, when the
same class is imported into another installation at a customer
site,
the
class ID may be different from the ID that was assigned in the
first installation site. The new object IDs that are assigned for
Microsoft
Dynamics
AX 2012 installations have a larger range than the previous object
IDs 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.
|
Because
of installation-
specific
IDs, conflicts are
avoided,
because an ID
is
not assigned until
installation
time.
Because
the assignment
of
object IDs is handled
at
the installation site,
Team
Server no longer
has
to manage IDs.
Team
Server is no longer
installed,
and the setup
of
version control is no
longer
dependent on
Team
Server.
|
|
7.
Modules
|
General
Ledger
Bank
Accounts
Payable
Accounts
Receivables
Inventory
Management
Expense
management
Production
Project
|
General
Ledger
Fixed
Assets (New)
Cash
and bank management
Accounts
Payable
Procurement
and sourcing (New)
Accounts
Receivables
Sales
and Marketing (New)
Product
information (New)
Inventory
and warehouse management
Travel
and expense management
Production
control
Project
management and accounting
Compliance
and internal control (New)
|
|
|
8.
|
Support SQL Sever 2005 and 2008
Support Oracle Database
|
Only Support SQL Sever 2008
Does't support Oracle Database
|
|
Hope
you find the above information useful.... :)
