Delete Record (Microsoft Dataverse) activity

An activity that deletes a record from a Microsoft Dataverse entity.


Delete Record activity

Configure the Delete Record activity

To configure the Delete Record activity, do the procedure in this topic.

Examples

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the Microsoft Dataverse tab.

    Open Common Data Service tab
  3. On the Microsoft Dataverse tab, drag the Delete Record activity onto your process.

    Drag Update Record activity

General Configuration

Specifies the basic settings for the Delete Record activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

  • Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field NameDefinition

Display Name

Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
No
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Delete Record Configuration

Specifies the information to delete a record from a Microsoft Dataverse entity.

Figure: Delete Record Configuration screen

Delete Record Configuration screen

Fields

Field NameDefinition

Microsoft Dataverse

Function:
Specifies the access token that connects to your Microsoft Dataverse.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Example:
Refer to:

Create Add Token icon

Opens this Screen:
Access Token for Microsoft Dataverse
Function of this Screen:
Configure an access token to connect to Microsoft Dataverse.
Example:
Refer to:

Entity

Function:
Specifies the name of an entity from which to delete a record.
Accepted Values:
An entity name from the list.

When you select the access token from the Microsoft Dataverse field, this field shows the entity names associated with the access token.

Default Value:
None
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Record ID

Function:
Specifies the ID of the record to delete.

The record ID comes from Microsoft Dataverse.

Accepted Values:
A record ID from Microsoft Dataverse.
Default Value:
None
Accepts Process Data Variables:
Yes
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?