The form's object model

A form that maps fields onto more than one object has an object model: which object it is mostly about, and, where the schema offers more than one way to join two of them, which lookup to use. Both live in Settings, under Object model, and the section only appears when there is something to ask.

Primary object

Left on Derived, Sliick picks the object your form maps most often, with ties going to the field that appears first, and that is almost always right, so existing forms need nothing re-entered.

Override it when the automatic choice picks the wrong one: the primary object scopes the mapping picker’s default and decides which of your mapped objects count as unrelated in the pre-publish review.

The list offers only objects the form actually maps. An object you chose earlier and have since stopped mapping stays on the list marked (no longer mapped, ignored), so you can see it and clear it rather than leaving a stored value behind a blank control.

Record link choices

When one mapped object has two or more lookups pointing at another, an Order with both a bill-to and a ship-to Contact, for instance, Sliick cannot guess which one should join the records your form creates, and guessing wrong is silent: the records save, just unrelated to each other.

So you are asked, one row per pair, to pick the lookup that should join them, or Don’t link these records if they genuinely should stand alone. Both are real answers. A pair left unanswered shows Not chosen, and publishing is blocked until you pick one, though you can still save the rest of your settings.

Two pairs are never listed, and neither is a fault:

• A pair whose lookup you mapped onto a form field yourself. The respondent’s own answer goes into that field and it is honoured over any recorded choice, so there is nothing to ask.
• A stored choice naming a field that no longer exists, or one your permission set cannot see, shows as (not available, choose again) and blocks publishing until you re-answer it.

Note: you do not have to open Settings to answer this. The moment a mapping creates an ambiguity, the same question appears in the inspector underneath that field’s mapping picker, and answering it there saves immediately. Settings is where you go to change an answer later.

If a control here is greyed out, your permission set has read access to the field behind it but not edit access. The hint under the control names the exact field to ask your Salesforce administrator for. Everything else in Form settings still saves normally: the locked control is withheld rather than silently discarded.