Skip to main content

A demo of the AxHierarchicalGridView

First of all i would like to give thanks to Anees Ansari and Mey Meenakshisundaram at Microsoft for their input.

I have been playing around with EP 2012 for one year now and few weeks ago I decided  I wanted to try out the new AxHierarchicalGridView. I opened my Ax 2012 VPC started Visual Studio and created a new Ax web user control to hold my AxHierarchicalGridView control. 

At first I wondered if the grid would support display of sales table information with the sales table as header and the lines as sub rows in the grid. This was not working so I started to wonder how the data model behind the grid should be. If few trials which all failed I contacted Mey Meenakshisundaram at Microsoft to get some information on how to use this control. He forwarded the request to Anees Ansari Product Manager at Microsoft - Web Platform and Standards Team.  
Anees contacted me and we setup a live meeting where he would demonstrate the use of the control and how the data model should be. 

And the answer was so easy; the grid expects all the data to be in the same table such as the project table (ProjTable). And the grid is intended to be used for the project module and display project information. Each project can have a parent project specified with the ParentId on the project record and that’s the trick. 

With this new information I realized it would be very easy to use this grid and I have created a simple demo.

Here is the project list structured according to the ProjId/ParentId relation setup in the ProjTable


I simply used the EPProjTableList DataSet as a data source for the demo



And this is the markup for the control


These are the properties that need to be set


I leave it up to you to play around with other properties such as indentation and other cosmetical things.


Comments

Post a Comment

Popular posts from this blog

Dynamics 365 for operations – Table extensions

Background Extensions are a new way to add functionality and custom code to the D365 system without changing the standard code. In fact, Microsoft has announced that edit standard elements like those that we have done in the past will not be possible after 2017. By using extensions, we can achieve the same result by simply extending the standard system => EXTENSIONS. To read more about the difference between overlaying and extensions follow this link https://ax.help.dynamics.com/en/wiki/customization-overlayering-and-extensions/#extensions Extending tables By using table extensions, we can create a new table that adds new fields, field groups, indexes, mappings, relations, methods, subscribe to event handlers and more. When extending tables we need to follow the naming rule as such: <TABLENAME><_Extension> the compiler understands the _Extensions suffix and knows that the table in question is extending a table from the standard system. This gives us access ...
Post a Comment
Read more

New Dynamics 365 for operations learning material

Latest Dynamics 365 for operations training material New learning material is now available on the Dynamics Learning portal 80773BE: Managing Users and Security in Microsoft Dynamics 365 for Operations 80924BE: Extending Elements, Code, and Event Handlers in Microsoft Dynamics 365 for Operations 80927BE: Form Methods and Controls in Microsoft Dynamics 365 for Operations 81002AE: Overview of the Sales and Marketing Module in Microsoft Dynamics 365 for Operations 81003AE: Set Up the Sales and Marketing Module in Microsoft Dynamics 365 for Operations 81004AE: Manage Sales with Sales and Marketing in Microsoft Dynamics 365 for Operations 81005AE: Manage Prospects in Sales and Marketing in Microsoft Dynamics 365 for Operations 81006AE: Manage Contact Information and Activities in Microsoft Dynamics 365 for Operations 81007AE: Create and Maintain Telemarketing and Campaigns in Microsoft Dynamics 365 for Operations 81008AE: Track Leads and Opportunities in Microsoft Dynamics 365 for Ope...
Post a Comment
Read more