Microsoft Dynamics AX Delete [Deprecated]

Write

This Snap deletes records from the Dynamics AX instance according to a specific ID key and ID value.

ETL Transformations & Data Flow

This Snap enables the following ETL operations and flows:

The Snap collects target Dynamics AX instance information from user input or pipeline parameters.  The Snap gets the ID Key and ID Value from user input, pipeline parameters or the upstream Document. It uses this data to send a SOAP request to the corresponding AIF inbound port on the Dynamics AX instance. The SOAP response from the server is passed to the downstream Snaps.

Input & Output

• Input: This Snap can have an upstream Snap that can pass a document output view such as Structure or JSON Generator.
  
  

• Output: This Snap has one Document output view that passes the results of the delete operations to the downstream Snaps.

Modes

• Ultra Pipelines: Works in Ultra Pipelines.

1. Microsoft Dynamics AX 2012 instance

2. An enhanced integration inbound port on the AX instance that has one or more delete operations setup

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

Required. The name for the Snap. 

The company name on which to perform the delete operation. The company should be defined on the AX instance side.

The property can be provided through user input or pipeline parameters.

Required. URI of the inbound port. You may find the information at the Dynamics AX instance: System administration > Setup > Services and Application Integration Framework > Inbound ports > [Your port name] > URI.

The property can be provided through user input or pipeline parameters.

Required. The object type on which to perform the delete operation. The value of the property depends on the object types contained in the target inbound port.

The property can be provided through user input or pipeline parameters.

Example: Customer

Required. The field name of the record's ID. The field names are different among different object types. It reflects the EntityKey.field in the AIF request. See: https://msdn.microsoft.com/en-us/library/aa638403(v=ax.10).aspx

The Id Key property is suggestible and:

• The Object type must support the findKeys operation.

• The findKeys operation must be included in the inbound port.

• There must be at least one record of the object type in the corresponding company (or DAT if not given).

The property can be provided through user input or pipeline parameters.

Example: AccountNum

Required. The ID value of the record that is to be deleted. It reflects the EntityKey.value in the AIF request. See: https://msdn.microsoft.com/en-us/library/aa638403(v=ax.10).aspx

The property can be provided through user input or pipeline parameters.