Converter (MS Dynamics 365) activity

An activity that does these conversions:
  • Kit To Product
  • Product To Kit
  • Quote To Sales Order
  • Sales Order To Invoice

Converter activity

Configure the Converter activity

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

    Drag Converter activity

General Configuration

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

Converter Configuration

Specifies the information to perform conversion from Product To Kit, Kit To Product, Quote To Sales Order, and Sales Order To Invoice.

Figure: Converter Configuration screen

Converter 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:

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?

Conversion Type

Function:
Specifies the type of conversion from the list.
Accepted Values:
  • Product To Kit.
  • Kit To Product.
  • Quote To Sales Order.
  • Sales Order To Invoice.

For more information, refer to the documentation for Microsoft Dynamics 365.

Default Value:
None

Store New Convert ID in This Variable

Function:
Specifies the process data variable that contains the convert 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?