cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
RIYxWRK
Helper II
Helper II

Lookup multiple columns in a related table

Hi all

 

Apologies if this has been asked before, but I am new to Model Driven apps and trying to figure out how to create a table that does lookups correctly.

 

  • I have a custom table called Tasks.
  • I need a column called 'Assigned' to lookup the User table.
  • I need another column called 'task manager' to lookup the same User table.
  • I then need to be able to have columns called 'Assigned email' and 'Task manager email' so that a flow has an email to send notifications to from the app when a stage gate is reached.

 

So basically what I don't understand I how I can make any column in a custom table lookup the different columns from the same relationship/lookup. Do I just create one relationship and set each custom column to be a lookup to the same table/relationship? Ideally, when you set a primary piece of information like 'User name', then the other custom columns like 'user email' should only show the email for the user you selected.

 

I hope that makes sense. Appreciate any help anyone can offer.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
MarioRing
Super User
Super User

  • PROJECT table shouldn't have any lookups related to TASKS and REQUEST.

 

  • TASK should have only one Lookup field to the PROJECT. Just name the field "Project" or "Related Project". I assume that a single TASK can be related to one and only one PROJECT. We don't need more lookup fields for the PROJECT's name or number. Imagine a situation where two lookups on the TASK will point to the PROJECTs, but one will refer to PROJECT1, and the other will refer to PROJECT2. It makes no sense. 

 

  • If you would like to show on a form of TASK some additional fields stored on parent PROJECT, you can create something called a "Quick View Form" of the PROJECT table. That Quick View form will consist of PROJECT fields (Project Number, Project Name, Project Type, etc.). You can put this QV form on TASK main form. If you do this, the user who fills in the TASK form, after they choose the proper PROJECT in lookup, will see the values of the related PROJECT on the TASK form (because of PROJECT's Quick View Form).

 

  • REQUEST DETAIL should have only one lookup to the TASK and one lookup to the PROJECT (from the database integrity and standards you shouldn't use PROJECT lookup, because choosing the TASK already points to the specific related PROJECT for the chosen TASK. Imagine if your request points to the TASK from different PROJECT that TASK points to. However, it will be easier for you to use both Lookups for now).
    You can use similar technique to with Quick View forms, to show related fields that belong to chosen PROJECT and chosen TASK. 

Answering another question - yes, you can apply a filter on the Lookup field, to allow users to choose records that fulfil filter criteria. 

 

Proposed Data Structure:

  • PROJECT
    • Name (main field, text)
    • Project Number (text)
    • Owner (probably Lookup to User, or Contact, or just a text field)
  • TASK
    • Name (main field, text)
    • Task Number (text)
    • Project (lookup to PROJECT)
  • REQUEST DETAIL
    • Project (lookup to PROJECT)
    • Task (lookup to TASK)
    • Other fields

 

FORMS:

  • Create a Quick View Form of PROJECT
    • Put there fields of Project you want to see on TASK and REQUEST DETAIL records form
  • Create a Quick View Form of TASK
    • Put there fields of TASK you want to see on REQUEST DETAIL records form
  • Edit the main form of PROJECT
    • Put the subgrid of TASKs to show all TASKS related to the given PROJECT
    • Put the subgrid of REQUEST DETAILS to show all REQUEST DETAILS related to given PROJECT
  • Edit the main form of TASK
    • Put there lookup to Project
    • Put there Quick View form of Project, connected to the lookup above
    • Put the subgrid of REQUEST DETAILS to show all REQUEST DETAILS related to given TASK
  • Edit the main form of REQUEST DETAIL
    • Put there lookup to PROJECT
    • Put there Quick View form of PROJECT, connected to the lookup above
    • Put there lookup to TASK
      • On the form editor, when you selct this field, and choose "Filtering" from the panel on the right, you'll be able to add filtering that shows only the TASKS that are related to previously chosen PROJECT.
    • Put there Quick View form of TASK, connected to the lookup above

View solution in original post

6 REPLIES 6
parvezghumra
Most Valuable Professional
Most Valuable Professional

@RIYxWRK 

If you Task table has been created with user/team ownership then you should get an ownerid column in it automatically - this can target the User or Team tables. You can then create an additional lookup to reference the manager, which can also target the User table.

 

When you create lookup column in a table, under the hood, there is a N:1 relationship created for you automatically. You can then traverse this relationship for records within your code, logic, customisations and automation to retrieve data from the related record. So in your case, this will mean the user's email address and managed email address do not need to be stored directly on the Task table. Instead you can grab this data from the referenced User in the lookup columns as and when you need. This approach will result in having a 'normalised' data model, with less data duplication etc




Parvez Ghumra, XRM Solutions UK
Microsoft Business Applications MVP | Power Platform | Dynamics 365 CE/CRM | Azure - Developer | Technical Consultant | Technical Architect | Community Super User | User Group Co-Organizer | Blogger

If this response helped you in any way, please give kudos by clicking the 'Thumbs Up'/'Like' button and/or marking it as an 'Accepted Solution'. This helps others by providing a quick way to identify likely solutions to their issues.

Also, for more useful content, please free to add me as a friend on this forum, follow my blog, follow me on Twitter and connect with me on LinkedIn

Thanks for this.

 

Can I check my understanding?

 

  1. I set up a one to many relationship to the User table, and use the Primary Key of the lookup column as the Column Display Name.
  2. Then I create a column called 'Assigned to' and tell it to lookup to that relationship.
  3. Then in the App designer, I can create new fields on the form to show the email for that user and Power Automate will be able to reference that information too, just from that relationship connection?

Thanks

When you create a 1:N or N:1 relationship, the Dataverse automatically creates a new lookup field (column).

When you create a new field (column) of Lookup type, the Dataverse automatically creates a proper relationship for the given lookup field.

That means you have to perform either of these actions, and obviously the easiest way is to simply create a lookup field to point another record in the system.

Moreover - each lookup field has its own relationship, and you can freely create multiple lookups connecting the same pair of records but with different contexts.

 

If you want to show the e-mail of the user on the form consider using a quick view form. This is an form element, that allows you to show fields that come from the foreign record set in lookup field. In your case, you need to create a Quick View Form of User table, where you put user's e-mail addres. Then you use this Quick View Form on main Task form, connect it to the lookup field. 

 

However, Power Automate can browse through relations in every direction (like a spider!;)), so you don't need to put the user email directly on the Task form. The automation will find the proper value.

RIYxWRK
Helper II
Helper II

Hi thanks for the replies.

 

Can I check my understanding on how to do this with you?

I will revise my requirement below to be closer to my actual use case.

 

My tables:

PROJECT

  • project number
  • project name [primary]
  • Project owner
  • more fields..

PROJECT TASK

  • task name [Primary] 
  • task number
  • Project name [same name in Project primary key in Project table]
  • more fields...

REQUEST DETAIL (custom table for app)

  • request notes
  • task lead
  • task reviewer
  • more fields....

 

I need to create a model driven app where users pick the Project number (Project table), pick the Project name (auto filtered from project number), and then the Task name and Task number (both filtered from the task name) value.

 

So in my case, I need to be able to use values from PROJECT table and PROJECT TASK which link on the Project Name column.

 

So my questions are:

1. Do I need to create these fields in my CUSTOM table as lookups (a separate relationship for each column?)

  • Project number [lookup to PROJECT]
  • Project name [lookup to PROJECT(again)]
  • Project task name [lookup to PROJECT TASK]
  • Project task number [lookup to PROJECT TASK]

2. I need to be able to filter on certain data like if the task is actually active or published. Do I do that configuration in the model driven app form? It seems you can only lookup the primary key of a lookup table when assembling the table itself without being able to tell it which column to actually look at in the related target, so do I tell the app form designer which column to actually look at in the related table? 

 

My main concern is the modelling of the data and building the relationship in the proper way, which right now I don't fully understand. I don't know if I need to recreate those columns in my custom table (it's a silly question in some respects but I keep getting conflicting info). I guess so because I will need to store that info somewhere so it may as well be in the CUSTOM table with my other custom columns?

 

I hope that makes sense and really appreciate any advice that can get me past the starting line 😁

 

MarioRing
Super User
Super User

  • PROJECT table shouldn't have any lookups related to TASKS and REQUEST.

 

  • TASK should have only one Lookup field to the PROJECT. Just name the field "Project" or "Related Project". I assume that a single TASK can be related to one and only one PROJECT. We don't need more lookup fields for the PROJECT's name or number. Imagine a situation where two lookups on the TASK will point to the PROJECTs, but one will refer to PROJECT1, and the other will refer to PROJECT2. It makes no sense. 

 

  • If you would like to show on a form of TASK some additional fields stored on parent PROJECT, you can create something called a "Quick View Form" of the PROJECT table. That Quick View form will consist of PROJECT fields (Project Number, Project Name, Project Type, etc.). You can put this QV form on TASK main form. If you do this, the user who fills in the TASK form, after they choose the proper PROJECT in lookup, will see the values of the related PROJECT on the TASK form (because of PROJECT's Quick View Form).

 

  • REQUEST DETAIL should have only one lookup to the TASK and one lookup to the PROJECT (from the database integrity and standards you shouldn't use PROJECT lookup, because choosing the TASK already points to the specific related PROJECT for the chosen TASK. Imagine if your request points to the TASK from different PROJECT that TASK points to. However, it will be easier for you to use both Lookups for now).
    You can use similar technique to with Quick View forms, to show related fields that belong to chosen PROJECT and chosen TASK. 

Answering another question - yes, you can apply a filter on the Lookup field, to allow users to choose records that fulfil filter criteria. 

 

Proposed Data Structure:

  • PROJECT
    • Name (main field, text)
    • Project Number (text)
    • Owner (probably Lookup to User, or Contact, or just a text field)
  • TASK
    • Name (main field, text)
    • Task Number (text)
    • Project (lookup to PROJECT)
  • REQUEST DETAIL
    • Project (lookup to PROJECT)
    • Task (lookup to TASK)
    • Other fields

 

FORMS:

  • Create a Quick View Form of PROJECT
    • Put there fields of Project you want to see on TASK and REQUEST DETAIL records form
  • Create a Quick View Form of TASK
    • Put there fields of TASK you want to see on REQUEST DETAIL records form
  • Edit the main form of PROJECT
    • Put the subgrid of TASKs to show all TASKS related to the given PROJECT
    • Put the subgrid of REQUEST DETAILS to show all REQUEST DETAILS related to given PROJECT
  • Edit the main form of TASK
    • Put there lookup to Project
    • Put there Quick View form of Project, connected to the lookup above
    • Put the subgrid of REQUEST DETAILS to show all REQUEST DETAILS related to given TASK
  • Edit the main form of REQUEST DETAIL
    • Put there lookup to PROJECT
    • Put there Quick View form of PROJECT, connected to the lookup above
    • Put there lookup to TASK
      • On the form editor, when you selct this field, and choose "Filtering" from the panel on the right, you'll be able to add filtering that shows only the TASKS that are related to previously chosen PROJECT.
    • Put there Quick View form of TASK, connected to the lookup above

@MarioRing ah this helps a lot thank you so much for taking the time to help me out.

There can be multiple tasks related to a project [name] and the use should be able to see a fileted list based on the Project [number and name] they in the app. The structure you propose makes sense -  I was overcomplicating it in my head.

 

Also thanks for clearing up the part about the lookup configuration in the app. 

Helpful resources

Announcements

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Users online (3,378)