How does GoodData handle connection points (ADDv2,

cp__

fields) where a given value of the connection point can be unique within a given

x__client_id

but non-unique across multiple

x__client_id

? I'm asking because each of my tenants have primary keys which are autoincrement ints, and currently I am proceeding to go around this by casting the ints to string and prefixing them with the

x__client_id

value

Hi Philippe, Your output stage table must contain a _`x__client_id`_ column and its unique primary key. Subsequenlty, every table that you are loading will have to include them as well to only get the data associated with specific client. May I know how does your LDM and table look like if possible? You can find more info and an example on this page: https://help.gooddata.com/doc/enterprise/en/data-integration/data-preparation-and-dis[…]-data-distribution-reference/use-automated-data-distribution

I'm not sure we understood each other correctly - I meant that for each of my tenants, a given value of

cp__sometable

is unique, but that across multiple tenant said within-tenant-scope-unique value is no longer unique. Example:

| x__client_id | cp__sometable |
|.        acme |             1 |
|.        acme |             2 |
|.        acme |             3 |
|.        zulu |             1 |
|.        zulu |             2 |
|.        zulu |             3 |

1 is unique within

x__client_id

= acme, and zulu respectively, but not across both. Same goes for the other values of

cp__sometable

. Is this something that is supported, or do I need to scope the values of

cp__sometable

as follows:

| x__client_id | cp__sometable |
|.        acme |        acme.1 |
|.        acme |        acme.2 |
|.        acme |        acme.3 |
|.        zulu |        zulu.1 |
|.        zulu |        zulu.2 |
|.        zulu |        zulu.3 |

This os OK Philippe. If your cp__ values are unique within each x__client_id but not unique globally, you have nothink to worry about. The deduplication/key enforcement is happening at the moment of upload to the workspace and that is defined by x__client_id so this will work.

Nice that simplifies things 🙂