cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Aditya16
Frequent Visitor

Displaying values of non-primary key column of one table as a lookup choice in another table in Dataverse for Model Driven Apps

Hi All,

 

I am doing a  test of converting a SQL table to dataverse table, below is the structure:

 

  1. Master Table : Company which has columns CompanyID(Autogenerated and Primary key), CompanyName(text)  and other columns
  2. Child Table :Products which has columns ProductID(AutoGenerated and Primary Key),ProductName(text), CompanyID(Lookup from Company table)

Front end application has a form for Products which has columns: ProductName and Company which has a dropdown to display CompanyName from the Company table and based on its selection it is  storing relative CompanyID from Company table in the CompanyID column of the Products table.

 

Following are the issues:

  • It seems that only value from primary key of a table can be used as lookup and other columns cannot be used hence  CompanyID instead of CompanyName is visible , and it is not useful as CompanyName should be visible instead of CompanyID.
  • Should CompanyName be made a primary key and CompanyID  as a Alternate key to resolve the issue of lookup and then create a additional column "CompanyNameLookup"  in the Product table that would display the CompanyName from the Company table. PowerAutomate can be used to update the value of CompanyId based on the value selected in CompanyName.

Please suggest the best approach when converting a sql table to dataverse and the secondary key of master table is used as a lookup in another table.

 

1 ACCEPTED SOLUTION

Accepted Solutions

What you can do in a Model Driven App is create a Quick View form on the table in the Lookup, on the quick view form you put the fields you want to display, then on the main form add the quick view linked to the Lookup field - when the lookup is populated the quick view will show the other fields. 

 

Terminology wise (it is a common mistake):

  • Primary Key is a GUID that is held in a field/column that is the same name as the Table with an "id" suffix
  • Primary Name field/Column is what is displayed by default on the form for the lookup value in Model Driven Apps.  The Primary Name field is not unique unless you create an Alternate Key on it.

Apart from Alternate Key's enforcing uniqueness, their other benefit is when integrating data as the Web API allows you to use them as the key rather than having to know the GUID.

  •  

View solution in original post

4 REPLIES 4
FLMike
Multi Super User
Multi Super User

Hi @Aditya16 

 

Did I answer this question for you before? its so oddly similar.

 

This Statement, is not a question, but it's also inaccurate.

  • It seems that only value from primary key of a table can be used as lookup and other columns cannot be used hence  CompanyID instead of CompanyName is visible , and it is not useful as CompanyName should be visible instead of CompanyID.

.

 

You can easily use any field you want, based on the LookUp, but it sounds like you do not know how, so you are making statements that are not true.

 

Also, when you look at the Tables in Dataverse, through the UI, you do in fact see the Name (if its the primary field) not the GUID.

 

So I am not following

 

Also this question is moot and makes inaccurate statements, learn how to use LookUps to get other values.

  • Should CompanyName be made a primary key and CompanyID  as a Alternate key to resolve the issue of lookup and then create a additional column "CompanyNameLookup"  in the Product table that would display the CompanyName from the Company table. PowerAutomate can be used to update the value of CompanyId based on the value selected in CompanyName.

 

Since there was no actual real question, per se, I responded in kind.

 

However to tell you how you correctly do it.

1. If you are in a Canvas App, you simply use the Current Record from TableA to do this

TableA.MyLookUpTableName.MyLookUpTableValue.

 

2. If you are in a power automate, you simply do a Get item by id, where the ID is equal to the Dynamic Property listed as FieldName (Value) 

 

3. If you want to pass the GUID of the lookup to power automate froma  canvas app

TableA.MyLookUpField.TableName


If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

 

Aditya16
Frequent Visitor

@FLMike 

 

Thanks for the reply,

I hope below points would make it clear:

  • I want to create Model Driven App and not the Canvas based app, In canvas app I can easily refer any column from another table.
  • When I am creating a lookup column in one table which is referring to another table, it do not give option to select which column should be referred and values from the primary key column would be displayed by default.
  • Please provide any link for referring non primary key column from one table as a lookup column in another table in case of model driven app

What you can do in a Model Driven App is create a Quick View form on the table in the Lookup, on the quick view form you put the fields you want to display, then on the main form add the quick view linked to the Lookup field - when the lookup is populated the quick view will show the other fields. 

 

Terminology wise (it is a common mistake):

  • Primary Key is a GUID that is held in a field/column that is the same name as the Table with an "id" suffix
  • Primary Name field/Column is what is displayed by default on the form for the lookup value in Model Driven Apps.  The Primary Name field is not unique unless you create an Alternate Key on it.

Apart from Alternate Key's enforcing uniqueness, their other benefit is when integrating data as the Web API allows you to use them as the key rather than having to know the GUID.

  •  

Could you please provide any reference link, I have tried the approach and following are my observations:

  • Created a quick view with columns Name and ID
  • If the ID column is my Primary Name field then the IDs are appearing in Lookup dropdown and for user they need to select  id to see the corresponding name in the Quick view, that's working fine and storing data in form of id
  • If the Name column is my Primary Name field then the required information is appearing but my backend needs to have ID value instead of name, so I have triggered a flow to update the ID column , any other approach to use apart from the power automate?

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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 in the Forums 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**   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. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (2,189)