Get Record (Microsoft Dataverse) activity

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


Get Record activity

Configure the Get Record activity

To configure the Get 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 the Process Builder, in the Activity Library, open the Microsoft Dataverse tab.

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

    Drag Get Record activity

General Configuration

Specifies the basic settings for the Get 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 Name Definition

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

Get Record Configuration

Specifies the information about the record to retrieve from a Microsoft Dataverse entity.

Figure: Get Record Configuration screen

Get Record Configuration screen

Fields

Field Name Definition

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 retrieve 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 retrieve the information.

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?

Store Response in This Variable / Map Response to Application Schema

Function:
Specifies where to store the response from Microsoft Dataverse.
Accepted Values:
  • Store Response in This VariableSelect this option if you expect Commom Data Service to return only one data item.

    In the text field, specify a variable to store the data Commom Data Service returns.

  • Map Response to Application SchemaSelect this option if you expect Commom Data Service to return more than one data item.

    Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper.

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

Default Value:
Map Response to Application Schema
Accepts Process Data Variables:
  • If you select Store Response in This Variable, you must enter a variable.
  • If you select Map Response to Application Schema, this does not apply.
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?