- 2 minutes to read
Saved Views: Technical Specifications
This page explains how Nodinite Mapify stores a saved Map, for administrators and architects who want to know what is kept and what isn't. To build and use Maps, read Saved Maps (Saved Views).
Back to Saved Views
Understanding how a Map is stored
A Map is not a JSON document or a file. It is a set of rows in the Nodinite Configuration Database, written when you save the Map on its General and Designer tabs.
graph LR
roMaps["fa:fa-bookmark Maps
name, description,
scope options"] roTypes["fa:fa-cubes MapTypesInMaps
item types and
relations"] roGroups["fa:fa-layer-group FilterGroups
brackets, AND/OR"] roFilters["fa:fa-filter Filters
field, operator, value"] roMaps --> roTypes roMaps --> roGroups roGroups --> roFilters style roMaps fill:#E47528,color:#fff style roTypes fill:#2678BD,color:#fff style roGroups fill:#2678BD,color:#fff style roFilters fill:#2678BD,color:#fff
name, description,
scope options"] roTypes["fa:fa-cubes MapTypesInMaps
item types and
relations"] roGroups["fa:fa-layer-group FilterGroups
brackets, AND/OR"] roFilters["fa:fa-filter Filters
field, operator, value"] roMaps --> roTypes roMaps --> roGroups roGroups --> roFilters style roMaps fill:#E47528,color:#fff style roTypes fill:#2678BD,color:#fff style roGroups fill:#2678BD,color:#fff style roFilters fill:#2678BD,color:#fff
One Map (orange) owns its item types and relations, and its filter groups with their clauses (blue).
| Table | What it holds |
|---|---|
| Maps | The Map itself: name, description, and the scope options Include Deleted, Include Related, Only With Relations, Depth, and Allow back-traversal |
| MapTypesInMaps | The item types and relations selected in the Items and Relations menus |
| FilterGroups | The brackets of the filter and how they combine (AND or OR) |
| Filters | One row per clause: the field, the operator, and the value. A clause on a Custom Metadata field keeps the field's ID (CustomMetaDataId) |
What this means in practice
- Opening a Map runs it. The rows hold the definition, not a result, so a Map always shows current data.
- Custom Metadata clauses survive renames. A Select value is stored by its option, so renaming an option keeps the Map working; an option that was deleted shows as #id.
- No layout is stored. Node colors, positions, and zoom aren't saved; the graph is laid out each time.
- No owner or visibility. Every Map is visible to every user with Access to Maps; the Mapify rights in the user's Roles decide who may add, edit, or delete Maps.
- No versions. Saving overwrites the Map. To keep a variant, use Duplicate first.
Next Steps
- Saved Maps (Saved Views) – Build, save, and reopen Maps