Matching types

The following table lists allowed data type combinations. Highlighted entries are demonstrated in examples in this document.

Data Type Combinations

QC Data type

QCS QC
Type

Dir

QCS SM
type

WSDL data type

Field type on form
in SM

SM DB
data type for SM

Number

Number

<->

Number

DecimalType
or IntType1IntType supports a data range from -2,147,483,648 to 2,147,483,647.

Decimal or Text

Number

String

String

<->

String

BooleanType

Check Box
or Radio Button

Logical

Date2QC data only supports Yr/Mo/Dt.

Date

<->

Date

DateTimeType
(required)

Date

Date/time

String

String

<->

String3It is recommended to leave this field blank. Otherwise “Invalid byte 2 of 3-byte UTF-8 sequence" might occur if certain I18N characters are synchronized.

StringType

Text, TextArea,
Combo Box
or Comfill

Character

Memo

Memo/
String

<->

String4See footnote 3.

StringType

Text, TextArea,
Combo Box
or Comfill

Character

User List5Write to the QC field User_List only if SM has exactly the same users (including logins, names, etc.) as QC. An incorrect entry can cause serious problems in QC. You can read from QC User_List field and write to SM String type field only if the field in SM is NOT a field with SM logins.

User List

->

String6See footnote 3.

StringType

Text, TextArea,
Combo Box
or Comfill

Character

Lookup List

Single-
value list

<->

Single-
value list/
String7See footnote 3.

StringType

Text, TextArea,
Combo Box
or Comfill

Character

String

String

<->

String

StringType

TextArea

Array8Only an array of characters is supported.

Memo

Memo String

<->

String

StringType

TextArea

Array9See footnote 8.

Lookup List

Single-
value List

<->

String

StringType

TextArea

Array10See footnote 8.

User List11See footnote 5.

User List

<->

String

StringType

TextArea

Array12See footnote 8.

Lookup List

Multi-
value List

<->

Multi-
value List

StringType

Text, Comfill
or Combo Box

Array13See footnote 8.

Attachment14 The SM-QC/ALM integration does not support synchronization of an attachment with 0KB size. Consider the following guidelines when mapping attachment fields: You can create only one mapping between attachment fields per link.Synchronizer identifies attachments by their file name, and not by their content. Therefore: If you change the file name of an attachment, even if you do not change its content, Synchronizer determines that the original attachment has been deleted and a new attachment added, and synchronizes the attachment fields accordingly.If you have different attachments in each of the endpoints, but they have the same file name, Synchronizer is not able to distinguish between them and considers them as the same attachment.For a bidirectional attachment field mapping, if an attachment was updated in both endpoints since the last synchronization, Synchronizer copies the attachment in the non-dominant endpoint to the conflict_backup directory, located under the main Micro Focus ALM Synchronizer directory. It then overwrites the attachment in the non-dominant endpoint with the attachment in the dominant endpoint.

Attachment

<->

Attachment

Attachment

Attachment

Image