SleekView Charts for JetEngine
Read directly from JetEngine CCT custom tables, postmeta, and the JetEngine relations table, then chart bookings, capacity, and pipeline without designing a Listing template just for admin reporting.
♾️ Lifetime License available
JetEngine builds the model, charts finally summarise it
JetEngine ships Custom Content Types backed by their own database tables, custom post types stored in postmeta, and a relations layer for one-to-one, one-to-many, and many-to-many connections. The default admin lists rely on basic columns and richer presentation comes from JetEngine Listing templates, which are great on the front end and awkward as an admin reporting surface.
SleekView Charts reads each CCT and post type directly. CCT custom tables are queried for speed, postmeta-backed fields surface through the meta layer, and the relations table resolves to titles or counts. A Number card pins total active sessions. A Pie shows status mix across an event run. A Bar ranks instructors by sessions taught. An Area card plots bookings per day so capacity pressure is a curve, not a manual count.
The chart layer coexists with the rest of Crocoblock. JetSmartFilters, JetThemeCore, and the JetEngine REST API keep reading the same CCT tables and relations data SleekView reads, with no sync layer in between. Saved chart views per role let event ops, sales, and support each get the cards that match their workflow.
Workflow
How SleekView Charts reads JetEngine data
Pick a model
Map fields to chart cards
Filter and group
Save per role
Sample dashboard
Charts you can build from JetEngine data
Active CCT records
Count
Sessions by status
Count
group by status
Sessions per instructor
Count
group by instructor_relation
Bookings per day
Count
group by booking_date
Comparison
Default JetEngine reporting vs SleekView Charts
Default JetEngine admin
- CCT admin lists show basic columns and require custom code for more
- Building a usable summary often means a JetEngine Listing template
- Relations counts (sessions per instructor) need a separate listing
- Bulk aggregation of meta fields needs query builder runs or exports
- Hard to share a controlled chart dashboard with non-admins
SleekView Charts
- Number cards for live counts across CCTs and post types
- Pie or Donut cards for status, category, and select-field distributions
- Bar cards ranking related posts using the JetEngine relations table
- Area or Line cards for booking and signup trends over time
- Same filters as the SleekView table apply to every chart card
Features
What SleekView Charts gives you for JetEngine
CCT tables drive fast charts
JetEngine CCTs use their own database tables, and SleekView queries them directly. Dashboards stay fast even on datasets with tens of thousands of rows because there's no postmeta join overhead.
Relations as chart sources
One-to-one, one-to-many, and many-to-many relations from the JetEngine relations table back Bar cards that count related items per anchor, with no manual join setup.
Type-aware aggregations
Numeric, date, and currency meta fields aggregate correctly because SleekView reads the underlying type from JetEngine's registry, not the raw meta string.
Audience
Who builds JetEngine charts dashboards with SleekView
Booking and event sites
Sessions by status, instructors by load, and bookings per day on one dashboard. Capacity pressure shows up as a curve before a session goes to waitlist.
Operations teams
Live status mix during sign-up surges, with saved views like Today's almost-full sessions so the team knows where to focus without scrolling a CCT admin list.
WordPress developers
Hand clients a per-CCT dashboard that tracks the schema as it evolves. SleekView reads the registry, so adding a field surfaces it in the chart picker on the next open.
The bigger picture
Why JetEngine sites need a chart layer
JetEngine's strength is that it lets you build serious content models without writing migrations: CCTs in custom database tables, post types in postmeta, and a real relations layer. The trade-off on Crocoblock-heavy sites is that the admin reporting story is light. Listing templates were designed for the front end, and using them as admin dashboards is awkward because they render through the theme builder and need a developer or designer touch every time the model changes.
Teams running event sites, booking platforms, or directory sites end up either building separate dashboard pages with JetEngine widgets or accepting that the admin is for editing one record at a time. SleekView Charts fills the gap. The same CCT custom tables, the same post meta, the same relations layer, now exposed as Number, Pie, Bar, and Area cards that refresh as records change.
Listings still own the front end; SleekView owns the back-end summary surface where the team triages the model.
Questions
Common questions about SleekView Charts for JetEngine
Yes. CCTs are a first-class chart source. The chart layer queries the dedicated 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 dashboard tracks the model as new fields are added.
Yes. One-to-one, one-to-many, and many-to-many relations resolve through the JetEngine relations table and back Bar cards that count related items per anchor. Sessions per instructor, bookings per session, and child records per parent all become single-card summaries.
Yes. SleekView reads the underlying meta type from JetEngine's registry, so price fields sum as numbers, date fields group by day or month correctly, and capacity fields aggregate as integers. Raw string ordering from a generic meta sort is replaced with proper type-aware queries.
Yes. The REST API continues to expose CCTs and post types to external tools, and SleekView Charts gives the same data a UI inside WP Admin without duplicating the API layer. Both can run on the same model because they read the same underlying tables.
Yes. SleekView is admin-only and reads from JetEngine's own data, so JetSmartFilters, JetThemeCore, JetFormBuilder, and other Crocoblock plugins keep working. There is no overlap in functionality; SleekView fills the admin-table and chart-dashboard gap that JetEngine itself doesn't fully cover.
JetEngine's query builder remains the way to define reusable queries that drive listings, dynamic widgets, and REST endpoints. SleekView Charts is for ad-hoc admin reporting that doesn't need a saved query inside JetEngine: aggregating, summarising, and filtering without committing the query to a widget.
Yes. CCT custom tables are designed for scale, and chart queries hit 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.
Yes. Each saved chart view is gated by WordPress capability, so an events dashboard, a sales dashboard, and a support dashboard can coexist with role-appropriate cards. The underlying JetEngine data is the same; the chart selection is per role.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout