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 CRM (Archived)

Lookup field only shows one column

(0) ShareShare
ReportReport
Posted on by

Hi everyone,

I've encountered a peculiar situation this morning. In one of our development instance, the lookup dropdown only shows one column from the lookup view.

6862.Screenshot_5F00_4.png

Normally it will show 3 columns like so:

2055.Screenshot_5F00_5.png

Any idea what might have caused this?

Thanks!

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    gdas Profile Picture
    50,091 Moderator on at

    Hi ,

    Please check lookup VIEW of the lookup entity  how many columns are defined. You can add remove columns as per your needs by editing lookup view of the entity.

    ledgeviewpartners.com/.../customize-lookup-views-in-dynamics-crm

  • Suggested answer
    Rawish Kumar Profile Picture
    13,758 on at

    Hi Alvin,

    Looks like someone has messed up with the lookup view of this unit entity.

    navigate to settings > customizations > customize the system > Entity >  unit entity > views > look for lookup view and add required columns again.

    publish all your customizations and see if that works.

  • Suggested answer
    Pawar Pravin Profile Picture
    5,237 on at

    Hi Alvin Budiman,

    It looks like someone has removed remaining column in lookup view. Can you please check lookup view on production instance.

  • Community Member Profile Picture
    on at

    Hi Goutam, Rawish, and Pravin.

    Thank you for your responses.

    I have checked the lookup view and the columns are still there.

    7510.Screenshot_5F00_7.png

    I have also made sure that this is the lookup view used by the field.

    7510.Screenshot_5F00_7.png

    In fact the 2 screenshots in my original question share the same customization. It's just the first one is on the upper layer instance where we make additional customization on top of the bottom's instance.

    Any further ideas are appreciated.

    Thanks!

  • Suggested answer
    gdas Profile Picture
    50,091 Moderator on at

    Hi ,

    Can you please put one single line text field (Make sure the field value available ) in the second position  of the view and do publish all customization.

  • Suggested answer
    Rawish Kumar Profile Picture
    13,758 on at

    That looks strange!

    few things you can try:

    1. try to publish the customizations again and clear the browser cache and see again.

    2. export this view from an environment where it is working and import to this environment and publish.

    3. finally you can look into the customization xml of this view to see if in the xml these all columns are available.

  • naZir Profile Picture
    850 on at

    Hi Alvin,

    Did you check for that effected look up contained records have all the field values. In Look up it shows next 3 field values in a row .

    Regards,

    Nazir

  • Suggested answer
    Alok Singh Profile Picture
    910 on at

    Hi Alvin,

    Could you please check the view used for lookup as sometime we use custom view in lookup and then validate the columns of the views. Ideally first 3 columns of view used in lookup will be displayed for entity.

  • Community Member Profile Picture
    on at

    Hi everyone, thanks for the response.

    I have checked your suggestions and there is no irregularity in the customization that might cause this. However, I accidentally found the fix.

    In the form editor, if you open the lookup field properties, you can select the lookup view to be displayed by the lookup field.

    5554.Screenshot_5F00_9.png

    What I did was I selected another default view, save, publish. After I did that, the lookup field shows 3 columns normally. I change back to the originally selected lookup view, save, and publish. Lo and behold, the lookup still shows 3 columns. This is the screenshot of the problematic instance after I applied that 'fix'.

    5554.Screenshot_5F00_9.png

    It's all working as intended now.

    Thank you for your responses guys, I really appreciate your time.

  • gdas Profile Picture
    50,091 Moderator on at

    Please close the thread , which may helps others in future .

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 April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

#2
GJones Profile Picture

GJones 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans