Inside Dynamics AX

In this post we will be exploring the basics of tables in Dynamics Ax 2012. OVER VIEW: •     Tables store business data. Each table in the AOT has a corresponding table in the underlying Microsoft  SQL  Server database. •     In Microsoft Dynamics AX, tables have advanced features beyond what tables might have in the underlying database. The advanced features include the following: •     Method members – A table can have methods, just as a class in X++ or C# can have methods. •     Table inheritance – A table can extend, or be derived from another table. That same table can be the base table for several derived tables. •     Tables  are specified at  AOT  >  Data Dictionary  >  Tables •     In Microsoft Dynamics AX, tables are located in the Application Object Tree (AOT) under the  Data Dictionary \ Tables  node. Each table contains the following primary...

In the previous post we explore the basics Extended data Types in Dynamics Ax 2012. To navigate to previous post go to this Link. http://dynamicsaxedtsandbaseenums.blogspot.com/ In this post we will be exploring the EDT's in some detail which include Array elements and Table References which you can see under the node of your EDT. ARRAY ELEMENTS: •     You can create an extended data type in the Application Object Tree (AOT) that contains multiple elements. This enables you to store multiple data elements in a single field that is based on this extended data type.       Array elements are very useful in the scenario where you want to create such EDT in which that particular EDT can contain similar elements, so instead of creating multiple EDT's you can create Array Elements of that particular EDT...   This concept will be more clear with the help of an example:       You have created an EDT for the Address as shown above. Now ...

Today We are going to explore EDT'S and Base Enums from Basics in Dynamics Ax 2012. EDT'S: Extended  data types (EDTs) are user-defined types, based on the primitive data types  Boolean , integer, real, string, and date, and the composite type container. You can also base EDTs on other EDTs. BENEFITS: •     Code is easier to read because variables have a meaningful data type. For example, Name instead of string. •     The properties you set for an EDT are used by all instances of that type, which reduces work and promotes consistency. For example, account numbers (AccountNum data type) have the same properties throughout the system. •     You can create hierarchies of EDTs, inheriting the properties that are appropriate from the parent and changing the other properties. For example, the ItemCode data type is used as the basis for the MarkupItemCode and PriceDisc...