Bug ID | Description | Resolution |
DCNG-21236 | When you fetch the schema for a table with a Varchar (max) field, then the SQL Server 2019 connector reports it as Varchar(1048576). | Fixed |
DCNG-21197 | When you run a map with Swift(edoc) connector, the Target Data browser does not display any data. However, the data is written in the target. | Fixed |
DCNG-21133 | After updating SAP JCO to 3.1, the engine loads SAP JCO native library two times. | Fixed |
DCNG-21114 | For SFDC connector, error messages are not logged in the target batch response file when the Target Object Name is missing, when target object name is invalid, and when invalid key is used for update, upsert, and delete the table operation. | Fixed |
DCNG-21113 | When you run a map with Salesforce connector and if you update operation without action key, DataConnect crashes. | Fixed |
DCNG-21102 | When you run a map with ASCII (Delimited) as the source connector and if a special symbol under text as ’ is added, then when you browse the source data, incorrect data is displayed. | Fixed |
DCNG-21058 | If relative path is used in the process step (stop, start and script), then process execution fails with "Validation failed " error message. | Fixed |
DCNG-21048 | In a map, the sorting option does not work. | Fixed |
DCNG-21023 | en dash character is written as a hyphen with v9 artifacts. | Fixed |
DCNG-20996 | The MSMQ Component, PutMessage and GetMessage actions fail with the MSMQ component. Also the PostMsg step fails with “Error writing message: Failed to write message body: -1072824318”. | Fixed |
DCNG-20974 | When you run a process using Websphere MQ 1.0.0 component using PutMessage or GetMessage, process fails with the following error message: Error writing message: ImqQueue::put failed with reason code '2029' in PutQueueMessage | Fixed |
DCNG-20884 | NCHAR and NVARCHAR2 field sizes are incorrectly set using the Oracle 19 Direct Path connector resulting in errors. | Fixed |
DCNG-20722 | Performance loss when using the ILAddrow function with greater than 600k records. | |
DCNG-20242 | In a map with Servicenow connector, Unicode characters are not inserted into target table. | Fixed |
DCNG-19151 | In a map that has a Numeric datatype in the source data field with two decimal places (e.g. 165.40) and if you directly map it into an Excel target spreadsheet, then if the second decimal place is a zero it will not be written and zero at second place gets truncated. | Fixed |
DCNG-18981 | When you run a map with Oracle 19c connector, incorrect values are inserted for BIGINT with Number(20) datatype in Oracle table. | Fixed |
DCNG-18959 | In a map, when you use Transformation object with Lasterrorcode and lastscriptingerror code property, then the actual value is not returned. | Fixed |
DCNG-18783 | When you run a map with JSON connector, you can read the array values from a JSON source file. However, you cannot write array values to target JSON field. | Fixed |
DCNG-18636 | The TimeStamp() script function is missing in Functions list. However, this function is available in Content Assist list when you type Time. | Fixed |
DCNG-18079 | When you run an existing map that has Numeric dataype, the following error message is displayed: Field type mismatch for Source connector schema record layout R1 field Registrar_ID | Fixed |
DCNG-17920 | Unable to load Unicode data into Actian Zen database and displays the following error message: Error 25507 opening target | Fixed |
DCNG-17793 | When you run a map with Salesforce as the source connector, and any connector as the target, the map runs successfully. However, the Logs tab displays the following and warning: Unexpected SOAP type 'xsd:anyType | Fixed |
DCNG-17120 | In New Process Wizard, the Finish button is not disabled in all the New Process Wizard windows until Use Studio option is selected in the Summary page. | Fixed |
DCNG-16709 | When an object global variable in a map has an Initial Value set and if you run the map, the engine displays the following error: Initialize Global Variables(2): Assigning non-object to object variable | Fixed |
DCNG-16587 | When creating a new package, if you click Browse to locate a runtime configuration on the hard drive, then the default workspace location is not displayed. | Fixed |