Duplicating a database

Is there a way to duplicate a database? I created a database and want to create another one (different data) but don’t want to create it from scratch.

1 Like

Duplicate the space containing the db (i.e. share as template, rename original, import shared template) and then delete any databases in the space you don’t need :slightly_smiling_face:

1 Like

I get this error. In the case below I’m trying to create another “bug” database named something else. Currently, nothing is named “bug”. I’m assuming this is the initial name of the database?

Cannot rename database

‘Development/Priority_Software Development/bug’ database cannot be renamed to ‘Development2/Priority_Software Development/bug’ database because ‘Development2/Priority_Software Development/bug’ database already exists.

Yeah, seems like there is some sort of internal/initial name in the database. Even when renamed it keeps the initial name.

‘Development/Priority_Development/Database 1’ database cannot be renamed to ‘Development2/Priority_Development/Database 1’ database because ‘Development2/Priority_Development/Database 1’ database already exists.

What were you doing exactly when you got this message?

Here is an example.

  1. Install Software Development Template
  2. Rename space to “Software Development Template 1”
  3. Rename “Bug” database to “Bug1”
  4. Install Software Development Template
  5. Move “Bug” database to space “Software Development Template 1”

Cannot rename database
‘Software Development/Priority_Software Development/bug’ database cannot be renamed to ‘Software Development 1/Priority_Software Development/bug’ database because ‘Software Development 1/Priority_Software Development/bug’ database already exists.

I’ve been trying to use templates as a workaround to “duplicate” databases as well: however the internal name/id prevents this from being done. as a safeguard it makes sense however I’m now stuck without a simple way to create “subtasks” for my existing and numerous projects and tasks… unless I rebuild all formulas and fields from “tasks” to a fresh/new “subtasks” db manually. :frowning:

Cannot rename database

‘PROJEKTE PROJECTX DB-DUPLICATOR/Typ_PROJEKTE PROJECTX/Task’ database cannot be renamed to ‘PROJEKTE PROJECTX/Typ_PROJEKTE PROJECTX/Task’ database because ‘PROJEKTE PROJECTX/Typ_PROJEKTE PROJECTX/Task’ database already exists.

the issue occurs when trying to “move” the duplicated template/DB BACK to the original, intended target-workspace… even after renaming the duplicated-workspace-db… even after removing all relationships except for “USER”.

obviously just “duplicating” a db for the sake of duplicating or using it exclusively in another, separate workspace is not much use.

It sounds like you might be wise to use a self-relation for the Task database, rather than creating another database with (almost) the same characteristics.

our current workaround is to use adjusted views/smartfolders from project-tasks and a duplicated/templated and hidden workspace, i.e. it’s needed db for the subtasks.

adding new subtasks has to be circumvented in a separate table view, as nested levels view in a list (task ► subtasks) only allows addition of top-level objects, i.e. tasks, but not subtasks. it’s workable so far and can quickly be nested down further levels if need be imo, but not yet tested for subtasks lvl2, lvl3 etc. as we really don’t need this depth.

I have not used self-relations at all yet: how would one go about handling “tasks → subtaskslvl1 → subtaskslvl2” when using self-relations. can they be nested at all? what would naming/handling and accessing nested subtasks roughly look like? self-relation can therefore be “one to many” too?

not sure if this is the way you suggest but I tried duplicating another template/workspace to test your suggestion: I created a one to many relation from “tasks” or “subtasks” to itself: however this kind of reference cannot be used in list level/nested views etc. unless I am doing things wrong here. currently list/nested and probably most/all views cannot be referenced to relations directed to “self”…

so it seems quite a bit more limited for tasks->subtasks than the workaround we are currently using:

image

so far it works quite nicely to edit data in “both” directions. as well as autopopulation/updating of existing assignees from tasks. or notification/differentiation on change/update of data for subtasks discernably as well.

How to import shared template ? Only thing I found is “Add custom app” under “Select source to import data”, but when using a share as template link it just says “Version is required”


Assuming you have the URL of a Fibery space template, you just paste it into your browser address bar and then you get to choose the workspace you wish to import it into.