Lookup column show only primary key - model driven

[dennisb88]

Hi all,

I'm building a model driven app where I've two tables:

• Equipment
• Equipment owner

In my equipment order I've an lookup field added to the equipment table, named Owner (this is also a lookup field to the related user table).

It works fine, but when I save an order It's shows me only the primary key column in the Main form (form based in equipment order).

I want display the column: owner column not the Equipment ID (the primary key column).

How can I achieve this? I've already changed the views and forms in the equipment owner table, but that wasn't help

[dennisb88]

I just found this topic, and it look that it isn't possible. Or is this changed?

[ChrisPiasecki · Accepted solution]

Hi @dennisb88,

Lookup fields will always show the primary name of the table and this cannot be changed. Therefore, it's advised to set the primary name field to something that is distinguishable and readable by your users. 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[CosmoKramer]

Hello all,

Continuing on with this threat topic, in my Dev lab my desired Table Primary Key is about 60 characters in length which will most likely cause database search performance issues further down the track, hence the reason why I used the 'Autonumber' primary key type instead.

But if I use this work-around solution approach, my future users will have no idea what the returned Cascading Filtered Lookup search number is...which makes the database useless....   😞

Question: How do I work around this Catch-22 scenario???

NB: I want the returned long Primary Key result to be displayed within the Cascade Lookup field and not within an additional 'Quick View Form' line.

[Stevieed]

find the lookup view in the table, modify it to add a few more column, inlcuding the 60 character one, then when you press search icon on the lookup field, it will show primary key + 60 character column together so the user can understand what they trying to look for in the lookup field

[CosmoKramer]

Thanks for your prompt response, however I already have my Table 'Lookup View' configured with the very long Primary column positioned #1 and the proper number Primary Key as position #2, which works perfectly. But the issue I'm trying to work-around is once the user selects their required 'Lookup View' column, the Table's Main Form displays it as the number.... 😞

So my problem is really with the Main Form Primary Key display, which is meanless to the user

[Stevieed]

Cant achieve that unfortunetly. 

Why cant you use quick view form?

[CosmoKramer]

Dam-it, Janet!!

I have a Quick View Form inserted into my Main Form to display the Primary Key proper 60 character name, but it appears under the Lookup field containing the returned Primary Number Key. It looks very average and will confuse the users.

I'm after the returned Lookup search field on my Main Form to contain the Primary Key Name and not the Primary Number.

I know if I re-create my entire solution to use a 60 character (plus) Primary Keys, the database will take a performance hit once it grows large in size.

[LinnZawWin]

@CosmoKramer 

The actual primary key is the Unique Identifier column with GUID value. What you're referring to is the Primary Name Column (which is displayed as the lookup field value) and increasing the maximum character limit of that column would not have a performance impact.

[CosmoKramer]

Mann you are good...A big thank you  🙂