It would make the world of difference if when you deploy a new workspace any copy or move row automations would update to the new workspace not point to the template.
Sign in to see the current vote count, add your own vote, or leave a comment.
I have the same issue. We use a template workspace which we save as new when starting new projects. If the copy and move to another sheet does not update automatically to the relevant sheets within that workspace it renders the function useless.
For one off sheets its fine but for multi-project companies this is a big flaw.
This issue also impacts me when I copy "template" folders to create new projects within the same workspace. The row automations in the new folder still point back to a sheet in the template folder, while all other linkages are updated to occur within the new folder as expected.
Currently the Automation Copy a row doesn't link to new sheet when you save as a new for a folder with all sub folders, sheets, dashboards, and reports.
I have an automation to Copy a row from a metric sheet to a historical sheet to create a trend. I have a report linked to the historical and utilize it in a dashboard. When I copy that folder structure, everything else links appropriately but not the automation copy a row. It stays linked to the original sheet.
I understand that it may be useful to have copy row go to the original sheet, but this should only be when the sheet isn't in the folder that is being copied.
As one of the system admins, it is absurd to me that I cannot view or have access to all of the items created in my organization. We have over 11,000 reports, sheets, and dashboards and I can't see them. I have no visibility to if people are using our plan for their own personal use, or what kind of work is going on unless…
I noticed this the other day and tested Ctrl + M – it does not work. I submit ticket to Smartsheet support – they told me that’s expected behavior because it’s not currently available even though it still shows as keyboard shortcut in the menu🙄 and told me to submit new product idea. Please add this keyboard shortcut to…
Summary of Issue All team members work a standard 7.5‑hour day, but only a portion of that day is allocated for project work (e.g., 25%, 50%, etc.). In Resource Management, however, the system currently interprets allocations as a percentage of the full 7.5 hours, instead of the project‑eligible portion of a person’s day.…