Overview
Field Mappings define how your custom schema fields translate to gu1βs unified entity model. Each mapping can include transformations to format, calculate, or conditionally process data during import.Mappings bridge the gap between your data structure and gu1βs entity model, enabling seamless data ingestion from any source.
Create Field Mapping
Create a mapping configuration for your custom schema.Request Body
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Mapping configuration name |
description | string | No | Mapping description |
sourceSchemaId | uuid | No | Source custom schema ID |
targetSchemaType | string | No | Target schema type (e.g., βgueno_entityβ) |
sourceSchemaName | string | No | Alternative to sourceSchemaId |
targetSchemaName | string | No | Alternative to targetSchemaType |
mappingData | object | Yes | Mapping configuration |
industry | string | No | Industry context |
collaborators | array | No | User IDs with access |
Mapping Data Object
| Field | Type | Required | Description |
|---|---|---|---|
mappings | array | Yes | Array of field mappings |
templates | array | No | Template IDs to apply |
validation | object | No | Validation rules |
transformationSettings | object | No | Processing settings |
Field Mapping Object
| Field | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique mapping identifier |
sourceField | string | Yes | Source field name |
targetField | string | Yes | Target field name (supports dot notation) |
transformation | object | No | Transformation to apply |
required | boolean | Yes | Is field required |
dataType | string | Yes | Expected data type |
defaultValue | any | No | Default if source is null/missing |
validationRule | string | No | Custom validation expression |
Response
Transformation Types
Direct Mapping
Copy value as-is with no changes:Format Transformation
Apply string, date, or number formatting:Calculate Transformation
Perform mathematical calculations:Conditional Transformation
Apply if/then logic:Lookup Transformation
Look up values from reference tables:Custom Transformation
Execute custom JavaScript:Validation Rules
Configure validation behavior:| Setting | Type | Description |
|---|---|---|
strictMode | boolean | Fail on any validation error |
allowExtraFields | boolean | Allow unmapped source fields |
requiredFields | array | Fields that must have values |
Transformation Settings
Configure processing behavior:| Setting | Type | Description |
|---|---|---|
errorHandling | enum | skip, fail, or default |
batchSize | number | Records per batch (1-1000) |
timeout | number | Timeout in milliseconds |
List Mappings
Get all mapping configurations for your organization:Response
Get Mapping
Retrieve a specific mapping configuration:Response
Update Mapping
Update an existing mapping configuration:Request Body
Delete Mapping
Delete a mapping configuration:Complete Example: Banking Customer Mapping
Error Responses
Validation Error
Transformation Error
Best Practices
Start Simple
Start Simple
- Begin with direct mappings for most fields
- Add transformations only when necessary
- Test each transformation individually
- Gradually increase complexity
Testing
Testing
- Test mappings with sample data before production
- Validate edge cases (null, empty, invalid values)
- Monitor transformation errors in logs
- Use strictMode in production environments
Data Quality
Data Quality
- Set appropriate defaultValue for optional fields
- Use validationRule for complex validations
- Apply format transformations for consistency
- Handle missing/null values explicitly
Performance
Performance
- Avoid complex custom transformations in hot paths
- Use batch processing for large datasets
- Set reasonable timeout values
- Monitor transformation execution times