Create and update related records using OData binding syntax and correct Dataverse value representations.
Implementation guide
For lookup assignments in the Web API, use the navigation property with @odata.bind, for example primarycontactid@odata.bind: “/contacts(GUID)”. Confirm the navigation property name from your environment’s metadata; it is not always identical to the lookup column’s logical name. Choice columns are represented by integer option values in requests. For multi-select choices, send the supported collection representation. Use $expand only when related data is needed and avoid retrieving entire related entities by default. Validate relationship behavior, required lookups, and cascade rules in a test environment before deploying integration code.
Developer checklist
- Confirm the message, table, execution stage, and security context.
- Use supported SDK or Web API contracts and verify metadata names.
- Handle errors explicitly and avoid unsafe retry behavior.
- Trace useful diagnostics without logging secrets or sensitive data.
- Test with least-privilege users in a non-production environment.
