We've launched a new site that hosts 30 database entity relationship diagrams for tables of Microsoft Dynamics AX 2012 R2: AxERD.
Check it out here: http://www.microsoft.com/dynamics/ax/erd/ax2012r2/
Check out the introductory blog post here: http://blogs.msdn.com/b/x/archive/2013/05/23/announcing-the-axerd-website-for-dynamics-ax-2012.aspx
Fabulous news! Shared on my blog, facebook, and LinkedIn! Thanks!
Great, this was much needed. Will there be more to come?
Hi Bijan, Thanks much for the feedback.
The Microsoft Dynamics AX product team will probably not be adding more ERDs to the AxErd website for Dynamics AX 2012 R2.
However, if AX professionals such as yourself send email to us with an ERD file attached, we may add it to the AxErd website.
Such ERD files should be in .PNG format, and should be valid for Microsoft Dynamics AX 2012 R2.
(If the ERD is also valid for the earlier version Microsoft Dynamics AX 2012, it would be good to mention that in the email.)
You can email us at email@example.com.
It would be wonderful if we could search with wildcards on more than just "table name" (i.e. column name, view name, module name, stored procedure, etc..) and have it list the number of times the search appears within those meta objects, much like the Oracle eTRM.
There is so much great info here it would be hard to sift through it one table at a time.
Thanks for this link!
Thanks Kurt--I'll pass your feedback along to the developer of the site.
Kurt, Your point is well taken.
Our search mechanism in the AxErd website works in a manner very similar to how searches work in Bing.com and Google.com. Those search tools do not offer wildcard searches.
However, in the AxErd search text box you can search for column names, module names, and other things beyond just table names.
Also, some of the AxErd file types in the drop-down box have content that approximates a useful search result. For instance, the 'MT' type contains all the tables just for one application module. The 'PC' type contains all the child tables of any given parent table of interest (within one module). And so on.