The Table Mapper¶

The Table Mapper is an interactive visual interface where you establish the relationships between database table columns and ASBO logical attributes. It opens automatically once you select a table in the Table Selection Wizard.

Interface Layout¶

The Table Mapper uses a two-panel design for intuitive drag-and-drop operations:

Left Panel: Database Columns¶

Displays all columns detected in the selected database table:

• Column name: The physical column name from the database
• Data type: The database-specific data type (e.g., VARCHAR, INTEGER, TIMESTAMP)
• Constraints: Visual indicators for primary keys, foreign keys, or required fields
• Draggable: Each column can be clicked and dragged to the right panel

Right Panel: ASBO Attributes¶

Shows the logical attributes defined in the ASBO:

• Attribute name: The logical business attribute name
• Data type: The BizMetry logical data type
• Status: Mapped or unmapped status indicator
• Drop targets: Each attribute serves as a drop target for columns

Mapping Columns to Attributes¶

The core functionality of the Table Mapper is establishing column-to-attribute relationships.

Basic Drag and Drop Mapping¶

To create a mapping between a column and an attribute:

1. Click on a column in the left panel
2. Drag it across to the right panel
3. Hover over the target attribute
4. Drop the column onto the attribute

When the drop is successful:

• A visual arrow or connection line appears, linking the column to the attribute
• The attribute card updates to show the mapped column name
• The column in the left panel may become grayed out or marked as "mapped"

Data Type Compatibility Validation¶

When you drag a column onto an attribute, BizMetry automatically validates data type compatibility.

Compatible Types¶

If the column's database type is compatible with the attribute's logical type:

• The drop is accepted immediately
• The mapping is created without warnings
• No type conversion is needed

Example Compatible Mappings:

Incompatible Types¶

If the column's database type is not compatible with the attribute's logical type:

• A warning message appears
• The incompatibility is clearly described
• A suggested type change is recommended
• The mapping is not created until resolved

Example Warning Message:

Resolving Type Incompatibilities¶

BizMetry offers automated resolution for type mismatches:

Option 1: Mutate Attribute Type (Recommended)¶

Click the "Mutate Type" button to automatically change the attribute's logical type to match the column:

1. The attribute type is updated to be compatible with the column
2. The mapping is created automatically
3. The warning disappears
4. The connection is established

Option 2: Select a Different Column¶

If mutating the type is not appropriate:

1. Cancel the current drag operation
2. Identify a different column with a compatible type
3. Drag the alternative column to the attribute instead

Option 3: Modify Attribute Type Manually¶

Before mapping:

1. Access the attribute definition in the ASBO configuration
2. Manually change the attribute's logical type to match the column
3. Return to the Table Mapper
4. Perform the drag-and-drop operation again

Creating New Attributes from Columns¶

The Table Mapper allows dynamic creation of new attributes directly from database columns, expanding your ASBO structure as needed.

Drop Zone for New Attributes¶

To create a new attribute from a column:

1. Drag a column from the left panel
2. Move it to the top of the right panel (above the first attribute)
3. A drop zone appears with a distinctive visual indicator
4. Drop the column into this zone

Automatic Attribute Creation¶

When you drop a column into the new attribute drop zone:

1. BizMetry creates a new attribute in the ASBO
2. The attribute name matches the column name (or is intelligently transformed)
3. The logical data type is automatically set based on the column's database type
4. The mapping is established automatically between the new attribute and the column
5. The new attribute appears at the top of the attributes list

Automatic Type Mapping Examples:

Naming Conventions¶

When creating attributes from columns, BizMetry may apply naming transformations:

• Snake case to Pascal case: client_name → ClientName
• Uppercase preservation: CLIENT_ID → ClientId
• Special character removal: client@email → ClientEmail
• Reserved word handling: select → SelectValue

Preventing Duplicate Attributes¶

BizMetry enforces uniqueness of attribute names within an ASBO to maintain data integrity.

Duplicate Detection¶

When you attempt to create a new attribute from a column:

1. BizMetry checks if an attribute with that name already exists
2. The check is case-insensitive in most cases
3. If a duplicate is detected, the drop operation is blocked

Visual Feedback for Duplicates¶

When you drag a column whose name matches an existing attribute:

• The drop zone is disabled (grayed out or marked with a prohibition icon)
• A tooltip or message appears explaining the duplicate conflict
• The drop operation cannot be completed

Resolution Strategies¶

If you encounter a duplicate attribute situation:

Strategy 1: Map to Existing Attribute¶

If the column and existing attribute represent the same data:

1. Drag the column to the existing attribute in the list
2. Create the mapping to the existing attribute instead
3. No new attribute is needed

Strategy 2: Rename Existing Attribute¶

If the existing attribute should have a different name:

1. Exit the Table Mapper
2. Edit the ASBO configuration
3. Rename the existing attribute to something more specific
4. Return to the Table Mapper
5. Now create the new attribute from the column

Strategy 3: Use Column Alias¶

If the database allows, create a view with aliased column names:

CREATE VIEW client_data_v AS
SELECT 
    client_name AS client_full_name,
    -- other columns
FROM client_table;

Then anchor to the view instead of the base table.

Removing Attribute Mappings¶

The Table Mapper allows you to easily remove column-to-attribute associations.

Unmapping a Column¶

To remove an existing mapping:

1. Locate the mapped attribute in the right panel
2. Find the "X" button or delete icon within the attribute card
3. Click the X button
4. The mapping is immediately removed

Effects of Removing a Mapping¶

When you remove a mapping:

• The visual connection (arrow or line) disappears
• The attribute returns to an unmapped state
• The attribute card no longer displays the column name
• The column in the left panel becomes available again for mapping
• Both the column and attribute return to their pre-mapping state

When to Remove Mappings¶

Common scenarios for removing mappings:

• Incorrect mapping: You mapped the wrong column to an attribute
• Type mismatch: After reviewing, you realize the types don't align semantically
• Structural changes: The ASBO structure needs to be reorganized
• Column deprecation: The database column is being phased out

Re-mapping After Removal¶

After removing a mapping, you can:

1. Map a different column to the same attribute
2. Leave the attribute unmapped temporarily
3. Delete the attribute entirely if no longer needed
4. Re-map the same column after making changes

Mapping Automation Features¶

The Table Mapper provides automation tools to streamline the mapping process, especially useful when working with tables that have many columns or when starting fresh.

Auto-Map Feature¶

The Auto-Map button enables BizMetry to automatically infer mappings between columns and attributes based on their names and data types.

How Auto-Map Works¶

When you click the "Auto-Map" button:

1. BizMetry analyzes all unmapped columns in the left panel
2. Compares column names and types against unmapped attributes
3. Identifies the best matches based on:
4. Name similarity: Exact matches, case-insensitive matches, or close approximations
5. Type compatibility: Ensures database types are compatible with logical types
6. Naming conventions: Recognizes common transformations (e.g., snake_case to PascalCase)
7. Creates mappings automatically for all identified matches
8. Displays the results with visual indicators for newly created mappings

When to Use Auto-Map¶

Auto-Map is particularly useful in these scenarios:

• Initial anchoring: When mapping an ASBO to a table for the first time
• Column-to-attribute alignment: When column names closely match attribute names
• Large tables: When dealing with tables that have many columns
• Standardized schemas: When database naming conventions align with ASBO conventions
• Time savings: When you want to quickly establish a baseline mapping

Example Scenario:

You have an ASBO with attributes named ClientId, ClientName, Email, and CreatedDate. The database table has columns named client_id, client_name, email, and created_date.

Clicking Auto-Map will:

• Map client_id → ClientId
• Map client_name → ClientName
• Map email → Email
• Map created_date → CreatedDate

All mappings are created automatically in seconds.

Auto-Map Matching Rules¶

BizMetry uses the following rules to determine matches:

Exact Match (Highest Priority):

• Column name exactly matches attribute name (case-insensitive)
• Example: ClientId (attribute) matches clientid (column)

Transformed Match:

• Column name matches after applying naming convention transformations
• Example: client_name (column) matches ClientName (attribute)
• Example: CLIENT_ID (column) matches ClientId (attribute)

Partial Match (Lower Priority):

• Column name contains or is contained in attribute name
• Example: client_email_address (column) might match ClientEmail (attribute)

Type Validation:

• All matches must have compatible data types
• Incompatible types are skipped even if names match

Auto-Map Limitations¶

Auto-Map may not create mappings in these situations:

• No name similarity: Column and attribute names are completely different
• Type incompatibility: Column type cannot be converted to attribute type
• Already mapped: The attribute already has a mapping from previous operations
• Ambiguous matches: Multiple columns could match the same attribute

In these cases, manual mapping is required.

Clear All Mappings¶

The "Clear All" button removes all existing column-to-attribute mappings, allowing you to start the mapping process from scratch.

How Clear All Works¶

When you click the "Clear All" button:

1. A confirmation dialog appears to prevent accidental deletion
2. If confirmed, BizMetry removes all mappings between columns and attributes
3. All attributes return to an unmapped state
4. All columns become available again for mapping
5. Visual connections (arrows/lines) are removed from the interface

When to Use Clear All¶

Clear All is appropriate in these scenarios:

• Starting over: You want to completely redesign the mapping strategy
• After bulk import errors: Incorrect mappings were created and it's easier to start fresh
• Testing different approaches: You want to experiment with different mapping configurations
• Before Auto-Map: You want to clear existing mappings before running Auto-Map for a clean slate
• Structural changes: The ASBO structure changed significantly and old mappings are no longer valid

Example Scenario:

You initially mapped columns incorrectly and realized that many attributes are pointing to wrong columns. Rather than removing each mapping individually, you can:

1. Click "Clear All"
2. Click "Auto-Map" to let BizMetry create correct mappings automatically
3. Manually adjust any remaining unmapped or incorrectly mapped attributes

Completing the Anchoring Process¶

Once you've established all desired column-to-attribute mappings in the Table Mapper, you need to complete the anchoring operation.

Finalizing Mappings¶

To complete the anchoring:

1. Review all mapped attributes to ensure correctness
2. Verify that critical attributes (especially those used for RN and RD) are mapped
3. Click the "Save" or "Complete Anchoring" button at the bottom of the Table Mapper
4. Wait for confirmation that the anchoring was successful

Master Environment Mapping Creation¶

When you complete the anchoring process successfully:

1. BizMetry creates the master environment mapping automatically
2. This mapping is associated with:
3. The selected datasource
4. The selected database schema
5. The selected table
6. The current environment context
7. The mapping includes:
8. All column-to-attribute associations
9. Structural metadata from the table
10. Configuration for resource imports

Post-Anchoring State¶

After successful anchoring:

• The ASBO is now linked to a physical database table
• The "Anchor" button is replaced with "Edit Anchors"
• You can proceed to:
• Configure Resource Name (RN) and Resource Description (RD)
• Set up resource import operations
• Create additional environment mappings for other environments
• Begin importing resources from the anchored table

Related Topics¶

• Anchoring Concept & Table Selection Wizard
• Anchoring Scenarios & Troubleshooting
• Editing Anchors
• Configuring Resource Name (RN) and Resource Description (RD)
• Importing Resources from Database