- CWLAT0001E: The {0} schema validation of map definition failed with the following message: {1}.
- Explanation: The error message explains the problem with the schema validation for the specified map.
- User Action: Delete the map and re-create it using the business object mapping editor.
- CWLAT0002W: The {0} business object that the {1} map refers to was not found.
- Explanation: If business objects that maps refer to are not in the current or dependency projects, then the program cannot find them.
- User Action: If the business object does not exist, add it to the current or dependency projects. If the current or dependency projects include the business object, the name of the business object might be incorrect. If so, correct the name of the business object.
- CWLAT0003E: The {0} submap that the {1} map refers to does not exist in the current or dependency projects.
- Explanation: If submaps that maps refer to are not in the current or dependency projects, the program cannot find them.
- User Action: In the Properties view, on the Details tab, choose another submap. Alternatively, locate the submaps and make them available by importing them or correcting the project dependencies.
- CWLAT0004E: The {0} relationship and the {1} role that map {2} refers to do not exist in the current or dependency projects.
- Explanation: If relationships and roles that maps refer to do are not in the current or dependency projects, then the program cannot find them.
- User Action: In the Properties view, on the Details tab, choose another role or relationship. Alternatively, locate the role or relationship and make it available by importing it or correcting the project dependencies.
- CWLAT0005E: The {0} variable name in the map is used more than once.
- Explanation: Each variable name in a map must be unique.
- User Action: In the map, change the name of every variable that does not have a unique name.
- CWLAT0006E: The {0} property of the {1} business object must be a string data type.
- Explanation: Only string data types are valid for the input of an Extract transform, also known as an Extract transform.
- User Action: In the business object mapping editor, retarget the Extract transform to string input data types.
- CWLAT0007E: The {0} property of the {1} business object is not a string data type.
- Explanation: Only string data types are valid for the output of a Join transform.
- User Action: In the business object mapping editor, retarget Join transform to a string output data type.
- CWLAT0008E: The {0} array property of the {1} business object must specify an index.
- Explanation: An index is required in a Move transform between array and non-array attributes.
- User Action: In the business object mapping editor, on the Cardinality property tab, specify an index for the array property.
- CWLAT0009E: The {0} array property of the {1} business object does not specify an index.
- Explanation: An index is required in a Join or Extract between array and non-array attributes. An Extract transform is also known as an Extract transform.
- User Action: In the business object mapping editor, on the Cardinality property tab, specify an index for the array property.
- CWLAT0010E: The map name {0} already exists in the project or dependency projects.
- Explanation: Duplicate map names are not allowed in the same project or dependency projects.
- User Action: Specify a unique name for every map in the scope.
- CWLAT0011E: The {0} property does not exist in the {1} business object.
- Explanation: The property name might be incorrect, or the property is not defined yet.
- User Action: In the business object mapping editor, change the property to an existing one.
- CWLAT0012E: The {0} variable cannot be found in the {1} map.
- Explanation: The specified variable is not defined as input or output, or as a temporary variable in the map.
- User Action: The variable name might be incorrect. If so, correct the variable name. Otherwise, change the variable to an existing one in the business object mapping editor.
- CWLAT0013E: The {0} value for the {1} temporary variable of the {2} data type is not valid.
- Explanation: The temporary variable, which is also known as the local variable, must have the following values for the corresponding data type: \nInteger data types\nbyte\tFrom +127 to -128\nshort\tFrom +32767 to -32768\nint\tFrom +2147483647 to -2147483648\nlong\tFrom +9223372036854775807 to -9223372036854775808\n\nReal numbers data types\nfloat\tFrom 3.4028235E38 to 1.4E-45\ndouble\tFrom 1.7976931348623157E308 to 4.9E-324\n\nOther data types\nchar\t16-bit Unicode character\nBoolean\ttrue or false
- User Action: In the business object mapping editor, in the Properties view, on the Details tab, update the local variable with a valid value.
- CWLAT0014E: The {0} property is not set, or it contains an empty string.
- Explanation: All properties must be set and must not contain empty strings.
- User Action: Add the property or set a value for the property.
- CWLAT0015E: The {0} document root is not defined as a businessObjectMap in the {1} map.
- Explanation: In maps, the document root must be defined as a businessObjectMap.
- User Action: Open the map in text editor and define the root element as a businessObjectMap.
- CWLAT0016E: The {1} input data type cannot be converted to the {2} output data type for the Move transform at run order {0}.
- Explanation: The input type can be converted to the output type when one of the following situations occurs:\nThe input is the same type as output.\nThe input or the output is anySimpleType.\nThe input or the output is anyType.\nThe input is a boolean or string type and the output is a boolean or string type.\nThe input is a date or long type and the output is a date or long type.\nThe input is a hexbinary or integer type and the output is a hexbinary or integer type.\nThe input is a dateTime-related type and the output is a dateTime-related type.\nThe input is a numerical type and the output is a numerical type.
- User Action: In the business object mapping editor, change the input or output data type on the Move transform to reflect one of the situations mentioned in the explanation.
- CWLAT0017E: The {0} variable that is used for a Submap transform in the {1} map does not exist in the {2} submap.
- Explanation: The variable name that is used for a Submap transform must exist in the submap.
- User Action: In the business object mapping editor, select the Submap transform. In the Properties view, on the Details tab, change the input or output variable to one that exists.
- CWLAT0018E: The business object type of the {0} variable is not the same in the {1} map and the {2} submap.
- Explanation: The business object type of a variable must be the same in the parent map and its submap.
- User Action: Change the business object type of the variable so that it is the same in both the parent map and its submap.
- CWLAT0019E: The {0} role in the {1} relationship that the {2} map refers to should not be managed.
- Explanation: A managed role is valid only for identity relationships.
- User Action: In the business object mapping editor, select the Relationship transform. In the Properties view, on the Details tab, select a non-managed role.
- CWLAT0020E: The blank type is set on the {0} property of the {1} type.
- Explanation: The Set transform, which is also known as an Assign transform, would not complete because the blank type can be set only on a rule logic property that has a string data type.
- User Action: In the business object mapping editor, in the Properties view, on the Details tab, specify the data type of the rule logic property as "string".
- CWLAT0021E: The {0} relationship that the {1} map refers to does not exist or is not in the same project or project dependencies as the map.
- Explanation: Either the specified relationship does not exist, the relationship and the map are not in the same module, or the relationship is in a library and the map is in a module but the library is not set as a dependent library for the module.
- User Action: In the business object mapping editor, select the Relationship transform. In the Properties view, on the Details tab, select a relationship that exists.
- CWLAT0022E: The {0} role that the {1} map refers to does not exist or is not in the same project or project dependencies as the map.
- Explanation: Either the specified role does not exist, the role and the map are not in the same module, or the role is in a library and the map is in a module but the library is not set as a dependent library for the module.
- User Action: Place the referenced role in the same project as the map or in a dependent library by selecting the role in the Business Integration view, right-clicking, and selecting Refactor > Move.
- CWLAT0023E: The {0} property of the {1} business object cannot be a hexBinary data type for an Extract transform.
- Explanation: Only non-hexBinary data types can be used as output for an Extract transform (also known as an Extract transform) on a business object.
- User Action: In the business object mapping editor, retarget the Extract transform to an output data type that is not hexBinary.
- CWLAT0024E: The {0} property of the {1} business object is a hexBinary data type for a Join transform.
- Explanation: Only non-hexBinary data types can be used as input for a Join transform on a business object.
- User Action: In the business object mapping editor, retarget the Join transform input data type to one that is not hexBinary.
- CWLAT0025E: The {0} output variable for the Move transform is not defined in the {1} map.
- Explanation: The variable for the Move transform must be defined as either output of the map or as temporary variable.
- User Action: In the business object mapping editor, select Add a variable and create the specified variable for the transform to refer to.
- CWLAT0026E: The {0} input variable is not defined in the {1} map.
- Explanation: The input variable for the Move transform is not defined as either input of the map or as a temporary variable.
- User Action: In the business object mapping editor, select Add a variable and create the specified variable for the transform to refer to.
- CWLAT0027E: The input and output are not compatible for the Move transform at the {0} run order.
- Explanation: If the input and output are not compatible, the input specified cannot be converted to the output specified.
- User Action: In the business object mapping editor, retarget the Move transform to an input data type that is compatible with the output data type.
- CWLAT0028E: The {0} variable name in the {1} map contains one or more invalid characters.
- Explanation: The business object variable name can only contain alphanumeric characters, underscore (_), and the dollar sign ($).
- User Action: In the business object mapping editor, select the specified variable. In the Properties view, select the Details tab and rename the variable so that it contains only valid characters.
- CWLAT0029E: More than one transform has the same run order.
- Explanation: Each transform in a map must have a unique run order.
- User Action: In the business object mapping editor, in the Properties view, select the Details tab and change the run order of the transform so that it is unique.
- CWLAT0030E: The transform failed for the {0} run order.
- Explanation: The input specified cannot be converted to the output specified because the input and output are not compatible.
- User Action: Make sure the input data type can be converted to the output data type.
- CWLAT0031E: The {0} property of the {1} business object cannot be used as output in a Join transform.
- Explanation: The output types xsd:any and xsd:anyType cannot be used in Join transforms.
- User Action: Double-click the error message. The Join transform is selected. Select the output connection and drag and drop the end node to an output that is a string property of the specified business object.
- CWLAT0032E: The {0} property of the {1} business object cannot be used as input in a Join transform.
- Explanation: The input types xsd:any and xsd:anyType cannot be used in Join transforms.
- User Action: Double-click the error message. The Join transform is selected. Remove the xsd:any and xsd:anyType input properties from the Join transform.
- CWLAT0033E: The {0} property of the {1} business object cannot be used in an Assign transform.
- Explanation: The xsd:any, xsd:anyType, or xsd:anySimpleType properties cannot be specified in an Assign transform, which is also known as an Assign transform.
- User Action: Double-click the error message. The Assign transform is selected. Change the transform type to a Custom Assign.
- CWLAT0034E: The {0} property of the {1} business object cannot be used as output in an Extract transform.
- Explanation: The output types xsd:any and xsd:anyType cannot be used in an Extract transform, which is also known as an Extract transform.
- User Action: Double-click the error message. The Extract transform is selected. Select the output connection and drag and drop the end node to an output that is a string property of the specified business object.
- CWLAT0035E: The {0} property of the {1} business object cannot be used as input in an Extract transform.
- Explanation: The input types xsd:any and xsd:anyType cannot be used in an Extract transform, which is also known as an Extract transform.
- User Action: Double-click the error message. The Extract transform is selected. Select the input connection and drag and drop the start node to an input that is a string property of the specified business object.
- CWLAT0036E: The Relationship transform cannot complete using the {0} static lookup relationship in the {1} map.
- Explanation: Relationship transforms must use only dynamic relationship definitions.
- User Action: Double-click the error message. The Relationship transform is selected. In the Properties view, on the Details tab, select a dynamic relationship in the Relationship definition property box.
- CWLAT0037E: The Relationship Lookup transform failed when using the {0} dynamic relationship in the {1} map.
- Explanation: Relationship Lookup transforms can use only static lookup relationship definitions.
- User Action: Double-click the error message. The Relationship Lookup transform is selected. In the Properties view, on the Details tab, select a static lookup relationship in the Relationship lookup definition property box.
- CWLAT0038E: The {0} input to the Relationship Lookup transform in the {1} map is not valid.
- Explanation: The input parameter to a Relationship Lookup transform must be a simple type attribute and it must not be an array.
- User Action: Double-click the error message. The Relationship Lookup is selected. Select the input connection and drag and drop the start node to an input that is a simple, non-arrayed type.
- CWLAT0039E: The {0} output to the Relationship Lookup transform in the {1} map is not valid.
- Explanation: The output parameter to a Relationship Lookup transform must be a simple type attribute and it must not be an array.
- User Action: Double-click the error message. The Relationship Lookup is selected. Select the output connection and drag and drop the end node to an output that is a simple, non-arrayed type.
- CWLAT0040E: The {0} input role of the Relationship transform is incompatible with the input parameters to the Relationship Lookup transform in the {2} map.
- Explanation: The input parameters to the Relationship Lookup transform must match the definition of the input role in the following ways: 1. The number of input parameters must match the number of the role key attributes. 2. If the role is a simple data type (boolean, double, float, int, string), then the input parameter must also be a simple type. 3. If the role is a complex or user-defined data type, then the input business object must also be that data type and the input business object must match all of the role key attributes.
- User Action: Double-click the error message. The Relationship Lookup transform is selected. Double-click the Relationship Lookup transform to open the relationship editor. In the relationship editor, define a compatible input role for the specified relationship, and then set up the Relationship Lookup transform in the business object map editor to select this role.
- CWLAT0041E: The {0} output role of the Relationship transform is incompatible with the output parameters to the Relationship Lookup transform in the {2} map.
- Explanation: The output parameters to the Relationship Lookup transform must match the definition of the output role in the following ways: 1. The number of output parameters must match the number of the role key attributes. 2. If the role is a simple data type (boolean, double, float, int, string), then the output parameter must also be a simple type. 3. If the role is a complex or user-defined data type, then the output business object must also be that data type and the output business object must match all of the role key attributes.
- User Action: Double-click the error message. The Relationship Lookup transform is selected. Double-click the Relationship Lookup to open the relationship editor. In the relationship editor, define a compatible output role for the specified relationship, and then set up the Relationship Lookup transform in the business object map editor to select this role.
- CWLAT0042E: The {0} role that is selected for the {1} Relationship transform defines no key attributes.
- Explanation: Roles that a Relationship transform refers to must define at least one key attribute.
- User Action: Double-click the error message. The Relationship transform is selected. Double-click the Relationship transform to open the relationship editor. In the relationship editor, revise the specified role definition and then set up the Relationship transform in the business object map editor with the revised role.
- CWLAT0043E: The {0} Relationship transform is missing the inputs and outputs.
- Explanation: Each Relationship must have at least one but can have two inputs and two outputs.
- User Action: Double-click the error message. The Relationship transform is selected. Add no more then two inputs and add no more then two outputs to the Relationship transform.
- CWLAT0044E: The {0} Relationship transform for the {1} composite role of the {2} relationship must be connected with the parent and child objects.
- Explanation: To run transforms for composite roles, the Relationship transform must have one connection to the parent (the role business object) and one connection to the child (the business object at the longest key attribute path of the role).
- User Action: Double-click the error message. The Relationship transform is selected. Add a connection between the child and parent business objects.
- CWLAT0045E: The {0} Relationship transform has more than one inputs or more than one outputs for the {1} simple role of the {2} relationship.
- Explanation: The relationship transform can have only one input and one output although the corresponding role is not a composite role, which can have multiple inputs and outputs.
- User Action: Double-click the error message. The Relationship transform is selected. Remove the one of the inputs or outputs so that only the connection to the role business object remains.
- CWLAT0046E: Either the input or output of the {0} Relationship transform is not connected to a business object that matches the {1} role business object type as defined for the {2} selected role.
- Explanation: A relationship transform must be connected with the business objects that correspond to its relationship definition.
- User Action: Double-click the error message. The Relationship transform is selected. Connect the Relationship transform with business objects that is defined in the relationship definition.
- CWLAT0047E: The parent business object that is connected to the {0} composite Relationship transform does not match the expected {1} role business object type.
- Explanation: The connected parent business object must be the same type as the parent role object that is used to define the corresponding role.
- User Action: Double-click the error message. The Relationship transform is selected. Connect the Relationship transform with the parent business object types that are defined in the relationship definition.
- CWLAT0048E: The {0} composite Relationship transform has two input or output connections from the same level business object.
- Explanation: Relationship transforms for composite roles must specify two connections: one from the parent business object (the role business object) and one from the child business object as defined in the corresponding role definition.
- User Action: Double-click the error message. The Relationship transform is selected. Connect one of the inputs or outputs to the child business object (the business object at the longest key attribute path of the role).
- CWLAT0049E: The child connection for the {0} composite Relationship transform refers the {1} child instead of the {2} child, which does not match the corresponding role definition.
- Explanation: The connections for a composite relationship transform must match the parent and child business objects that are defined in the corresponding role.
- User Action: Double-click the error message. The Relationship transform is selected. Reconnect the child connection to the correct child property.
- CWLAT0050E: The {0} Relationship transform for the {1} role has two inputs and two outputs.
- Explanation: Relationship transforms for composite roles require two connections for the composite role, but they can have only one connection on the opposite side.
- User Action: Double-click the error message. The Relationship transform is selected. Remove one of the inputs or outputs.
- CWLAT0051E: The {0} Relationship transform has a lower run order than the last {1} Submap transform.
- Explanation: The specified Relationship transform might depend on the output of one or more Submap transforms and must, therefore, have run after a Submap transform in the current map.
- User Action: Double-click the error message. The Relationship transform is selected. Change the run order of the Relationship transform so that it runs after the last Submap transform.
- CWLAT0052E: The key attributes of the {0} role that is selected for the {1} relationship transform are inconsistent with the role type.
- Explanation: The key attribute path must be a valid path expression for existing business objects.
- User Action: Double-click the error message. Relationship transform is selected. Double-click the Relationship Lookup to open the relationship editor. Select the specified role and include a valid path expression for an existing business object. Then, in the business object map editor, revalidate the role definition from the Details tab in the Properties view.
- CWLAT0053E: The {0} property path of the {1} business object for the {2} transform contains one or more array properties that are missing an index.
- Explanation: Each array property in a transform must have an index.
- User Action: Double-click the error message. The transform with the error is selected. In the Properties view, select the Cardinality tab and specify an index for each array property (starting with 1).
- CWLAT0054W: The {0} property path contains one or more indexed properties whose indexes do not refer to the first listed input or output element.
- Explanation: Targeting a list of elements with a transform that is not the first element in the list is possible only if earlier transforms have indices that refer to the preceding elements in the list. Otherwise, this error can cause runtime failures.
- User Action: Double-click the error message. The transform with the warning is selected. In the Properties view, on the Description tab, ensure that the run order is higher than the run order of the transforms that are associated with preceding elements of the list.
- CWLAT0055W: The source or target of the {0} Move transform is an array property that does not have an index.
- Explanation: Although this application of the Move transform is allowed, correct runtime behavior is more likely if you specify an index.
- User Action: Double-click the error message. In the Properties view, select the Cardinality tab and specify an index for the array property.
- CWLAT0056E: At least one of the required properties is not selected for the {0} Relationship Lookup transform of the {1} map.
- Explanation: The input, output, relationship definition, and the input and output roles must be specified for the relationship Lookup transform.
- User Action: Double-click the error message. The Relationship Lookup is selected. In the Properties view, on the Details tab, select a Relationship Lookup definition, input role name, and output role name.
- CWLAT0057E: A Top level Business Object cannot be specified as output for the move transform {0}.
- Explanation: A Top level Business Object cannot be specified as output a move transform in which input is of type AnyType.
- User Action: For a Move transform in which input is AnyType, output cannot be a Top Level Business Object.
- CWLAT0058E: The Relationship Lookup transform cannot be performed using the {0} non-identity relationship in the {1} map.
- Explanation: Relationship Lookup transforms can use only identity relationship definitions.
- User Action: Double-click the error message. A Relationship transform will be selected. Change the Relationship transform to a Relationship Lookup transform. Then, in the Properties view, on the Details tab, select the Relationship lookup definition, input role name, and output role name.
- CWLAT0060I: The value for the target xsd:anyAttribute field of a Custom transform must be set explicitly as a global property on the parent business object.
- Explanation: The value of output variables for xsd:anyAttribute fields are not stored automatically in the target business object.
- User Action: To store the values of output variables, you must set attributes and corresponding values for xsd:anyAttribute fields in the parent business object.
- CWLAT0061E: The {0} Submap transform cannot be performed.
- Explanation: The output of a Submap transform cannot be an xsd:any property
- User Action: Re-create the Submap transform, selecting another property type as the output of the transform.
- CWLAT0062E: The {0} Submap transform has multiple business objects specified as the input or multiple business objects specified as the output.
- Explanation: When an xsd:any or AnyType type property is part of a Submap transform, only one business object can be specified as the input and only one business object can be specified as the output.
- User Action: Re-create the Submap transform, selecting only one business object as the input and only one business object as the output.
- CWLAT0063E: The {0} Move transform cannot be performed because the input to the transform is a Business Object.
- Explanation: When an xsd:any is the target of a move transform, the source property cannot be a Business Object.
- User Action: Re-create the Move transform by selecting another property as input of the transform.
- CWLAT0064W: The {0} transform includes an inherited type, which might produce unwanted side effects when the map runs.
- Explanation: When an inherited type is the source of a transform and , if the map includes another transform on the base type, then processing the map might cause both of the transforms in the map to run: the base type and the inherited type.
- User Action: Remove either the transform on the inherited type or the base type so that only one transform runs.
- CWLAT0065E: The {0} target namespace of the map definition in {1} is not valid.
- Explanation: A valid target namespace must begin with a protocol (such as, http://). After the protocol, the namespace must not contain double forward slashes (//).
- User Action: Double-click the error message. In the business object mapping editor, on the Properties tab, correct the Namespace field in the Description area.
- CWLAT0066I: The target of the transform at run order {0} is a particle in an xsd:choice compositor. It should be validated for schema consistency after the transform.
- Explanation: The xsd:choice compositor defines a group of mutually exclusive particles. Only one particle should be found in the instance document for every occurrence of the xsd:choice compositor.
- User Action: If the business object map is a part of an interface map, select the interface of the next component in the assembly editor. On the Qualifiers tab, click Add and select Data validation. If the business object map is a part of a mediation flow, create a custom mediation primitive after the business object map mediation primitive in the mediation flow editor, and validate the target business object of the map for schema consistency. If the business object map is a part of custom code, validate the target business object of the map for schema consistency in the custom code.
- CWLAT0067E: You must be set an index for the {0} property in the Submap transform at run order {1} in the {2} map.
- Explanation: When either the source or the target parameter of a Submap transform is an array and a member of a substitution group, and the other parameter is not an array, you must set an index for the array parameter.
- User Action: In the business object mapping editor, select the specified Submap transform. In the Properties view, select the Cardinality tab, and specify an index for the property (start with 1).
- CWLAT0100E: The map definition in {0} does not contain a transform.
- Explanation: A valid map definition must contain at least one transform.
- User Action: Double-click the error message. In the business object mapping editor, create a transform by connecting an input business object to an output business object.
- CWLAT0101E: The map definition in {0} does not have a name.
- Explanation:
- User Action: In the text editor, open the map definition file and specify a name for the map:name property.
- CWLAT0102E: The map definition in {0} does not contain an input business object.
- Explanation: A valid map definition must contain at least one input business object.
- User Action: Double-click the error message. In the business object mapping editor, add a new input business object.
- CWLAT0103E: The map definition in {0} does not contain an output business object.
- Explanation: A valid map definition must contain at least one output business object.
- User Action: Double-click the error message. In the business object mapping editor, add an output business object.
- CWLAT0104E: The map definition in {0} is missing the {1} property required in the {2} transform at run order {3}.
- Explanation:
- User Action: Double-click the error message. In the business object mapping editor, select the specified transform. On the Properties tab, input a value for the specified property in the Details area.
- CWLAT0105E: The map definition in {0} is missing the required {1} property.
- Explanation:
- User Action: In the text editor, open the map definition file and input a value for the specified property.