---
title: FAQ del modello dati
description: Frequently asked questions about Twenty's data model.
---

## Gestione degli Oggetti

<AccordionGroup>
  <Accordion title="Can I delete a custom object?">
    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.
  </Accordion>

  <Accordion title="Posso eliminare gli oggetti standard (Persone, Aziende, ecc.)?">
    No, standard objects cannot be deleted. You can only deactivate them, which hides them from the interface but preserves the data.
  </Accordion>

  <Accordion title="How many custom objects can I create?">
    You can create as many custom objects and fields as you need — the price doesn't change.
  </Accordion>

  <Accordion title="Can I rename a standard object?">
    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.
  </Accordion>

  <Accordion title="Can I change an object's icon?">
    Yes, you can change the icon for both standard and custom objects in **Settings → Data Model**.
  </Accordion>

  <Accordion title="Posso riordinare gli oggetti nella barra di navigazione a sinistra?">
    Non ancora. L'ordinamento degli oggetti nella navigazione è attualmente fisso, ma questa funzionalità è pianificata per una futura versione.
  </Accordion>

  <Accordion title="Posso nascondere gli oggetti dalla barra di navigazione a sinistra?">
    Tutti gli oggetti attivi appaiono nella navigazione. Puoi disattivare gli oggetti di cui non hai bisogno in **Impostazioni → Modello dati**.
  </Accordion>
</AccordionGroup>

## Funzionalità dei Campi

<AccordionGroup>
  <Accordion title="Can I change a field type after creation?">
    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.
  </Accordion>

  <Accordion title="Perché ho bisogno di nomi singolari e plurali diversi?">
    La nostra API GraphQL utilizza entrambe le forme per operazioni diverse:

    * `createPerson` (singolare) per azioni su singoli record
    * `createPeople` (plurale) per operazioni di massa

    Questo crea limitazioni quando le forme singolari e plurali sono le stesse, ma migliora l'esperienza dello sviluppatore.
  </Accordion>

  <Accordion title="Perché alcuni nomi di campi sono protetti?">
    Certi nomi di campi come `Tipo` o `Applicazione` sono riservati per uso di sistema. Scegli nomi alternativi come `Categoria` o `Classificazione`.
  </Accordion>

  <Accordion title="What happens when I deactivate a field?">
    * 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
  </Accordion>

  <Accordion title="Can I make a field required?">
    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.
  </Accordion>

  <Accordion title="What's the difference between unique and required?">
    * **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)
  </Accordion>

  <Accordion title="Posso creare campi di formula?">
    I campi di formula arriveranno nel **Q1 2026**. Nel frattempo, puoi utilizzare i Workflows per calcolare e aggiornare automaticamente i valori dei campi.
  </Accordion>

  <Accordion title="Posso avere campi nidificati nei miei oggetti?">
    I campi nidificati arriveranno nel **Q1 2026**. Attualmente, puoi utilizzare i Workflows per importare i valori dei campi da oggetti correlati. Ad esempio, per visualizzare il settore di un'azienda sul record di una Persona, crea un campo personalizzato su Persone e utilizza un Workflow per sincronizzare il valore.
  </Accordion>

  <Accordion title="Posso riordinare i campi negli oggetti?">
    Il riordino dei campi sarà disponibile con layout personalizzati nel **Q4 2025**. Currently, fields appear in alphabetical order.
  </Accordion>
</AccordionGroup>

## Relazioni

<AccordionGroup>
  <Accordion title="Can I have a relation pointing to the same object?">
    Sì! 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.
  </Accordion>

  <Accordion title="Posso creare relazioni molti-a-molti?">
    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)
  </Accordion>

  <Accordion title="What are relations to multiple object types (Morph relationships)?">
    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](/l/it/user-guide/data-model/capabilities/relation-fields).
  </Accordion>

  <Accordion title="Can I have multiple relations between the same objects?">
    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.
  </Accordion>

  <Accordion title="What happens to relations when I delete a record?">
    When you delete a record, the relation link is removed from the related records. The related records themselves are not deleted.
  </Accordion>

  <Accordion title="Can I create circular relations?">
    While technically possible, circular relations (A → B → C → A) should be avoided as they can cause confusion and potential performance issues.
  </Accordion>
</AccordionGroup>

## Accesso e Permessi

<AccordionGroup>
  <Accordion title="Dove posso vedere e modificare il mio modello dati?">
    Go to **Settings → Data Model** to view and edit all your objects and fields.
  </Accordion>

  <Accordion title="Perché non riesco a vedere il Modello Dati in Impostazioni?">
    Contatta l'amministratore del tuo workspace. L'accesso al modello dati è solitamente riservato solo agli amministratori.
  </Accordion>
</AccordionGroup>

## Data Management

<AccordionGroup>
  <Accordion title="Is there a limit to how many records I can have?">
    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.
  </Accordion>

  <Accordion title="Can I import data into custom objects?">
    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](/l/it/user-guide/data-migration/how-tos/prepare-your-csv-files).
  </Accordion>

  <Accordion title="Can I export my data model configuration?">
    Currently, there's no built-in export for data model configuration. Contact support if you need to migrate your data model between workspaces.
  </Accordion>
</AccordionGroup>

## Need More Help?

Check our [Implementation Services](/l/it/user-guide/getting-started/capabilities/implementation-services) for help with complex data model design.