• 6

    Deleting a Survey

    Suggested by Miia Fohlin Rejected  1 Comments

    When I create a new Project, CV automatically creates a new Survey under it and if I want to delete that automatically generated Survey, the system will delete also the Project. This is a nuisance as I would need to create a new Project where I would copy existing Surveys from other Projects and I do not need the original automatically generated blank Survey at all. But I cannot delete it as the system would delete also the Project. Deleting only Surveys should be allowed.

  • 4

    API Support for forms Pro cababilities

    Suggested by Kunal Murarka Rejected  1 Comments

    At this point we can read data from survey specific entities in CDS and use Microsoft Automate to create survey invite. Having direct API Support for various forms pro survey function/capability will increase the boundary to serve various real-life use case.

  • 3

    Truncation of Response in Dataverse

    Suggested by Graeme Gourlay Rejected  2 Comments

    I have found that the text responses in Dataverse are being truncated to 100 characters. I have surveys that have free-form "long answer" and respondents are exceeding 100 characters. In Customer Voice itself the responses are not truncated. They are truncated in Dataverse which is causing issues when outputing from Power BI or Excel. Please consider this a high priority fix; I have users losing confidence in Customer Voice and requesting regression to a previous toolset.

  • 2

    Form Parameters: Remove or allow deletion of default variables

    Suggested by Rejected  0 Comments

    When creating new forms 3 variables are defined by default: FirstName, LastName and Locale. Currently only Locale can be removed. The option to remove FirstName/LastName variables needs to be added as not all surveys will require these.

  • 1

    Ensure that Voice of the Customer surveys have valid and accessible HTML

    Suggested by Richard Lund Rejected  0 Comments

    Currently the HTML produced by VotC generates warnings and errors when passed through the W3C Validator at https://validator.w3.org/ and the Web Accessibility Validation Tool at http://wave.webaim.org/. While none of the issues appear to be critical in rendering the survey or making it accessible, the errors/warnings raise concern. Some look to be relatively easy to fix (meta tag at the top of the document outside the html tag for instance).