Import or export options
This page describes how to import and export options into existing custom field.
When you configure Multilevel Select with many levels and options, don't lose this data; save it for later. Then, you have a ready-to-import file to speed up your work and eliminate tedious, manual typing.
Import values to Multilevel Select custom field
Steps 🐾
Create a custom field from the advanced library: Multilevel Select
Go to the context page and edit the custom field config.
Now, in the left corner, expand settings.
You can import values from CSV or JSON format.
Choose a file, and voilà 🎉
In the same way, you can also export your configuration to the CSV or JSON file.
How to prepare a file to import?
Accepted formats: .CSV and JSON
Prepare your file in columns. Below you can see the correctly prepared file where:
Row 1: Add header for this table - headers for Levels are required; the rest is optional, but there you can put level names and descriptions, mark them as default, and enable field and option ID.
Row 2-29: Options in hierarchical tree.
Column H: Optional level name
Column I: Optional description
Column J: If the option is default (forms accepted: YES/NO, 0/1, yes/no, y/n, Y/N, Yes/No, True/False, TRUE/FALSE, true/false, T/F, t/f )
Column K: If the option is enabled (forms accepted: YES/NO, 0/1, yes/no, y/n, Y/N, Yes/No, True/False, TRUE/FALSE, true/false, T/F, t/f )
Column L: Option ID
This is an example of a correct file with a use case about Internal Service Catalog.
Download CSV to see how it should look like.
| Level 1 | Level 2 | Level 3 | Level 4 | Level 5 | Level 6 | Level 7 | Level name | Level description | Default | Enabled | Option ID |
|---|---|---|---|---|---|---|---|---|---|---|---|
Technical Support | Service Categories | Choose a service | YES | ||||||||
Hardware Issues | Technical support | YES | |||||||||
Laptops | Hardware Issues | YES | YES | ||||||||
Desktops | Hardware Issues | YES | |||||||||
Software Issues | Technical support | YES | |||||||||
Apps Error | Software Issues | YES | |||||||||
App XYZ | Apps | YES | YES | ||||||||
Crashes | App XYZ | YES | |||||||||
Features | App XYZ | YES | |||||||||
Slow performance | App XYZ | YES | |||||||||
App ABC | Apps | YES | |||||||||
Crashes | App ABC | YES | |||||||||
Features | App ABC | YES | |||||||||
Slow performance | App ABC | YES | |||||||||
Project Management | Service Categories | Choose a service | YES | ||||||||
Project planning | Project Management | YES | |||||||||
Requirements Gathering | Type | YES | |||||||||
Resource Allocation | Type | YES | |||||||||
Project Closure | Project Management | YES | |||||||||
Deliverable Handover | Project Closure | YES | |||||||||
Post-Implementation Review | Project Closure | YES | |||||||||
Development Services | Service Categories | Choose a service | YES | ||||||||
Web Development | Development Services | YES | |||||||||
Frontend Development | Web Development | YES | |||||||||
Backend Development | Web Development | YES | |||||||||
Mobile App Development | Development Services | YES | |||||||||
iOS Development | Mobile App Development | YES | |||||||||
Android Development | Mobile App Development | YES |
Next, export this file to CSV format (.csv), and ensure the separator is comma.
Import file in Multilevel Select configuration.
The levels and options will be automatically loaded if the file is corrected. If not, there will be a list of errors that make it easier to track mistakes.
Export is to the same format.
The separator in .csv must be a comma.
JSON format
For this kind of format, use JSON writer tools and prepare the file as the code below:
Last updated