Yes. Any value written to wp_postmeta for the metform-entry post type can be pivoted into a column. That covers text, email, number, select, checkbox, date, file upload, and payment fields. The parent form's field configuration provides the labels and types so columns are typed correctly.

Yes. SleekView writes through MetForm's entry update path where supported, falling back to update_post_meta with conflict detection on post_modified. The write respects the field's original type and any sanitisation hooks the plugin registers.

SleekView reads the unique meta_key values for entries belonging to the selected form (or across forms) and exposes each as an addable column. The pivot runs at query time using a join, so new form fields appear immediately without a rebuild step.

Yes. Add the parent form ID as a column and either filter to a subset of forms or leave it open. Only meta keys shared across the selected forms become broadly useful columns; SleekView labels each so the chooser stays sensible.

Payment-field values (Stripe, PayPal, transaction IDs, status) live in wp_postmeta as standard meta keys. SleekView surfaces them as sortable, filterable columns and cross-form payment audits filter on payment-status meta without per-form scripting.

Upload-field meta stores the file URL or attachment ID. SleekView renders these as filename cells linked to the file or media library, and the filter "has attachment" works on the meta presence.

MetForm's data retention settings affect wp_posts and wp_postmeta directly. SleekView reflects the resulting state, so deleted or anonymised entries show whatever placeholder MetForm wrote during processing.

The query joins wp_posts and wp_postmeta with form-aware filters applied first. For large tables, scope a view by date range and the column chooser only inspects meta keys in that window, keeping the UI responsive.