User Guide > Change Log > Change Log for 11.6.0 (Build Number 11.6.0-20)
Was this helpful?
Change Log for 11.6.0 (Build Number 11.6.0-20)
The following table provides the list of fixed issues’ details in the 11.6.0 release with 11.6.0-20 build number.
 
Bug ID
Description
Resolution
DCNG-17892
In a map that has a target multimode connector, unable to delete records that contain NULL values using the Delete operation.
Fixed
DCNG-17858
In a DI9 map, the Append mode is not working on the Reject tab.
Fixed
DCNG-17810
In a map > Configuration tab, if you set the Execution Option to Treat as Error and run the map, Truncation warning is displayed in the Logs tab and Truncation error is displayed on the Result tab.
Fixed
DCNG-17697
Before creating a new message property for each option, a check is required to make sure that the message property with the same name as the option does not exist.
Fixed
DCNG-17646
When using a djmessage object with the Excel (xlsx) or Excel 2010 source connectors, the following error message is displayed.
Failed to connect: Unable to locate Excel file
Fixed
DCNG-17643
In a process (with compatibility mode on), the relative path does not work for the Transformation step. If you double-click on the step, the following error message is displayed:
Unable to open transformation specification
Fixed
DCNG-17640
On Linux, when you run a map with Avalanche as the target connector and if the CommitFrequency target property is set to 5 or 10, the map must fail and return the error code 42.
Fixed
DCNG-17597
Unable to duplicate a process that contains a SQL session and results in the following error:
getOptionValue not supported in SQL Sessions
Fixed
DCNG-17357
The data type for a field having long integer values is incorrectly recognized by the ASCII Delimited and Unicode Delimited connectors when the connector property AutomaticStyling is set as True.
Fixed
DCNG-17064
When you create a new schema using Cobol Flat File as the source connector and Metadata connector as Cobol 01, DataConnect crashes.
Fixed
DCNG-17063
On AIX machine, when you run a map with ServiceNow as the source connector, it fails with the following error message:
Error connecting: Error 19 loading map: Failed to connect: Received fatal alert: handshake_failure
Fixed
DCNG-16971
In JDBC connector, for the Transcation Isolation Level and Cursor Type properties, numbers are displayed instead of labels.
Fixed
DCNG-16948
In a process, if the Max Thread Count is set to a value greater than 1, then the value returned is a temporary log file that is assigned to the thread. It is deleted by the time the process finishes running. The value returned should be the value configured in Log file name.
Fixed
DCNG-16901
In a map with ServiceNow connector as the target, when you insert data with decimal or float data types, the target data browser does not show the numbers after the decimal point.
Fixed
DCNG-16759
In map or a process, if you edit an existing global macro value, then a copy of the macro is created, marked as global with the same value. After you save, close, and reopen the map or process, the existing macro is displayed as global and the copy is displayed as local macro with the updated macro value.
Fixed
DCNG-16448
Map does not load if relative path is specified in the Transformation Step.
Fixed
DCNG-16399
In Process Editor, when you hover on the step properties and parameters, the tool tips doed not display the description. Instead the property name repeats as the description.
Fixed
DCNG-16385
When you run a map with Salesforce as the source connector, and the QualifiedRecordName source property is set to Full, then the map fails with the following error:
field type mismatch for source connector schema record layout
Fixed
DCNG-16255
When you browse the source data in a map that has NetSuite as the source connector, the custom fields are not displayed in the table schema.
Fixed
DCNG-16207
On Linux and AIX, the DataConnect version is not displayed correctly in the cosmos.ini file.
Fixed
DCNG-16195
When you run a process from the command line with Max Thread value greater than 1 and has a Transformation step that contains a map with DMS connector, the process fails with null pointer exception and 28025 error code.
Fixed
DCNG-16149
When you open the EZScript Editor from a map or a process and go to the DJImport/Export Object Connection wizard > BUILD Connection String window, select a connector and try to paste a macro in the connection parts, the Configuration Macros are not available for selection in the Paste Macro dialog.
Fixed
DCNG-16002
When you open a map with Actian Zen connector and if the source and targets are not connected, then clicking Show Results icon > Connect for Me on the Mapping tab, displays the following error message:
Error 25507 opening target ‘Actian Zen’: Exec SQL: SQL Statement < DROP Table “orders”>
Also, the result is not displayed on the Results tab.
Fixed
DCNG-16000
In a map, if the conditional expression inside a Record Started event is commented, then the map runs without errors but does not write any records to the target.
Fixed
DCNG-15938
When you open a map that contains unresolved macros, an error message is displayed and if you click OK, an empty map opens in the map editor.
Fixed
DCNG-15736
If you configure a target such as JDBC or ServiceNow without using multimode wizard or Schema Selector, then the following error message is displayed:
No schema defined
Fixed
DCNG-15532
The execution time for Excel in xlsx format is more compared to running an excel file in xls format.
Fixed
DCNG-15212
In a map with Excel as target connector, the Multimode wizard does not reset the header line even if the HeaderRecordRow property is reset.
Fixed
DCNG-15173
On AIX, maps with DMS connectors fails to run and returns error code 19 along with the following message:
Cannot locate 'com/pervasive/dms/AbstractConnectionFactory' class.
Fixed
DCNG-14782
In a map with Netsuite 2018 connector, unable to retrieve schema if the Nested Children property is set to True.
Fixed
DCNG-14753
In a map, when connecting to a Excel connector file to establish the fields and field sizes, the field size defaults to 16 regardless of the actual field size. The field sizes must be set to the largest value for each field.
None
 
Last modified date: 08/10/2022