To change the datatype of your fieldsyou can use the datatype change feature. To change the type, click on the cogwheel icon against the field mapping.

The Field Configuration dialog box is displayed. It displays the current datatype selected. If required, change the datatype on the appropriate adapter using the dropdown menu in the Data Type Mapping field, and save the change. 

Text Format Conversions

While configuring an Integration, you can choose a datatype in the Field Configuration screen. This datatype determines the data conversion format of the text that users enter in the text fields.

Important Information

In most cases, rich-text can be converted between formats accurately. However, there are some scenarios in which this may not be possible. Transformation difficulties are more likely to occur when the text has multiple overlapping formatting, combinations of special characters, or accented characters. Some applications have formatting irregularities and idiosyncrasies, and some formatting just can’t be preserved programmatically when switching between formats and tools. Due to this, the accuracy of the text format conversions is not guaranteed.

The ‘Text Format Conversions’ feature enables formatting and conversion of rich-text fields such as ‘Description’, ‘Comment’ and any ‘Custom-rich text field’.  This is supported for four datatypes namely–Wiki, HTML, Inline HTML, and Plaintext. 

Note: If you want ‘Text Format Conversion’ support in your existing automations, you have to choose an appropriate datatype (supported for your application) in the Data Type Mapping field.  If you don’t select a datatype, the default datatype for that application will be taken.  The advantage here is, selecting the correct datatype according to your application enables the text to be converted automatically in the required format

Points to remember

  • You have to select the datatype (based on the adapter) from the DataType Mapping drop-down list. For example, Jira supports ‘Wiki’, and QC supports 'HTML' formatting.  In this case, if you choose ‘Wiki’ for QC, data syncing will not happen in the desired way.
  • In scenarios where the source and destination have the same datatype, ConnectALL will not do ‘Text Format Conversion’ as it is not required.
  • For certain adapter-specific datatypes such as string, text, and text area — ConnectALL defines the datatype as ‘Plain Text’; For ‘Memo’ — it defines the datatype as HTML. Hence, if a particular field’s datatype is either string or Text or Textarea, and if it is an RTF component field, formatting is done automatically.

To find out more about the datatypes supported for each application,  check the below-provided list. 

Adapter Names

Default Datatypes

Other DataType (if any)


Atalassian Jira


Jira, by default, supports Wiki. However, if any plugin such as a JEditor plugin is used, then Html formatting will be supported by the plugin. So if a JEditor type field is mapped in ConnectALL, then, the datatype should be selected as Html.

Atlassian Jira CloudADF (available from version 2.10.24)

The ADF format will be displayed by default only for the new automations. In the existing automations, the datatype chosen earlier will be displayed. If you wish, you can change it to ADF. Note that nodes are also supported. 





Micro Focus ALM/Quality Center


Azure DevOps (VSTS or TFS2015+)/ Microsoft Common Adapter)


Azure DevOps Server (formerly TFS)

7. Agility (Formerly VersionOne)

PlainText Agility's description supports formatting. So you have to choose 'Html' as Description datatype.


BMC Remedy


13.IBM RTCHtml

Octane's description-default datatype is 'Memo'. So change the datatype to  InlineHtml (as the datatype 'Memo' is represented as Html in ConnectALL)



PlainTextCherwell's Description supports RTF. So you need to choose Html as Description DataType 



Data received from the source will be synced 'as is' to the destination.