Dataverse - Model Driven App Cascading Lookup Columns -> Not Working

[CosmoKramer]

Hello all,

I'm new-ish to Dataverse and Model Driven Apps and I have tried every (well, close to it) YouTube video on how to to create a basic 101 Cascading Lookup Form, but the final App never looks up correctly. I've been referencing the 3 below YouTube videos, but with no luck  and the Lookup fields don't lookup....  😞

• https://www.youtube.com/watch?v=GbqnAH5m11o 
• https://www.youtube.com/watch?v=41dptP00KQE 
• https://www.youtube.com/watch?v=2ufzeKcy8D0

I've created following basic 3 Database Relationships and Family App as detailed below:

• Family -> Contains just a single 'Surname' Column with a Many-to-1 relationship with Children database created from the Children database side. With the Form Relationship filtering as per these above YouTube videos
• Children -> Contains 'First Name' and 'Surname' Columns with the Surname as the Primary Key with a Many-to-1 relationship created from the Parents database side
• Parents ->  Contains 'First Name' and 'Surname' Columns with the Surname as the Primary Key with a Many-to-1 relationship created from the GrandParents database side
• GrandParents -> Ditto
• The Family App pointing to the Family Database and using the 'Lookup View' and 'Main Form'.

Lastly, my object creation steps are as shown below -> Does the order of configuring the View and Forms matter??

1. Create the databases
2. Create the 1-to-MANY Relationships by adding the Primary Key Column of the One into the MANY side's Table, View and Form entities
3.  Configure the various Table Views
4. Configure the various Table Forms
5. Create the final App object and Run it

Can anyone see what I'm doing wrong?

Cheers,

Cosmo Kramer

[LinnZawWin]

Can you try to explain how it "never looks up correctly" with the screenshot of your app? I just want to understand how you want to cascade the lookup fields on your form.

Based on the wild guess, I believe you are trying to filter the lookup (of Child, Parent or GrandParent) based on the "Surname".

Did you configure the Filtering for your lookup as in those demo videos? If so, can you please provide the screenshot of that configuration as well?

[CosmoKramer]

Hello Linn,

To answer your question, I've attached a Word doco of what I'm trying to achieve. Are you able to respond back within this 'Living' Word document??

Cheers,

Cosmo  🙂

[LinnZawWin]

I've checked your screenshots and you are creating the relationship wrong for the Family < Children table. You need to create a lookup in the Children table. (check the comments in the attached document)

In the document, I still don't see the part about configuring the form and the Cascading Lookup, so I am not sure how you want to filter.

Based on my guess, you will have to create the Family lookup on your Parents table and when the user selects the Family lookup on the form, you need to show the Child Lookup filtered based on the selected Family lookup value.

[CosmoKramer]

Hello again Linn,

Good pickup, I have corrected this Relationship within my updated attached Word doco v1.2.

I haven't created any of the Views and Cascading Filtered Forms yet, as I first would like to confirm the order of the following steps, as removing all the incorrect Dependencies is an absolute pain!!

Are the next required logic steps correct?

1) For the desired Lookup search Column, go to the MANY side of the Relationship, which in my case is the 'Parents' Table

2) ...What comes next with configuring these pages:

- Any need for additional Relationships to make the below 'Cascading Filtered Lookup' functionality to work? 

- 'Lookup View'...and on which Table...

- 'Quick View Find'...and on which Table...

- 'Active View'...and on which Table...

- Inserting one of the above custom Views into another View or Form object

- 'Main Form'...and on which Table...

[LinnZawWin]

Before answering your questions, I need to understand how you want to configure the Cascading Filtered Lookup. I tried to re-read your first post and the last post but I couldn't find the actual requirement other than making the 'Cascading Filtered Lookup' functionality work. You only have one lookup column in each table (Children and Parents). You need x2 lookup columns to make the 'Cascading Filtered Lookup' functionality work.

On which form, do you want to configure the Cascading Filtered Lookup of which column based on which value?

e.g. On the Parent form, I want to configure the Cascading Filtered Lookup of Parents-2-Children Lookup column based on the Parents-2-Family lookup value. (That is a new lookup)

And I don't think we need to configure the 'Lookup View', 'Quick View Find' and 'Active View' to achieve the Cascading Lookup. You also don't have to insert those views into another view or form object. Those views are available as soon as you create the table and the lookup will just work without configuring anything additional. You just need to configure the Form and Cascading Lookup first. Only if the view of the lookup is not what you expect, you just need to configure the columns, filter, etc.

[CosmoKramer]

Hello again Linn,

Firstly, if the Dataverse would allow you to easily ‘Force’ delete a Table and all its Dependences in a single action, I could create my entire solution and show you in one go, but I’m doing it in 1 step at a time…As you can tell from my Table names (e.g. FAMILY10), I have 10 previous legacy attempt Tables which I can’t get rid of and the only thing I can do is ‘Hide’ them…  

Again, this is just an exercise to learn how to create a Cascading Filtered Lookup Form and not a real application.

1) Although, my desired search logic is:

• Click on the single displayed field (i.e. Surname) on the Family Main Form, which then cascade filters and shows the only ‘Child’ Field (i.e. ‘Tegan’). Upon selecting ‘Tegan’, it displays both ‘Parents’ (i.e. Brett and Claire).

2) Then after I get that working, I’d like to add in a Subgrid to perform the same actions, but in a different display method.

3) To further clarify your “…You only have one lookup column in each table (Children and Parents). You need x2 lookup columns to make the 'Cascading Filtered Lookup' functionality work….”, point, sorry, what Lookup Columns are these and do I always create the One-to-MANY relationship from the MANY side table?

4) To answer your ‘…And I don't think we need to configure the 'Lookup View', 'Quick View Find' and 'Active View' to achieve the Cascading Lookup….’ question, my below 3 reference articles state I have to customise many Views/Forms and even insert a ‘Quick Find View’ into the ‘Quick View Form’…or something to that effect.

• https://www.youtube.com/watch?v=GbqnAH5m11o 
• https://www.youtube.com/watch?v=41dptP00KQE 
• https://www.youtube.com/watch?v=2ufzeKcy8D0

Have I answered all your questions??

Cheers,

Cosmo

[CosmoKramer]

I'm from Australia and its 10pm at night now, so I'll read your response in the morning

[CosmoKramer]

Me again, I managed to get my solution finally going after discovering many 'traps' for Newbees...

To share the love, I'll create a full end-to-end 'How to' doco tomorrow...Stay tuned  🙂

[LinnZawWin]

I'm glad it is working... Great job. 😉👍

Re: ‘Force’ delete a Table, you can just reset the environment or back up before you start your exercise and restore the environment would be the fastest way.

Otherwise, you need to remove the dependencies before you can delete them. Not for the table but if you want to delete the column by removing it from the forms/views automatically, you can use the Attribute Manager from the XrmToolBox.