Create Multiple Records (MS Dynamics 365) activity

An activity that creates more than one record in Microsoft Dynamics 365. You can work with standard entities or custom entities in Dynamics 365.


Create Multiple Records activity

Configure the Create Multiple Records activity

To configure the Create Multiple Records activity, do the procedure in this topic.

Examples

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 MS Dynamics 365 tab.

    Open MS Dynamics 365 tab
  3. On the MS Dynamics 365 tab, drag the Create Multiple Records activity onto your process.

    Drag Create Multiple Records activity

General Configuration

Specifies the basic settings for the Create Multiple Records activity.

Figure: General Configuration screen

General Configuration screen

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

Connection Timeout (Seconds)
Function:
Specifies the number of seconds permitted to complete an action before the connection stops.
Accepted Values:
An integer, representing a number of seconds.
Default Value:
600
Accepts Process Data Variables:
No

Create Multiple Records Configuration

Maps request data from Microsoft Dynamics 365 to your process when you create more than one record. You can work with standard entities or custom entities of Dynamics 365.

Figure: Create Multiple Records Configuration screen

Create Multiple Records Configuration screen

Fields

Field NameDefinition

MS Dynamics 365
Function:
Specifies the access token that connects to your Microsoft Dynamics 365 application.
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 Dynamics 365
Function of this Screen:
Configure an access token to connect to Microsoft Dynamics 365.
Example:
Refer to:

Entity Name
Function:
Specifies the name for your entity.
Accepted Values:
One line of text that can have spaces.
Default Value:
None

When you select the Microsoft Dynamics 365 access token, the name of the entity shows in the Entity Name field.

Accepts Process Data Variables:
No

Request Mapping
Function:
Connects the Microsoft Dynamics 365 API request parameter to your process schema. This is mandatory only if the request passes data from the process schema to parameters in the Dynamics 365 API.
To Open this Field:
  1. On the Create Multiple Entity Configuration screen, click the Request tab.
Accepted Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper.

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

Default Value:
None
Example:
Refer to:

Map Response to Application Schema
Function:
Specifies the connection from the Microsoft Dynamics 365 API response parameter to your process schema.
To Open this Field:
  1. On the Create Multiple Entity Configuration window, click the Response tab.
Accepted Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

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

Example:
Refer to:

Store Response in This Variable
Function:
Specifies the process data variable that contains more than one entity ID from Microsoft Dynamics 365.
To Open this Field:
  1. On the Create Multiple Entity Configuration window, click the Response tab.
Accepted Values:
A process data variable that accepts an alphanumeric string with no spaces.
Returns more than one entity ID in this format:
  • [entity ID];[entity ID];[entity ID]
Default Value:
None
Accepts Process Data Variables:
Yes
Example:
7d00b35d-7174-e811-a961-000d3ac01a1b;8200b35d-7174-e811-a961-000d3ac01a1b;8700b35d-7174-e811-a961-000d3ac01a1b
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 Ownership
Function:
Specifies the owner of the entity.
To Open this Field:
  1. Click the Record Ownership tab.
Accepted Values:
Default Value:
Service Account used in Access Token