Fix Broken Mappings

After user-defined methods have been defined, changing certain parts of a mapping can break the mapping. For example, if you have defined a method that takes an attribute, A, as an input parameter, and then you delete A from the mapping, the user-defined method will be broken. Similarly, if you change A's type, the method might be broken. Also, when a method is initially validated, it will be broken if Data Access Builder is unable to determine a parameter's SQL type.

If a mapping is broken, the mapping icon has a red 'X' . To fix a mapping, you must fix each broken method:

  1. Check both Methods and Manager Methods windows for broken methods, designated by a red 'X' . These may be in the Customized SQL Statement list, the SQL Predicate list, or the Stored Procedure Call list.
  2. Do the following steps to fix a broken method:
    1. Select the method.
    2. Click Modify. Parameters that are causing the method to break are indicated by an 'X' in the Parameters list.
    3. To assign a type to a parameter of unknown type, go to the SQL Type page, select the broken parameter, and select the appropriate type from the SQL Type drop-down list.
    4. To fix a broken parameter, go to the Parameter page, select the broken parameter, and change its settings to match the mapping or the stored procedure definition, as appropriate.
    5. Click OK. If the method definition is valid, the red 'X' icon will be replaced by a method icon .

    Alternatively, remove the method by selecting it and clicking Delete.

When you have fixed all broken methods, the mapping icon will return to normal .

Note: If a method is broken when code is generated for a mapping, the code for the broken method is excluded from the generated classes.



User-Defined Methods


Add User-Defined Methods
Modify User-Defined Methods


Data Access Class Library and Generated Code