I often have issues with DataMesh breaking because it is mapping by column name, rather than columnID on the back end. Is there any way this can be updated so if I change a column name, it does not break our DataMesh workflows?
Sign in to see the current vote count, add your own vote, or leave a comment.
Dear @Samuel Mueller Agreed. Datamesh should be updated as the latest column renamed.
Although we are extremely proficient when it comes to reducing load on our smartsheets (we use pivot, data mesh and data shuttle extensively), we still find ourselves hitting capacity limits (mostly because of the number of columns in conjunction with some pretty complex formulas). Breaking up data between sheets and…
Be able to print and/or export Workflow Automations in PDF and/or export to Visio. this would be used for document control and troubleshooting aid
It would be beneficial to be able to leverage Smartsheet Automations to make REST API calls. This has many potential use cases, but one I could see is adding users to Smartsheet groups when the are added to a 'roster sheet' in Smartsheet. It would allow us to use the full power of Smartsheet's API within easy to use…
