Data settings
Two of these three let you store things CIQRA did not anticipate. The third lets you leave with them.
What is in this group
Section titled “What is in this group”| Destination | What it governs |
|---|---|
| Custom data | Structured records of your own design — a type you define once and then create entries against. |
| Custom fields | Extra fields attached to things CIQRA already knows about, such as a product or a customer. |
| Data export | Taking your data out of CIQRA. |
Custom data and custom fields answer different questions
Section titled “Custom data and custom fields answer different questions”They look similar and are not. A custom field hangs off something that already exists: a product gains a “care instructions” field. Custom data is a thing in its own right — a “store event” or a “size guide” that is not an attribute of anything else and needs its own list.
The rule of thumb: if deleting the product should delete it, it is a field. If it should outlive the product, it is custom data.
Export exists so that leaving is possible
Section titled “Export exists so that leaving is possible”Data export is listed under Settings rather than buried, deliberately. A platform that makes it hard to leave is a platform you cannot safely evaluate. Whatever you have put into CIQRA, you can take out.
What this page does not say
Section titled “What this page does not say”- It does not give click-paths. No verified screenshot of these screens exists in this help centre yet.
- It does not describe browsing entries of a custom type. In this release a type’s shape can be inspected but its entries are not browsable from that screen, and the admin says so on the screen itself rather than leaving you looking for a list that is not there.
- It does not cover backups. Data export is a copy you ask for; the platform’s own backup and restore posture is described under Transparency, with dates and measurements.