Publish/Use templates without copying items

Today was the first time I converted an organization wide system into a template that I could copy into another new Tape system and it worked like a charm. All of the workspaces, apps and related automations were copied over, and none of the webhooks, which I think is the absolute right move.

What I learned after is that it also copied over all of the items, which I think swiftly deleted from the newly installed template because we’re starting fresh. I intend on doing this a couple more times in the near future, so I will now copy this template somewhere while it contains no items, but this shouldn’t have to be the case. I would highly recommend that when someone is choosing to duplicate a template, they can choose whether or not they want the items copied over as well. It seemed like there was no other option but to do it this way.

Hi @andrew.cranston,

thank you so much for the kind words and the great feedback. You’re absolutely right, this would be a really valuable addition when you want to reuse an existing structure as a template without bringing over the existing records :100:

We’ll take a closer look at where and how this can best be implemented. There are basically two possible ways to approach it: either the admin decides this when creating the duplication link, or the user can choose it directly when duplicating the template. We’ll need to look at the pros and cons of both options in a bit more detail, but this is definitely very helpful feedback and something we’ll explore.

Thanks again, Andrew. Really appreciate you sharing this with us!

Cheers,
Leo

3 Likes

This is a really cool idea, Andrew. To your point, Leo, the two different paths that you’re going to take a look at absolutely make sense. It might even make sense to have two settings for the admin:

  1. Choosing to include the items to begin with
  2. Allowing a user to have the option to include or uninclude them from their end

I can see building out a demo and wanting to include the demo data so that somebody can see the way things work when they duplicate it over, but then also giving them the option to exclude it because they’re starting fresh or in a live build.

3 Likes