Create your first Entity with Fields

Prerequisites

• You are in the correct Application.
• A Metamodel exists (or you are creating one).
• You have permissions to manage Metamodels, Entities, and Fields (commonly Owner or Data Steward role). 

Steps for Creating an Entity

1. Go to Management > Metamodels
2. Open the Metamodel you are working on
3. Find the Entities section on the left.
4. Click Add

There are two ways to add an Entity in WOODY.IO.

Option A: Add New (manual)

1. Click Add New.
2. Fill in:
   • Name
   • Technical name
   • Description
3. (Optional) Enable Needs Clearance (toggle), if the entity should require clearance handling.
4. Save.

Result: The entity exists, but it cannot be used effectively until fields are defined. The steps to adding Fields to an Entity manually are described further down in the article.

Option B: Add from Connection (import)

1. Click Add from Connection.
2. Select the Connection.
3. The system shows a list of Tables/Entities the connection user has access to.
4. After you select the Table/Entity, a Fields list is displayed. Review the available fields the connection user has access to.
5. Select which fields to include in the entity by:
   • selecting individual fields, and/or
   • using a “select all” option, and/or
6. (Optional) Enable Needs Clearance (toggle), if the entity should require clearance handling.
7. (Optional) Adjust the Friendlyname.
8. Save.

Steps for Adding Fields to an Entity manually

1. Open the Entity
2. Find and Click Add Field (top-right of the Fields list)
3. Configure at minimum:
   • Field name
   • Data type
   • Required (if the field must be present and not null)
   • Key (if it identifies a record for matching)
   • Identity (if it is system-generated)
   • Lookup-related settings (if your setup uses lookups/lookup fields)

How to choose the most important field properties

Key fields (when and why)

Mark fields as Key when you need WOODY.IO to match incoming rows to existing rows (for example for Merge or Update transaction types). Without correct key fields, matching behavior will not work as intended.

Required fields

Mark a field Required when the process should treat missing/empty values as invalid (typically enforced via validation/business rules).

Identity fields

Use Identity for fields that should not be provided by users/import files because the destination generates them (or because they are managed outside the import).

If you have any further questions, please feel free to Contact Us.