Bug ID | Description | Resolution |
---|---|---|
DCNG-16125 | In a process, the Salesforce bulk loader invoker does not work and fails with the following error message: “Unable to Connect: unexpected element': parser was expecting element ...https but found html” | Fixed |
DCNG-16085 | In a map with ASCii (Fixed) as the source connector, if you click Browse Data, the Source Data tab does not display the complete data from the specified source file. | Fixed |
DCNG-16019 | Performance issues related to data type conversions | Fixed |
DCNG-15988 | When fetching the schema for a table with a Varchar(max) field, the SQL Server 2016 connector reports it as Varchar(16) field. Even if the length is changed in the DataConnect schema, the data is truncated when writing to a target. | Fixed |
DCNG-15955 | In a map with SQL Server as the source connector, when you edit the query statement in the text box, the map is not marked as unsaved (* does not appear next to the map file name in the map tab). Also, if you disconnect and connect again, the data is not displayed in the Source Data Browser. | Fixed |
DCNG-15950 | In a map with XML-DMS as the target connector, when you drag and drop the fields from source to target: • Field size in target is not the same as the field size in source • Field size must not change after reopening the map | Fixed |
DCNG-15888 | When you modify the macro set’s macro value, the macro value and macro count is not refreshed and does not display the modified value. It is displayed correctly only after save and reopen the artifacts. | Fixed |
DCNG-15877 | When you open Package Inventory and update an artifact, the Package Inventory version number is incremented. | Fixed |
DCNG-15843 | The macros in the second workspace overrides the macros in the first workspace. | Fixed |
DCNG-15828 | In a process, when you create a new map from the Transformation step, the macros from the process cannot be used by the map, you cannot add a macro from the process. | Fixed |
DCNG-15710 | If the file destination is not checked to make sure it is not in an arbitrary location, then java.util.zip is vulnerable to zip slip. | Fixed |
DCNG-15686 | Macro artifact reference paths are not converted to the djar root relative paths. | Fixed |
DCNG-15673 | FileExits() and IsFile() functions does not work for file sizes greater than 2 GB. | Fixed |
DCNG-15646 | Adding a number to a text field causes trailing zeros to be truncated and adds decimal point to the number. | Fixed |
DCNG-15644 | When maps are run in parallel using the ETL Framework settings, a core dump is generated during the Transformation step execution. | Fixed |
DCNG-15633 | When compatibility mode is enabled, if you create a package with the process run time configuration file as the entry point (process file has missing project level macrosets), the package inventory fails with a null point exception. | Fixed |
DCNG-15632 | When compatibility mode is enabled, if the map used in the process is outside the process folder and the transformation step preference is selected as Always create a copy of transformation file created by the Map Designer, package is not created. | Fixed |
DCNG-15625 | When you create a map with source and target connector as XML-DMS connector, the following message is displayed: “Defaults records events were also added. You can change these on the mapping tab” However, the default event is not added in the Mapping tab. | Fixed |
DCNG-15562 | On AIX, when you run a map with XML target connector, the int attribute datatype value is not written in the target file. | Fixed |
DCNG-15493 | When you reinstall and launch DataConnect, the following error message is displayed even if the correct license path is specified: “License is missing or invalid. Browse below to a valid DataConnect license file.” | Fixed |
DCNG-15447 | With v9 compatibility mode enabled, in Options > Preferences > DataConnect > Process Designer > Steps, if you select the Always use the existing transformation file created by the Map Designer option, then DataConnect ignores this setting and creates a copy of the map that is selected for the Transformation step in a process. | Fixed |
DCNG-15446 | In a process (compatibility mode enabled), after you specify the map file in the transformation step, the Transformation Step pop-up window is displayed. If you select Use the existing transformation file created by Map Designer option and click OK, then DataConnect ignores this selection and creates a copy of the map. | Fixed |
DCNG-15368 | In a map with multimode target connector, selecting multiple tables does not create the schema properly and the schema contains fields from only the first table. | Fixed |
DCNG-15366 | In Multimode Target Wizard, while selecting multimode connector, the following error message is displayed: “Widget is disposed” | Fixed |
DCNG-15363 | In Mutlimode Target Wizard, Next is enabled even if you have not selected any table from the table list or any new filename in case of new table or sheet. | Fixed |
DCNG-15337 | In Extract editor, wrong data is highlighted if Pad Lines are not enabled. | Fixed |
DCNG-15238 | When you run a map with JSON as the source connector and the source file size is greater than 256 MB, then the following error message is displayed: java.lang.OutOfMemoryError: Java heap space | Fixed |
DCNG-15190 | In Options > Preferences > DataConnect > General, when invalid path is provided in the field, all the preference settings are lost. | Fixed |
DCNG-15177 | Global Variables in EZScript parameters displays duplicates variables. | Fixed |
DCNG-14036 | The version of the documents within a package inventory file does not reflect the actual document version. | Fixed |
DCNG-13799 | In a map with Excel as the source connector (compatibility mode off), if you access DJImport properties for metadata, the following error message is displayed: “Unexpected exception, error code 31013: Runtime error 112: Spoke container access error” The source connector's ConnectString is not logged | Fixed |