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…
As the smartsheet admin for Europe, it would be extremely helpful to be able to view all Automations / recurring emailed reports in one place as opposed to sheet level. It's almost impossible to ensure everything is working correctly / delete recurring emailed reports without this.
It would be extremely beneficial to have the ability to manually assign colors to individual projects within the Timeline View. Currently, project colors are automatically determined by the Dashboard Theme, which limits flexibility and makes it challenging to visually differentiate projects in a meaningful way. Allowing…
