Home/Field Guide/Objects & workflow
CONCEPT 10
Form fragments and Data Sets
Turn a data model into a page form and a configurable listing with supported components.
Separate input from display
An Object owns the fields and validation rules. A form built from page fragments can expose a supported subset of those fields for a user to edit. A Data Set can render items from a compatible headless endpoint and expose supported columns, filters, sort options, and actions. These choices let the page author compose a business interface around the same data contract.
Design an intake and review queue
- Publish the Partner Request Object and verify its fields in API Explorer.
- On a test page, configure a form container for the supported Object and map the input fragments to the request fields. Set success and error behavior.
- Configure a Data Set backed by the intended collection endpoint. Select concise columns, a default sort, and a useful filter. Add a supported detail link or action.
- Place the listing on a reviewer page and test with the reviewer role. Submit a request as a normal user and check that it appears only for eligible readers.
- Add a custom element or supported cell renderer if the built-in views cannot express a needed interaction.
Debug the seam
A successful form submission followed by an empty listing can mean a scope, status, permission, or filter mismatch. Read the entry directly and replay the collection request under the same identity. Then inspect the field mapping and client response. Verify feature availability on the target. The 2025.Q1 DXP release notes list Data Sets as a release-flag feature for that build.