Hi, Richard,
That’s an interesting use case. So you’re working with multiple records in a single model, but you want to show a single record from the model on each tab?

I think there are couple ways you could tackle this:

1. Create a model (off of the same object) for each tab. It’s a little clunky, but shouldn’t be too bad if you have a known number of tabs. The upside to this is it would allow the user to easily jump back and forth between steps.


2. On each step, run a few actions: (a) Save the model, (b) Empty rows from the model, (c) Create a new row in the model. The downside to this is it really isn’t optimal for the user going back a step in the process. If you go with this approach, I would recommend using the Wizard component rather than the Tabset. On each Wizard step, provide a button to go forward to the next step, but not to go back a step.

Hi Emily, 

Thanks for the response!

I am currently already using a Wizard on a bigger scale and wanted to potentially avoid, using a wizard inside of a wizard. (I was not sure the implications of this, but if it is a usable alternative let me know)

I have tried to use actions to set this up; between setting conditions when re-querying a model, deleting rows, creating new rows, etc. etc. Unfortunately, I have not been able to successfully make this happen through actions. 

The main purpose behind this was that a user does not have to scroll down to add 3 or 4 records of the same kind, all requiring the same fields and related objects and fields. 

Again I appreciate the response!

Richard

Richard,
I would go for the approach of using multiple models (1 model for each record they need to submit). Do you think that will work for what you’re trying to do?
Emily

Emily, 

I will look into whether or not this will work for my use case and post back if anything comes up! Again I appreciate your time and the response!

Thanks, 
Richard

Hi Richard -

If you know up-front how many Outlets will be needed, I think Emily’s approach would be the simplest.  However, I’m guessing the number of Outlets that a user would want to create is unknown in which case, multiple models, at least in a declarative manner, would not suffice.

I would need to understand your scenario & use cases in more detail to be sure, but I believe there is a way you can accomplish what you are after.  In short, it would require javascript as you would need to apply a context to the field editor on each tab and/or dynamically create components on the tab.

One alternative to multiple tabs would be to use a table and a row action that displays a popup (the popup would replace the tab).  This would allow users to create new Outlets and modify their information all from one screen with a single save button at the top.

If multiple tabs are needed and your open to javascript based solution, let me know and we can explore further.