How Zenpo Web Parts Use Your SharePoint Data
List-driven Zenpo web parts read your existing SharePoint lists and libraries. They map roles to columns you already have. They do not require a mandated schema.
Roles, not column names
Each product asks you to point a role (Title, Image, Link, Manager, Value, and so on) at whichever column already holds that content. Unbound optional roles show (none) and render nothing.
The pane states this as Roles, not column names — map any schema.
The view carries order, filter, and limit
Where a product offers a View setting, that view's own filter, sort, and item limit decide which rows reach the web part. Most products have no separate sort or filter settings. Change the view, or point at a different one, and the web part follows.
The pane states this as The View carries the order, the filter and the item limit.
Changing the source resets mappings
Changing the data source resets the mappings. The product then re-detects likely columns in the new list. Changing only the view keeps your mappings, because mappings belong to the list, not the view.
Exception: Zenpo Mosaic — Masonry Gallery & Cards re-detects mappings when the view changes as well, because its card bindings follow the view's columns.
Appearance, layout, and behavior settings are never reset by a source change.
Caching
Products with a Cache duration setting reuse loaded content in the browser before asking SharePoint again. The shared options are:
- No caching (always fresh)
- 1 minute
- 5 minutes (recommended) (default on most parts)
- 15 minutes
- 30 minutes
- 1 hour
Side Navigation defaults to 15 minutes (recommended).
Set No caching (always fresh) while you are authoring, then put it back. If SharePoint cannot be reached, most products fall back to the most recently cached copy and say so. Typical notice: Showing the last saved copy — SharePoint could not be reached just now.
License data is cached separately for 24 hours. That is not the same setting.
Caps refuse rather than truncate
Where a product enforces a source cap, it rejects an over-cap source and tells the author to use a filtered view. It never drops rows quietly. Caps are not universal. Check the product's own page. The two calendar products, for example, do not enforce a total item cap.
List reads page at 500 rows per request under the current user's permissions.
SharePoint permissions always apply
Every product reads as the signed-in user. Zenpo never elevates access. See Permissions and Data Access.