Yes. Piotnet stores field values as serialized data inside pafe_form_records. The dashboard reads the form definition, decodes the payload, and exposes each field as a chart dimension, including repeater children and conditional fields.

Yes. Piotnet's payment add-ons store gateway, amount, and transaction reference within the record payload. The dashboard surfaces these as chart fields so revenue, gateway mix, and payment-status charts work over the same data the table view shows.

Each repeater is a list of rows inside the record. The dashboard counts repeater rows per record (Sum of line items) or aggregates across repeater entries when the workflow needs that. Both patterns are supported.

Yes. When Piotnet creates a CPT post on submission, the resulting post ID stores in the record. The dashboard resolves that ID, joins ACF meta, and exposes any ACF field as a chart dimension. Useful for listing-style or directory forms.

No. The charts are read-only. Inline edits from SleekView's table view route through Piotnet's submission update hook, so webhooks and notifications fire. The dashboard itself is purely a read aggregation.

Queries hit indexed columns on pafe_form_records (id, form_id, created_at) directly. Field-value aggregations parse the payload, which is inexpensive on tens of thousands of records. For very large datasets, opt-in materialized columns can be enabled per form for frequently-queried fields.

Yes. Pick a list of form IDs and the cards aggregate across them with a form filter chip to scope when needed. Two patterns work: cross-form rollup or single-form deep dive.

It sees every record in pafe_form_records. To exclude tests, filter out the test source page or internal email domains before the cards aggregate. The filter persists with the saved view.