cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
HFG
Advocate III
Advocate III

Multiple LookUp columns using same table in Model Driven App

Hi all, 

 

I have a section in a model driven app which is recording deliveries. A delivery can be split up and stored in 3 different silos. I  therefore need to have 3 fields in the deliveries table which use a lookup to the "Silo" table, but Dataverse will only allow me to create one LookUp column using this table. I have tried adding a Many-to-Many relationship to see if that would work, but it hasn't. Does anyone know how I can solve this?

 

Thanks

2 ACCEPTED SOLUTIONS

Accepted Solutions
dpoggemann
Super User
Super User

Hi @HFG 

 

I would do the following from a model perspective to accomplish:

dpoggemann_1-1622548794847.png

This way you can have a single lookup field on the Delivery Silo to the Delivery table.  

Advantages:

1.  You could have anywhere from 0 to N silos the delivery is split into.

2.  Look at Silo at any time to see deliveries tied to it

3.  You can have fields on the Delivery Silo table that would define metadata about this delivery and silo combination.

 

Hope this helps.  Please accept if answers your question or Like if helps in any way.


Thanks,


Drew

 

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

View solution in original post

HFG
Advocate III
Advocate III

Hi @dpoggemann 

 

You're right, this is best from a modelling persepctive. 

 

For info, for anyone else wanting to do this, I found out that the problem was not that I can't have mulitple fields looking at the same table, but that the relationship which is created had the same name so I wasn't able to save without changing to the name of the relationship. 

View solution in original post

2 REPLIES 2
dpoggemann
Super User
Super User

Hi @HFG 

 

I would do the following from a model perspective to accomplish:

dpoggemann_1-1622548794847.png

This way you can have a single lookup field on the Delivery Silo to the Delivery table.  

Advantages:

1.  You could have anywhere from 0 to N silos the delivery is split into.

2.  Look at Silo at any time to see deliveries tied to it

3.  You can have fields on the Delivery Silo table that would define metadata about this delivery and silo combination.

 

Hope this helps.  Please accept if answers your question or Like if helps in any way.


Thanks,


Drew

 

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew
HFG
Advocate III
Advocate III

Hi @dpoggemann 

 

You're right, this is best from a modelling persepctive. 

 

For info, for anyone else wanting to do this, I found out that the problem was not that I can't have mulitple fields looking at the same table, but that the relationship which is created had the same name so I wasn't able to save without changing to the name of the relationship. 

Helpful resources

Announcements
Power Apps Africa Challenge 2022

Power Apps Africa Challenge

Your chance to join an engaging competition of Power Platform enthusiasts.

Super User 2 - 2022 Congratulations

Welcome Super Users

The Super User program for 2022 - Season 2 has kicked off!

September Events 2022

Check out all of these events

Attend in person or online, there are incredible conferences and events happening all throughout the month of September.

Government Carousel

New forum: GCC, GCCH, DoD - Federal App Makers (FAM)

In response to the unique and evolving requirements of the United States public sector, Microsoft has created Power Apps US Government.

Users online (3,103)