Delete Action Guides

Difficulty	Advanced
EMS Compatible
iMIS 2017 Compatible
Usage Notes	Use with caution. It is recommended to reach out to CSI before using the Delete action to make sure you are properly trained
Length of Video	n/a
iImport
iUpdate
Actions	Delete

When using the Delete Action, there is no undo button. CSI highly recommends running a test of your job in a test environment or with test records to ensure the job is properly designed to achieve the desired results.

Deleting Contacts

The REST API does not support a way to delete contacts, so it is not possible to use iDMS to delete contacts. You can, however, use the Update Action to Mark Contacts for Erasure using the Contacts source. You can then pair those updates with the iMIS Process Automation Contact erasure task.

Mark Contacts for Erasure

Deleting Activities

The safest way to delete activities is to know the SEQN (Sequence) number of the Activity. This is the ONLY way to guarantee that you are deleting a specific Activity. If you do not have the SEQN Number, it is recommended you match on as many fields as possible. Matching only on ID will result in all of the ID's Activities being deleted.

Activities with an Originating Transaction Number should NOT be deleted, as they are associated with a financial transaction.

View example

Your IQA should be specific, and while it can return any number of fields from Activity, it must contain the Sequence number.

In this example, we created Committee records today that were erroneous, so we need to delete them, so the IQA query is filtered to find all Committee records added since today.

2. Using this IQA, we Match On Sequence Number (SEQN Number) using the Delete Action

Clearing Shopping Carts

When clearing out users' shopping carts, you must map on iMIS ID.

One possible use case is creating an IQA that pulls all carts where the CreatedOn date is greater than 1 month ago, then mapping the iMIS ID to clear those carts.

View example

Deleting Relationships

Removing relationships requires the iMIS ID, Relationship Type, and Target iMIS ID.

View example

Deleting Panel Data

The type of panel can be determined by how many key fields are available to match on - Single Instance and Standalone Panels will have one key field (iMIS ID and Ordinal respectively), while Multiple Instance panels will have two key fields.

Single Instance Panels: Matching the key field (usually iMIS ID) is highly recommended. This will delete the data for that given iMIS ID from the panel.
Multiple Instance Panels: Matching on two key fields (usually iMIS ID and Ordinal) is highly recommended. Matching on only ID will delete ALL information for that ID within the panel. Matching on both the ID and Ordinal will only delete the row of data where there is a match to both. If you want to delete only part of the data from the Ordinal and not the whole Ordinal, you must use an Update action instead.
Standalone Panels: Matching on the key field (usually Ordinal) is highly recommended.

View example

Single Instance

First match on ID, the only key

field

Because there is only one key

field, it is okay to match on only that one field. You can, however, match on the additional fields listed.

Multiple Instance

Note how both key

fields are matched.

Standalone

Because there is only one key

field, it is okay to match on only that one field. You can, however, match on the additional fields listed.

Deleting Communication Logs

Removing a Communication Log requires the Recipient iMIS ID AND the Subject. If there are multiple line items in the Communication Logs with the same ID and Subject, more logs than intended may be deleted. EMS only.

View example

Deleting Group Members

Removing a group member from a group requires the Group Name and the iMIS ID of the member to be removed. Additionally, Role, Is Active, and Join Date, are optional fields that may be matched on.

View example