This has been reported to the website support team and we are looking into it. In the meantime, please add your votes from the list view or by commenting on that idea.
You can see Statuses by filtering the main list.
Select which columns to copy or move from one sheet to another
Comments
-
Adding my support for this idea - I will try helper sheets etc., but this feature would be a significant improvement for automations. In the ideal world one would have a mapping from column to column with the option of functions (for instance, Column A in target sheet is Column B + Column C from the source sheet), but even simply mapping would help!
-
Title says it all. When I'm moving rows or columns to different sheets I'd like the ability to select which columns of information I'm moving. Not all of them are relevant to the other sheet and it adds for a lot of bloat and clutter. Especially because if I delete the columns on my new sheet when the next batch of rows comes in they re-add all the columns.
Michael - Alternative Delivery Analyst
-
This would be quite valuable!!
-
Our sheets continued to get too big because we only have the option of moving the entire row (usually 30-45 columns or more). Because we are not able to choose which columns to copy/move, I found my own workaround I titled "Single Cell moves":
1. Single Cell sheet - copy the row to this sheet with automation rule(s) - allows for certain criteria to determine occurance.2. Create a Mesh to move only the columns/cells you want on the new processing sheet (I usually only move the primary key/ID field and mesh in any other info from our primary database sheets - we have over 25 so it get's a little problematic to do these, but they rarely break).
3. Clear off the Single Cell Sheet once a day (I chose at 2am each day) to an "archive" sheet for the info
I have this work around in place for over 20 processing sheets. It works pretty well, and you don't have to worry about formulas or automations breaking to any great extent. -
It would be nice if in a Copy Row workflow action, you could select which columns to copy. This would allow for new entries on one sheet to create new rows in another related sheet, where the target sheet only needs partial information. Currently all columns are copied, and columns are created if they don't already exist in the target sheet, even if those columns are unwanted (or contain confidential data). This would reduce the need to enter data in one sheet, and then enter a unique identifier in another sheet, and then set up a Mesh to move only specific columns over.
-
Yes! This workflow is incredibly valuable. I have noticed that it has been frequently requested on the forums, with suggestions for workarounds such as using vlookups and helper sheets. Implementing this feature would significantly enhance SmartSheet's functionality.
-
We need this as well. Our use case is managing a multi-level governance process. We have market-level and national governance. I want to copy approved rows from market-level governance sheets to a national sheet. We need to retain the attachments and comments, but would like to select specific columns leaving behind non-relevant market details.
-
Adding this feature would significantly enhance SmartSheet's functionality. It has been requested many times over the years. Do you have any updates on when we might see this feature rolled out?
-
I just want copy some of the columns when moving a row in automatization section instead of all of them.
-
It would be a GAME CHANGER if in the "Copy to Another Sheet" or in the "Copy Rows" automations/workflows, that we could choose which columns to copy instead of being limited to sending over every column included in the row.
As an example, I have an automation to copy a row to another sheet when a box is checked. The sheet I'm copying from is a master list, so it has A LOT of columns. The sheet I'm copying to only has maybe 5 columns, and I would really prefer that all the columns from the master list not be added to the other sheet.
As a bandaid, I hide the columns that are unnecessary to the sheet, but when it comes to situations where I'm building a report, having so many unused columns makes the process more complicated.
-
Yes, please add the enhancement to move only selected columns. When moving all columns, it makes our destination sheet too large and cannot handle enough data with the current cell limitations. This would be a great improvement to help, especially if the increase on cell limits is still a long time coming.
-
Definitely would use this functionality. We have two different sheets for tracking enterprise and department level project portfolio, with different needs so we have different columns. They were intentionally set up to be different sheets. Due to the growing need to share some data between the sheets, we ended up copying some rows, which of course brought all of the extra source columns with it. We have some overlap in column names so some of the data that we did not want was brought in and now messes with our recipient column data. And we have a lot of "crap data" now in our recipient sheet.
Please implement this! thanks
-
We truly need the ability to copy specific rows to a new sheet, even if we have to map the fields. It is impossible to copy full rows when you have a 'system' field such as created/modified. Utilizing 3 sheets to handle 1 task is inefficient, uses too much space, and creates unnecessary sheets.
-
@Cindy B if you are open to mapping fields, DataMesh will allow you to do just that and map and copy over new records with only certain columns.
Danielle W.
Product Marketing
Smartsheet
-
This is another feature I would really find helpful and another one that has not been updated in years. For me I have a sheet with all the data that comes via a form and then various admin manual updates are made and pricing for jobs is done up. I don't want the sensitive information in this sheet to be linked to the production floor data and therefore having the ability to turn certain columns into the production order on a separate sheet would solve my issues.
