Virtual Fields

Virtual fields are added by the adapter to simplify data loading and direct processing activity. Virtual fields are shown as fields in the Workbench, even though the fields may not actually exist as fields in that object according to the Microsoft Dynamics 365 API.

A virtual field always begins with the characters vf, for "virtual field". For example, a virtual contact field might be named vfPrimary.

When you set a virtual field to a value, you inform the adapter to call different methods in the Microsoft Dynamics 365 API. Processing occurs for the record after the insert, update, or upsert. If the insert, update, or upsert fails, the virtual field processing is not attempted.

In an update operation, if there are data links only to virtual fields, and no other fields, only the virtual field processing takes place for that step, the update does not actually process. If the update includes data links to non-virtual fields, and the update succeeds but processing the virtual field fails, the update is preserved. If the operation is an insert, and if processing the virtual field fails, a compensating delete is performed to roll back the insert.

Note:  
  • Virtual fields cannot be used as lookup links.
  • Any account or customer that is set to inactive or closed cannot be updated.

See also

Field Properties

Dynamics 365 As A Target

Upsert

Getting Acquainted