---
title: "Syniti Releases"
slug: "december-2022"
updated: 2024-10-17T15:01:13Z
published: 2024-10-17T15:01:13Z
canonical: "skthelp.syniti.com/december-2022"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt
> Use this file to discover all available pages before exploring further.

# December 2022

| Week of 12/16/2022 | **Bug Fix** **Syniti** **Knowledge Platform** Fixed an issue on the *Systems* page where the Scan Results card was not displaying correctly. |
| --- | --- |
| Week of 12/02/2022 | We released the December updates for Migrate and Construct this week, but you may not see them until they are deployed to your tenant. Check back mid month if you don't see these features today! **New Features** **Migrate** - **Content Export** -To provide access to export parts of the data model for import into other projects, we added new MIG_EXPORT views to SRCCONSTRUCT snapshot datasource stored in [Snapshot Management](/v1/docs/snapshot-management). The MIGRATE_APP system datasource now contains these additional views: - MIG_EXPORT_ETL - MIG_EXPORT_MAPPING - MIG_EXPORT_REPORTS - **Training Reset Button**-Syniti Training Department can now reset the training login IDs for base content using a new button added to the Syniti Training tenant. **Enhancements** **Syniti** **Knowledge Platform** Within Enforcements on the Implementation tab, we now show the Implementation Name rather than the Asset ID. **Construct** - The Syniti logo links to the Syniti Knowledge Platform, and the Construct logo links to the Construct Landing page. - Messages shown on the right panel now display in Syniti Knowledge Platform colors. - The Navigation panel has changed to use Syniti Knowledge Platform colors. - The Footer has been removed and the version has been moved to display within Change Settings. **Migrate** - Datasources with a Purpose Type of Reporting or Working are created within Environments, and have been removed from the list of options stored in the [Datasources](/v1/docs/adding-editing-datasources) section. - Importing a table from a [datasource](/v1/docs/adding-editing-datasources) that supports DB connectivity has added validation to ensure that the table name entered exists in the datasource. - Improved the look and feel of Import for , Mapping, and Reporting to match that of the Excel Import process in the [Imports](/v1/docs/etl-import) section of Administration. - [ETL Tasks](/v1/docs/etl-jobs) now include the field Timeout in Seconds to provide an override of the timeout for insert, delete, and update tasks. **Bug Fixes** **Syniti** **Knowledge Platform** - Fixed an issue where asset links existed for category values that had no associated assets. - Fixed an issue where the Markdown editor on certain assets was displaying incorrectly. - Fixed an issue where the Version History page was inaccessible within Enforcements. **Migrate** - When entering a value for an Import Table, the auto-complete functionality within [Datasources](/v1/docs/adding-editing-datasources) Import Table is only relevant to datasources with a server, otherwise, it does not apply. - The system now allows for importing a SQL Server view with a custom schema as the [Datasource](/v1/docs/adding-editing-datasources) table from Data Catalog. - Within [ETL](/v1/docs/etl-jobs), if the **Refresh Target Readiness Reports** task is executed, the field ZTARGET_READY flag is now updated as expected for records where the Target Ready report contains a row. The ZTARGET_READY flag is marked as FALSE and the ZERROR_LOG field contains a message for each row affected. - Within a [Target Report](/v1/docs/create-reports) that provides Segment By filtering, the Sampling quantity selected is now reflected against each Segment quantity and not the report quantity. - Within [Mappings](/v1/docs/mappings), logic for inserting a Construction/Enrichment table as a Source now checks for the Migrate standard fields (ZSOURCE or ZDEPLOY) and will only add these standard fields if they do not already exist as part of the insert. - When adding a non-mapping migration field to the [Dataset](/v1/docs/dataset-design), the system now automatically updates the Working and Target tables for the added field. - When using **Oracle** as the working DB, the following issues are resolved: - Oracle Build table error in mapping - Fixed an issue where ZCRITICAL was using format INT1 incorrectly. Tables now build as expected. - Excel import error - Length too long for Datatype - Corrected the default datatype to NVARCHAR(2000) from NVARCHAR(4000) for importing from Excel to an Oracle working database. - Value Mapping Datatype Xref error - Corrected an issue where the Value Mapping Config views were failing to refresh due to a BOOLEAN datatype. - When using **HANA** as the working DB, the following issues are resolved: - HANA uses BOOLEAN as a format type, and the scripting now recognizes and produces correct scripting for these types for Xref insert, Report Automation, . - HANA scripting has been updated to use MERGE INTO rather than UPDATE FROM for correct script syntax. - When inserting a table across servers, the scripting is now using proper syntax for XSERVER_INSERT task. - Corrected HANA scripting for Update and Delete steps within Value Mappings Config. The use of "Update From" or "Delete From" is not valid in HANA. - Fixed an issue where during the insert for Xref to XTVALUEMAP table the scripting was treating field values for CREATED_ON and CREATED_BY as field names rather than values. - Fixed an issue where, when a mapping field is changed that affects the working or target table fields, a delay was in place prior to making the actual changes. Now, the updates take place in the working or target tables immediately upon saving these changes so that users know the process is working. |