No. SleekView reads from frm_items and frm_item_metas with scoped queries. Each upvote increments the mapped number field on the same item row through the Formidable update API, so the admin entry view and the public board always agree on every vote count and status value.

Yes. SleekView honors the same capability checks Formidable uses for entry visibility. Entries restricted by user role or by Pro entry permissions are filtered out of the public board automatically. You can also require login before voting if your site uses Pro registration forms heavily.

Pro hooks fire normally. Because SleekView uses the Formidable update API, hooks subscribed to item update events trigger on each vote write. If you have a hook that does heavy work on update, consider scoping it to specific status changes rather than every update, since votes update items frequently.

Yes. Views and SleekView read the same underlying data and do not conflict. Many teams use Views for an admin or member-only data view and SleekView Feedback for the public ranked board on the same form. Both keep showing live entries because both query the same items table directly.

Yes for rendering simple fields. Repeater sections do not render as the card title or status, since those are single-value fields. You can map a non-repeater field as the title and a repeater count as a secondary metric on the card if needed. Repeater data stays intact on the form side itself.

Add a hidden number field with a default value of zero. SleekView writes upvote increments to that field on each item. Existing entries start at zero and rise as votes come in. A short WP-CLI command can backfill older entries with a starting count if you want to seed initial activity on the board.

No. Conditional logic decides which fields a visitor sees during submission. By the time the item is saved, only the resolved values exist. SleekView reads those, so any field hidden by conditional logic on a given submission simply has no value on that card, no pill or column rendered ever.

Yes. Calculations run on the form before save and write a numeric value to the item. SleekView can use that value as the vote count, a sort key, or a secondary metric per card. The calculation continues running on every submission, the board just reads the latest result for any view.