How to Install and Configure Survey Plus Web PartSurvey Plus Web Part extends SharePoint’s native survey capabilities by adding richer question types, improved reporting, conditional logic, and a more user-friendly interface. This guide walks you step-by-step through installation, configuration, and best practices to get the most out of Survey Plus Web Part in your SharePoint environment.
What you’ll need before starting
- A SharePoint site where you have at least Site Collection Administrator permissions (farm/admin rights may be required for some deployment methods).
- The Survey Plus Web Part package (typically a .wsp or an app package depending on the vendor and SharePoint version).
- A testing site or a non-production environment to validate installation first.
- Browser with access to the SharePoint Admin Center (for SharePoint Online) or Central Administration (for SharePoint Server).
1. Determine your SharePoint version and package type
Survey Plus Web Part packages differ by SharePoint version (SharePoint Online, SharePoint 2019/2016/2013). Confirm whether you have:
- SharePoint Online (modern/classic experience) — usually an SPFx package or App Catalog package.
- SharePoint Server (on-premises) — often provided as a .wsp solution or farm-scoped package.
Installing the wrong package will fail; check the vendor documentation or download page for the correct version.
2. Backup and test environment
Always install first in a development or staging site:
- Create a site collection snapshot or export the site if possible.
- Note existing customizations that may conflict with web parts or scripts.
- Ensure you have a rollback plan (restore point or backup) in case of issues.
3. Installation — SharePoint Online (SPFx / App Catalog)
- Upload package to the App Catalog:
- Go to the SharePoint Admin Center > More features > Apps > App Catalog.
- Open the App Catalog site, then go to Apps for SharePoint and upload the Survey Plus package (.sppkg or .app).
- Deploy the solution:
- When you upload, you’ll be prompted to trust the package. Check permissions and click Deploy (or Trust).
- If the package includes tenant-scoped assets, approve tenant deployment when requested.
- Add the app to a site:
- Navigate to the site where you want the web part.
- Site contents > New > App > find Survey Plus and add it.
- Add the web part to a page:
- Edit the page (modern or classic) and insert the Survey Plus Web Part from the web part toolbox.
4. Installation — SharePoint Server (WSP / Farm solution)
- Upload WSP to the Solution Gallery or Central Administration:
- Central Administration > System Settings > Manage farm solutions > Upload solution.
- Deploy the WSP:
- After uploading, select the solution and choose Deploy Solution. Choose the web application(s) where you want it deployed.
- Activate features:
- Go to Site Settings > Site collection features (and Site features if applicable) and activate Survey Plus features.
- Add the web part to a page:
- Edit a page, Select Insert > Web Part, locate Survey Plus under the vendor category and add it.
5. Initial configuration
After installation, configure global settings (some settings may be available only to site owners or admins):
- Access the Survey Plus configuration page (often available in Site Contents or via a settings gear on the web part).
- Common configuration options:
- Enable/disable specific question types (matrix, rating, file upload).
- Set default language and regional settings.
- Configure storage options (where responses are stored — lists, external DB).
- Permissions for who can create, edit, or delete surveys.
- Notification settings and email templates for responses and reminders.
- Data retention and anonymization policies.
6. Create your first survey
- From the site where Survey Plus is installed, open the Survey Plus app or web part and select Create New Survey.
- Define survey metadata:
- Title, description, start/end dates, response limits.
- Add questions:
- Choose question types: Single choice, multiple choice, text (single/multi-line), rating, matrix, file upload, date/time, conditional branching.
- For each question, set validation rules, required flag, default values, and help text.
- Configure branching/logic:
- Use conditional rules to show/hide or skip questions based on prior answers. Test logic with several scenarios.
- Permissions and sharing:
- Decide whether the survey is anonymous or tied to user identity. Set item-level permissions if responses should be restricted.
- Preview and test:
- Use preview to verify layout and logic on desktop and mobile. Submit test responses and confirm storage and notifications.
7. Reporting and exporting results
Survey Plus typically provides built-in reporting and export features:
- Built-in dashboards: charts and aggregate summaries for each question.
- Export options: Excel, CSV, PDF, or connection to Power BI for advanced analytics.
- Filtering and segmentation: filter responses by date, user, or custom metadata fields.
- Data retention/export policies: schedule exports or enable auto-archiving if required.
Example: export to Excel for ad-hoc analysis, or connect the survey response list to Power BI for interactive dashboards that refresh on a schedule.
8. Advanced configuration and integrations
- Power Automate: trigger flows on new responses (send approvals, save attachments to document libraries, notify teams).
- Power BI: connect live to the responses list or export to a dataset for richer visualizations.
- External systems: integrate with CRM or HR systems via connectors or APIs if the web part offers webhooks or REST endpoints.
- Localization: enable multiple languages if the package supports resource files or in-product translations.
- Theming: match survey styles to your site using CSS overrides or theming options provided by the web part.
9. Security and compliance
- Ensure permissions follow least privilege: only necessary users can create or manage surveys.
- If responses contain personal data, enable encryption at rest and ensure retention policies meet compliance requirements.
- Audit logs: enable auditing to track who created/edited/deleted surveys and responses.
- For anonymous surveys, verify no identifying metadata is captured inadvertently (IP addresses, usernames).
10. Troubleshooting common issues
- Web part not visible: check feature activation, web part gallery, and permissions.
- Deployment failed (SharePoint Online): ensure package is trusted and tenant deployment is allowed.
- Conditional logic not working: verify rule order and test with multiple answer combinations.
- Exports blank or incomplete: confirm response list permissions and that responses were committed (not in draft).
- Performance issues: large surveys can be slow—use paging, limit heavy client-side scripts, and offload reporting to Power BI.
11. Maintenance and updates
- Apply vendor updates in a staging environment first. Read release notes for breaking changes.
- Monitor usage and storage; archive old surveys and responses.
- Periodically review permissions and data retention settings.
- Keep a change log for survey templates and major configuration changes.
12. Best practices
- Start simple: design surveys with the minimum necessary questions.
- Use branching sparingly to avoid complexity.
- Provide clear instructions and progress indicators for long surveys.
- Test across devices and browsers.
- Use templates for recurring surveys (employee feedback, event registration).
- Protect respondent privacy and be transparent about data usage.
13. Example: Quick setup checklist
- [ ] Confirm package matches SharePoint version
- [ ] Backup or use staging environment
- [ ] Upload and deploy package to App Catalog or Central Admin
- [ ] Activate features and add app to site
- [ ] Configure global settings and permissions
- [ ] Create and test survey with branching and notifications
- [ ] Set up reporting/export/power automate flows
- [ ] Review security, compliance, and retention
If you want, I can: provide step-by-step Power Automate flow examples for sending notifications on new responses, create a sample survey template with branching rules, or draft a short test plan to validate installation. Which would you like next?
Leave a Reply