Problem statement

In model-driven apps, Customer-type lookup fields always display both Account Lookup View and Contact Lookup View in the lookup dialog. There is currently no supported option for administrators to restrict or hide one of these views (e.g., hide Contacts and show Accounts only).

This creates confusion for end users in scenarios where the business process is Account-only, even though the lookup technically supports both entities.

Business impact

• End users accidentally select Contacts instead of Accounts, leading to:
• Incorrect data association
• Downstream automation or plugin failures
• Additional validation logic or training required
• Customers are forced to:
• Redesign data model (create Account-only lookup)
• Duplicate fields
• Apply custom JavaScript or unsupported workarounds
• just to achieve a simple UX requirement

Ask / Feature request

Provide a supported configuration option to control visible lookup views for Customer-type lookups, such as:

• Toggle to hide Account or Contact lookup view
• Ability to define default and allowed entity types per lookup
• Form-level or column-level setting (similar to lookup filtering)

Why this matters

• Improves data quality and user experience
• Reduces need for customizations and unsupported scripts
• Aligns with real-world business scenarios where:
• Only Accounts are valid customers
• Contacts are managed separately
• Keeps the Customer lookup flexibility while allowing controlled usage

Expected behavior (example)

If an admin configures:

• Customer lookup = Account only

Then:

• The lookup dialog shows only “Account Lookup View”
• “Contacts Lookup View” is hidden and inaccessible