New

Create Node Endpoint

You can now create Nodes using the Create Workspace Node endpoint. Create Workspace Nodes supports creating all Node types. Combined with the Set Node endpoint, create and update Nodes programmatically.

Updates

• We’ve made multiple API updates including:

• Added pagination to List Environments. In addition to existing fields, we have added:

  • total - Number of results

  • startingFrom - The id the request starts from.

  • limit - The request page size. 100 is the default.

  • next - The value where the next page of results starts after.

• Added type to List Run Results. Type indicates if it is a sql or sqlTest run.

• When using ref functions, an error message will return if there is a cyclical dependency.

• We’ve made some user interface improvements including:

• Added tooltips for all statuses in the Activity Feed.

• The Fetch button in the Git Modal has moved to be in-line with commit and branches.

• Improved Column Lineage so it's easier to see the Node lineage.

Packages

New - View-Qualify Advanced Deploy Node

We’ve released a new package Node, View-Qualify Advanced Deploy UDN. This is a versatile Node that allows you to create and deploy views in Snowflake using the QUALIFY filter. It gives you a streamlined way to filter records within a View using window functions such as, RANK or ROW_NUMBER. It supports common use cases like deduplicating data, selecting top and bottom records, and applying customer filters.

Bug Fixes

• Clicking on a Node in the Docs no longer results in an error screen.

7.17.1

Node and Column Test Failures

These features are currently in Private Preview. Please reach out to your Coalesce account manager to sign up.

We’ve introduced a new feature that lets you know when a Node or Column Test has failed during a refresh.

On the Deploy page, statuses are now color coded for easy review.

• Green - It was successful with no errors.

• Yellow - The Refresh was successful, but had Column or Node test failures.

• Red - The Deploy or Refresh failed.

Take a look at Troubleshooting Deploys and Refreshes.

Updates

• You can now use OAuth to run concurrent jobs using the Snowflake Tasks API.

• You can now type to search within all dropdown filter menus on the Deploy page, making it faster and easier to find the option you’re looking for.

Bug Fixes

• Previously credential errors and mismatches would return a 500 for the`startRun` endpoint.`startRun` now returns either a400 or 401.

• We fixed an issue where an invalid project ID would make the application unresponsive.

• [Object Object] no longer appears in the hash column.

Version 7.16.1

Deprecated node metadata changes were completed with the release of 7.15.

Previous posts

• March 13, 2025 - Upcoming Deprecated Node Metadata Changes

• March 3, 2025 - Deprecated Node Metadata Changes

• The coa CLI will now display plan warning messages even if the plan was successfully created. This will help you identify any issues that come up before deployment.

• The /api/v1/environments/{environmentID}/nodes and /api/v1/workspaces/{workspaceID}/nodes endpoints now have pagination. You can use the following query parameters to organize your responses:

  • Limit - The maximum number of Nodes to return.

  • startingfrom - The cursor point for paging the query results.

  • orderBy - The field to order the results by.`

Version 7.15.1

• Turning off the multi-source toggle will now properly remove the additional source from the YAML file.

• [Object Object] no longer appears in the hash column.

• Column lineage will now display a loading spinner and will only render when column lineage is ready.

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:

• Release 7.14 - Already completed ✅

• Release 7.15 - Coming soonCompleted on March 18, 2025 ✅.

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.

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

This release includes bug fixes and performance improvements.

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.