How to configure a externally managed cascade field
- Thiago Manini
If you need to manage a large amount of data (as outlined in our limitations document) or if you already have your data prepared for your cascade field, you can opt to use an externally managed field. This brief guide details the configuration process.
Begin by creating a 3+ level cascade field as you normally would. Then, navigate to the configuration page within our app.
Toggle on the “Externally Managed?” option.
Input the URL where your data is stored. Once the data is successfully pulled, review it and click the “Save” button.
All done! Your data is now set up to be used for the options available in your cascade field.
Data format
It is important to note how the app is expecting the data. Any URL that serves immediately a JSON file with the following format should work.
[
//...
{
"enabled": true, //Optional
"id": "1",
"parentId": "0",
"value": "North America"
},
{
"enabled": true,
"id": "2",
"parentId": "1",
"value": "California"
},
{
"enabled": true,
"id": "3",
"parentId": "2",
"value": "Silicon Valley"
},
{
"enabled": true,
"id": "91",
"parentId": "3",
"value": "Hivemind Offices"
},
//...
]Performance and Limitations Disclaimer
Please be aware that when using your own server to store the data for the options, the performance will depend on the server's configuration. Based on our internal tests, this solution should be capable of handling up to a million options. However, loading such a large number of options will result in some performance impacts on the app’s UI.
If you don’t have a server ready, we can recommend a python server configuration if it helps! Python Server Recommendation