data-operations

To build paginated Wix CMS list pages, use BaseCrudService to fetch items via getAll and render results supporting load-more. You must handle paginated result objects containing items, totalCount, hasNext, and nextSkip properties to manage pagination state reliably.

Optimistic updates for Wix CMS CRUD operations immediately reflect create, update, delete, and reference changes in the UI. If a mutation fails, the system automatically rolls back the optimistic state by re-fetching the correct data from the collection.

To hydrate single and multi reference fields in Wix CMS detail pages, fetch items by id using BaseCrudService and apply optional reference loading. This hydrates linked collection data for richer detail pages and connected list content.

The correct parameter order for Wix CMS CRUD operations using BaseCrudService requires passing the collection-id first, followed by the item-id second. Maintaining this strict ordering prevents mismatched pagination and inconsistent data behavior.

To add or remove references between items in a Wix CMS collection, use the addReferences and removeReferences mutation actions provided by BaseCrudService. These operations trigger optimistic UI updates with automatic rollback via re-fetch on failure.

Yes, you can use BaseCrudService for Wix CMS routing and data-driven page generation. It enables reliable collection-driven workflows by implementing consistent CRUD and reference-handling flows for list and detail pages without mismatched pagination.