---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Manage decision tables in Excel

# Manage decision tables in Excel {#ariaid-title1}

Release version: Australia  
Updated July 22, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Manage decision tables in Excel

This guide explains how ServiceNow customers can efficiently manage large decision tables by exporting them to Excel, editing them, and importing them back into Workflow Studio.
This process allows for faster rule authoring, delegation of tasks, and easier handling of extensive decision tables.
Show full answer Show less  

## Key Features

* **Exporting to Excel:** Export decision tables as .xlsx files containing two worksheets---one with the table itself and another with detailed instructions to help avoid import errors. Advanced rows are read-only in Excel.
* **Editing in Excel:** Users can add, remove, edit, or reorder decision rules by modifying only the Condition and Result columns. Operators and values must be selected or entered following the instruction sheet. Drop-down lists for reference columns include only records with read access based on ACLs.
* **Importing from Excel:** After editing, import the Excel file back into Workflow Studio where changes are validated. Successful imports update the decision table immediately, while failed imports provide an error file to facilitate corrections.
* **Export and Import History:** Workflow Studio tracks and displays export/import history, showing user details and timestamps. Users can download exported, imported, or error files directly from the history sidebar.
* **System Property Configuration:** The property *glide.ui.export.choicelistmaxcharacters* controls the maximum characters shown for condition fields in Excel exports and UI lists, defaulting to 80 characters. It can be adjusted in system properties but does not affect actual data length.

## Practical Considerations and Limitations

* Do not add or modify condition or result columns in Excel---only edit the data within existing columns.
* Retain original headers and do not copy-paste content into new Excel files; only rename the original exported file if needed.
* Avoid empty rows; any data following five consecutive empty rows will be ignored on import.
* Import is only possible after exporting a decision table to Excel.
* Editing in Excel is unsupported for decision tables without condition columns, with unsaved changes, with unsupported field types, or with inactive related inputs.
* The Edit in Excel feature supports only English instances due to localization limitations.  
Manage large decision tables in Excel. Export a decision table to an Excel file, edit the file to add or update rows, and import the file back into Workflow Studio.

## Exporting a decision table to Excel {#manage-decision-tables-ms-excel__section_ip1_xjz_ztb}

After creating and saving inputs, condition columns, and result columns, export a decision table to Excel in .xlsx format by selecting Export. The exported file contains two
worksheets: One with the decision table and the other with instructions on how to build decision rows and prevent import errors.

Editing your decision tables in Excel can help you build large tables more quickly. It also gives you the ability to assign the structural setup to a developer, and then delegate rule authoring to someone else, who could fill it
out in Excel.  
Note:  
If you have any advanced rows in your decision table when you export to Excel, these rows are read-only and cannot be edited in Excel. You can edit the rest of the table in Excel and import it back into Workflow Studio.

## Access to reference column data {#manage-decision-tables-ms-excel__section_vnp_qpk_xkc}

For decision tables that contain reference columns, the drop-down lists that are exported to Excel include only records that you have read access to, plus any records that are already used as values in the decision table. Read
access is determined by the access control lists (ACLs) on the referenced table.

## Modifying the decision table in Excel {#manage-decision-tables-ms-excel__section_q1f_p1z_ztb}

After you export a decision table to Excel, you can add, remove, edit, or reorder decision rules. Follow these directions to build your decision table.

* Build conditions using the operator and value columns.
  * In each Operator cell, choose the relevant operator from the drop-down list. The operator list is specific to the condition column field type.
  * In each Value cell, enter or select the condition value, following the format guidance from the instructions sheet.
  * When building date, due date, date/time, reference, or choice conditions, you can select a value from the drop-down list.
  {#manage-decision-tables-ms-excel__ul_sgh_pky_ztb}
* Specify result values.
  * In each Result cell, enter the result value.
  * For reference or choice results, select a result value from the drop-down list.
  {#manage-decision-tables-ms-excel__ul_snh_nkt_25b}
{#manage-decision-tables-ms-excel__ul_ytj_hhy_ztb}  
Consider the following limitations when modifying a decision table in Excel.

* Use Excel to add, remove, or edit decision rules, but do not use Excel to add or modify condition columns or result columns.
* Edit only cells in the Condition and Result columns. During the import, any data entered to the right of these columns are ignored.
* Retain the headers in the exported file, and do not modify them in any way.
* Modify only the original exported file in Excel. Do not copy and paste the contents of an exported file into a new Excel file. However, the original file can be renamed.
* Ensure that there are no empty rows. Any entry after five consecutive empty rows is ignored.
{#manage-decision-tables-ms-excel__ul_yfv_tkt_25b}

## Importing an Excel file into Workflow Studio {#manage-decision-tables-ms-excel__section_alq_l1z_ztb}

Note:  
The import option is only available after you export the decision table to Excel.  
During the import process, all the modifications in the Excel file are validated before your changes are imported to Workflow Studio. The following outcomes are possible while attempting to import.

* Successful import: The Excel file import is successful. The Import window closes automatically, and your decision table is updated with the imported data. Save your changes before continuing.
* Failed import: The Excel file import has failed. Download the Error.xlsx file that contains the detailed description about the errors and how to fix them. After fixing the errors, follow the import process and import the corrected error file.
{#manage-decision-tables-ms-excel__ul_prm_5py_ztb}

## View export and import history {#manage-decision-tables-ms-excel__section_apy_sff_15b}

View the export and import history of a decision table in the History sidebar. Each entry
displays the name of the user who imported or exported the file and the timestamp.  
You can download the relevant Excel file based on the history type: The exported file (Export Successful), the imported file (Import Successful), or the error file (Import Failed). History records are not created when you select Cancel in the import window.  
Note:  
The `glide.ui.export.choice_list_max_characters` property sets the maximum number of characters that will be included from a condition field type when exporting to Microsoft Excel, as well as the maximum number of characters displayed in the list view condition builder in Core UI. This property is of type integer and has a default value of 80. To use this property, add it to the System Property \[sys_properties\] table. It's important to note that this property does not affect the length of condition field values in tables.

## Limitations {#manage-decision-tables-ms-excel__section_rcl_21z_ztb}

The following are scenarios when you cannot modify a decision table in Excel.

* Decision table does not contain a conditions column.
* Decision table has unsaved changes.
* Decision table has condition columns with unsupported field types.
* Decision table has a condition column that is related to an inactive input.
{#manage-decision-tables-ms-excel__ul_fm5_pry_ztb}  
Note:  
The Localization Framework is integrated in decision tables. However, because the Edit in Excel feature doesn't support localization, you cannot use this feature in any instance that doesn't use English.