---
title: "Flow Execution Extension CRUD Actions"
slug: "flow-execution-extension-crud-actions"
tags: ["CRUD Actions", "Flow Execution Extension"]
updated: 2024-10-29T20:38:47Z
published: 2024-10-29T20:38:47Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flow Execution Extension CRUD Actions

## Overview

The Flow Execution Extension Data Structure is primarily used to store data that goes through states in chronological order. This Data Structure uses Process Folders to track states, assignments and store files within them. These Process Folders will contain the data created when a user runs a Flow that creates a record. Process Folders are most commonly stored within a normal Folder.

CRUD Action Steps: Flow Execution Extension

In the Toolbox, the **Create**, **Update**, and **Delete**steps cannot be searched for. Users will have to navigate to **USER DEFINED TYPES > FLOW DATA EXTENSIONS**to add CRUD actions to the workspace.

---

### [Prerequisite](/v9/docs/creating-flow-execution-extension-data-structure)

In this tutorial, a Flow Execution Extension was created with the following fields:

| Employee_FlowExec |
| --- |
| FirstName | String |
| LastName | String |
| Email | String |

Flow Execution Extensions store data; however, users will have to create a normal Folder to store the process data. In this example, a normal Folder called **FlowExec_Employee Data**.

Do Not Store Data In The Configuration FolderData Structures that are a part of the Decisions Entity Framework will automatically have a Configuration Folder. Do not store data within that Folder. The Configuration Folder is meant for creating Flows, Rules, and other Designer elements to enhance that custom Data Structure. For more information, please navigate to the [Configuration Folder](https://documentation.decisions.com/docs/en/flow-execution-extension-crud-actions) article.

---

## Setup Process Folder

1. In a Designer Project, click CREATE FLOW and [create a new Flow](/v9/docs/creating-your-first-flow-2).
2. In the **Toolbox** panel, navigate to the**PROCESS** category and attach a **Setup Process Folder** step to the workspace and connect it to the **Start**and **End**steps.Flow Execution Extension Data Structures do not have a Create step like other Data Structures. In order to create a record in a Flow Execution Extension Data Structure, a **Setup Process Folder** step is necessary**.**

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_10h48_11.png)
3. On the **Properties**panel, click PICK under the Parent Folder field and select the folder **FlowExec_Employee Data**. Select the **Use Extension Data** option and use the dropdown list to select the Flow Execution Data Structure.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_10h51_26.png)
4. In the **Extension Data** field, change the input mapping to**Build Data**. Set the **Email**, **FirstName**, and **LastName**fields to **Constant**mapping and enter values for each.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_10h55_01.png)
5. Set the **Folder Description** and **Folder Name**fields to Constant mapping and enter values.Auto-ID GenerationThe Id field is automatically created when the Flow runs even though the input value is set to **Ignore**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_10h55_45.png)
6. On the top action bar, click **Debug**.
7. Click START DEBUGGING. This will create data in the folder.

---

## Update

Flow Execution Extensions****do not have an **Edit**or **Selective Update** step like other Data Structures. In order to update the Flow Execution Extension Data Structure, the **Save**step is required.

The entire object must be passed through and updated. Attempting to selectively update via**Build Data** mapping may result in data loss. Any blank values passed into a saved Build Data would overwrite the value as **Null**.

1. In the Flow Designer, attach a **Fetch Entities** step to the **Start**step to fetch all the entities in the Flow Execution Data Structure.
2. Connect a **ForEach Step** to the **Results**path. Map **EntityResults** to the **Collection**field and select the Flow Execution Extension Data Structure.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_10h58_32.png)
3. Attach a **Show Form** step to the **Next**path and [create a new Form](/v9/docs/create-forms).
4. Configure the Form to have three **TextBoxes** (FirstName, LastName, Email) and **Button**(Update) controls. Click Save and close the Form.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_11h00_11.png)
5. Under the INPUTS category, map the fields by selecting **Select From Fl****ow** and selecting the respective values from**Item**. Under the OUTPUTS category, change the mapping for each field to **Change Value**. Under the Item category, select the respective field and click PICK.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_11h02_22.png)
6. In the Toolbox panel, navigate to **USER DEFINED TYPES > FLOW DATA EXTENSIONS > EMPLOYEE_FLOWEXEC** and attach a **Save**step to the **Update**path.
7. On the Properties panel, map Item to the **Value**field.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_11h03_20.png)
8. Connect the Done path of the Save step to the ForEach step. Connect the Done path of the **ForEach**step to the **End**step. Click Save to save changes to the Flow.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_11h04_24.png)
9. On the top action bar, click Debug.
10. Click START DEBUGGING.
11. After the debugger runs, update the fields that are displayed and click Update to have the changes saved.  
![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2022-05-12-10h44-06-Trim.gif)

---

## Delete

With a Flow Execution Extension Data Structure, the steps used to delete records are the **Delete**and **Delete Object** steps. The Delete Object step will delete a specific piece of the record and the Delete step will delete the entire record.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-07-30_11h07_47.png)

---

For further information on Data Structures, visit the [Decisions Forum](https://community.decisions.com/categories/Datastructures).