You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new ModelAdmin searchForm uses a graphql search lookup service. It is being applied to has_many relationships on a dataobject in modeladmin and this can cause queueing and the user experiences delays. Also when the search field is exposed, the "Link Existing" field disappears.
Steps to Reproduce
We've got a complex data model with 41 has_many relationships on a particular dataobject. When we use ModelAdmin to edit that object, we see an explosion of graphql queries to load the search forms for those 41 relationships. The browser can only handle a handful of queries at a time, so they all get queued up and the user has to wait for them all to complete. Many of the requests return 400 error anyway (response is "No search form could be generated"). Is there a way to disable the search lookup per relationship?
Perhaps it would be more preactical if the searchForm schema was queried on demand (when someone clicks the search icon) rather than all relationships queried on page load?
The text was updated successfully, but these errors were encountered:
Affected Version
4.3.1
Description
The new ModelAdmin searchForm uses a graphql search lookup service. It is being applied to has_many relationships on a dataobject in modeladmin and this can cause queueing and the user experiences delays. Also when the search field is exposed, the "Link Existing" field disappears.
Steps to Reproduce
We've got a complex data model with 41 has_many relationships on a particular dataobject. When we use ModelAdmin to edit that object, we see an explosion of graphql queries to load the search forms for those 41 relationships. The browser can only handle a handful of queries at a time, so they all get queued up and the user has to wait for them all to complete. Many of the requests return 400 error anyway (response is "No search form could be generated"). Is there a way to disable the search lookup per relationship?
Perhaps it would be more preactical if the searchForm schema was queried on demand (when someone clicks the search icon) rather than all relationships queried on page load?
The text was updated successfully, but these errors were encountered: