Create Association (MS Dynamics 365) activity

An activity that creates a many-to-many relationship between two entities.

Configure the Create Association activity

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

Examples

(Example) How to Get the Access Token Credentials from Microsoft Dynamics 365

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
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?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the MS Dynamics 365 tab.
On the MS Dynamics 365 tab, drag the Create Association activity onto your process.

General Configuration

Specifies the basic settings for the Create Association activity.

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
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 Association Configuration

Specifies to create a many-to-many relationships between two records.

Fields

Field Name	Definition
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: (Example) How to Get the Access Token Credentials from Microsoft Dynamics 365
Create	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: (Example) How to Get the Access Token Credentials from Microsoft Dynamics 365
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
Record ID	Function: Specifies the Microsoft Dynamics 365 entity ID. Accepted Values: A valid Microsoft Dynamics 365 entity ID. 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?
Relationship	Function: Specifies the entity from the list which is related to other entity of the many-to-many relationship. Accepted Values: An entity column name from the list Default Value: None Accepts Process Data Variables: No
Related Record ID	Function: Specifies the ID of the associated entity. This value is usually a variable. Accepted Values: A valid ID. 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 New Association ID in This Variable	Function: Specifies the process data variable that contains the association ID from Microsoft Dynamics 365. Accepted Values: A process data variable that accepts an alphanumeric string with no spaces. 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?