Interface MJEntityRelationshipEntity_ICloneFieldRules

Columns that must be cleared together (all-or-nothing CHECK pairs). Each group is cleared as a unit when any member is reset.

Explicit copy allow-list, used with Strict.

Never copied; take the column default. Beyond the always-excluded set (PK, _mj*, identity, computed, virtual, denied-create).

JSON columns that embed record IDs, one entry per column.

Set to the cloning user's ID.

The user must supply a value; un-suffixable uniques such as Email. Missing → plan Blocked.

Literal stamps applied after the copy. Values pass through BaseEntity.Set and validation.

Rich rewrites. Evaluated per row with the source row as fields, plus clone context (user, now, root, keyMap) — see §7.5.

Server-minted values (numbers, slugs): blanked so the entity's Save hook allocates.

Drift guard (§13.3): every field must appear in Copy, Exclude, Reset, Ownership, PromptFor, ServerAllocated or JsonRemap, or validation fails. Default false.

Unique keys the metadata cannot see: composite and filtered indexes. See §7.3.