+27

Hierarchy control to replace deprecated control for model-driven apps

Niels 1 year ago updated by Konrad 2 weeks ago 9

The hierarchy control in model-driven apps is being deprecated by April 2025

A custom PCF control with flexibility to be used on standard and custom tables would be really useful for many organizations since Microsoft is not replacing this with a new universal control.

Hierarchy control in model-driven apps is deprecated

Effective October 2024, the hierarchy control, which is used to define and query hierarchically related data in model-driven apps, is deprecated. The control will continue to work in existing apps until April 2025, at which time it will be removed from the product.

The hierarchy control allows users to visualize relationships between records for a table. This is applicable for any table that has a self-referential relationship.

Why is this needed?

Due to low usage, issues with accessibility, and incompatibility with the modern look, the hierarchy control will no longer be supported.

Impact

After its removal, end users will not be able to view the visual representation of the hierarchical relationships of records.

Action required by you

You can enable the control until its removed in the product by editing the app settings. Go to Power Apps (make.powerapps.com) and open the app you want for editing. Then go to Settings > Features tab and enable the Enable the "View hierarchy" capability setting.

If the hierarchy view is essential to your app, a custom PCF control that handles the hierarchy view must be created and deployed.

+4

Anyone with self referencing tables will understand how useful the Hierarchy view is! It might not be used on a daily basis, but I am sure the calls will start rolling in when people want to understand the parent/child relationships for accounts or opportunities and other custom, self-referencing tables.

+1

Resco brings a new hierarchy control PCF to Power Platform | Resco

supporting multiple tables, providing even more value than deprecated one

It looks great Mario. I am looking forward to trying it out. 

Microsoft is releasing an advanced Hierarchical Visualization control in Dynamics 365 Sales. The control is highly customizable, provides in-place editing of records in the hierarchy view, and most exciting, supports complex cross-table hierarchies.   

We have finished the private preview of the v1 (single table self-referential hierarchies) which is now shipping in D365 Sales to public preview in September. We plan to GA the control in October.  If you have a single D365 Sales seat, you can configure the control and make it available to your organization.

The v2 control supporting complex cross-table hierarchies is already in private preview and will GA January or February of 2026.

 

https://learn.microsoft.com/en-us/dynamics365/sales/hierarchy-visualization

Updated

I'm happy to announce that Microsoft is releasing an advanced Hierarchical Visualization control in Dynamics 365 Sales. The control is highly customizable, provides in-place editing of records in the hierarchy view, and most exciting, supports complex cross-table hierarchies.

Version 1 (Sept. preview, October GA)
The v1 release supports single table 'self-referential' hierarchies. The v1 base release displays customizable tiles in a hierarchy you define.  When tiles are selected, a details form side pane is displayed where the records are fully editable. You select a form for the tile and the form for the details page as well as the view used to filter data to just the records you need. 


This release introduces 4 different layouts users can toggle between to find a layout that works well with the hierarchy data's shape. Tiles support customizing the size, color, whether to show or hide the profile picture, and the ability to include labels for fields as needed. Build your hierarchy on any Standard or Elastic table in Dataverse, both out-of-the box tables as well as custom tables.


Version 2 (October preview, February GA)
The v2 release builds on the v1 base adding support for customizable complex cross-table hierarchies. An example could be a hierarchy where an Account has child Contacts which have child Opportunities. Each child table included in the hierarchy can be configured to show just records with a direct relationship to the parent, or you can choose to show a full self-referential sub-hierarchy. For example, in the Account > Contacts > Opportunities hierarchy, the Contacts table, any or all of the 3 tables could be configured to display a full self-referential hierarchy. You can design your hierarchies based on your data and business needs.


Licensing: If you have any Dynamics 365 Sales licenses, you can configure the control and make it available to your organization.


v1 documentation is live!

https://learn.microsoft.com/en-us/dynamics365/sales/hierarchy-visualization

Hi Scott, 

That sounds really great - especially the support for complex cross-table hierarchies.

I have two questions. 

1. Licensing
You write that "if you have a single D365 Sales seat, you can configure the control and make it available to your organization" and "if you have any Dynamics 365 Sales licenses, you can configure the control and make it available to your organization.".

Does that mean, that Power Apps licensed users can use Hierarchical Visualization Control without having a D365 Sales license?

2. Navigate to Hierarchical Visualization Control from views

Will it be possible to navigate to the Hierarchical Visualization Control from views like in the old version? 

BR,

Niels

I'll be frank, this is ridiculous.

On the official deprecations list (https://learn.microsoft.com/en-us/power-platform/important-changes-coming) the reason for it being removed in a month is:
"Due to low usage, issues with accessibility, and incompatibility with the modern look, the hierarchy control will no longer be supported." - not fitting with the new look as one of the main reasons? And instead of making it more accessible you remove it? If it was not accessible then it also may explain 'low usage' right?

Another note on the low usage part - As someone mentioned people generally use self referencing tables. I can imagine lots of companies could rely on them, for example imagine sales departments being able to view relationships between nested clients for thousands of their clients. Or for basicaly any nested entity - as it is just representation of parent-child relationship, which is like the most basic relationship there is for entities. 

But If the usage is so low why bother with the Hierarchical Visualization control in Dynamics 365 Sales, when in the official deprciation list I linked above Microsof just said that, quote:

"This feature is fully removed October 2025. If the hierarchy view is essential to your app, a custom PCF control that handles the hierarchy view must be created and deployed." It seems the general plan was to leave users on their own, but I see that something changed.

Maybe there were some signals from people,that the feature is in fact crucial, and thus the V1 of the new control is being created? Anyways, I hope that this rushed V1 will come in a way that allows for seamless switch form the old hierarchy control to the new one, or that the elimination of the current hierarchy control will be postponed. Because, as I understand, old one is removed in October, and V1 of the new one will be available in October? But is it at the start or end of October? I guess we'll see soon enough.

I'm struggling to implement hierarchical view in our CRM Model Driven Power App in our org for a few days now, and learned that the feature is hidden and in the process of being put down for bogus reasons, with no good replacements. I can imagine there are more people like me, not all of them will stumble upon this thread here.