Zum Hauptinhalt springen

​
Objektverwaltung

Yes, custom objects can be deleted. You can also deactivate them first, which hides the object and its data from the interface while preserving the data.
No, standard objects cannot be deleted. You can only deactivate them, which hides them from the interface but preserves the data.
You can create as many custom objects and fields as you need — the price doesn’t change.
You can rename the label of standard objects (People, Companies, Opportunities), but not their API names. The API names are fixed for consistency across all Twenty workspaces.
Yes, you can change the icon for both standard and custom objects in Settings → Data Model.
Noch nicht. Die Reihenfolge der Objekte in der Navigation ist derzeit festgelegt, aber diese Funktion ist für eine zukünftige Veröffentlichung geplant.
Alle aktiven Objekte erscheinen in der Navigation. Sie können Objekte, die Sie nicht benötigen, unter Einstellungen → Datenmodell deaktivieren.

​
Feldmöglichkeiten

No, field types cannot be changed after creation. If you need a different type, create a new field with the correct type, migrate your data, then deactivate the old field.
Unsere GraphQL-API verwendet beide Formen für verschiedene Operationen:
  • createPerson (Singular) für Einzelaktionen
  • createPeople (Plural) für Massenoperationen
Dies schafft Einschränkungen, wenn Singular- und Pluralformen gleich sind, verbessert jedoch die Entwicklererfahrung.
Bestimmte Feldnamen wie Typ oder Applikation sind für Systemnutzung reserviert. Wählen Sie stattdessen alternative Namen wie Kategorie oder Klassifikation.
  • The field is hidden from the interface
  • Existing data is preserved
  • You can still access the field via API
  • Existing relations remain but you can’t create new ones
  • You can reactivate the field later
Currently, you cannot make custom fields required. All fields accept empty values. You can use workflows to enforce required fields by sending alerts or blocking actions when fields are empty.
  • Unique: No two records can have the same value in this field
  • Required: The field must have a value (not currently supported for custom fields)
Formelfelder kommen im 1. Quartal 2026. In der Zwischenzeit können Sie Workflows verwenden, um Feldwerte automatisch zu berechnen und zu aktualisieren.
Verschachtelte Felder kommen im 1. Quartal 2026. Aktuell können Sie Workflows verwenden, um Felderwerte von verwandten Objekten einzuholen. Zum Beispiel: Um die Branche eines Unternehmens in einem Personen-Datensatz anzuzeigen, erstellen Sie ein benutzerdefiniertes Feld für Personen und verwenden Sie einen Workflow, um den Wert zu synchronisieren.
Feld-Umsortierung wird mit benutzerdefinierten Layouts im 4. Quartal 2025 verfügbar sein. Currently, fields appear in alphabetical order.

​
Beziehungen

Ja! Self-referencing relations are supported and recommended for use cases like account hierarchies. For example, create a relation from Companies to Companies to track parent/child accounts.
Many-to-many relationships are coming in H1 2026. Currently, create an intermediate object with two one-to-many relationships as a workaround.For example, to link People and Projects (many-to-many), create a “Project Assignments” object with:
  • A relation to People (many assignments → one person)
  • A relation to Projects (many assignments → one project)
These allow one object to relate to multiple different object types through a single field. For example, Notes can be attached to People AND Companies AND Opportunities simultaneously.Each Note links to one Person, one Company, and one Opportunity at the same time.Learn more in Relation Fields.
Yes, you can create multiple relations between the same two objects. For example, a Company could have both a “Primary Contact” and “Billing Contact” relation to People.
When you delete a record, the relation link is removed from the related records. The related records themselves are not deleted.
While technically possible, circular relations (A → B → C → A) should be avoided as they can cause confusion and potential performance issues.

​
Zugriff und Berechtigungen

Go to Settings → Data Model to view and edit all your objects and fields.
Wenden Sie sich an Ihren Arbeitsbereichs-Administrator. Der Zugriff auf das Datenmodell ist in der Regel nur für Administratoren eingeschränkt.

​
Data Management

There’s no hard limit on record counts. However, very large datasets may impact performance in some views. Use filters and views to manage large datasets effectively.
Yes, you can import CSV data into any object, including custom objects. The import process supports field mapping for custom fields. See How to Prepare Your CSV Files.
Currently, there’s no built-in export for data model configuration. Contact support if you need to migrate your data model between workspaces.

​
Brauchen Sie mehr Hilfe?

Check our Implementation Services for help with complex data model design.