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

On February 11, there were reported issues with our 7.13.1 release. We have fully resolved any issues with version 7.13.2. If you experience any further issues, please contact our support team.

We apologize for any disruption and thank you for your patience.

Follow us at https://status.coalesce.io/ to stay updated on Coalesce system status and any service interruptions.

• Added reliability improvements to the checkout process to ensure first-time success.

• Updated Node deletion to immediately reflect removed nodes in the UI without requiring a page refresh.

Fixed “marked failed errors” during refresh.

We fixed a bug where Nodes with a joinTemplate in their definition did not generate code for the join condition, resulting in the join tab being blank..

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.

• We fixed a bug where deployments fail to proceed past the deploy plan in environments where the initial deploy has failed and no subsequent deployments exist.

• We fixed a bug where the placement of the merge conflict marker (>>>>>>) would invalidate the line of code it was on.

• We fixed a bug where the Results panel would not expand.

• We fixed a bug where if Job names were too long, the Deploy menu would be hidden.

• We fixed a bug where Nodes using joinTemplate didn’t automatically add dependencies.

• We fixed a bug where clicking Validate Select on certain Nodes caused the page to freeze.

• We fixed a bug where missing or corrupted metadata would cause the Mapping Grid to crash.

• We fixed a bug where clicking Discard All in the Git Modal caused a validation error.

• We fixed a bug where package and non-package nodes could lose metadata if a deployment failed without finishing.

Updates

• We’ve made it easier to manage SSO users that have been disabled or deleted.

Bug Fixes

• We resolved an issue in graph execution during deploys where changes to indirectly dependent nodes could result in failed deployments due to incomplete lineage evaluation. The deploy process now accurately accounts for the full dependency lineage of views, ensuring proper ordering of drop and add phases, even when gaps exist in the runtime graph. This fix enhances reliability and reduces the need for redeployments to resolve dependency conflicts.

• We fixed an issue where deploys for advanced deploy node types generated duplicate SQL, causing extra stages to run. SQL is now correctly generated for each stage, improving deployment efficiency and accuracy.

• We fixed an issue where trying to deploy returned an error that Node type does not exist.

This release includes bug fixes and performance improvements.