Create Record (Microsoft Dataverse) activity

An activity that creates a record in a Microsoft Dataverse entity.


Create Record activity

Configure the Create Record activity

To configure the Create 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 Create Record activity onto your process.

    Drag Delete Record activity

General Configuration

Specifies the basic settings for the Create 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

Description:
Specifies the activity name that shows in your process.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Accepts 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

Description:
Specifies an optional text description for your activity.
Allowed Values:
More than one line of text.
Default Value:
None
Accepts Variables:
No

Create Record Configuration

Specifies the information to create a record in a Microsoft Dataverse entity.

Figure: Create Record Configuration screen

Create Record Configuration screen

Fields

Field NameDefinition

Microsoft Dataverse

Description:
Specifies the access token that connects to your Microsoft Dataverse.
Allowed 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

Description:
Specifies the name of an entity for which to create a record.
Allowed 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?

Request Mapping

Description:
Connects the Microsoft Dataverse request data to your process schema.
Allowed Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

Use this screen to connect the request to the data model for your process.

Default Value:
None
Example:
Refer to:

Store Record ID in This Variable

Description:
Specifies the process data variable to store the ID of the record.

The record ID comes from Microsoft Dataverse.

Allowed Values:
A process data variable that accepts an alphanumeric string with no spaces or special characters.
Default Value:
None
Accepts 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?