Optimization options for a large number of selection field items?

Technical assistance
1

Hi

I’m trialing Zammad on a self-hosted instance. Have hit a bit of an issue. We have 19 schools, with a total of ~2000 staff, ~14000 students, ~5000 classes and other related data. We need selection fields for these, as we’d need to automate a large number of our tickets, and cannot rely on customers to manually enter accurate information.

Zammad appears to load all objects, even those that are hidden - So when creating a new ticket, there is a noticeable delay.

What are our options to reduce this delay? I’ve thought of a couple, but these do not appear to be possible in Core Workflows;

  • Disable all selection objects, and automatically enable those linked to the required school.
  • Automatically change from single-selection to multi-selection based on the request type (We currently have separate objects for each).

Any suggestions welcome.

2

It’s a little bit related to the detailed use cases / situations for the fields. But maybe the external data source field could help for such a large number of options.

3

Thanks for the suggestion dominikklein - I’ll explore this route.

4

Hi. Any idea on how I can include the current organization into the query of the external data source?

5
6

I’ve read that. Just saw your note on Pass organization to external data source - #3 by Shaun_Dark_Lord saying that this is probably not possible. That’s annoying, as it means for each external data source object I need (around 30), I need 19 copies to hard code the organization filter (so that schools can’t see each other’s data) and that many core workflows to make the right objects visible… This won’t be fun to maintain…