Subscribe to updatesTurning 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 soon
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:
Making a commit with the changes.
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.
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
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
Project Architects and Project Contributors can now delete Workspaces in any projects they are part of.
Our Join string editing capability now saves correctly when rapidly switching between multi-source nodes.
Our Hash editor automatically displays all columns with proper scrolling functionality.
Keep your CLI up to date to ensure access to the latest features, bug fixes, and security enhancements. Run`npm upgrade -g @coalescesoftware/coa` or download the latest version on NPM.
The previously reported issue affecting users on coa version 7.5.8 and below has been resolved.
No immediate action is required for users on older versions.
The fix maintains backward compatibility across versions.
While older versions are now supported, we recommend updating to the latest version of coa when possible.
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.
You can now add a "Re-Sync Columns" button to custom Nodes. This feature allows users to sync columns that are not part of a source Node. Learn more in Custom Node Types.
We’ve made updates to product feature speed.