Dynamic fields support for multitentancy case

[vitakili]

Feature Request: Dynamic Templates & Tenant-Aware Fields

Summary

In multi-tenant projects it’s common to work with a single collection (e.g. Items) but require different sets of fields depending on the tenant or a selected template. Right now this is only possible by combining JSON fields, custom admin components, and hooks. It works, but it adds a lot of boilerplate and is not very ergonomic.

Use Case

• A shared Items collection across multiple tenants.
• Each tenant (or template) defines which fields are relevant:
  • Real estate → area, rooms, map location
  • Car dealership → mileage, fuel type, year
  • Restaurants → cuisine, opening hours
• Admin UI should display only the relevant fields depending on the tenant/template.
• On save, values should be validated against the template definition.
• Indexed values should be queryable through the API so filtering (gte, lte, equals) works without extra hooks.
• Optionally, fields could include metadata such as icons to improve usability in the admin panel.

Current Workarounds

• Use a json field (e.g. dynamicFields) with a custom admin component that renders inputs dynamically.
• Add a separate item-templates collection to store field definitions.
• Validate values in beforeValidate hooks.
• Flatten values into an indexedFields object in beforeChange so they can be queried.

While this approach works, it requires maintaining schema logic, validation, UI, and indexing in several places.

Proposal

1. Template-based schema extension
   Link a document to a template that defines which fields apply. Payload would render those fields automatically in the admin panel.

2. Tenant-aware conditional fields
   Allow field visibility and requirements to depend on tenant or template without writing custom components.

3. Native indexed dynamic fields
   Values stored as dynamic fields should automatically be indexed to support filtering in REST and GraphQL queries.

4. Admin UI improvements
   Support optional icons, grouping, and help text for template-defined fields to make dynamic UIs more user-friendly.

Benefits

• Cleaner schemas without duplicating collections per tenant type.
• Less boilerplate: validation, UI rendering, and indexing handled natively.
• Easier to maintain as projects scale across different industries.
• A standardized way to handle a very common multi-tenant requirement.