Specifies whether @odata.bind requests should be sent only for navigation properties.

Data Type

bool

Default Value

true

Remarks

In Microsoft Dataverse, you can link an existing resource to another by including a navigation property with the @odata.bind suffix and a reference to the related resource. This creates a relationship so the records appear in each other’s navigation properties when queried.

By default, driver attempts to detect and bind related resources automatically during INSERT or UPDATE operations by using foreign key values in the table. For example, setting CustomerId on the Orders table could result in the driver sending an [email protected] request to link the order to that customer.

However, in some Microsoft Dataverse implementations, a single foreign key can be associated with multiple navigation properties. In these cases, automatic binding may link records in unintended ways.

When set to true, OnlyBindOnNavigations restricts binding to navigation properties only. Binding must be performed through Linked columns, which are available when IncludeLinkedColumns is set to true. Linked column values can be provided in a #TEMP table, JSON, or XML. Supplying only primary keys references existing records. Omitting primary keys creates new related records.

When set to false, the driver attempts to determine the corresponding navigation property automatically based on foreign key values and sends @odata.bind requests accordingly.

This property is useful if a foreign key maps to multiple navigations and may cause unintended links.