Hi,
I've been googling the entire internet to figure out how I do auto-population of my child lookup columns, pending on first selected choice of parent lookup. Unfortunately, I can simply not figure it out. I have been experimenting with business rules in hopes of this would actually solve my problem, men without any luck..
I have this extremely simple thing where I have a form, first field is a lookup to another table where I have some meta-data. When I select a value from this lookup, I want several other fields to be auto-populated based on the parent value. The relationship from the parent to the child is 1:n and all data is stored in Dataverse.
How do I do this?
I have a couple of lookup fields and a choice field I would like to have populated based on the parent value. I noticed on the internet that JavaScript was potentially an approach, but I have zero skills in that, so if someone could teach me just the basics of that approach - or even simpler, can this be done via business rules?
Thanks a lot in advance!
Hi @CDFS,
It is possible filter out-of-the-box lookups based on another lookup and to filter subgrids based on a lookup on the form:
Filter Lookups
On your form designer, switch to classic view by clicking the "Switch to Classic" button in the top menu, then in the classic form designer, select your lookup and click "change properties". Configure the filtering as per below:
Filter subgrids
There are 2 main ways: create a quick view form (QVF) or Form Component Control on the lookup entity that you want to filter. Add a subgrid on that form with filtering on the current record (see image below), then add the QVF or set the Form Component Control on the main form and you'll see the related records filtered to the lookup.
Hope this helps!
I have this extremely simple thing where I have a form, first field is a lookup to another table where I have some meta-data. When I select a value from this lookup, I want several other fields to be auto-populated based on the parent value. The relationship from the parent to the child is 1:n and all data is stored in Dataverse.
So, filtered Lookup is as per CDFS post. To populate data off a parent Table on the child there are a number of options, and it depends on what you need to do
Note: the above is for a Model Driven App, completely different for a Canvas App.
Hi - Thanks for this! I actually already did this, but this is not really solving the matter of populating e.g. a dropdown field on the form when I select a value from the parent lookup 🙂
Hi @Fubar ,
You hit it correctly. My users can use the create child record from the parent record, but I also have users that will go straight to the child table and start populating values (a pre-requisite for the app itself). So as far as I can see, I need to utilise the first other option (JavaScript), because I need this to be populated onChange of the primary parent lookup field. In that regard I can also start using business rules to show/hide relevant fields based on choices (hopefully).
I'm an absolute newbie regarding JavaScript. Would you be able to write a simple example code that onChange of a primary lookup field then fetches the object value from that, and then populates other lookup fields on the child form (fields that are also on the parent form)? And how would an example be to take a dropdown value from the parent lookup and then populate the same dropdown field on the child record (I suppose this is slightly different from regular parent to child lookups).
If I just have an example, I would be able to hopefully experiment myself out of it 🙂
Sorry, I don't write other peoples code for them unless they are clients. You can google or search the forum and find lots of examples also see https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/walkthrough-write...
User | Count |
---|---|
19 | |
15 | |
14 | |
10 | |
8 |
User | Count |
---|---|
39 | |
30 | |
22 | |
20 | |
16 |