---
title: "Quicklist Import/Export"
canonical: "https://kb.myframeworks.com.au/space/FRAM/145948708/Quicklist%20Import%2FExport"
format: markdown
---
The Quicklist Import/Export function allows you to bulk create and update quicklists and their associated products in Frameworks. This scheduled task streamlines the process of managing multiple quicklists, their groupings, subgroupings and sequence numbers across your organisation.
Common uses for this function include:
- Creating multiple new quicklists with their product associations.
- Updating existing quicklist details and product groupings in bulk.
- Adding or modifying sequence numbers, groupings and subgroupings across multiple quicklists.
- Managing quicklist structures prior to initial rollout or seasonal updates.
> ✅ Refer to [Quicklist Maintenance - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/141820078) for managing individual quicklist records.
> ℹ️ This process involves downloading a template CSV file, editing it with your required data, and uploading it back to Frameworks for processing.
---
## Accessing Quicklist Import/Export
To access the Quicklist Import/Export function:
1. Click the **Frameworks Menu** and navigate to **Inventory > Maintenance > Quicklist Import/Export** from the navigation tree.
2. The **Import Criteria** tab opens by default.
---
## Downloading a Template
Downloading a template is recommended as it provides the correct CSV file format with the appropriate column headings for your import.
### Steps
1. From the **Process** drop-down menu, select **Export**.
2. From the **Update Field** list, select the fields you want to include in your template (hold the CTRL key to select multiple fields). Refer to the **CSV Field Reference** table in the Additional Information section for a full list of available fields.
3. In the **From Quicklist** and **To** fields, optionally specify a range of quicklists to include in the export.
4. Click **Submit** to send the export task to the Task Scheduler.
You can choose to download a template without any data by clicking the **Download Template Only (No data)** button. The template file downloads instantly and can be opened, edited and saved as quicklist.csv to your PC.
---
## Uploading the Import
Once you have edited your CSV file with the quicklist data you want to import, you can upload it to Frameworks.
### Steps
1. From the **Process** drop-down menu, select **Import**.
2. From the **Update Field** list, select which fields you want to update from your CSV file (hold the CTRL key to select multiple fields). Refer to the **CSV Field Reference** table in the Additional Information section for a full list of available fields.
3. Click the **Upload CSV** button to open the **File Upload** window.
1. Click the **Browse** button to browse your PC.
2. Select your edited quicklist.csv file.
3. Click **Open** to confirm the file selection.
4. Click **Upload** for the file to be ready for import.
5. The filename displays in the **Import File** area once uploaded.
4. Choose to enable or disable the **Report Only** checkbox.
5. Click **Submit** to send the import task to the Task Scheduler for processing.
When the **Report Only** checkbox is enabled, Frameworks validates your data and produces a report of any errors that need to be corrected in your CSV file before the actual import can proceed.
> ℹ️ Always run your import with **Report Only** enabled first to validate your data before committing changes.
---
## Import Rules
- The **Quicklist Name** column is required and is used to match records to existing quicklists. If the quicklist does not exist, the import creates a new record.
- Only fields selected in the **Update Field** list are updated. Fields not selected are ignored, even if values are present in the CSV file.
- Each row in the CSV file contains both header fields and product line fields. The header fields (**Quicklist Name**, **Quicklist Description**, **Quicklist Sequence** and **Active**) are only read from the first row for each quicklist. Subsequent rows for the same quicklist are used for product line details only — header field values on those rows are ignored.
- The **Grouping** value must be present on a product line before any **Subgroup 1** through **Subgroup 7** values can be imported for that line. Product lines with subgroup values but no grouping are rejected.
- Subgroup fields must be populated sequentially. For example, **Subgroup 2** cannot be imported if **Subgroup 1** is blank for that product line.
- Grouping and subgroup values are automatically converted to uppercase on import.
- Field values containing commas, quotation marks or newline characters must be enclosed in double quotation marks in the CSV file.
- The import adds new records and updates existing records. It does not delete existing quicklist product associations.
- Invalid product codes are rejected. The product must already exist in Frameworks before it can be imported into a quicklist.
- When running in **Report Only** mode, the output file includes a **Success** column (Yes or No) and a **Notes** column describing any validation errors for each row. Review the **Notes** column to identify and resolve errors before committing the import.
---
## Schedule and Output Tabs
The import and export tasks are recommended to be run as a once-off by clicking the **Submit** button on the **Import Criteria** tab. For large imports, the task can be scheduled to run after hours via the **Schedule** tab.
After a task is submitted, the screen navigates to the **Output** tab where you can view any generated reports, including validation results from **Report Only** runs and import processing summaries.
If the **Report Only** option was enabled and there were no errors in the generated report, repeat the upload process with **Report Only** disabled to commit the changes. If there were errors, resolve them in your CSV file before importing.
> ✅ Refer to [Scheduled Task - Scheduling and Output](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28402256) for information on scheduling tasks and viewing output.
---
> ✅ ## Related Information
> ✅
> ✅ - Refer to [Quicklist Maintenance - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/141820078) for information on maintaining individual quicklist records.
> ✅ - Refer to [About Quicklists](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/145326130) for an overview of how quicklists work and how they are used during transaction entry.
> ✅ - Refer to [Quicklists - Setup and Configuration](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/146440221) for guidance on configuring quicklists for use in your business.
---
## Additional Information
### CSV Field Reference
The following fields are available for import and export. All field names in the CSV file must match exactly as listed.
Input/Output fields — included in both the import file and the export file:
| Field Name | Type | Description |
| --- | --- | --- |
| Quicklist Name | text | The unique keyword identifier for the quicklist. Required. Used to match existing records or create new ones. |
| Quicklist Description | text | The descriptive text for the quicklist.
Read from the first row per quicklist only. Ignored on subsequent rows for the same quicklist. |
| Quicklist Sequence | int | The display sequence number for the quicklist in the Quicklist Finder window. Read from the first row per quicklist only. Ignored on subsequent rows for the same quicklist. |
| Active | text | The active status of the quicklist. Valid values: yes or true (active), no or false (inactive). Read from the first row per quicklist only. Ignored on subsequent rows for the same quicklist.
Read from the first row per quicklist only. Ignored on subsequent rows for the same quicklist. |
| Product Id | text | The product code to associate with the quicklist. Must already exist in Frameworks. |
| Product Description | text | The product description. Populated automatically by Frameworks on export. This field is ignored on import. |
| Grouping | text | The group name for the product line. Must be present before any Subgroup fields can be populated. Automatically converted to uppercase on import. |
| Subgroup 1 | text | The first level of subgrouping within the grouping. Automatically converted to uppercase on import. |
| Subgroup 2 | text | The second level of subgrouping. Requires Subgroup 1 to be populated. Automatically converted to uppercase on import. |
| Subgroup 3 | text | The third level of subgrouping. Requires Subgroup 2 to be populated. Automatically converted to uppercase on import. |
| Subgroup 4 | text | The fourth level of subgrouping. Requires Subgroup 3 to be populated. Automatically converted to uppercase on import. |
| Subgroup 5 | text | The fifth level of subgrouping. Requires Subgroup 4 to be populated. Automatically converted to uppercase on import. |
| Subgroup 6 | text | The sixth level of subgrouping. Requires Subgroup 5 to be populated. Automatically converted to uppercase on import. |
| Subgroup 7 | text | The seventh level of subgrouping. Requires Subgroup 6 to be populated. Automatically converted to uppercase on import. |
| Sequence | int | The display sequence number for the product within its group or subgroup. |
Output-only fields — included in the Report Only results file but not required in the import file:
| Field Name | Type | Description |
| --- | --- | --- |
| Success | text | Indicates whether each row was processed successfully. Values: Yes or No. |
| Notes | text | Describes any validation errors for each row. For example, "Invalid Product [ProductCode] (ERROR)". Blank if the row was processed successfully. |