Connect with peers, share your expertise, and inspire what’s next in Smartsheet — from proven practices to practical how-to insights from fellow users and product experts.
Sign in to see the current vote count, add your own vote, or leave a comment.
Within DataMesh it would be really helpful to include an additional field to provide a description of what workspace/purpose etc. that the DataMesh config is applicable to. Currently I have ~50 configs for various workspaces. I have come up with a naming structure however I am limited to how much space I can use.
I like the idea of having a note or description field in DataMesh too. When you’re managing dozens of configs across different workspaces, it can get hard to remember which one is tied to what purpose. A simple description box (even with a character limit) would help a lot with organization and reduce the need to rely on naming conventions alone.
Until Smartsheet adds something like this, one workaround could be keeping a separate “Config Tracker” sheet where you log each DataMesh setup, its workspace, and its purpose. It’s not as seamless as having notes directly in DataMesh, but it gives you more flexibility in how much detail you store.
Hope it answered your question. 😊
Totally agree, this would be a big usability win 😊. A dedicated notes or description field would make it much easier to understand the purpose of each DataMesh config, especially when managing dozens across different workspaces . Naming conventions help, but they are not a great substitute for proper context built into the product.
Thank you for your question about file transfer performance. To keep the process smooth and efficient, it’s important to first verify that your network speed can handle high-speed transfers, as file transfer performance depends heavily on the network environment. Make sure UDP is enabled on your network because it allows fast, uncapped speed; if it’s blocked, the system automatically switches to TCP, which can slow things down. For best results, use a dedicated file transfer session instead of transferring files during a remote-control session, and always minimize file size by sending only what’s necessary. Just like choosing the right travel insurance policy protects you from delays and unexpected costs, upgrading RAM and ensuring your CPU and network hardware are capable will help protect your workflow from performance bottlenecks. 🙂☺️
Totally agree — this would be a big usability improvement. A dedicated notes or description field would make it much easier to understand the purpose of each DataMesh configuration, especially when managing many across different workspaces. Naming conventions help, but they can’t replace proper built-in context. 😋
😋
The DataMesh Note Section is a feature used to add important notes, comments, or additional information within a DataMesh project or report. It helps users organize details clearly and keep all relevant information in one place. This section can be used to write explanations, instructions, reminders, or observations related to the data. By using the Note Section, teams can improve communication, maintain documentation, and ensure that important points are not missed during analysis or project work.😊
😊
This would be a really helpful addition. When managing a large number of DataMesh configs across different workspaces, naming conventions alone aren’t always enough—especially with character limits. An optional description field would make it much easier to quickly understand the purpose and context of each config without relying solely on abbreviated names. Great suggestion! 😊
That’s a great point, and I can see how managing ~50 configs would quickly become difficult with naming alone.
Adding a dedicated description field for each DataMesh configuration would definitely improve clarity and make it much easier to identify the intended workspace or purpose at a glance. Naming conventions help to an extent, but they’re not always enough—especially when you’re constrained by character limits.
It would be really useful if DataMesh allowed for additional metadata (like descriptions or tags) so users can better organize and manage multiple configurations. Hopefully this is something the team can consider for future updates.
In the meantime, you might also consider maintaining a quick reference document externally to map config names to their purposes, just to make things more manageable. 😊
Sign in to comment or add your vote.
