Hi Rebecca - what do you want to do with the rows in the wizard? My first instinct is that you probably want to adopt them into another model, but that depends on what you’re doing with the selected rows.

Here’s a basic page that captures what you’re after.

So im trying to recreate a screen flow from my salesforce org thats really just too many screens, the rows that are selected will then be used for the users to answer questions to. Basically you are my customer you have 4 of my products installed & its your yearly inspection or having an issue with one, my technician pulls up your work order launches hopefully the skuid page that goes through a series of steps, first is selecting which product(s) worked on it could be 1 or could be all of them and then takes the information from the row looks up the individual item and the user answers question on that item and then its repeated for the rest of the rows selected of course, Does that make sense?

Yeah that makes sense. Josef’s example below shows how to get the list down to the selected items. Do you need help beyond getting it down to the list of what is selected?

I will try that out and if I do let you know . Would you know how to pass an ID into the page via Field Service Lightning Mobile App?

I think you could try what Mark & Erik are discussing in this conversation - https://community.skuid.com/t/using-param-id-and-lightning

Do you know if i can save each row selected to individual model i am wanting to show fields for each one but on different pages, i dont want all the fields for each row on one page, does that make sense?

Yeah, the least complex solution may be to have them step through things 1 product at a time from the get go. Instead of having them select all the products at once to start, have row actions where they select which one they want to answer questions about. When they finish answering questions bring them back to the beginning so they can select another product.

There are ways to guide them through it where they mass select then step through one by one, but it takes a bit more logic. It’s something along the lines of adding a UI only field to the adopted model (one with only the 4 selected products) that gets updated. When it’s updated, have a branch that checks to see if its the first row (a 2nd UI only formula field with {{index}} to see row . If it is then run whatever actions you have for determining what questions to show using that row as context & remove the row. After they finish answering have the same action run that updates all the UI formula fields, which will get the loop going again.