...
- Always use the New Form UI.
- Be optically similar. Max size 1000 px or corresponding gridline size as in the style guide.
- Do not capture Snap borders when showing configurations in the Examples section. You can add a border in the editor here.
- See Image Style Guidefor details.
...
...
| title | General Guidelines. Remove Before Publishing. |
|---|
In this article
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Use this Snap to
...
update calendar event.
...
Prerequisites
...
- Valid
...
- Exchange Online tenant and associated site.
- Valid Azure application with all the required API permissions.
Support for Ultra Pipelines
...
- Works in Ultra Pipelines.
...
See Snap Support for Ultra Pipelines.
...
Limitations
None.
Known Issues
None.
Snap Input and Output
Input/Output | Type of View | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
| Input | Document |
...
Binary or Document
|
|
...
|
...
| Requires the |
...
| Existing Event ID to identify the event. | |
| Output | Document |
Binary
...
. |
|
...
- ..
- ..
| Confirmation on updating the event with required modification.. |
Snap Settings
...
| title | Documenting Fields Based On Data Type/UI Element |
|---|
**Delete Before Publishing**
Choose from the following sentences to document specific field types.
...
Parameter Name | Data Type | Description | Default Value | Example |
|---|---|---|---|---|
| Label | String | Required. 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. | Update Event | Update Event |
| User/Shared MailBox | String | Enter the mailbox from which you want to update the event. If not provided, then the mailbox associated to the account. | N/A | john.doe@microsoft.com |
| Existing Event ID | String | Enter the ID of the existing event to be updated. | N/A | AAMkAGYxODZiNjM5LTcxMzItNGE1Yy1hNjZkLTM0NjY5ZjIzZTJiMgBGA |
| Title | String | Specify a title for the event that you are updating. | N/A | Team Meet |
| Attendees | String | Specify attendees to send an invite for the event. | N/A | steven.smith@microsoft.com |
| Start Time | String | Enter the start time of the event. | N/A | 2020-09-29T04:18:00.000 |
| End Time | String | Enter the end time of the event. | N/A | 2020-09-30T03:19:00.000 |
| Repeat Interval | Drop-down List | Specify the repeat interval after which a recurring event will be automatically created. The option as are as follows:
| NONE | WEEKLY |
| Location | String | Enter the location of the event. | N/A | Meeting Room |
| Event Description | String | Enter a detailed description briefing about the event. | N/A | Modifying to suit the schedule |
| Number Of Retries | Numeric | 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. | 0 | 4 |
| Retry Intervals (seconds) | Numeric | Specifies the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. | 1 | 21 |
| Snap Execution | Drop-down List | Specifies the execution type:
|
...
|
...
Examples
Excluding Fields from the Input Data Stream
We can exclude the unrequired fields from the input data stream by omitting them in the Input schema field set. This example demonstrates how we can use the <Snap Name> to achieve this result:
<screenshot of Pipeline/Snap and description>
|
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.
...
Field Sets
Specify advanced parameters that you want to include in the request.
This fieldset consists of the following fields:
- Field 1
- Field 2
- Field 3
Troubleshooting
...
Batch execution failed
...
The Pipeline ended before the batch could complete execution due to a connection error.
Verify that the Batch size field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.
| Execute only | Disabled |
Troubleshooting
Error | Reason | Resolution |
|---|---|---|
| Event ID is required field | Event ID field is null or empty | Ensure to provide the right Event ID to identify the event you want to modify. |
Examples
TBD.
Download this Pipeline.
Downloads
...
| Attachments | ||
|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...
See Also
...