Open topic with navigation
There are a number of additional adapter settings that you can change or adjust to more closely reflect your application's unique needs.
To Open The Settings Dialog Box
This setting only affects fields that are not validated by Dynamics 365. You cannot turn off Dynamics 365 field validation.
Most picklist fields are not automatically validated by the Dynamics 365 server. This means you can import values into picklists that are not yet defined in Dynamics 365. Some Dynamics 365 picklist fields validated by the application are statecode, statuscode, and objecttypecode or objecttypeid.
To view the picklist items for a target field, open the target field's properties. When this option is selected, specifying the sum of two grant rights picklist values causes an error. For more information about granting rights, see .Granting Access.
To use bulk processing features, the Use Bulk mode check box must be selected on the Operation tab of the Configure Steps dialog box in the Workbench. For more information, see the Bulk Operations and Operations Tab topics in the TIBCO Scribe® Insight Help.
When this option is selected:
For example, if your source data store is set to a batch size of 1000 records, Insight opens five threads that process 200 records each:
Clear this option for Insight to use a pre-seek operation to determine the records to update or delete before actually performing the Update or Delete operation. If no primary or alternate key exists, Insight performs the pre-seek operation.
When this option is selected, if TIBCO Scribe® Insight determines that an update operation may not complete successfully without a pre-seek operation, TIBCO Scribe® Insight performs a pre-seek operation before performing the update.
When this option is selected, target variables on unlinked fields cannot return data.
Alternate keys are only available with Dynamics CRM 7.1 and later.
This feature applies to Adapter for Dynamics CRM 4.x only.
Note: For the Adapter for Dynamics 365 and CRM, this information is contained in the trace file.
Each request/response is logged to a separate file, with a prefix based on the date and time followed by the name of the Dynamics 365 request. For inserts, updates, and deletes, the date and time prefix is followed by the name of the object. These files are written to the Log folder that you specify. When XML logging is started, the trace file provides the path to each file at the point in the trace where the request/response occurs.
Note: This setting can have significant impact on performance and disk space usage. TIBCO recommends enabling logging only when troubleshooting the DTS.
For example, as the login user, you might have administrator credentials. If you set the Run As user to be a salesperson and run a contact import, all the contacts appear to have been entered by the salesperson.
To impersonate a user through the Run As user feature, the login user must belong to the Active Directory PrivUserGroup under the organization where Dynamics 365 is installed. Otherwise, the following message appears when a job is run:
Not enough privilege to access
the Microsoft CRM object or perform the requested operation.
To specify a Run As user, select the Run As User checkbox, then click the button and select a user.
Connecting To The Adapter