The connector supports the data types shown in Table 14. When you add a business object attribute, set the
attribute data type according to the data type of the field in the Clarify CRM
table.
Table 14. Business object attribute and database types
Clarify CRM data types | WebSphere Business Integration Adapter attribute data types |
---|---|
int, tinyint, smallint |
integer |
real |
float |
varchar, text |
string |
decimal |
string |
datetime |
string |
The connector supports Clarify CRM text fields of types varchar and text. WebSphere Business Integration Adapter business objects for Clarify CRM can include attributes with a data type of string that reference fields in Clarify CRM with the data type of text.
Note, however, that an attribute that references a field of type text cannot have a relation in its business object application-specific text. To work around this, you can add a preceding attribute that represents the object ID of the table, put the relation between the tables in the application-specific text of that attribute, and then reference the table in the application-specific text of the attribute representing the text field.
For example, suppose that you have a business object named Clarify_Case that represents the Clarify CRM case table. You want to add a relation to the notes_log table so that you can include an attribute for the text of a note related to a case.
To do this, you add an attribute in the Clarify_Case business object for the object ID of the notes_log table, and, in the application-specific text for this attribute, include the relation between the tables. Then add an attribute for the text of the note. In this example, the attribute you want to reference is notes_log:description, which is a field of type text. Figure 6 illustrates these attributes in the example Clarify_Case business object.
Figure 6. Referencing attributes of type text
If the connector attempts to select or update a text field in Clarify CRM, and the business object attribute with the text data type does not refer to the attribute representing the table object ID, the following errors may result:
Note that although ObjId is necessary for text fields, it is not necessary for varchar fields.