Yes. Piotnet Forms stores field values as serialised data inside pafe_form_records. SleekView reads the form definition, decodes the payload, and exposes each field as a column — including repeater children, conditional fields, and hidden fields populated by query strings or logic rules.

Yes. Piotnet's payment add-ons store gateway, amount, and transaction reference within the record payload. SleekView surfaces these as columns so a finance view shows submission and payment data side-by-side — useful when reconciling Stripe or PayPal against your form pipeline.

Yes. SleekView writes through Piotnet's submission update hook, so any custom action wired to record changes — webhooks, email notifications, ACF update sync — still fires. Bulk operations iterate through the same hook so side effects match manual edits.

Each repeater is a list of rows inside the record. SleekView gives you two patterns: a flattened column ("3 line items") for an at-a-glance count, or an expanded sub-table per record so each repeater row is its own line. Pick whichever matches the workflow.

Yes. When Piotnet creates a CPT post on submission, the resulting post ID is stored in the record. SleekView resolves that ID, joins the post and ACF meta, and exposes any ACF field as a column — so a submission that creates a listing shows the listing's status and ACF data inline.

No — it's an additional admin surface. The default Piotnet Forms screens stay where they are for editing forms and reviewing single submissions. SleekView gives sales, finance, and support teams row-level views without disturbing the form-editor experience your team already knows.

Queries hit indexed columns on pafe_form_records directly (id, form_id, created_at). Field-value filters parse the payload — cheap on tens of thousands of records. For very large datasets, opt-in materialised columns can be enabled per form to push frequently-queried fields into dedicated indexed storage.

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 fields specific to that form — both patterns work from the same Piotnet source.