Edit

Share via

Troubleshoot Lookup issues in model-driven apps

The Lookup control combines the Lookup field and its relationships, the assigned view, the entity's Quick Find view, the search string, and any applied custom script to build a fetchXML for retrieving search results.

Issues with this operation usually fall into one of these categories:

Search results are incorrect

If the Lookup's search results are missing items or include unexpected items, inspect the fetchXML of the outgoing network request that the control makes.

  • If the fetchXML is incorrect, then the problem is that:

    • The Quick Find view or the view being searched is misconfigured:

      • Missing search fields.
      • Missing the primary field.
      • Using a filter that's blocking results.

    • A client script modifies the control's behavior with API such as addPreSearch or addCustomFilter.

  • If the fetchXML is correct, but the data returned is incorrect, the issue is on the server, such as a misconfigured relationship. Another possibility is that the user doesn't have correct permissions for some entities, which might not be apparent in the network response other than with an omission of results.

Note

  • Selecting the text area (the input box of the Lookup) will show a list of the most recently used items, not a fresh search.
  • Selecting the magnifying glass will trigger a search based on your input, showing results that match your search terms. You can configure the control to always perform a search when you select the text area, instead of showing recent items.

Views are incorrect

  • If an entity or view is missing from the Lookup views or results, or the default view is incorrect:

    • Verify that the entity is enabled for the app.
    • Verify that the user has permissions and roles required to interact with the entity and related entities.

  • If the addCustomView API is being applied, verify that the viewId isn't already used.

  • If the lookupObjects or setDefaultView API is being applied, verify that the viewId belongs to a view that's included in the current app.

Result fields are incorrect

The Lookup control's search results are presented in the order that they're listed for that entity's Lookup view, with blank fields being replaced with the next nonblank field. A multi-entity Lookup can have results with different orders of fields if the entities' Lookup views have different field combinations.

See also