Breaking news from around the world
Get the Bing + MSN extension
The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Tested on:Dynamics 365 version 9.0.2 (web client)
Project hierarchy is a frequently asked question in a Dynamics 365 Project Service Automation implementation. While visualizing hierarchically related data is not yet supported on the Unified Client Interface but is just around the corner, the classic web client can be used for this. If you are going to update to PSA V3.x very soon, the hierarchy visualizations on UCI will be just around the corner for you.
The whole customization process of visualizing a project hierarchy is quite fast and simple to accomplish. What you do want to keep in mind is that you want to create a new self-referential one-to-many (1:N) relationship as the OOTB one named msdyn_msdyn_project_msdyn_project_ProjectTemplate is used for Project Templates and should be set to Hierarchical = No.
1. Create a self-referential one-to-many (1:N) relationship for the Project entity. Make sure you set Hierarchical = Yes.
2. Add the new lookup field to your Project main form.
3. Create a new Quick View form the Project entity. Remember that the first four fields will be displayed on the visualization/tile.
4. Edit Hierarchy Settings and choose the Quick View form created in step 3.
5. Create a new Project record. One is a parent on which the created lookup is not populated and one is a child on which the lookup holds the value of the parent project.
6. Verify that the hierarchy visualization can be seen on your active view. Clicking on the small icon next to the record name opens up the hierarchy visualization.
I hope this brief article helps you visualize project hierarchies more effectively. For more details and requirements on visualizing hierarchically related data, check out the official article on docs.microsoft.com here.Disclaimer:All my blog posts reflect my personal opinions and findings unless otherwise stated.
Business Applications communities