Data Models
Data models group related tables into domains inside an enterprise. They keep a growing catalog organized, and let you clone entire domains across business units in one action.
What is a Data Model?
A Data Model is a logical container that groups related tables inside an enterprise. Think of it as a subject area: Customers, Products, Suppliers, Locations. One enterprise can hold many data models, and each model can contain many tables.
Data models earn their keep in two ways. First, they give structure to a catalog that would otherwise become one long list of tables. Second, they act as a unit of reuse: an entire domain (tables, attributes, and the relationships between them) can be duplicated or moved as a single package when your business changes.
The list view
The main screen lists every data model you can access, one row each:
| Column | What it shows |
|---|---|
| Data Model | The model's icon, name, and description. |
| Enterprises | The enterprise that owns the model, as a purple badge. |
| Tables | How many tables the model contains. |
| Created | When it was first set up. |
| Actions | The Open button and a row menu. |
An enterprise filter sits at the top of the page, next to the + Create Data Model button, which appears only if you can edit the selected enterprise.
Inside a data model
Clicking Open takes you into the detail view. The header shows the model's name (with a pencil icon for inline renaming) and a back arrow to return to the list. Below it, the tables panel lists everything the model contains, with a + Add Table button to grow it.
For each table you can see, at a glance:
- The table name and its number of attributes.
- Golden and pending record counts.
- Counters for properties, access, and assigned responsibles.
- A Records > button that jumps to the Records screen filtered to that table.
- A three-dot menu with Manage Attributes, Edit Table, Duplicate Table, and Delete Table.
In other words, once you are inside a data model, you can manage its entire contents without leaving the page.
Creating a data model
Click + Create Data Model and provide three things:
- Enterprise — only enterprises you are allowed to edit are listed.
- Name — a short, meaningful label such as Customers.
- Description — optional context for the rest of the team.
Duplicating a data model
The row menu's Duplicate Model action copies a model into the same or a different enterprise. You choose the target enterprise and a new name (defaulting to <original name> (Copy)). Every table inside the model is duplicated too, and reference relationships between attributes are remapped automatically, so the copy is fully self-contained from the moment it is created.
Deleting a data model
As everywhere in Rapida MDM 2.0, deletion is a soft deactivation. The confirmation dialog warns that all tables and records inside the model will be hidden along with it. Reactivating the model brings everything back exactly as it was.
Common questions
How should I decide what goes in one data model versus several?
Group tables that belong to the same business domain and tend to be governed by the same people: Customer Master and Customer Address naturally share a Customers model. If two sets of tables have different owners and different lifecycles, give them separate models.
When I duplicate a model, are the records copied too?
Duplication copies the structure: the tables, their attributes, and the reference relationships between them (remapped to the copy). It is designed for rolling out schemas, so the new model starts ready to receive its own records via entry, import, or integration.
Do changes to a duplicated model affect the original?
No. After duplication the two models are completely independent. Editing tables or attributes in one has no effect on the other.
Can I move a data model to a different enterprise?
Use Duplicate Model with the other enterprise as the target, then deactivate the original once you are satisfied with the copy. Because deletion is soft, the original remains recoverable if you ever need it back.