DCNG-18564

When fetching a UTF-16 text file with the FTP 4.0 Queue, the byte order mark (0xFF,0xFE or 0xFE,0xFF) is replaced with 0xFD, 0xFD, rendering the file invalid.

Fixed

DCNG-18563

After you import v10 maps, DataConnect renames the datasets but does not correctly attribute them to the maps they were previously assigned to.

Fixed

DCNG-18562

When you run a process using DJMessage with JSON as the target connector, then the schema describe error is displayed for space or "/" in the name of the field.

Fixed

DCNG-18561

If DJMessage reference string is present, then import step doctoring XSLT process steps must skip file or file/macro for source and target. 

Fixed

DCNG-18547

On the Configuration tab, when you edit macro sets that are a copy of another macro set, then the updated macro sets are not saved.

Fixed

DCNG-18539

When a zip file is extracted for v10 zip import, extraction fails if any of the file names inside the zip begins with _

Fixed

DCNG-18516

HIPAA (and maybe EDI) connector is not recognizing component separator in maps (with compatibility mode on). Maps imported from v9 are producing invalid output with * for sub-element separator.

Fixed

DCNG-18482

When importing an existing v11 project using the Import > DataConnect > From File Folder option, and copying to the new workspace, links between artifacts are updated to their new locations, but the log files that refer to the old workspace location are not updated.

Fixed

DCNG-18481

When importing a v10 exported project, dataset artifacts are renamed from .dataset to either .src.dataset or .trg.dataset. If the names include a dot before the final extension dot, then part of the name after the first dot is removed. If this results in duplicates, _1 (and higher depending on the number of duplicates) is appended to the name.

When runtime configurations are created or updated based on these datasets, they will correctly use the truncated name but all RTCs will use the first of any duplicates, even if the dataset that the map previously pointed to has been renamed to _1.

Fixed

DCNG-17890

If source connector is ODBC 3.5 and you select any source table and connect it, the schema is loaded. After adding a column to that table and in DataConnect, click Disconnect and Connect, the No schema mismatch error is displayed. Again, if you click Disconnect and Connect, the schema is updated with the new column.

Fixed