Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet


Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Thursday, August 16, 2012

AX 2012 - Understanding & Extending the Organization Model





I wanted to take the time today, and point out some great resources around the concept of extending the Organization Model in Microsoft Dynamics AX 2012.



Before we dive right into the mix of common task that are typically associated with customer implementations of Microsoft Dynamics AX 2012, I would first like to point out a great learning webinar around the topic of Modeling Your Organization with AX 2012. What I'm speaking about can be found here.: Modeling your Organization: Microsoft Dynamics AX 2012

The above link will take you through a nice webinar that really gives you a feel for the thought process of modeling an organization with AX 2012. This is the 'unified natural models' that Microsoft speaks about a lot. I should correct that really and say one of the unified natural models. See.: Enabling Agility through Unified Natural Models



When we start to think about extending the organizational model that comes out-of-the-box in AX 2012, there are two common task that are typically done for customers. The first task is around adding custom Operating Units. Microsoft has a done a good job at creating the following walk through.: Walkthrough: Create and Use a Custom Operating Unit Type [AX 2012] I will add that this walk through does leave out specifics, for example if you want the new Operating Unit to appear under the GL > Setup > Organization for management of said new custom operating unit.



The second most common extension that takes place for customers is around the creation of custom purposes. The following resource from Microsoft is a nice walk through as well, for this topic.: How to: Create a New Purpose [AX 2012]



Adding a new custom purpose for organization hierarchies helps further shape and allow customers to truly model AX as they run their business. Purposes for hierarchies can help relate policy and reporting needs.

With all of this one of the best resources for understanding how to implement and extend the organization model for AX 2012 can be found here.: Implementing and Extending the Organization Model in Microsoft Dynamics AX 2012

Update: I wanted to take the time and update this post, to include the fact that InformationSource located at InformationSource.Dynamics.com has some good resources on this topic as well. This includes some video's, which the webinar is based on. Further a specific PowerPoint artifact that I would like to point out.:



The above PowerPoint has some good information around understanding the concepts of organization modeling, as well as common task involved with the process. Further it has common task typically associated with extending the organization model offering for AX 2012. It mentions further task around Security with XDS, and relating Master as well as transaction data.

Now With the above information and resources, someone familiar with Microsoft Dynamics AX 2012 can extend the organization model(s) for a customer. Further, if your an ISV there could be good reason to include in your IP offering extensions to the organization model offerings. Keeping in mind that a customer could have a need for several organization hierarchies in their instance. Powering everything from Operations, reporting, relating to security, workflow approvals and more.

That's all for this post, but check back soon as I will continue with my focus around BI for AX, extending the reach of AX with Office 2013 and more! Till Next Time!
Follow Me @:
RSS Feed  LinkedIn  Twitter

"Visit the Dynamics AX Community Page today!"

Labels: , , , , , , , , , , ,

Wednesday, January 26, 2011

Dynamics AX 2012 - Table & Type Hierarchies

One of the huge, underlying changes from a architecture, and really database design point of view for Microsoft Dynamics AX 2012 is the use of Type or Table Hierarchies.

This is actually extending upon the type hierarchy system that already existed within Dynamics AX, however to a whole new level!


[Image Source: techmaniac1, Rodrigo Fraga while attending #DAXCONF 11]


As you can see from above, thanks to Techmaniac1, the screen shot shows off the Type Hierarchy of a given table. This is actually showing from within the Dev workspace, looking at the AOT as a new add-in for Microsoft Dynamics AX 2012.

With this concept, OO Design is being forced onto Relational data. I know, I know, that statement seems like it would be an oxymoron. I mean how can relation data truly be and live with OO attributes, design concepts, and adhere to such rules that govern things like: inheritance & polymorphism?

The answer to that is super normalization! That is what is taking place with Microsoft Dynamics AX 2012 and type hierarchies for Table objects.

Because Microsoft Dynamics AX 2012 manages it's relation database, through a meta layer, then through the combining of these two concepts, such things as inheritance and polymorphism can be applied.

So with this, we now have new attributes of tables, called: concrete or abstract, as well as if a table inherts from another table or not.

In doing this 'extending from' at a table level, the table that extends from an abstract table, inherits the fields and methods of the super or base table being inherited from.

This new approach along, plus just adhereing to BP, means that you should *never* access to the database of an Microsoft Dynamics AX 2012 instance directly. So many reasons why, and with Microsoft Dynamics AX 2012, so many more reasons will exists.

And this is true today actually, should not have direct access to the DB of an AX instance, however it's still done today in certain cases.

That's all for now on the continued coverage from the #DAXCONF 11. I hope that I have your wheels turning, and thinking about the possibilities this means, and doors this opens from an Architecture and Design POV. Also, what this means for outside development that may directly access the database of an AX instance today.

This leads me into my next focus, which is OData Feeds and EDM, and how they will enable secure, easy access to Microsoft Dynamics AX 2012 data and business logic, without ever needing direct access to the DB again!

See you next post!

"Visit the Dynamics AX Community Page today!"

Labels: , , , , , , , , , ,


Copyright 2005-2011, J. Brandon George - All rights Reserved