This page provides details of the properties for the delete node.

Overview

Use a

 node to delete selected records from a table. Delete nodes will delete records that where the Primary Key for the selected record(s) match those on the specified table. 

A delete node will only delete records from a table with a Type of Transactional.

The Delete node will persist Audit History of records when they are deleted. This is achieved by superseding the previous record and adding a new deleted record into the next recordset. This persists the history of the record. If you wish to purge records from your PhixFlow system entirely including Audit History see Bulk Delete Node

Example

In the Actionflow instance illustrated in the screenshot above, an application has a list of Companies in a grid. When the user clicks the delete button, the Actionflow runs.

1. The Primary Key of the selected records on the All Companies grid are mapped onto the Input Connection Point.

2. The Delete Node uses the mapped Primary Key to select the records from the All Companies table and delete them.

Basic Settings

Field	Description
Name	Enter the name for the action node.
Table	The table in which the records will be updated. This table must have a Period of Transactional. See Table.
Auto Save Attributes	Enable to automatically delete unmapped attributes from the input, matched by the UID.

Mapped Attributes

Field	Description
Name	Enter the name for the attribute mapped to the Delete node.
Type	The data type of the attribute mapped to the Delete node. See Understanding Data Types.

File Tidy Up Settings

This section is available in PhixFlow version 11+.

Advanced Settings

Field	Description
Prioritise throughput over ordering	When this option is ticked records are processed in parallel to optimise performance. This means the order records are processed is nondeterministic. When unticked (default), records are processed in the order they are provided.