June 10, 2011 in Blog by Amer

The Use of Visual Studio .NET in the New Microsoft Dynamics AX 2012

Developing applications is now easier and faster in the new Microsoft Dynamics AX 2012 than its earlier versions. .NET developers who are familiar with Visual Studio .NET will be comfortable with developing Dynamics AX applications although Dynamics AX has its own IDE which called MorphX and its own programming language with is X++.

This image shows the Dynamics AX AOT (Application Objects Tree), one of the MorphX IDE objects that Dynamics AX developers use to navigate through programming objects like Forms, Reports, and X++ Classes:

With Microsoft Dynamics AX 2012, you can view that AOT in the Microsoft Visual Studio 2012:

Dynamics AX 2012 Applicatoin Explorer in VS.NET

Proxies

Microsoft Visual Studio 2010 now creates proxies internally to support interacting with Microsoft Dynamics AX 2012 X++ classes, tables and base enums. By creating those proxies, developers will interact with Dynamics AX objects in C# and VB.NET exactly as if they are interacting with it in X++. After the proxy is created, that type is available as a strong type and features such as IntelliSense are available. For example, table fields and X++ methods are now exposed to be used in C# with one click. The created proxies are using .NET business connector internally to connect to the Dynamics AX objects.

The following pictures speak quietly how you can access and interact with Microsoft Dynamics AX 2012 objects from within Microsoft Visual  Studio 2010:

Adding Visual Studio Project to the Dynamics AX 2012 AOT

Visual Studio Project inside Microsoft Dynamics AX 2012 AOT

Adding a Dynamics AX 2012 object to the VS 2010 Creates an Internal Proxy

The CustTable Appears in the Solution Explorer. You Can Now Use the Dynamics AX CustTable Methods, Properties and Fields!

February 6, 2011 in Blog by Amer

Populating Data from Different Companies

I came across a case where I needed to select a field value from different companies in Dynamics AX.

Simply what you have to do is the following (I choose ItemId to be taken from different companies as an example):

1. Create a field in your table with an ExtendedDataType than has NO relation, MyNewItemIdEDT in our example
2. Create an ItemCompany field, put the extended data type as dataAreaId
3. Create a Relation in that table with the following elements (Normal relation elements):
   • <<NewTableName>>.MyNewItemId == InventTable.ItemId
   • <<NewTableName>>. ItemCompany = InventTable.dataAreaId

By this you would be able to select the ItemId field based on the selected dataareaid without writing any code even.

May 31, 2010 in Blog by Amer

How to Create a Primary Key for a Dynamics AX Table

This topic might not be new to most of you guys, but I always wondered how can I create a primary key to a Dynamics AX table?

You could easily create index in any table in Dynamics AX and you could specify that this index is “not duplicated”, which means that values of the field(s) should be unique among the table values. But this does not mean that you this index is a Primary Key index!

To create a Primary key you have to set the PrimaryIndex property in the list of that table properties.

When you choose the PrimaryIndex property you have to set that index as “not duplicated”. Once you do that, you will have the icon of that index changed to be like this: