SplatDev.Umbraco.Plugins.Surveys 2.4.0

UmbracoCms.Plugins.Surveys

A full-featured survey builder plugin for Umbraco 13 and Umbraco 17.

Features

• Create surveys with multiple question types: Multiple Choice, Free Text, and Rating
• Publish/unpublish surveys with optional expiry dates
• Collect respondent email addresses (optional)
• View aggregated results per question and option
• U17 backoffice dashboard (Lit 3 web component)
• U13 backoffice dashboard (AngularJS)
• Razor view component for embedding surveys in Umbraco templates
• EF Core against Umbraco’s database (schema: surveys)

Targets

API Endpoints

Usage in Templates

@* A fixed survey: *@
@await Component.InvokeAsync("Survey", new { surveyId = 1 })

@* Or the one chosen on this page with the Survey property editor: *@
@await Component.InvokeAsync("Survey", new { surveyId = Model.Value<int>("survey") })

Building the Client

cd client
npm install
npm run build

The built file will be placed in App_Plugins/Surveys/dist/.

Database Schema

Tables created in the surveys schema:

• Surveys - Survey definitions
• SurveyQuestions - Questions per survey
• SurveyOptions - Answer options for MultipleChoice/Rating questions
• SurveyResponses - Individual response submissions
• SurveyAnswers - Per-question answers within a response

Run EF Core migrations to create the tables: The tables are created for you the first time the site starts: the plugin runs its own Umbraco migration against the database Umbraco is already using, on whichever provider it is configured with — SQL Server or SQLite. There is nothing to scaffold and nothing to run by hand.

Changelog

2.4.0 — 2026-08-23

The Razor view behind @await Component.InvokeAsync(...) is now compiled into the package. It was previously carried as a loose file that nothing packed, so the component threw "view not found" on every install and the front-end usage shown in this README could not have worked.

The view also still referenced the package's pre-rename namespace, so it would not have compiled even had it shipped. That is fixed, and the view is now built with the project — a broken view fails the build instead of failing a visitor's request.

2.3.0 — 2026-08-23

• A content editor can choose which survey a page shows. The view component takes a numeric id, so until now putting a survey on a page meant knowing that id and writing it into a template by hand — there was no way to pick one.

2.2.4 — 2026-08-22

• Surveys with questions can be listed. The listing loads each survey's questions, every question carries a reference back to its survey, and the serializer looped — so the endpoint returned 500 as soon as a survey had a single question. A survey with no questions serialized fine, which is why an untouched install looked healthy.
• Editing a survey no longer returns 500. A body the server could not read arrived as nothing at all and the first thing that touched it threw; sending a question type outside the allowed set was enough. It now answers 400 and says what was wrong.
• The API returns a plain shape — questions, their options and a response count — rather than the database entities.

2.2.3 — 2026-08-21

• README no longer tells you to scaffold EF Core migrations by hand — the plugin creates its own tables on first start, on SQL Server or SQLite.

2.2.2 — 2026-08-21

• Dashboard now sends the backoffice token with its API calls. On Umbraco 17 those calls were arriving unauthenticated and coming back 401, which the dashboard rendered as an empty state rather than an error.
• A failed request now raises a notification instead of leaving the dashboard looking like there is simply no data.
• The plugin's tables are created on startup. They were never created before, so anything touching them failed on a fresh install.
• Runs on SQLite as well as SQL Server. It previously assumed SQL Server and failed with "Keyword not supported: 'cache'" on the database Umbraco's installer offers by default.