It is possible to link data connections together. This can have the following benefits.
...
These objects also come from the ‘parent’ data connection so cannot be edited or deleted here.
...
If you see such a structure this is the first indication that you are working on a linked data connection or a ‘child’ connection.
If you now look at the connection tab,
...
| Note |
|---|
You have the ability to transform an existing data connection into a child at any point, but it's important to approach this process with caution! |
Now that our data connection is linked , i.e. it is a child, we can add local content to it.
You add tables / objects and joins as you would with any other data connection. The only difference is that you can’t edit any of the content that comes from the parent.
You can add objects to tables that come from the parent though.
...
If anyone creates new content in the parent data connection it will automatically appear in your child data connection.
You can only edit content in the child when you are in the child.
| Note |
|---|
Always make sure you do join your tables back to the content of the main data connection. If the admin in the parent connection creates a user restriction for you, all your queries will fail with a SQL error (this is intended) until you link back to the main structure. |
Exporting / Import A Child Connection
You cannot currently export / import child connections.
Using a Child Data Connection
It makes no difference to the user in the Edit Chart screen, the child data connection is presented to the user, without making them aware of which objects come from the parent and which from the child.
Linked Data Connections + Organisations
If we are giving one of our tenants the ability to create data connections then we probably do not want to.
Share the database connection details with them.
Not allow them to create a child from any of our data connections. We want them only to be able to use specific seed data connections.
Do want to enforce any [[VARIABLE]] replacement in the data connection details.
Enforce database tenancy using user restrictions (or Variables).
Share a set of default content that can be used as a starting position.
The configuration will look a little like this;
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
It is very important that all of the security related details are configured in the top level organisation. |