Using The Adapter Objects

The Adapter for Microsoft Dynamics 365 and CRM provides a set of adapter objects that can be used to perform the following types of operations on selected Dynamics 365 data:

Any account or customer that is set to inactive or closed cannot be updated.

About Adapter Objects

Using Association Objects

Setting Object Ownership

All Dynamics 365 objects that can be owned by a user have a field named ownerid. This field returns the ID of the current owner on queries and seeks.

Ownerid can be set on insert to specify the owner of the new object, and on updates to change the owner.

Ownership assignments have a cascade effect: When setting the ownerid, assign a user as the owner of the record and of all related records. The original owner loses ownership of the record and related records but is granted full access to the records. The assigned owner must have a valid license and role.

User Mapping

You may find it necessary to create a mapping between User IDs in some external system and Dynamics 365 User IDs. These mappings are maintained in the SCRIBEINTERNALVALUEMAP table.

The file ..\Scribe\Samples\MicrosoftDynamicsCRM\UserMap.dts is provided with the adapter. This DTS file populates the VALUEMAP table with a default mapping between the full name of Dynamics 365 users and their IDs.

You can modify UserMap.dts to generate other mappings. The DTS file can be scheduled to run periodically and update the map based on any changes in Dynamics 365.

Use the VALUEMAPLOOKUPB function to convert external users to Dynamics 365 user IDs.

Default Fields

Default fields appear in italics in the Workbench Target pane.

The default fields are:

Available Adapter Objects

Some adapter objects are only available on the Adapter for Dynamics 365 and CRM:

See also

Dynamics 365 As A Target

Granting Access

Key Values

Upsert