Anchoring an ASBO to a Database Table¶

Overview¶

Anchoring is the process through which an Application Specific Business Object (ASBO) is linked to a datasource and table, enabling the mapping of physical database columns to the logical attributes of the ASBO.

Anchoring establishes the foundation for resource management by:

• Connecting logical and physical layers: Links abstract business concepts to concrete database structures
• Enabling attribute-level configuration: Allows definition of Resource Name (RN) and Resource Description (RD) at the attribute level
• Facilitating automatic imports: Enables automatic resource importation directly from the anchored table
• Creating environment mappings: Establishes the relationship between business objects and physical data sources

Master Environment Mapping¶

When an ASBO is anchored to a table for the first time, BizMetry automatically creates a master environment mapping. This mapping serves as the source of truth for the ASBO's structure and configuration.

Master Mapping Characteristics¶

• Automatically created: Generated during the initial anchoring operation
• Associated with origin: Tied to the datasource and environment used during the first anchoring
• Defines structure: Establishes the canonical structure that all other environment mappings must match
• Cannot be edited: The master mapping is immutable to preserve structural integrity
• Can be deleted: Deletion breaks the anchoring relationship

When to Anchor an ASBO¶

You should anchor an ASBO in the following scenarios:

Newly Created ASBO¶

If you manually created an ASBO through the template editor:

1. The ASBO exists as a logical definition only
2. No connection to physical data exists
3. Anchoring links it to a database table
4. Resources can then be imported automatically

Imported but Unanchored ASBO¶

If you imported an ASBO definition from a template file:

1. The ASBO has logical structure but no physical mapping
2. Anchoring connects it to your database
3. Enables resource import and management

Previously Anchored ASBO¶

If a previously anchored ASBO had its master mapping deleted:

1. The ASBO reverted to unanchored state
2. Re-anchoring establishes a new master mapping
3. New structure definition is created based on the newly selected table

Accessing the Anchor Function¶

To begin the anchoring process:

1. Navigate to the Resource Types tab within the template editing dialog
2. Locate the ASBO you wish to anchor
3. Click the "Anchor" button for that resource type

Datasource Prerequisites¶

Before you can anchor an ASBO, certain prerequisites must be met.

Required Datasource Configuration¶

At least one datasource must be:

• Configured: Properly set up in BizMetry with valid connection parameters
• Active: Enabled and not in a disabled or maintenance state
• Online: Successfully connected to the database server

Table Selection Wizard¶

Once you click the "Anchor" button, the Table Selection Wizard opens, guiding you through the process of selecting the appropriate table.

Wizard Steps¶

The wizard presents a hierarchical selection interface:

Step 1: Select Datasource¶

Choose the datasource that contains the target table from the dropdown list.

• Available datasources: Only datasources that are active and online appear in this list
• Connection status: BizMetry displays the current connection status for each datasource
• Database type indicator: Icons or labels may indicate the database type (PostgreSQL, MySQL, Oracle, etc.)

Step 2: Select Schema¶

After selecting a datasource, choose the database schema where the target table resides.

• Dynamic loading: The schema list is populated based on the selected datasource
• Permission-based: Only schemas you have permission to access are displayed
• Alphabetical ordering: Schemas are typically listed alphabetically for easy navigation

Step 3: Select Table¶

Finally, choose the specific table to anchor to your ASBO.

• Table listing: All tables within the selected schema are displayed
• Metadata preview: Some table information may be shown (row count, size, etc.)
• Search capability: For schemas with many tables, a search function may be available

Exploring Table Structure¶

Before committing to a table selection, you can inspect its structure:

1. Click the information icon (i) next to any table in the list
2. A schema viewer opens, displaying:
3. Column names
4. Data types
5. Constraints (primary keys, foreign keys, unique constraints)
6. Nullable status
7. Default values

Proceeding to Mapping¶

Once you've selected your target table:

1. Review your selections (datasource, schema, table)
2. Click the "Map to [table_name]" button
3. The Table Mapper tool opens automatically

Table Mapper¶

The Table Mapper is an interactive visual interface where you establish the relationships between database table columns and ASBO logical attributes.

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

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

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

Best Practices for Anchoring¶

Pre-Anchoring Planning¶

Before beginning the anchoring process:

Understand Your Data Model¶

• ✓ Review the database table structure thoroughly
• ✓ Understand the meaning and purpose of each column
• ✓ Identify primary keys and required columns
• ✓ Document any business rules or constraints

Plan Your ASBO Structure¶

• ✓ Decide which columns should map to which attributes
• ✓ Determine appropriate logical data types
• ✓ Identify which attributes will serve as RN and RD
• ✓ Consider future scalability and additional environments

Verify Prerequisites¶

• ✓ Ensure datasource connectivity is stable
• ✓ Confirm you have appropriate database permissions
• ✓ Test datasource connection before anchoring
• ✓ Verify the target table contains actual data (if possible)

During Anchoring¶

Systematic Mapping Approach¶

• ✓ Map critical attributes first (primary key, RN, RD candidates)
• ✓ Review each type incompatibility warning carefully
• ✓ Use meaningful attribute names if creating new attributes
• ✓ Document any type mutations or transformations applied

Validation and Review¶

• ✓ Double-check all mappings before saving
• ✓ Verify that required business attributes are mapped
• ✓ Ensure data types make logical sense for the use case
• ✓ Test drag-and-drop operations before committing

Post-Anchoring Actions¶

Immediate Follow-up¶

• ✓ Configure RN and RD for the anchored ASBO
• ✓ Perform a test import of a small number of resources
• ✓ Verify imported data matches expectations
• ✓ Review and validate the master environment mapping

Documentation¶

• ✓ Document the anchoring decision and rationale
• ✓ Record which datasource/schema/table was selected
• ✓ Note any special mappings or type mutations
• ✓ Update team documentation and knowledge base

Testing and Validation¶

• ✓ Import a sample set of resources
• ✓ Verify all mapped attributes are populated correctly
• ✓ Test RN and RD rendering
• ✓ Validate data integrity and completeness

Common Anchoring Scenarios¶

Scenario 1: Anchoring a New ASBO to an Existing Table¶

Situation: You manually created an ASBO and need to link it to an existing database table.

Steps:

1. Click the "Anchor" button on the newly created ASBO
2. Select the appropriate datasource, schema, and table
3. Review the table structure using the schema viewer
4. Open the Table Mapper
5. Systematically map each ASBO attribute to the corresponding table column
6. Address any type incompatibilities using the Mutate Type feature
7. Verify all critical attributes are mapped (especially RN and RD)
8. Save the anchoring configuration
9. Test import a small set of resources to validate the mappings

Outcome: The ASBO is now anchored and ready for resource imports.

Scenario 2: Re-anchoring After Master Mapping Deletion¶

Situation: A master environment mapping was deleted, and the ASBO needs to be re-anchored.

Steps:

1. Verify that the ASBO shows as "unanchored" in the interface
2. Click the "Anchor" button (which becomes available again)
3. Select a datasource, schema, and table
4. In the Table Mapper, map columns to attributes
5. Note that you're creating a new master mapping with a potentially different structure
6. Complete the anchoring process
7. Consider re-importing existing resources to align with the new structure

Outcome: A new master environment mapping is created, and the ASBO is anchored again.

Scenario 3: Anchoring to a Database View¶

Situation: You need to anchor an ASBO to a database view rather than a base table.

Steps:

1. Ensure the database view exists and is accessible via the datasource
2. Click "Anchor" on the ASBO
3. Select the datasource and schema containing the view
4. In the table selection list, locate and select the view (views are typically marked with a special icon)
5. Review the view's column structure using the schema viewer
6. Open the Table Mapper and establish column-to-attribute mappings
7. Complete the anchoring process

Outcome: The ASBO is anchored to the view, and resource imports will execute queries against the view definition.

Scenario 4: Anchoring with Minimal Attribute Set¶

Situation: You want to anchor an ASBO but only map a subset of available columns.

Steps:

1. Begin the anchoring process as normal
2. In the Table Mapper, map only the essential columns:
3. Primary key column
4. Columns for RN and RD
5. Critical business attributes
6. Leave other attributes unmapped for now
7. Save the anchoring configuration
8. Test import resources to verify the minimal mapping works
9. Return later to add additional mappings as needed

Outcome: The ASBO is anchored with minimal mappings, allowing for incremental configuration.

Scenario 5: Anchoring with Type Transformations¶

Situation: Database column types don't match your desired logical types, requiring transformations.

Steps:

1. Begin the anchoring process and open the Table Mapper
2. Drag a column to an attribute and encounter a type incompatibility warning
3. Review the suggested type change carefully
4. If acceptable, click "Mutate Type" to apply the transformation
5. If not acceptable, consider:
6. Creating a database view with CAST or CONVERT operations
7. Modifying the ASBO attribute type manually before mapping
8. Using a different column that has the correct type
9. Repeat for each column requiring type handling
10. Complete the anchoring process after all transformations are resolved

Outcome: The ASBO is anchored with appropriate type mappings, either through mutations or database-level transformations.

Troubleshooting Anchoring Issues¶

No Datasources Available¶

Symptoms: - Error message appears when clicking "Anchor" - "No active datasources" warning displayed - Cannot proceed to table selection

Resolution:

1. Navigate to the Datasources configuration section
2. Verify at least one datasource exists
3. Check that the datasource status is "Active" and "Online"
4. Test datasource connectivity:
5. Click "Test Connection" if available
6. Review connection parameters (host, port, database name)
7. Verify credentials are correct and not expired
8. If no datasources exist, create a new one:
9. Provide connection details
10. Test the connection
11. Activate the datasource
12. Return to the ASBO and retry anchoring

Schema or Table Lists Empty¶

Symptoms: - Datasource is selected but no schemas appear - Schema is selected but no tables appear - Dropdown lists show "No items found"

Resolution:

1. Verify permissions:
2. Ensure the datasource credentials have SELECT permission on information schema
3. Check that the database user can enumerate schemas and tables

4. Verify no database-level restrictions on metadata access

5. Check datasource configuration:

6. Confirm the datasource is pointing to the correct database server
7. Verify the default schema or database is set correctly

8. Review any schema filtering or exclusion rules in the datasource settings

9. Test database access directly:

      -- Test schema access
      SELECT schema_name FROM information_schema.schemata;
   
      -- Test table access
      SELECT table_name FROM information_schema.tables WHERE table_schema = 'your_schema';
   

10. Refresh the datasource:

11. Navigate to datasource configuration
12. Click "Refresh Metadata" or "Reconnect"
13. Return to anchoring wizard and retry

Type Incompatibility Cannot Be Resolved¶

Symptoms: - Repeated type mismatch warnings - Mutate Type doesn't produce the desired result - No compatible columns available for an attribute

Resolution:

1. Understand the root cause:
2. Review the column's actual data type in the database
3. Determine if the data can be safely converted to the desired logical type

4. Check if sample data matches the expected format

5. Database-level solutions:

      -- Create a view with type conversions
      CREATE VIEW compatible_table_v AS
      SELECT 
          CAST(varchar_column AS INTEGER) AS numeric_attribute,
          TO_DATE(string_date, 'YYYY-MM-DD') AS date_attribute,
          CAST(bit_column AS BOOLEAN) AS boolean_attribute
      FROM source_table;
   

6. ASBO-level solutions:

7. Modify the ASBO attribute type to match the column type
8. Add a transformation step in your data pipeline

9. Use middleware or ETL to pre-process data before import

10. Alternative approaches:

11. Map to a different column that has compatible type
12. Store the raw value and transform at the application level
13. Create a computed column in the database with the correct type

Drag and Drop Not Working¶

Symptoms: - Columns cannot be dragged - Drop zones don't activate - No visual feedback during drag operations

Resolution:

1. Browser issues:
2. Refresh the browser page
3. Clear browser cache and cookies
4. Try a different browser (Chrome, Firefox, Edge recommended)

5. Disable browser extensions that might interfere with drag-and-drop

6. UI state issues:

7. Close and reopen the Table Mapper
8. Exit the anchoring wizard and start again

9. Log out and log back in to BizMetry

10. Data loading issues:

11. Ensure the table structure has fully loaded (watch for loading indicators)
12. Wait a few seconds after the interface opens before attempting drag operations

13. Check browser console for JavaScript errors

14. Alternative mapping method:

15. If drag-and-drop continues to fail, check if there's a manual mapping option
16. Some interfaces may provide dropdown-based mapping as an alternative

Anchoring Saves But Resources Won't Import¶

Symptoms: - Anchoring completes successfully - Import operations fail or return no data - Error messages about missing columns or invalid mappings

Resolution:

1. Verify the master environment mapping:
2. Navigate to Env Mappings for the ASBO
3. Confirm the master mapping was created

4. Check that it points to the correct datasource/schema/table

5. Check attribute mappings:

6. Review each attribute in the ASBO configuration
7. Verify the column_metadata_name field is populated correctly

8. Ensure critical attributes (especially primary key) are mapped

9. Test datasource connectivity from import context:

10. The import process may use different credentials or connection pooling
11. Verify the agent or import service can reach the database

12. Check firewall rules and network connectivity

13. Review import logs:

14. Check detailed error messages in the import logs
15. Look for SQL errors, connection timeouts, or permission denials

16. Identify which specific column or query is failing

17. Validate data compatibility:

18. Query the table directly to ensure data exists
19. Check that data values are compatible with mapped types
20. Verify primary key values are unique and not null

Duplicate Attribute Names Causing Issues¶

Symptoms: - Cannot create new attributes from columns - Drop zone is always disabled - Error about attribute name conflicts

Resolution:

1. Identify the conflict:
2. Review all existing ASBO attributes
3. Note which attribute name matches the column name

4. Determine if they should represent the same or different data

5. If they represent the same data:

6. Map the column to the existing attribute instead of creating new

7. Verify the existing attribute has the correct type

8. If they represent different data:

9. Rename the existing attribute to something more specific
10. Use the ASBO configuration editor to change the attribute name

11. Return to Table Mapper and create the new attribute

12. If using a view:

       -- Alias column to avoid naming conflict
       CREATE VIEW table_with_unique_names AS
       SELECT 
           existing_column AS existing_column_v2,
           -- other columns
       FROM source_table;
    

Cannot Remove Mappings¶

Symptoms: - X button doesn't respond - Mapping remains after clicking remove - Error when trying to unmap

Resolution:

1. UI refresh:
2. Close and reopen the Table Mapper
3. Refresh the browser page

4. Try clicking the X button again

5. Check for dependencies:

6. Some mappings may be protected if used in RN/RD configuration
7. Verify the attribute isn't marked as required or locked

8. Check if the attribute is used in any business rules

9. Alternative approach:

10. Save the current state and exit Table Mapper
11. Edit the ASBO configuration directly
12. Remove the column_metadata_name value for the attribute
13. Return to Table Mapper to remap if needed

Impact of Anchoring on ASBO Lifecycle¶

Understanding how anchoring affects the ASBO throughout its lifecycle is important for effective management.

Structural Definition¶

Once anchored, the ASBO's structure is permanently defined by the table used during anchoring:

• Column snapshot: The structure reflects the table columns at the moment of anchoring
• Immutable base: This structure cannot be changed without re-anchoring
• Validation basis: All future environment mappings must match this structure

Environment Mapping Compatibility¶

After anchoring, any additional environment mappings you create must have table structures that match the anchored structure:

• Validation enforcement: BizMetry validates new environment mappings against the master structure
• Column matching: All columns from the master must exist in new environment tables
• Type compatibility: Data types must be compatible across environments

Resource Import Capability¶

Anchoring directly enables resource import functionality:

• Before anchoring: Cannot import resources from database
• After anchoring: Can import resources using the established mappings
• RN/RD configuration: Becomes possible only after anchoring

Anchoring vs. Environment Mapping¶

It's important to understand the distinction between these two related concepts:

Anchoring (Master Mapping Creation)¶

• Purpose: Initially links an ASBO to a physical table
• Occurs: Once, when first connecting an ASBO to a database
• Creates: The master environment mapping
• Defines: The canonical structure for the ASBO
• Requirement: ASBO must be unanchored

Environment Mapping (Additional Mappings)¶

• Purpose: Links the same ASBO to tables in other environments
• Occurs: Multiple times, after initial anchoring
• Creates: Secondary environment mappings
• Validates: Against the master structure
• Requirement: ASBO must already be anchored

Workflow Example:

1. DEV Environment: Anchor ASBO to dev_db.clients table (creates master mapping)
2. QA Environment: Create env mapping to qa_db.clients table (validates against master)
3. PROD Environment: Create env mapping to prod_db.clients table (validates against master)

Related Topics¶

• Understanding Environment Mappings
• Creating a New Environment Mapping
• Editing an Environment Mapping
• Deleting an Environment Mapping
• Importing Resources from Database
• Configuring Resource Name (RN) and Resource Description (RD)
• Configuring Datasources
• Managing Environments
• Resource Type Configuration
• Table Structure Validation
• Troubleshooting Import Issues