Yes. CCTs are a first-class table source. SleekView queries the dedicated jet_cct_* tables directly, which is faster than postmeta-based reads at scale because there's no join through wp_postmeta. The CCT field registry tells SleekView which columns are available, so the admin table tracks the model as new fields are added.

Yes. One-to-one, one-to-many, and many-to-many relations resolve to titles or counts inline. Edit either side from the table through a picker, and the change writes through JetEngine's relations API so JetSmartFilters and front-end listings see the new state on the next query.

Yes. SleekView writes through JetEngine's data classes, so query builders, listings, and dynamic widgets stay in sync. Action triggers attached to data updates fire as they would on a JetFormBuilder submission, and custom validation registered in JetEngine continues to apply on cell edits.

Yes. SleekView complements the REST API by giving the same data a working admin table, useful for staff who don't build front-end listings or external integrations. The REST endpoints continue to expose CCTs and post types to external tools, and SleekView gives that data a UI inside WP Admin without duplicating the API layer.

Yes. Any view exports to CSV from the table header, with active filters and column order respected. The export reads from the same query the table is showing, so the file matches the on-screen state exactly. Useful for backups, moving content between staging and production, or feeding CCT data into an external tool.

Yes. SleekView is admin-only and reads from JetEngine's own data, so JetSmartFilters, JetThemeCore, JetFormBuilder, JetBooking, and other Crocoblock plugins continue to work as before. There's no overlap in functionality; SleekView fills the admin-table gap that JetEngine itself doesn't cover.

JetEngine's query builder remains the way to define reusable queries that drive listings, dynamic widgets, and REST endpoints. SleekView is for ad-hoc admin work that doesn't need a saved query committed to a widget: filtering, sorting, and inline editing across CCTs and post types. Both can coexist on the same model.

Yes. CCT custom tables are designed for scale, and SleekView paginates against the same indexes JetEngine uses. Heavy relation columns load on demand so the initial query stays lean, and saved views don't pre-fetch anything until they're opened. Tens of thousands of rows are routine.