Yes. The gquiz_* meta keys are written by the Quiz add-on. Without it there's no quiz data in gf_entry_meta. SleekView detects the keys' presence and lights up the quiz-specific column suggestions automatically.

Yes. SleekView writes through Gravity's CRUD APIs where field types allow, firing gform_after_update_entry. For numeric quiz fields, direct DB writes with conflict detection cover edge cases. Use this for regrade scenarios, not regular grading.

Each quiz question stores its correctness as a meta row keyed by field ID. SleekView surfaces these as boolean columns (correct/incorrect) you can add to the table individually. Sort and filter by them to find common wrong answers.

Yes. Pivot the regular Gravity field values (essay-type questions or follow-up explanations) alongside the quiz score columns. The pivot mechanism is identical; quiz keys are just specific meta keys.

Yes, each attempt is its own row in gf_entry. Filter on user ID or email and sort by date to see all attempts; pivot a max-score or latest-attempt view via saved views with appropriate sort + limit.

Use a saved view filtered to a single user with one row per attempt; rolling aggregates live downstream in your reporting tool. SleekView is the operational layer, not a stats engine; the right grouping varies by curriculum.

If the form doesn't capture identity, attempts still record with score data but no user. Useful for public knowledge checks or marketing quizzes. Filter to has email when you need a follow-up list.

If you've added a Gravity Flow workflow step on top, attempt rows carry workflow status in additional meta. SleekView can surface those alongside quiz scores so you see attempt result, plus approval state in one row, useful for compliance gating on top of a passing score.