You’re offline. This is a read only version of the page.
Announcements
782
I'm trying to connect a bunch of different entities. Most are simple one to many relationships and those are fine. The part I'm confused on is connecting three levels of related entities.
What I mean by that is say my entities are Purchase Order, Businesses, and Contacts. My Businesses entity is just the business information for the places we would order from. But each of these businesses could have multiple contacts I want to keep track of. I don't want duplicate businesses (Best Buy - Craig Phillips, Best Buy - Janice Janiston), so I thought I would break the contacts out to its own entity.
So you would start filling out your Purchase Order, and select the Business. The Business address and other info is brought in. Then I would ideally have a filtered lookup that only pulls in Contacts that have the selected Business. Also, it is necessary to be able to pick multiple contacts in a repeating table sort of way.
Hopefully my explanation makes sense. Can anyone point me in the right direction for how I would accomplish this?
Is this a canvas app or a model driven app?
One way or the other you would have a purchase order entity and add a lookup field for business and a lookup field for contact.
Don't bring address fields from business into purchase order--for good data quality, leave the address data on the business entity and display them on the form for purchase order.
For model driven apps you can do this with a quick view form from business (suggest using account entity, as that already has addres fields). Here is why you should never build a custom company/business entity, but use the OOTB account entity https://crmtipoftheday.com/1302/should-i-recreate-the-account-entity/
for a canvas app where you have a drop-down for account, you can add a drop down for contact and filter it like the following:
Share
Report
All responses (
Answers (
Filter(Contacts,_parentcustomerid_value =Dropdown1.Selected)
If instead of canvas app you are doing model driven app, there is a special form property that can be set to filter a dependent lookiup
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/special-field-properties-legacy
Let me know if you are doing model driven and I will update with steps for that.
@notj if this answers your question, please mark it a solution
