Best Practices on a form that will be a lot of yes/No questions? - InfoPath Dev
in

InfoPath Dev

Best Practices on a form that will be a lot of yes/No questions?

Last post 03-04-2014 09:38 AM by wilkies0106aw. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 03-03-2014 12:59 PM

    Best Practices on a form that will be a lot of yes/No questions?

    I just got the specs from the users on the form/questionaire I need to build in Infopath and host in Sharepoint. It will contain 90 questions and yes/No answers.

    So it looks like 2 fields, 1 for the question text and one containing Yes/No option buttons. People from various countries will be filling out their individual form based on the template.

    I plan to have them select their country from a drop down listbox and name the form with their country and theri name or something like that.

    How would I do reporting on this when all the forms are in. Any design issues here..... Would I merge all the forms and export everything to excel...is that a sound way to go?

     

    Thanks for your help.

     

     

  • 03-04-2014 09:38 AM In reply to

    Re: Best Practices on a form that will be a lot of yes/No questions?

    Yes, you can export to Excel and/or create an Excel Dashboard for managers with slicers etc.

    You can also use the various chart webparts. Depends on what your reporting requirements are.

    Note, if connecting to a SharePoint library, security is controlled via the SharePoint library permissions. i.e. if you don't see X in the library, you don't see it in Excel.

    Several things to note that I've discovered:

    If you're going to print out a form, I've found it better to use a drop down control and not an option control.

    When highlighting mandatory fields which must be answered, conditional formatting of a drop down control is far more 'in your face'.

    Recording answers.

    On a drop down control, set your values to numbers and your display name to text i.e. 0=No, 1=Yes.

    The 0 and 1 get recorded in the library, not the Yes/No. You can always create calculated columns, if people what to see Yes or No.

    This makes doing math much easier, especially if you're going to use pivot tables - Pivot Tables don't like text.

    Hide a submit button until all required questions have been completed.

    In addition I avoid using the names of people in form names because:

    Not all characters work with a url.

    I tend to use a translate function in a MyFileName which is set if blank on form load - translate(now(), !:-T","")

    In addition, Names can be very long and use up a lot of characters in web url.

Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.