問題文
An insurer loaded 1.2 million child asset rows after loading their parent policy rows. The load reported no errors, yet the lookup to the policy is empty on every child row. The file's parent column holds the legacy policy number, and the policy object has that number in an external ID field. What most likely happened?
選択肢
- The parents must be loaded after the children so that the platform can attach them, so the order of the two loads has to be reversed.
- Lookup fields are populated by the nightly sharing recalculation, so the values will appear after the next overnight run.
- The parent column was loaded into an ordinary text field instead of being used to resolve the relationship through the parent's external ID, so nothing ever populated the lookup and the rows saved successfully without a parent.
- The children were loaded with record identifiers copied from the source sandbox, and because record identifiers are not portable between orgs the platform silently cleared the relationship as each row was saved, which is why the load reported success on all 1.2 million rows.