Ability to Edit Source and Destination Sheets in Data Mesh Configurations

Amr

Currently, once a Data Mesh configuration is created, it is not possible to change the source or destination sheets without deleting the entire configuration and starting over. While the system allows for updates to column mapping, the core sheet references remain locked

CindyMadrid

Hi Smartsheet Team and Community,

I would like to raise an urgent enhancement request regarding Data Mesh source sheet configuration. This limitation is causing significant operational issues for teams relying on automated updates through APIs and database integrations.

📌 The Problem

When the source sheet connected to a Data Mesh workflow is updated via API or replaced due to backend database syncs, Data Mesh immediately shows the source as "Not Found" and removes it from the configuration.

At that point:

• There is no option to re-select or reassign a new source sheet.
• The entire Data Mesh workflow becomes unusable.
• The only workaround is to recreate the entire Data Mesh configuration from scratch.
• If multiple Data Mesh workflows depend on the same source (with different lookup keys), the issue becomes exponentially more complex and time-consuming.

This is especially problematic for environments where source sheets are refreshed frequently as part of automated data pipelines.

📌 Why This Needs Immediate Attention

This limitation affects:

• Scalability
• Automation reliability
• Maintenance efforts
• Data governance and consistency

For teams managing multiple Data Mesh connections, a single backend update can break all configurations at once — requiring full reconstruction instead of a simple re-link.

📌 Proposed Enhancement

Please consider adding the ability to:

**➡️ Edit or Replace the Source Sheet in an Existing Data Mesh Configuration

without requiring the workflow to be rebuilt.**

A simple “Change Source Sheet” option in Step 1 of the Data Mesh setup would solve this and dramatically improve usability and maintenance efficiency.

📌 Impact

Implementing this enhancement would:

• Reduce hours of rework
• Prevent accidental data-flow interruptions
• Support enterprise-level automation pipelines
• Improve flexibility for API-driven and database-synced environments