Update Event

Owned by Kalpana Malladi
Last updated: May 07, 2024 by Gouri Bhagchandani
5 min read

In this article

Overview

You can use this Snap to update a calendar event.

Snap Type

Update Event is a Write-type Snap that updates calendar event fields.

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. 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 & Known Issues

None.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document



  • Min: 0

  • Max: 1

  • Mapper Snap

Requires the Existing Event ID to identify the event.

Output

Document

.

  • Min: 0

  • Max: 1

  • Union Snap

Confirmation on updating the event with required modification..

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.

Parameter Name

Data Type

Description

Parameter Name

Data Type

Description

Label*

 

Default Value: Update Event 
Example: Update Event 

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.

User/Shared MailBox

 

Default Value: N/A
Example: john.doe@microsoft.com

 

String/Expression

Specify the mailbox/account for which to create the event from which you want to create the event. If not provided, then the mailbox associated to the account is used.

Calendar Name

 

Default Value: N/A
Example: Calendar

 

String/Expression

Specify the name of a calendar.

Existing Event ID

 

Default Value: N/A
Example: AAMkAGYxODZiNjM5LTcxMzItNGE1Yy1hNjZkLTM0NjY5ZjIzZTJiMgBGA

String/Expression

Specify the ID of the existing event to be updated.

Title

 

Default Value: N/A
Example: Team Meet

String/Expression

Specify a title for the event that you are updating.

Attendees

 

Default Value: N/A
Example: steven.smith@microsoft.com

String/Expression

Specify the attendees to send an invite for the event.

Start Time

 

Default Value: N/A
Example: 2020-09-29T04:18:00.000

Integer/Expression

Specify the start time of the event.

You can also specify time zone using 2020-09-29T04:18:00.000+0530 and if UTC time zone the using 2020-09-29T04:18:00.000+0000.



End Time

 

Default Value: N/A
Example: 2020-09-30T03:19:00.000

Integer/Expression

Specify the end time of the event.

You can specify also time zone using 2020-09-29T04:18:00.000+0530 and if UTC time zone the using 2020-09-29T04:18:00.000+0000.



Repeat Interval

 

Default Value: NONE
Example: WEEKLY

Dropdown List

Specify the repeat interval after which a recurring event will be automatically created. The option as are as follows:

  • NONE

  • DAILY

  • WEEKLY

  • MONTHLY

  • YEARLY

Location

 

Default Value: N/A
Example: Meeting Room

String/Expression

Specify the location of the event.

Event Description

 

Default Value: N/A
Example: Modifying to suit the schedule

String/Expression

Specify a detailed description briefing about the event.

Number Of Retries

 

Default Value: 0
Example: 4

Integer/Expression

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: 21

Integer/Expression

Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception.

Snap Execution

 

Default Value: Execute only
Example: Validate & Execute

Dropdown list

Select one of the three following modes in which the Snap executes:

  • Validate & Execute. Performs limited execution of the Snap and generates a data preview during Pipeline validation, then performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only. Performs full execution of the Snap during Pipeline execution without generating preview data.

  • Disabled. Disables the Snap and all Snaps downstream from it.

Troubleshooting

Error

Reason

Resolution

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 to modify.

Examples

Event Management

We are using an example of event-based management, where we have a chain of event Snaps in this Pipeline, designated to perform specific tasks pertaining to their functionalities.

In this example, our Pipeline activities are as follows:

  1. Creating an event with required input using the Create Event Snap.

  2. Mapping the event’s information using Mapper Snap.

  3. Updating an event using Update Event Snap.

  4. Listing the events in the calendar using List Events Snap.

  5. Mapping the event’s information using Mapper Snap.

  6. Deleting an existing event from the calendar using Delete Event Snap.

Here, let us look into the role of the Create Event Snap in this Pipeline.

We create an event in the calendar with all the required inputs. Let us provide input in the Snap Settings and look at the output.

Create Event Snap

Output

Create Event Snap

Output

Upon execution, we see an output confirming the creation of an event with the given input.

We use Mapper Snap to map the newly created event’s details with the details of another event to update.

Mapper Snap 

Mapper Snap 

Next, we configure the Update Event Snap to use the inputs from the Mapper Snap as shown below:

Update Event

Output

Update Event

Output

 

Upon execution, we see an output with the update reflecting.

We retrieve the list of events from the calendar associated with an individual's mailbox. Let us provide input in the Snap Settings and look at the output.

List Events

Output

List Events

Output

 

Upon execution, we see a list of events and details related to the events shown in the output.

We use the Mapper Snap to map the event’s ID received from the List Events Snap with the Existing Event ID field’s value in the Delete Event Snap.

Mapper Snap

Mapper Snap

We then add the Delete Event Snap and configure it to delete the specified event as shown below:

Delete Snap

Output

Delete Snap

Output

 

 

Upon execution, we see an output with the update reflecting saying the event with a specific ID is deleted.

Download this Pipeline. 

Downloads

  File Modified

File Exchange Online_All Event snaps(Create,Update,List Events and Delete).slp

Nov 15, 2020 by Siddharth Menon (Unlicensed)

Snap Pack History

See Also

Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.