Data Store
Client-side collections in App Connect: define a schema, store records, and perform record actions like insert/update/delete.
Data Store
Section titled “Data Store”Data Store is a client-side collection that can persist in session storage and supports record actions.
What it’s for
Section titled “What it’s for”Use Data Store when you need a collection you can add/update/delete on the client (for example: a cart, temporary edits, or a local list for UI state).
Where you’ll use it
Section titled “Where you’ll use it”Data Store appears as a data source in bindings and pickers, and you can manage its records with client-side actions (insert/update/delete).
Core Properties
Section titled “Core Properties”These are the key fields you’ll configure in Properties.
Orient yourself in Properties panel
Section titled “Orient yourself in Properties panel”Start with the wider context in the Properties panel so the next control makes sense in the full workflow. In the next step, you will focus on ID and see how it fits into this area.
The ID is how you reference the Data Store in bindings and action pickers. This step matters because ID is part of Selection Panels Properties Datastoreid, and understanding that context makes the next action easier to repeat in your own project.
Session storage
Section titled “Session storage”Enable session persistence when you want data to survive a reload within the same browser session.
Schema
Section titled “Schema”Define your fields so bindings and record actions have a reliable structure. This step matters because Schema is part of Selection Panels Properties Datastorescheme, and understanding that context makes the next action easier to repeat in your own project.
Conclusion
Section titled “Conclusion”Next, learn how to filter/sort/page through collections using Data View.
Pick your next tour
Section titled “Pick your next tour”Continue with traversal and filtering.