-
Branding template
Suggested by Nicolai Schjørmann – Under Review – 4 Comments
Make it possible for organizations to create a branding template with images and colors, so that all users in the organization will be able to create surveys with the same look and feel no matter who is creating it. -
Match Date field format to customer locale settings
Suggested by Inspired Admin – Under Review – 2 Comments
Date field in surveys always seem to follow the US format (M/d/yy), despite having a different region and locale setting for the Microsoft Office profile. We want the date field to be customisable, most importantly (dd/M/yy) format which is used in other parts of the world. -
UX Enhancements for Header/Banner
Suggested by Charlotte Alberta – Under Review – 2 Comments
Make the header smaller/more customization. Currently it takes a HUGE amount of real estate when someone first clicks on the survey and that will decrease survey response rates. Either give me more options to brand it, empower me to make it the size for my needs, or get rid of it. -
Survey Footer - Privacy Statement URL - introduce levels (tenant, environment, project, survey)
Suggested by Pasha Pilgrim – Under Review – 1 Comments
Idea: Customers should be able to provide Privacy Statement on various levels relevant to their organization: tenant level / environment level / project level / survey level Context for the idea: Currently, Microsoft forces the customers to provide a Privacy Statement URL on a tenant level (Azure Portal > Azure Active Directory > Properties > Privacy Statement URL). This is done through displaying the following automated message in the footer of each survey: "The owner of this form has not provided a privacy statement as to how they will use your response data. Do not provide personal or sensitive information." The problem we, as a large organization with hundreds if not thousands of business units, find with the current state is that the privacy statement can only be provided on the tenant level, which makes it literally impossible to make this statement relevant to a specific responder group, as it has to be kept super high level and general. In our case it would make more sense if we could have a separate Privacy Statement per survey or at least per project. -
Default Language set by choise NOT by browser language
Suggested by Frank Peters – Under Review – 1 Comments
The Default language in a survey is set by browser native language setting of the User. It can not be changed to set up surveys for different default language. This is a huge missing functionality (lets says a big GAP) for all who want use Customer Voice in international organizations. -
Allow lookups on questions
Suggested by Clare Norfolk – Under Review – 0 Comments
Allow lookups so the user starts typing and the option list gets smaller. For example, users in AD. The question is who is asking for the survey to be completed. The answer must be a person in the business. The lookup will suggest names as you start typing their name -
Export Survey Question Number
Suggested by Graeme Gourlay – Under Review – 0 Comments
When using the export functionality, it would be ideal to have the question number in the export file. This will enable external tools, like Excel, to display the questions in the same order as they survey itself. -
Add support for question templates and reusable questions
Suggested by Lars Fastrup – Under Review – 0 Comments
In scenarios where the same questions are asked across many surveys, it would be extremely useful to be able to create a predefined collection of questions that survey authors can pick and choose from. Today it is somewhat possible by copying an existing survey. But this should be easier by also have templates questions. I envision two ways to offer this kind of functionality: 1. Selected questions are copied into the new survey. Authors can then modify it as needed. 2. Selected questions are referenced in the new survey. Question is locked and authors cannot modify it. It would be great to have both options. It is critical that the questions have a permanent question ID that can later be used in Power Automate flows to process survey responses in CDS. -
Option to add branching rule on a choice type question with other option
Suggested by Supreet Kaur – Under Review – 0 Comments
Currently, if we create a choice type question with "Others" option we cannot apply branching rule if the response is "others" as the option is not displayed in the branching rule responses. Please add this feature. Thanks!! -
Randomization of question answers
Suggested by Poul Melbye – Under Review – 2 Comments
Would be nice to have the option to rotate/randomize answer options to eliminate eventual order bias