10th of December, 2024
Service
User and Group support
We have added support for searching for and adding users and groups from Azure Active Directory in Loome. This will simplify the process of user management.
For example, you can search for a user in your directory and add this user to an application role.
This new feature requires that your organization consent to new permissions to lookup users and groups on your behalf.
We will reach out to you over the coming weeks with instructions on how you can enable this feature.
Improvements
- Monitor: Added ability to group on columns in most lists, including rule results.
- Monitor: Author details are now shown for connections.
- Monitor: When editing a monitor rule, we have improved the experience when a connection is currently unavailable.
- Integrate: Added a new type of incremental data migration mode: Changes Only.
- This mode is suited to output on to Azure Data Lake for ingestion by downstream systems such as Databricks as it only includes just the new rows, rather than incrementally appending rows to an existing file.
- You must update your agent to use this mode, older agents will use the classic style of incremental migration if configured for this mode.
- Integrate: Added the ability to use row version columns from SQL as the currency column in an incremental data migration.
- Integrate: Added the ability to group on columns in most lists.
- Integrate: Added parquet as an intermediary option when migrating to Azure Synapse.
- Integrate: Author details are now shown for connections.
- Assist: Greatly improved the speed of loading the projects page.
- This will result in no spend data appearing on the projects page for up to 4 hours after initial deployment until it is background loaded.
- Assist: Added ‘Data Classification’ to solution collection injected variables.
Fixes
- Monitor: Fixed an issue where some users may not be notified when a row in a results view has been updated.
- Monitor: Fixed an issue where user preference for list or card view may not be saved.
- Monitor: Fixed an issue where the DateOnly datatype from SQL Server would incorrectly display as a mismatch in a Reconciliation rule. This is a display issue in the UI only, underlying data will correctly be labelled as a match.
- Monitor: Fixed an error that would appear in the browser console (did not affect user experience).
- Monitor: Fixed a bug where modifying API keys did not produce a toast notification.
- Monitor: Fixed an issue with users signing in with no access were not being redirected to sign up.
- Monitor: Fixed an issue where the user belongs to multiple tenants, and the top-left Loome icon would link to another tenant that the user belongs to instead of their current tenant.
- Monitor: Fixed an issue where the user belongs to multiple tenants, and on page refresh the user would sometimes end up in a different tenant that they also belong to instead of their current tenant.
- Integrate: Fixed a bug where the ‘Add Schedules’ button was visible during schedule creation.
- Integrate: Fixed an issue where a job may fail to retry when configured for multiple retries and become stuck in a running state.
- Integrate: Fixed a display issue with job executions where the job runs over two days.
- Integrate: Fixed an issue where viewing logs for a job that has never executed would throw an error.
- Integrate: Fixed an issue where filtering on error tasks in a job execution would fail to show errors.
- Integrate: Fixed a display issue where action buttons were not visible on small screens in the job executions page.
- Integrate: Fixed a bug where modifying API keys did not produce a toast notification.
- Integrate: Fixed an issue with users signing in with no access were not being redirected to sign up.
- Assist: Fixed a bug where modifying API keys did not produce a toast notification.
- Assist: Fixed an issue with users signing in with no access were not being redirected to sign up.
- Assist: Fixed a bug where some account level budget users may not receive a budget alert.
- Assist: Fixed a bug where you could not delete a storage account that has been removed from Azure.
- Assist: Fixed an issue where you may not be able to add an API Key to a project.
- Assist: Fixed an issue where you could not switch to another VNET on an account when the original VNET was removed from Azure.
Agent
This update requires agent version - 2024.12.09.1
Please download a new install script and update your agent to use new features, improvements, and fixes.
Some features listed below have already been delivered via an agent hotfix.
Improvements
- Integrate: Added a new type of incremental data migration mode: Changes Only.
- This mode is suited to output on to Azure Data Lake for ingestion by downstream systems such as Databricks as it only includes just the new rows, rather than incrementally appending rows to an existing file.
- You must update your agent to use this mode, older agents will use the classic style of incremental migration if configured for this mode.
- Integrate: Added the ability to use row version columns from SQL as the currency column in an incremental data migration.
- Integrate: Improved Parquet file output to better handle various data types and scenarios.
- Integrate: Added parquet as an intermediary option when migrating to Azure Synapse.
- Integrate: Updated Google BigQuery and Storage drivers, this should result in improved performance.
Fixes
- Monitor: Fixed a bug where timestamp columns from Snowflake may not be mapped to DatetimeOffset in SQL.
- Monitor: Fixed an issue where the DateOnly datatype from SQL Server would incorrectly display as a mismatch in a Reconciliation rule. This is a display issue in the UI only, underlying data will correctly be labelled as a match.
- Integrate: Fixed an issue where offline logging in the agent may cause an exception.
- Integrate: Fixed a bug where timestamp columns from Snowflake may not be mapped to DatetimeOffset in SQL.
- Assist: Fixed a bug where you could not delete a storage account that has been removed from Azure.