Custom Lists & Fields

Flexible data modeling without the EAV mess.

Create definition‑specific fields with tight validation. Keep schemas versioned in code so environments stay in sync.

  • Per‑org uniqueness and indexes enforced
  • Server‑side validation mirrors UI rules
  • Migrations gated by CI checks

FAQs

  • Can options come from a list?

    Yes. Reference a Custom List and manage options centrally.

  • Do you support read‑only fields?

    Yes. Mark fields read‑only and we’ll enforce it in API and UI.

import Script from "next/script";