web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Answered

How to show a different column in a lookup field instead of the primary name column?

(0) ShareShare
ReportReport
Posted on by 190

I have two related tables:  Requests and a custom users table.   It's a N:1 relationship. In the custom user table I have the user's full name as the primary name column.  I also have the email as another column.  

In the Requests form, I have two lookups to the same custom user table:  Requester and Requester email.  The user manually selects the Requester, then I have a javascript webresource that uses

XMLHttpRequest() to use the Requester value to select the email, and set the value to this Requester email field.  But the field still shows as the Requester instead, even though I am still able to get this email field to do something else with it and it works.  But I just want to know how to get it to show the email column instead of the primary name.  Thanks. 
I have the same question (0)
  • Verified answer
    a33ik Profile Picture
    84,331 Most Valuable Professional on at

    Hello,

    Lookups were created to show the Primary Field value as a displayed value.

    If you want to have the requestor's email as a field on the form - create a text field instead of a lookup.

  • Verified answer
    Steve Zhao2 Profile Picture
    Microsoft Employee on at

    Hi bp3378,

    Andrew Butenko is correct. Lookup field displays the primary field value. This is by design and there is no OOB way to change this behavior. Although, you could use JS to modify the display name and the display name would not save into dataverse. However, it's not recommended to do like this.

    So, Andrew Butenko's suggestion (use text field instead of lookup) should be the way.

  • jdalske Profile Picture
    547 on at

    I am attempting to do this with the Lead Topic field so that it displays in the connected Opportunity.  If I use a lookup it pulls in NoName because why on earth would Contact be the primary field (that makes no sense and we don't even use that field).  Topic is our only required field.  I am no JS expert.  If you have any ideas on what JS I can put in my "Originating Lead" field on the Opportunity to show the topic of the Lead that would be most helpful.  Thank you in advance.

  • jdalske Profile Picture
    547 on at

    I think I got it without JS.  I just mapped the two fields in 1:N relationship:

    subject - Lead entity

    originatingtopic (text field) - Opportunity entity

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 172

#2
ManoVerse Profile Picture

ManoVerse 58 Super User 2026 Season 1

#3
Niki Patel Profile Picture

Niki Patel 42

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans