Product Updates

Breaking Change in listRun Endpoint – Version 7.19

by Coalesce
Action Required

Breaking Change in List Run Endpoint – Version 7.19

Effective in version 7.19, there is a breaking change to the listRun endpoint:

  • The orderBy parameter is now mandatory whenever the startingFrom parameter is included in a request. This change ensures consistent and predictable pagination behavior when using the startingFrom cursor.

What you need to do:

  • If your integration uses startingFrom, make sure to include a valid orderBy value in the same request. Requests missing the required orderBy parameter will now return an error.

Version 7.18.1

by Coalesce
Announcement
Updates
Bug Fix

Action Required: Upgrade to CLI v7.17.1

We are notifying all Coalesce customers using command-line tools that an immediate upgrade to the Coalesce CLI version 7.17.1 or higher is required. Snowflake's recent 2025_02 release includes changes that may cause service interruptions for users running older versions of the Coalesce CLI.

To prevent any disruption, please check your CLI version by running:

coa --version 

If your version is lower than 7.17.1, upgrade your CLI by running:

npm upgrade -g @coalescesoftware/coa 

For more information on the Snowflake bundle changes, please visit the Snowflake Release Notes.

Updates

We’ve made several improvements to the Coalesce user experience:

  • Nodes in the Build Interface panel and source Node selector are now alphabetically sorted for easier navigation.

  • The Deployment page features interconnected filters—selecting a value in one filter automatically updates options in related filters.

  • You can now view Column Lineage while in Column Grid view, enabling quick lineage access when working with large graphs.

  • When viewing a selected (blue) Node in Column Lineage, you can edit it directly without having to locate and select it again.

  • Selecting a Node in the DAG or Graph View now highlights its counterpart in the sidebar, maintaining view consistency and eliminating redundant selections.

Bug Fixes

  • Deployments now succeed when a Node's source changes while its name remains unchanged.

  • The Node editor now shows an accurate number of Columns that are in a Node.

Packages

Find the right building blocks for your data pipelines and accelerate initial development by using ready-made Packages from Coalesce Marketplace.

New

Delta Stream Merge Node

View-Qualify Advanced Deploy

Updates

Bug Fixes

  • A bug in Dimension Zero Key Node related to handling certain edge cases around null value handling has been fixed.

  • Persistent Stages change has been made to fix an error caused when all column are chosen as change tracking for Type-2.

Action Required: Upgrade to CLI v7.17.1

by Coalesce
Action Required

We are notifying all Coalesce customers using the command-line tools that an immediate upgrade to the Coalesce CLI version 7.17.1 or higher is required. Snowflake’s recent 2025_02 release includes changes that may cause service interruptions for users running older versions of the Coalesce CLI.

To prevent any disruption, please check your CLI version by running:

coa --version

If your version is lower than 7.17.1, upgrade your CLI by running:

npm upgrade -g @coalescesoftware/coa

For more information on the Snowflake bundle changes, please visit the Snowflake Release Notes.

Thank you for your immediate attention to this matter.

Upcoming Deprecated Node Metadata Changes

by Coalesce
Action Required

In our ongoing efforts to enhance performance and maintainability, we're removing some legacy metadata fields that are no longer needed.

This process is happening in two stages:

What this means for you:

  • No workflows will be disrupted.

  • No data will be affected.

When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected when deprecated metadata is removed. You will need to:

  1. Making a commit with the changes.

  2. Continue on with your workflow.

Example of a commit with metadata changes

Deprecated Properties Removed:

Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status. These fields may still appear in our API, but are no longer used in the Node metadata.

  • dataset

  • table

  • metadata.join

  • metadata.sourceMapping - already absent from most sources

See our previous changelog post about the changes in 7.14.

Deprecated Node Metadata Changes

by Coalesce
Action Required

Coalesce cleaning up deprecated metadata fields in Nodes. The change will improve data integrity across Coalesce. This will happen in two stages:

  • Release 7.14

  • Release 7.15

When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected while deprecated metadata is removed. We suggest making a commit with the changes then continuing on with your workflow. Do not delete, edit, or modify the deprecated fields in any way.

Changes in Release 7.14

Deprecated fields in 7.14 will primarily affect older workspaces that haven't been accessed recently. For actively maintained workspaces, the impact should be minimal. However, if you attempt to commit against previously archived or long-dormant workspaces, you may encounter these changes.

Deprecated Properties Removed

The following properties will be completely removed if present:

Top-level column properties:

  • ghostRecordValue

  • descendedFrom

  • hashColumns

  • columnsForHash

Inside hashDetails object:

  • hashType

  • hubHashes

Properties corrected for Invalid Data

Properties set to empty string (""):

  • dataType - if not a string type

  • transform - if empty

Properties completely removed if invalid

  • appliedColumnTests - if null

  • config - if null

  • hashDetails - if it's a string (should be an object)

Column Reference Fixes

Column Reference (columnReference)

  • stepCounter - if null/undefined, set to the node's ID

  • All IDs within column references are converted to strings (previously numbers were allowed - this change has been around for a long time)

Source Column References (sourceColumnReferences)

For each reference in the array:

  • All IDs within column references are converted to strings

  • stepCounter - if null/undefined, set to empty string ("")

Hashed Columns Fixes

For hashedColumns array:

  • All IDs within column references are converted to strings

Upcoming Changes in Release 7.15

Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status.

Deprecated Properties Removed:

  • dataset

  • table

  • metadata.join

  • metadata.sourceMapping - already absent from most sources

Planned Maintenance Notice

by Coalesce
Announcement

Coalesce will be taking a scheduled maintenance window. During this time, search functionality within the generated documentation pages will be temporarily unavailable.

Maintenance Details:

Date: Monday, February 17, 2025

Time: 8:00 PM - 10:00 PM US/Pacific

We are performing this maintenance to enhance the stability and performance of our platform. We expect search services to be fully restored by 10:00 PM PST, but will notify users if there are any delays or updates.

The rest of the platform will remain fully operational during this time.

We appreciate your understanding and apologize for any inconvenience this may cause. If you have any questions or concerns, please feel free to reach out to our support team.

Command Line Users on Versions 7.5.8 or Below

by Coalesce
Action Required

Command line users on version 7.5.8 or below should upgrade to coa version 7.10.2 immediately.


Users on`coa` version 7.5.8 and below may encounter deployment and refresh errors. The issue occurs with the presence of`platformKind:snowflake` in the data.yml.

To fix any critical deployment or refresh issues:

  • Upgrade to coa version 7.10.2 as soon as possible to prevent further issues.

If you are unable to upgrade your coa version and need to deploy immediately:

  • Check your commits for platformKind:snowflake in the data.yml file.

  • Manually remove the platformKind:snowflake and commit the changes.

  • Deploy as normal

We are working on a change to be delivered within the next 24 hours to allow backwards compatibility for older versions of coa as to not disrupt operations.

Important Changes Coming

by Coalesce
Action Required

On September 5, 2024, Coalesce will begin enabling two upgrades for all organizations.

We encourage you to prepare for the changes by:

  • Upgrade the CLI to the latest version.

  • Have your organization's administrators enable the Git Repo Format Upgrade before the mandatory deadline.

  • Optionally, contact support to enable the RBAC migration early.

  • Review existing roles and understand the permissions they will have under the new system.

By preparing for these changes early, you can avoid unintended consequences, such as being unable to make commits until the upgrade is complete.

We encourage you to review our documentation for more details:

Contact our support team to start preparing.

Contact Support