Examples

Basic Use Case

The following pipeline describes how the Snap functions as a standalone Snap in a pipeline:

The pipeline uses a Mapper Snap to simulate the upstream pipeline that provides the data that is used by the Dynamics AX Create Snap to create an AX object.

Saving the pipeline allows the Dynamics AX Create Snap to populate the input schema to Mapper. This makes it easier to pick the fields:

Image RemovedImage Added

The Dynamics AX Create Snap is configured as below:

The exported pipeline is available for download in the Downloads section below. 

Typical Configuration

Key configuration of the Snap lies in how the data is passed. There are two ways of doing so in the Microsoft Dynamics AX Create Snap:

• Without Expressions

Data is passed directly into the Snap:

• With Expressions
  • Using Pipeline parameters: Data is passed as a pipeline parameter. The parameters to be applied can be selected by enabling the corresponding checkbox under the Capture column.

Configuring using upstream parameters

Here are some JSON representations of the mandatory fields for AX object types. They can be copy-paste to JSON Generator Snap and used as the input for the Dynamics AX Create Snap.

[
  {
    "CustomerServiceCreateRequest": {
      "Customer": {
        "CustTable": [
          {
            "CustGroup": "TestGroup",
            "Currency": "USD",
            "Name": "test1",
            "class": "entity",
            "AccountNum": "terence-010",
            "DirParty": [
              {
                "class": "entity",
                "Name": "test create1",
                "xsiType": "AxdEntity_DirParty_DirOrganization"
              }
            ]
          }
        ]
      }
    }
  }
]

[
  {
    "SalesOrderServiceCreateRequest": {
      "SalesOrder": {
        "SalesTable": [
          {
            "CustAccount": "DAT-000001",
            "LanguageId": "en-us",
            "class": "entity",
            "PurchOrderFormNum": "1234",
            "ReceiptDateRequested": "2017-10-10"
          }
        ]
      }
    }
  }
]

Advanced Use Case

The following describes a pipeline, with a broader business logic involving multiple ETL transformations. It shows how, in an enterprise environment, Create, Read, Search and Delete functionalities can typically be used. The pipeline download link is below.  

This pipeline moves records from a Salesforce instance to the Dynamics AX instance, where the records are created, searched and read for the required IDs and deleted as needed.

The ETL Transformations:

1. Extract: The Salesforce Read Snap retrieves the records from an object type from the Salesforce instance.
2. Transform: The Mapper Snap maps the records from the Salesforce object to the Dynamics AX instance.
3. Load:The Dynamics AX Create Snap creates the records on the AX instance.

The pipeline further uses:

• The Mapper Snap maps the records to be searched from an Object type.
• The Dynamics AX Search Snap searches all the records.
• The JSON Splitter Snap splits the the records based on the field names.
• The Dynamics AX Read Snap reads the records based on the given fields. They are retrieved from the bottom using the Tail Snap.
• The Mapper Snap maps the records to be deleted using the Dynamics AX Delete Snap.

Downloads