Microsoft Dynamics AX Execute [Deprecated]

Write

This Snap calls the Dynamics AX AIF endpoint using the incoming data and writes out a SOAP response.

ETL Transformations & Data Flow

This Snap enables the following ETL operations or flows:

• Extract data from the upstream Snap containing the data for performing the provided action on the Dynamics AX object(s)

• Transform the input document into a SnapLogic-friendly JSON Document

• Load the data into the Dynamics AX Execute Snap to perform the operation on the AX object(s)

Expected upstream Snaps: Mapper Snap

Expected downstream Snaps: None

Input & Output

• Input: Needs to have an upstream Snap that contains the mandatory fields for performing the respective operation on the AX objects(s). The Mapper Snap is a preferred upstream Snap as it populates the input schema for the selected Dynamics AX Object Type.
  
  

• Output: A document with the result set. If the operation is successful, then the output document will contain the information on the AX object(s) being operated.

Modes

• Ultra Pipelines: Works in Ultra Pipelines when the connection timeout is not 0 seconds.

1. Microsoft Dynamics AX 2012 R3 instance

2. An enhanced integration inbound port on the AX instance that containing the Update operation configured

NA

Account & Access

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Microsoft Dynamics AX Account for information on setting up this type of account.

Views

For troubleshooting purposes, try performing the same operation directly on the User Interface or by sending the appropriate SOAP request to the Dynamics AX AIF Endpoint. Use Soap UI (version 4.6.3) and collect the necessary data. To see if there are any inconsistencies, compare the data used in the User Interface or Soap UI with the SnapLogic pipelines.

Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Required. The URL for the Dynamcis AX AIF Endpoint WSDL.

Example: http://AXMachine/MicrosoftDynamicsAXAif60/AXCustomer/xppservice.svc?wsdl

Default value: [None]

Required. The system function that has been exposed to Web-based protocols.

Example: {http://tempuri.org/}RoutingService

Default value: [None]

Required. Basic HTTP Endpoint that contains the operations of the particular object type.

Example: {http://tempuri.org/}BasicHttpBinding_CustomerService

Default value: [None]

Required. Operation to invoke.

The list of operations that can be invoked on the Dynamics AX objects are: getKeys, getChangedKeys, find, findKeys, create, delete, update, read

Example: {http://tempuri.org/}getKeys

Default value: [None]

Required. Timeout for the web service call (in seconds). 0 indicates no timeout.

Example: 60

Default value: 60

Select this option to trust all certificates, such as self-signed certificates.

Default value: Not selected 

Select this option to output the whole SOAP envelope instead of just the SOAP body.
Default value: Not selected

Select this option to output the HTTP headers in the response.
Default value: Not selected

Advance setting, leave blank to allow a Java default.  

Required. Specifies an action to be taken when a SOAP call returns an empty response. The default action is Output no documents.

You can handle SOAP call with an empty response in the following ways:

• Output no documents: The Snap executes successfully and returns no output document.

• Output empty document: The Snap executes successfully and returns an empty document in the output view.

• Write error document: The Snap execution fails and returns an error document in the error view. 

Default value: Output no documents

Specifies the maximum number of attempts to be made to receive a SOAP response. The SOAP request is terminated if the attempts do not result in a SOAP response. If no value specified, only one attempt is made before terminating a SOAP request.

Default value: 3

Specifies the interval between two successive SOAP requests. A retry happens only when the previous attempt resulted in an exception. 

Default value: 2

An expression to match success criteria in the SOAP response.

Example: (with expression toggle on) $['SOAP-ENV:Body']['ns2:orderResponse']['ns2:result'] == "success"

This would match the success criteria in this SOAP response:

The user can find the SOAP output by setting Execute during preview on the SOAP Execute Snap, then seeing what comes out. You can also hook up a Mapper Snap and see the schema there. You can do that on the input view, but not the output view.

Default value: [None]

This property enables Snap execution over HTTP. Use the appropriate library to utilize the latest SOAP capabilities. The available options are:

• Apache HttpComponents

• Apache CXF

Default value: Apache CXF

Launches the XML editor which will generate a SOAP envelope based on the defined properties, WSDL URL, Service name, Port name and Operation. The editor will load an envelope if it was defined previously. The editor allows you to save SOAP envelopes in SnapLogic's file system or import existing SOAP envelopes from it. The Apache Velocity template can be used to pass dynamic values from upstream Snaps.

Any content that needs escaping from Velocity editor parsing can be enclosed with the following syntax:

#[[ <data> ]]#

See https://velocity.apache.org/engine/1.7/vtl-reference.html#unparsed-content for more information.

Default value: [None]

This property lets you supply HTTP header key-value pairs.

Default value: [None]

This property lets you add attachments.

Default value: [None]