Limits
NexusDM sets a few hard limits on node types and nodes, so a campaign stays fast and easy to work with. This page gathers them in one place. Each row links to the part of the Guide that explains it, and the rules at the end say what you can and can’t change once a type is published.
| Restriction | Limit | Read more |
|---|---|---|
| Node types per campaign | 32, and archived types count too | Archive and restore |
| Fields per node type | 64 | The field kinds |
| Options per Choice field | 128 | Choice |
| Items per List field | 100 | List |
| Size of one node’s values | 256 KiB: far more text than you’ll write by hand | Not explained elsewhere in the Guide |
| Short text length | 1,000 characters | Short text |
| Long text length | 100,000 characters | Long text |
| A List can’t be Required or have a default | Rule | List |
| One Description and one Primary state per type | Rule | The two roles |
| A limit can be changed, but not removed, once published | Rule | What each change does |
| A type is read-only while it is publishing | Rule | While a type is publishing |
| A field’s kind changes only along the conversion rules | Rule | Changing a field’s kind |