---
title: "Track and store results"
slug: "image-resizer-rotator-track-and-store-results"
updated: 2026-10-09T18:07:21Z
published: 2026-10-09T18:07:21Z
canonical: "help.quickbase.com/image-resizer-rotator-track-and-store-results"
---

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

# Track and store results

By default, Image Resizer/Rotator replaces each original image with the processed one. These optional parameters let you keep the original, and record what happened to each image. They work the same for resizing and rotating.

| **To...** | **Create this field per image** | **Parameter** | **What's written** |
| --- | --- | --- | --- |
| Keep the original and save the result elsewhere | File Attachment | falist | The processed image. The original stays in its field. |
| Flag that the image was processed | Checkbox | updatefidlist | Checked |
| Record when it was processed | Date / Time | datefidlist | The date and time |
| Record the original file size | Text | currfsfidlist | For example, *130.96 KB* |
| Record the new file size | Text | newfsfidlist | For example, *27.16 KB* |

File sizes are written with two decimal places and a unit of Bytes, KB, MB, or GB.

## How the lists match up

Each of these parameters is a period-separated list of FIDs with **one entry per image in clist, in the same order**. For example:

```
& "&clist=14.15"
& "&falist=38.39"          // image 14 → field 38, image 15 → field 39
& "&updatefidlist=36.37"  // checkbox 36 for image 14, 37 for image 15
& "&datefidlist=34.35"
& "&currfsfidlist=30.31"
& "&newfsfidlist=32.33"
```

If any list has a different number of entries than **clist**, nothing is processed and the result names the list, for example *Error - FAList not provided correctly 38*.

Field names don't matter—choose names that make sense to your users, such as *Image 1 Resized?* or *Image 1 - Original Size*. Add the fields to the form if users should see them.

## Show progress on the record

To show status on the record itself, create a **Text - Multi-line** field and pass its FID as **triggerfid**. While images are processed it reads *Processing Images...*. When finished it reads *Batch_Process_Completed_* followed by the date and time, or *Batch_Process_Failed_* followed by the date and time and each error message. This field is required for [batch processing](https://help.quickbase.com/quickbase-extensions/docs/en/image-resizer-rotator-batch-processing), and optional for buttons.

The status is written to the record identified by **dbid** and **recid**—the record with the button—so the trigger field must be on that table, and **recid** is required whenever you use **triggerfid**. That includes [multiple-record mode](https://help.quickbase.com/quickbase-extensions/docs/en/image-resizer-rotator-multiple-records): keep *recid=[Record ID#]* next to **query**. Without it, the status can't be saved and the field never changes.

For every parameter, see [Formula URL parameters](https://help.quickbase.com/quickbase-extensions/docs/en/image-resizer-rotator-formula-url-parameters).