Set which databases to include in workspace template

Ideas & Features
1

I have a problem. There’s a limit of 1000 entities in workspace template. This is an issue because one of the databases is “Status” and many automations use this database and specific entities from this database. Indeed I don’t need to import all tasks and projects from the template (ideally not actually because things can’t be truly deleted), but there are some databases (and their entities) that need to be in the template for it to work.

Hope this makes sense.

I am aware that another solution is to build it without the data, and keep a copy of it before the client data is added, but what usually happens is that new features are added as time passes, and then would force me to maintain two workspaces.

2

You could temporarily move the databases you want to include in the template to all be in one or two spaces, export only those spaces, and then move the dbs back out into the spaces where you want them to finally live.

3

Hmm interesting. I think the relationships wouldn’t come through then, no?

4

I’m not sure what you mean. If you’re exporting a workspace template (from the workspace map) and you choose several spaces to include, then all databases in those spaces will be included, and all relations between those dbs will be included.
Of course, any relations to databases in spaces that are not included in the export will be ignored.