Loading

Component Visibility with filter on null reference field may prevent page from loading

Дата публикации: Apr 3, 2026
Описание
If the lookup field that is being used as the filter of the component's visibility doesn't have a value, the page will not load its entire content.

As an example, consider a user that doesn't have a Manager defined. If they navigate to a Lightning page that includes a component with the following Component Visibility criteria:

User > Manager > Last Name Not Equal Doe

They may encounter a silent error that prevents the page from completely loading.
Решение

 

This is a known limitation in Lightning Experience Component Visibility. When a component's visibility filter references a lookup field (such as User > Manager > Last Name), and that lookup field is null for the current user, the page may fail to load silently.

 

Workaround:

 

Ensure the lookup field used in the Component Visibility filter always contains a value. Options include:

 

  1. Set a default value on the lookup field using a Flow or assignment rule so that a record is always populated.
  2. Adjust the Component Visibility filter to use a non-lookup field (such as a checkbox or picklist) instead of a lookup relationship chain.
  3. Add a validation rule to the object to require the lookup field before save.
Номер статьи базы знаний

000380891

 
Загрузка
Salesforce Help | Article