Contact your Iterable CSM to discuss adding Catalog to your plan.
This document describes known issues and limitations related to Iterable's Catalog feature.
Table of contents
- Organizations must store no more than 15GB of catalog data across all their Iterable projects.
- Catalog names must be unique (regardless of case).
- Catalog names may contain letters, numbers, and dashes (no spaces, underscores, or other special characters) and must be 255 characters or less.
- It is not possible to rename a catalog.
- Each catalog item must be less than 30kb.
- In a given catalog, each catalog item must have a unique
- In catalog item field names, periods are disallowed (for example,
first.nameis not a valid field name).
- In a given catalog, there can be no more than 350 unique catalog item fields/columns.
- The JSON viewer will incorrectly render catalog items containing a
lengthfield. Use tabular view instead.
- The JSON editor will incorrectly render catalog items containing a
lengthfield. Use the text editor to edit these items.
- Iterable's web interface can page through 30,000 catalog items or fewer. If the item you are looking for is deeper in the list than that, try changing the sorting order.
- A CSV file containing catalog items must be no longer than 1000 rows, excluding the header row.
- A CSV file containing catalog items must only contain data of type string, date, boolean, double, and long.
- Once a data type has been given a data type, it cannot be changed.
- A catalog item's
keyfield may contain letters, numbers, and dashes (no spaces, underscores, or other special characters) and must be 255 characters or less.
- A collection can return at most 50 items.
- It is not possible for a collection to search catalog item fields that do not have explicitly assigned data types.
- It is possible to create nested catalog objects in a catalog item. However, collections cannot search nested objects. In a top-level object, collections can only search non-object fields.
- Once a catalog item field has been given a data type, collections can search that field on all future data added to the same catalog. To search that field in previously created data, you must re-create or re-upload that data.
- Collection definitions do not support Handlebars expressions.
- The JSON view of a collection builder preview does not correctly render
catalog items that contain a
lengthfield. To view this data, use tablular view instead.