Skip to main content
Solved

Duplicate a whole G-Sheet Workbook with Pigment Connectors

  • Oct 21, 2026 3:19 PM UTC
  • 2 replies
  • 25 views

Forum|alt.badge.img+1

When I duplicate a G-sheet Workbook with Pigment connectors, the duplicated workbook loses all of its Pigment connectors and I need to re-establish them. Is there a way to preserve them? It gets frustrating when I’m creating a dozen templates with a dozens of connectors in each template.

Best answer by Jack

Hi ​@Justin.Alpert,

 

Currently, the connector is not built to preserve its configurations when you duplicate the whole workbook. Preservation only happens when you create a copy of the connection configuration on a different sheet in the same spreadsheet. 

 

With that said, this is something we have heard would be valuable so as to save you re-creating the connection details. Hopefully, we see this in a future iteration of the product though I'd recommend upvoting the feature request our team are tracking here: https://community.pigment.com/ideas/keep-pigment-connection-with-gsheet-when-making-a-copy-3293

View original

2 replies

Forum|alt.badge.img
  • Employee
  • Answer
  • Oct 26, 2026 3:25 PM UTC

Hi ​@Justin.Alpert,

 

Currently, the connector is not built to preserve its configurations when you duplicate the whole workbook. Preservation only happens when you create a copy of the connection configuration on a different sheet in the same spreadsheet. 

 

With that said, this is something we have heard would be valuable so as to save you re-creating the connection details. Hopefully, we see this in a future iteration of the product though I'd recommend upvoting the feature request our team are tracking here: https://community.pigment.com/ideas/keep-pigment-connection-with-gsheet-when-making-a-copy-3293


Adding a workaround on top of Jack’s answer, since I’ve been through the “dozens of templates” pain too. Instead of putting connectors inside every template, keep one master workbook that holds all the Pigment connections, one tab per export. Then have each template pull from the master with IMPORTRANGE (or QUERY on an IMPORTRANGE if you need filtering). Duplicating a template then costs you nothing because the template has no connectors to lose, and refreshing data is a single place to maintain. The trade-off is one more hop and you need to grant IMPORTRANGE access once per new template, but that’s a one-click prompt rather than rebuilding connections.