What's new: AxErd tool for discovery of table relationships [AX 2012]

Updated: August 28, 2013

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2

The AxErd website provides 30 database entity relationship diagrams (ERDs). The ERDs display the foreign key relationships between the core tables in each of the application modules.

Aside from its ERD webpages, AxErd also has hundreds of other webpages that enable developers to easily find a variety of foreign keys. The website displays both the parent and child tables for any given target table. The website is rich with links that enable developers to traverse chains of tables that are associated by foreign key references. A display of tables categorized by their application module is also available. All this information is brought together to enable developers to extend our core ERDs, or to create new ERDs.

AxErd matches the database for Microsoft Dynamics AX 2012 R2, so it only approximates the database for Microsoft Dynamics AX 2012.

In addition to the ERD webpages, the AxErd website is composed of hundreds of webpages, each being one of four types:

  • PC - list of parent’s child tables.

  • CP - list of child’s parent tables.

  • MT - for each module, the tables in the module.

  • TM - for each table, the module that the table is in.

The webpages have numerous links to each other. For example, in many cases you can click on a parent table name in a PC page to jump to a CP page where that same table is the child.

What can you do?

Microsoft Dynamics AX 2009

Microsoft Dynamics AX 2012 R2

Why is this important?

Easily understand the boundaries between application modules in ERDs.

Security keys could provide information about module boundaries, in theory. But in practice it was a challenge to manually coordinate the references made to this information with foreign key information referenced separately from the cross-reference feature and from the AOT.

Security keys are obsolete and are ignored by the system.

The AxErd website has webpages dedicated to categorizing each table by its primary application module. On other types of webpages each table is tagged with its primary module as a clickable link.

An application developer who must customize a particular module benefits from knowing which tables are most essential to that module.

Easily reference the foreign key information for a table, or for a chain of tables, to use when creating an ERD.

Versions earlier than Microsoft Dynamics AX 2012 R2 do provide information about both the parent and child tables for each given table. In the AOT under Data Dictionary > Tables > MyTable > Relations there is a list of all the parent tables of the given table. But the AOT does not list the child tables of the given table.

Information that identifies the child tables can be obtained by using the cross-reference feature, but laborious clicking and scrolling is necessary to reach each child table.

The AOT and the cross-reference feature provide their foreign key information in different places from each other. This makes it more time-consuming to combine their information to create an ERD.

AxErd brings all foreign key information together in one place for both the parent and child tables.

The parent and child information is linked together in one place. This enables you to quickly and easily follow any chain of foreign keys, in either direction.

It is now more workable for you to create ERDs for the specific tables that are involved in your customization.

Look at ERDs provided by AxErd, each illustrating the relationships between the core tables in one application module.

There are no ERDs for earlier versions.

The AxErd website provides 30 core ERDs.

The application developer who customizes an application module often writes SQL in his X++ code. But the developer must first understand the relationships between the relevant tables before the SQL can be intelligently written. ERDs display the relationship information in a vivid and compact format.

  • AxErd website home page 

  • For instructions on how you can partially automate the task of extending or creating an ER diagram, click the Help link on the AxErd Home page. The steps involve using Microsoft Dynamics AX to generate a .ERx file, and then importing that file into Microsoft Visio 2010.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

ADD
Show: