Welcome to the Smartsheet Forum Archives


The posts in this forum are no longer monitored for accuracy and their content may no longer be current. If there's a discussion here that interests you and you'd like to find (or create) a more current version, please Visit the Current Forums.

Re-importing Comments Fields after external data cleansing

Options

We are planning to export a large Smartsheet data set to an external database for merging and deduping with a number of other data sets. we then want to re-import the enriched dataset back into Smartsheet.

 

The challenge is that the curent Smartsheet has a large number of Comments that we don't want to lose. We can easily create a match key in the (2-tab) export file to match rows on the main tab with corresponding comments on the Comments tab, before enriching the data.

 

However, is there then a robust process to follow to import the new, enriched file back into Smartsheet, re-associating the Comments with the corresponding rows?

 

Any help very gratefully received - thanks

Comments

  • J. Craig Williams
    J. Craig Williams ✭✭✭✭✭✭
    Options

    Spencer,

     

    Off the top of my head, I see two possiblities that I would investigate.

    1. In your workflow, do not import the enriched data, but rather update the existing rows in Smartsheet. This could be a clean (all column data removed but the the rows (and thus the comments/attachments and history remain).

    You'd need to capture the row ID on the way out and use that on the way in.

    A third party tool like Zapier (www.zapier.com) that can update rows might be involvecd in the process.

     

    2. Use the API.

    Just like (1), you'd need to capture the row ID but using the Update Row(s) operation might be able to handle this.

     

    Again, off the top of my head, but that's where I would start.

     

    Craig

  • Spencer Marlow
    edited 03/06/17
    Options

    Thanks Craig, really appreciate the feedback ... we will being looking into it over the next couple of days.

This discussion has been closed.