Creating a survey - What is they best way to start?

[JTischler]

Hello Power App Geniuses!  

I have limited experience with PA, and its been a while since I have built anything so I am a bit rusty.  I am hoping that I can get some guidance on how to start out my survey.

The Use Case is post event training evaluations.  I have created a list on SP that consists of 30 columns, each column header is the question text.

The first two questions are:

1. Course name - This would have a drop down/combo box linked to a list of Courses  on SP

2 .Session date/time - This would be a drop down/combo box linked to a list of sessions on SP and Filtered by Course name selected in Question 1.

The rest of the questions are all a 1-5 scale, 1-10 scale or free text for comment.

I am wanting 1 screen per Question.

Whenever I connect to the SP list that has the questions, all of the questions pop up and I have to remove all except the one that I want to display.  Before I go and create 30 separate screens, is there an easier way to have this automatically create the 30+ screens with 1 question (data card) per screen?

Any other feedback or suggestions on how this could be configured would be greatly appreciated!

Thanks!

[mmollet]

If you want one per screen I would just make my own "form" out of controls and use a patch statment to upload the answers. You can use a label to show the question and the proper control based on the question then have a next question button that patches the answer to the data source. 

One thing you will have to decide is if the user will be doing this in one sitting or if you want to support saving and resuming where the user left off etc. This can be done by having another list with the username/email of the user as well as the ID of the row in the questions/answers database. So if I start and stop on question 8 then my row in the answers list will show my name, email, and the first 8 answers I gave. The other list should show my name, email, and the ID of the row in the answers list. Say it was 118. Next time the user logs into the app you cando a lookup in that second list and if you find one you can load that ID and if not you know it will be a fresh questioinaire. 

Hope this wasnt as confusing as I fear it was 😅

[TheRobRush]

Single screen,

OnVisible of Screen has UpdateContext({recordNum:1}) h

On this screen, place a gallery that has an items property of LookUp(ListName, ID=recordNum) //listname needs to change to your list name, and set gallery template size to self.height

Have a next and prev icon somewhere outside the gallery, like to left and right of it.

on left arrow you put, Switch(First(ListName).ID, recordNum, UpdateContext({recordNum:Last(ListName).ID}), UpdateContext({recordNum:recordNum-1}))

on right arrow you put, Switch(Last(ListName).ID, recordNum, UpdateContext({recordNum:First(ListName).ID}), UpdateContext({recordNum:recordNum+1}))

then inside the gallery jsut put the controls you want, first two controls would have a visible of thisitem.id=1 and then thisitem.id=2 so you get those two unique questin types, then the rest would share same control and its visible would be Not(Or(ThisItem.ID=1, ThisItem.ID=2))

[JTischler]

@mmollet Thanks, attempting to test your suggestion.  I have created just a few questions, 1 per screen.  Where do I put a patch statement, and how do I tie it to a Sharepoint column?

Expectation is to complete the survey in one sitting.