Overview

You can use this Snap to delete objects in Microsoft Dynamics 365 for Sales databases.

Settings for Dynamics 365 for Sales Delete Snap

Snap Type

Dynamics 365 for Sales Delete is a Write-type Snap that deletes records from Microsoft Dynamics 365.

Prerequisite

You must have a Dynamics 365 OAuth2 Account Online, data to query, and access to the objects concerned.

Support for Ultra Pipelines

Works in Ultra Pipelines. However, we recommend that you not use this Snap in an Ultra Pipeline. To know the list of Snaps that work in Ultra and the related caveats, see Snap Support for Ultra Pipelines.

Limitations

The following limitations are due to the API limitations from the Microsoft Dynamics 365 for Sales application:

The Snap fails with an error when the number of requests exceeds 6000 within 300 seconds. We recommend that you limit the number of requests you make within 300 seconds (5 minutes). You can gradually increase the requests that reduce the retry-after duration, optimize your throughput, and minimize resource spikes on the server.
The Snap fails with an error when the combined execution time of incoming requests exceeds the limit of 1,200,000 milliseconds within the window of 300 seconds. We recommend that you reduce the number of concurrent requests or reduce the duration of requests and try later.
The Snap fails with an error when the number of concurrent requests exceeds the limit of 52. We recommend that you reduce the number of concurrent requests.

Known Issues

When deleting more than one object in batches, the Batch Size ranges from 1 to 1000. This is a limitation set by Microsoft Dynamics 365.
Microsoft Dynamics 365 limits the number of API calls to 60,000 per minute, per user org. This should be considered when configuring the size of any batch process.
The Object Type suggestions are limited to the Object Types available within the Microsoft Dynamics 365 For Sales v8.2 and v9.0. There is no current ability to suggest Custom Object Types.

Snap Views

Type	Format	Number of Views	Examples of Upstream and Downstream Snaps	Description

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input

Document

Min: 0
Max: 1

CSV Parser
Mapper

The name of the object type and ID that must be deleted.

Output

Document

Min: 1
Max: 1

Mapper
Filter

The file name and the deletion status of the file.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

Stop Pipeline Execution: Stops the current Pipeline execution when the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

Asterisk (*): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon (): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon (): Indicates that you can add fields in the field set.
Remove icon (): Indicates that you can remove fields from the field set.

Field Name		Field Type	Description

Field Name		Field Type	Description
Label* Default Value: MS Dynamics 365 for Sales Delete Example: MS Dynamics 365 for Sales Delete		String	Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.
Object Type* Default Value: account Example: account		String/Expression	Specify the Microsoft Dynamics 365 for Sales object type. You can either enter the name of the object type in this field, or you can select it from the drop-down list displayed when you click the Suggest button.
ID* Default Value: N/A Example: 5D5F5B6A-CE6D-EA11-A812-000D3A86D7B6		String/Expression	Specify the GUID of the Microsoft Dynamics 365 for Sales Object. You can either enter the ID in this field, or you can select it from the drop-down list displayed when you click the Suggest button. When processing a Batch of documents, it is required that each document contains the object ID, which varies between objects; for example: accountid, contactid. The GUID from the object ID field in each document will be used to delete that object.
Batch Size Default Value: 200 Example: 100		Integer/Expression	Specify the number of records processed in each request. Batch size range is from 1 to 1000. Batch processing results can contain both successful and unsuccessful results. Successful results will be written to the output view. Unsuccessful results, along with intuitive error information will be written to the error view; therefore, it is recommended to activate the error view within the Snap. A single unsuccessful batch processing document will not halt the batch processing, unless there is a configuration problem; in this special case, the Snap would fail with intuitive error information.
Number of Retries Default Value: 0 Example: 1		Integer	Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response.
Retry Intervals (seconds) Default Value: 1 Example: 5		Integer	Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. When the Snap encounters 429 error, the response includes the `retry-after with <number of seconds>` in the header and the Snap automatically retries after the specified `<number of seconds>`.
HTTP Header	Use this fieldset to add additional HTTP headers to pass when sending requests to the Dynamics 365 for Sales instance. For instance,
	Key Default Value: N/A Example: Prefer	String/Expression	Specify an HTTP header key.
	Value Default Value: N/A Example: odata.include-annotations=""*	String/Expression	Specify an HTTP header value.
Enable continue on error Default Value: Deselected		Checkbox	Select this checkbox to enable the service to continue processing the remaining requests in a batch when an error occurs. The code continues to execute until all requests are processed. It then returns the response to the output view. When this checkbox is deselected, the batch process errors out immediately on the first failed request. It then returns a response in the error view that includes the error message.
Snap Execution Default Value: Execute only Example: Validate & Execute		Dropdown list