I'm having a issue while designing the form that presents the Recipient data.
In the Database I've satellite tables that might or not be populated if this recipient has that kind of characteristics, our recipient form is use only as a way to see information about a recipient and I'm designing it around that concept, by hinding the contexts that this recipient does not include, for example he might or not be part of the loyalty program and will only have an entry in the loyalty table if he does belong to it.
I can hide the data via the use of containers but ACC tries to load it non the less and throws out an error saying that such data does not exist (it is not suppose to).
So my question is how to prevent ACC from loading data about a recipient that it does not have and is not supposed to?
The error displayed may depends on the schema source definition for your satellite tables, dblink, if you used reverse link or not, etc.
Please describe how you manage the relationship depending on the cardinality 0:n or 0:1 or n:n, with reverse link or not (reverseCardinality, etc) ?
Please in case of elements of type link, most of time used for lookup tables (referential tables) values to display in the main form (here recipient), may you also share the <join xpath-dst="@DSTKEY_ID" xpath-src="@SRCKEY_ID"/> in the element of type="link" of the schema customized cus:recipient (or whatever the prefix)?
But it seems that it is not your issue in your case.
Moreover, most of times, it is highly recommended to insert a record with ID = 0 value in each satellite table, because Adobe Campaign simulates external join to avoid performance issues. I don't find easily where it is written in the online documentation, but I am sure this is documented.