Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
I have created a hierarchical relationship on the territory entity but I do not see the button View Hierarchy. What could be the problem? My environment is on Wave 2.
I test it in my environment and I can see the hierarchiacl relationship on the territory entity normally.
Basically, you need to do two things, select Hierarchical to Yes, and fill the lookup field of the relationship on the territory entity form.
Please refer to my process to see if you have any omissions.
1) Open the relationship territory_parent_territory, change Hierarchical to Yes.
2) Go to Territory, select the Parent of the Territory.
3) Go to Territory view, wo can see the hierarchiacl relationship icon, click it, we will turn to the hierarchiacl relationship view.
If you create a new 1:N relationship for the territory entity, you still need to select Hierarchical to Yes, and populate the lookup field.
Thanks Lu Hau, but that is in deep a customization, I was expecting that I could visualize that without having to modify the standard objects. It is that on Microsoft Pipeline?
In my opinion, that is acceptable. Because the Hierarchical option of the relationship attribute is only to privode the feature of the hierarchical relationship, it has no other role.
If you would implement this feature through Microsoft Pipeline, I recommend you also post this theme in Azure Community.
Business Applications communities