In this article

Overview

Provide an overview of the account type.

Use this account type to connect MS Dynamics 365 for Sales Snap Pack with data sources that use Dynamics 365 OAuth2 for Online Account.

You can configure an MS Dynamics 365 for Sales account in SnapLogic from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to either create a new account or use an existing account. These accounts can be created in or used from:

Your private project folder: This folder contains the pipelines that will use the account.
Your project space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.

The steps required to create an account in any of these cases remain the same.

As of now, this Snap pack supports only OAUTH2 accounts for Dynamics 365 Sales online.

Prerequisites

Provide all prerequisites for configuring the account type or use 'None.' if there are no prerequisites.

Valid client ID.
Valid tenant URL.
...
...

Limitations

None.

Known Issues

None

Account Settings

Include a screenshot of the fully configured account. Do this for each account type. If the account type has fields that are auto-populated when you validate/authorize it, mention so before the screenshot. For example: To create your REST OAuth2 account in SnapLogic, you must provide at least your Client ID, Client secret, OAuth2 endpoint, and OAuth2 token and click Authorize. SnapLogic sends your account details to the OAuth2 endpoint specified and populates the Access token, Refresh token, and Access token expiration fields using the details received from that endpoint.

**Delete Before Publishing**

Choose from the following sentences to document specific field types.

Drop-down lists/Option Buttons (radio buttons):

You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list.

<State what the field contains>. Available options are: <bullet list of LoVs>
The Salesforce API to be used. Available options are:...
Select the <category> that you want to use. Available options are...
* Option 1<italicized>: <third person singular form of the verb>
* Option 2<italicized>: <third person singular form of the verb>
Select the API that you want to use. Available options are:
Bulk API: Sends the Snap execution request details as a bulk API call.
REST API: ...
Indicates.... Available options are:
Indicates how the Snap must be executed. Available options are:
* Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.
* Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.
* Disabled: Disables the Snap and, by extension, its downstream Snaps.

Check boxes:

If selected, <Snap behavior>.
If selected, an empty file is written when the incoming document has no data.
If selected, <behavior>. If not selected/Otherwise, <behavior>
Use "If not selected" if the first sentence is long.
If selected, the Snap uses the file path value as is. Otherwise, the Snap uses the file path value in the URL.
If selected, an empty file is written when the incoming document has empty data. If there is no incoming document at the input view of the Snap, no file is written regardless of the value of the property.

Select to <action>
Use this if the behavior is binary. Either this or that, where the converse behavior is apparent/obvious.
Select to execute the Pipeline during validation.

Text Fields

Describe what the field represents/contains. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc.
The name of the account.
The account ID that you want to use to log in to the endpoint.
Required if IAM Role is selected.
Do not use this field if you are using batch processing.

Numeric Text Fields

Describe what the field represents/contains. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc. Include special values that impact the field's behavior as a bullet list.
The number of records in a batch.
The number of seconds for which you want the Snap to wait between retries.
The number of seconds for which the Snap waits between retries.
Use the following special values:
* 0: Disables batching.
* 1: Includes all documents in a single request.

Parameter	Data Type	Description	Default Value	Example
The field's name in the UI. Ensure that it is captured accurately so as not to confuse the user.	The data type of the field. For example, string, numeric, alphanumeric, etc. Check box for check boxes	Any and all information that the user needs to configure the field correctly. This includes a description of the property and the expected entry. If the user needs to look at the endpoint's console to retrieve a certain property's configuration, add that information as well. Include links to official documentation as necessary. If the field has numeric inputs, list out maximum and minimum accepted values, if applicable. Field Prefacing for Mandatory/Conditionally mandatory fields: ---------------------------------------------------------------------------------- If field is mandatory (has a * in the UI), add, "Required" in italics. See Label's description below. If a field becomes mandatory based on the configuration of another field then add, "Required if <field_name> is configured". If a field is applicable based on certain situations then add, "Applicable only to <situation>"; for example, "Applicable only when using SSL with KMS." These conditions must always be in italics and in the beginning of the description. These prefacing conditions must always be in italics and in the beginning of the field's description.	N/A if there is no default value.	Use italics for examples. Show multiple examples to show variations. If N/A then no italics.
Label	String	Required. Unique user-provided label for the account.	N/A

Troubleshooting

Error

Reason

Resolution

Enter the error message that is displayed.

Account validation failed

Briefly describe why this error is triggered. An experienced user will be able to troubleshoot the error looking at the reason itself.

The Pipeline ended before the batch could complete execution due to a connection error.

List the steps that the user must take, if necessary, to rectify this error. If a procedure is extensive, add it as a separate section after this table and reference it with a link in this cell.