A group administrator can now remove users from a tenant. Their user ID record will be removed from the database and this can be done on the Manage Tenant page.
You can now view which agent is attached to a particular task on your job page. This will display which agent a task will use and also whether the agent is healthy or unhealthy, and can be viewed beside the task’s last modified date.
You can make a job from one project now dependent on a job from another project, as we have added cross project job dependency. While viewing a job in a project, click on the Job Dependency button and you can browse jobs in all projects and select which job it should be dependent on, or view any existing dependencies.
In a data migration task users can now also filter target tables. The filter will be available once you have selected your source tables.
We have improved the process for deleting an agent and have added clear instructions that will guide you through each step. You can migrate your jobs from the agent you want to delete onto another agent, and then proceed to delete your agent after this recovery of jobs. This will also prevent you from deleting an agent if a job was running during the time you selected to remove your agent.
For a smoother user experience, when configuring Snowflake Data Migration tasks the internal stage will be used by default. This can still be changed during configuration of your task.
We have improved the format of our notifications.
The connection name limit has been increased to 50 characters.
We have improved Snowflake installation on non-containers so that it will automate SnowSQL installation for Snowflake users rather than installing it manually.
We have added connection validation for file definitions to test whether the files in the file path are readable. If files are not readable Loome Integrate will notify you in an error message.
‘FlatFileDetectDataTypeMaxRow’ can now be used as a setting in tasks. You can select the amount of rows to profile before a flat file migration is executed as we have added this as a setting in tasks. This is aiming to replace the ‘FlatFIleDetectDataTypeMaxRow’ setting in the tenant settings. Migrations will also still use this setting until they are individually updated in the Loome Integrate Application.
We fixed the issue where it would not save the normalize tables setting under some circumstances, and it will no longer revert the saved value.
The issue where you could not change the frequency of an existing schedule from ‘recurring’ to ‘just once’ has been fixed.
We have fixed a bug that did not allow users to submit feedback via the ‘Submit Feedback’ button.
We have corrected an issue with the configurable advanced options for tables, and you can now submit and save changes made to these tables.
We have fixed an issue so that the agent will now ensure that when cancelling a job it will cancel running tasks in the agent using a task cancellation source and this has been factored in for all task types. The behaviour was somewhat temperamental before this update.
Version 2019.11.22.1
You can pull in data from Oracle, as a data source, using a Oracle Data Provider connector while it also supports column level mapping, incremental configuration and column filters.
We have added a Microsoft Graph connector that allows you to pull in data from Microsoft Graph. It also currently supports pulling in Azure Active Directory Sign Ins and Audits, and more objects will be available in coming updates.
We have improved our Snowflake connection for Snowflake to Snowflake migrations by using CTAS for the initial creation of tables.
We improved our Snowflake Internal Stage performance by allowing users to choose between a CSV based import or a Parquet based import to provide you with a faster experience for your Snowflake migrations.
We have updated the Snowflake ADO.NET driver for the Loome Agent, as the ADO.NET driver was updated to fix an issue with scalar precision. Users will no longer be able to include the username and password in the connection string and instead will need to provide it in the connection form.
We have added a setting in the agent that enables experimental features so that you can use a beta version of these features before they are officially released. The first of these features will be in an upcoming update concerning Data Migration stability.
We have improved Snowflake installation on non-containers so that it will automate SnowSQL installation for Snowflake users rather than installing it manually.
We have added connection validation for File Definitions to test whether the files in the file path are readable. If files are not readable Integrate will notify you in an error message.
‘FlatFileDetectDataTypeMaxRow’ can now be used as a setting in tasks. You can select the amount of rows to profile before a flat file migration is executed as we have added this as a setting in tasks. This is aiming to replace the ‘FlatFIleDetectDataTypeMaxRow’ setting in the tenant settings. Migrations will also still use this setting until they are individually updated in the Loome Integrate Application.
We have fixed an issue that occurred in the Snowflake connection string that did not override the default role of a user after you have defined the role in the connection string.
When importing Kepion fact tables it used to import both enabled and disabled tables, we have improved this Kepion connection so it will no longer import disabled fact tables.
We have improved column type mapping across source and target connections. Previously with some column mappings, selecting columns would cause their data types to malform. This has now been fixed for a number of connections including Snowflake, ODBC and various API Connectors.
We fixed a bug where views did not display when configuring a data migration using an ODBC connection.
We fixed an issue where table normalisation would fail on Linux due to the case sensitive file system.
We have corrected an issue with the configurable advanced options for tables, and you can now submit and save changes made to these tables.
We have fixed an issue so that the agent will now ensure that when cancelling a job it will cancel running tasks in the agent using a task cancellation source and this has been factored in for all task types. The behaviour was somewhat temperamental before this update.