Yes. SleekView joins jet_fb_records to jet_fb_records_values so each field becomes a column. The agent UI scans the form definition and lists fields actually in use, including repeater children and conditional fields, so you pick from a real list instead of typing field names from memory.

Yes. JetFormBuilder Pro stores payment records in jet_fb_payments with status, amount, gateway, and transaction reference. SleekView joins them on record ID so a finance view can show submission and payment data on the same row — useful when reconciling Stripe or PayPal against your form pipeline.

Yes. SleekView writes through the plugin's action API where supported, so jet-form-builder/record-update, payment-status hooks, and any post-form notifications still fire. Bulk operations don't bypass these — they iterate through the API so the side effects match a manual edit.

Yes. JetFormBuilder's Insert/Update Post action stores the resulting post ID in the record's meta. SleekView resolves that ID to a posts row and surfaces title, status, and edit link as columns, so a record created from "Submit a listing" links to the listing it created without manual joining.

Yes. Repeater rows are stored as serialised values inside jet_fb_records_values. SleekView either flattens the count ("3 line items") into a column or expands the repeater into a related sub-table per record — useful when each submission carries an order with multiple items.

No — it's an additional admin surface. The default Submissions and form-editor screens stay where they are. SleekView gives sales, finance, and support teams the row-level views they actually use, without disturbing the form editor or the workflows your team already knows.

Queries hit indexed columns on jet_fb_records (id, form_id, status, created_at) directly. Field-value filters use a join on jet_fb_records_values with the field-name index. Aggregate columns (total spent, submission count) are opt-in per view since they're heavier; keep them off the default list and on per-contact detail views.

Yes. Pick a list of form IDs and SleekView returns records across all of them, with a Form column to disambiguate. Or scope a view to a single form and add field-specific columns that only make sense for that form — both patterns are supported in the same JetFormBuilder source.