Hierarchies and Self-Joins in Power Apps [Dataverse Relationships Part 2]

[@taar]

Thank you Brian. very clear explanation.

[@PragmaticWorks]

Glad it was helpful!

[@berggrog1]

Brian! Thank you so much these are some deep subjects but I really appreciate your help on this one. Still using classic editor for the this option. Keep up the good work. Great subject

[@PragmaticWorks]

Glad it was helpful! - Brian

[@TheOmegaAlfa]

Thank you for this video! I have only to figure out how to set query/filter on the records that have ~ 'can be parent:yes' and other filters just to see the much less numerous records in the lookups.

[@meganleecy4658]

Great lecture!!! love it!

[@PragmaticWorks]

Glad you enjoyed it!

Hi Brian, Really appreciate all the good content. I am really stuck on this one. In the modern view the Hierarchical checkbox is simply missing. In the classic view it is not enabled. What is missing? I am trying to do as in your second example: Principlals have teachers, teachers have students. I am trying to do a rollup on the number of students per principal, but it seems I can only do one level (students per teacher).

[@LandscapeInMotion]

Excellent showcase mate! What columns represent the hierarchy relationship? And how many sub branches can you have?

[@oysterhoys]

Thanx Brian, great stuff. It is still neccesary to switch to Classic today for the final setting. It seems also that only the first 3 columns of the Quick form can be shown in de Hyrarchy view. Never the less, nice functionality !

[@PragmaticWorks]

Hi there, it's no longer necessary to open the classic mode.

[@oysterhoys]

@@PragmaticWorks The step to create the scheme for the quickform seemed still neccessary. Could you maybe point to where ist can be set in the modern interface ?

[@alexbanzay1519]

good job. thank you

[@ramiromatos1899]

excellente Brian!!, you can indicate an example where only the rows are displayed according to their hierarchy.

[@PragmaticWorks]

You'll see these a number of ways but a common one is a project that has sub-projects.

[@capitanmelanito]

Hello! thanks for the video! I was wondering how to do the opposite, to select a potential parent, and then to add the multiple children in the lookup column,. I see we cannot add multiple values in the lookup, I wish I could do this in canvas too. Thank you!

[@martinnoah9716]

How do you only show the Parent Project on the main view?

[@HatFullOfData123]

Great video, really helped in a solution I'm building. Is there anyway to hide Inactive items in the hierarchy?

[@bankswalshie913]

Great stuff as always! I'm wondering how to get the total value of used relationships. Example: Parent table is "Office", Child table is Staff (1:N). I want to make a database Chart showing All offices on the Axis with Bars showing the number of Staff for each office on the Series(Vert). I was thinking of using a calculation column that pulls the number of staff entries using the relationship, but I'm unsure how to get that data. Thanks again as always.

[@PragmaticWorks]

There's quite a few ways you can implement that. You can use the built in charting to count to build the bar chart you're looking at and counting the rows or you can get a more boring view by doing a rollup column that respects the hierarchy. You can also use a custom PCF component to visualize that. You can find those components at pcf.galleries

[@bankswalshie913]

@@PragmaticWorks The Charting was very simple, I think I was pulling the wrong data to begin with. All working now, thank you.

[@maliarismendi4858]

Hi! Great example!! Can this hierarchy be consumed from a Power BI report?

[@mkavo]

Hi Brian, this is very cool. Say if the Parent project had certain attributes the child doesn't have and vice versa is it still ok to manage it all in one table? Would you have a lot of blank fields then for the different types of projects depending on your hierarchy or does that matter? And lastly if you wanted to propagate some of the attributes from a Parent through to the Child you probably don't need to right because it exists already against the Parent record so you can show it in Views anyway by virtue of the lookup?

[@THEMASTERTM]

But how do you do this with multiple tables? say for example Table A= Building, table B = floor and table C = offices one being the parent of the next respectively as oppose oh having them all in the same table?

[@owenwetherow]

Hi Raul I was thinking about the same problem. Unfortunately when you do a lookup to a table that is not the source table there is no option in the "Relationship" to create a hierarchy. The one option I could think of was to create different views/forms for the same table so that you could use the hierarchy. Did you find a solution?