I have a parent model with a child model that has one or several (up to about five) records. I want a page that shows some parent info at the top, a set of fields and UI-only fields on each child, and actions that execute making changes to any/all of the parent and child model records. I’d love to show a field editor with the parent model, then tab set below that with a tab for each record in the child model, each with an identical content for that record. I guess what I’d ideally want seems to be a cross between a tab set and a queue, where I can show model records across multiple tabs and save them all with a single button at the top of the page.
I thought about using a table with drawers, but the necessary field editor for the child model is too impractical to render as a table drawer, and the table will look silly with only the “name” column or only one record.
A queue would get me the dynamic navigation list, though it is only on the side (right?) and would require using a page include such that users would have to save each record/tab separately (right?), which becomes very clumsy for the functionality I want.
I considered just making a field editor that repeatedly renders for each child record (vertically on the page) instead of tabs. I’d say that normally would be a fine compromise. However, I actually need a panel set with some columns and rich text fields for each child record, and there doesn’t seem to be a way to make such a component repeat for each child record.
Is there a way to create a dynamically generated tab set (or it’s equivalent) as a UI for my child model?
I also was looking to implement a design that needed to create a tab for each record. I instead used a field editor combined with a queue to make this happen, similar to your middle bullet but without the user having to remember to save:
(you would still be stuck with the vertical list that queues offer, but it gives you all the functionality needed)
For example, say you want to load an account page and have access to each account contact:
Create three models:
Account - loads single account record
Contacts - loads all contacts related to account
ActiveContact - create a condition where ID= specified value with nothing listed, then set to filterable default off.
Add a queue to the page using the contacts model. For the actions, have it save the ActiveContact model(this is important!), set the condition so the ActiveContact ID = ID (from queue), and then re-query the ActiveContact model.
Then add a field editor or whatever else you would have put on the tabs as referencing the ActiveContact.
How about a custom table view? You can create your own ‘card’ with the fields you want and a single save button would handle committing changes to Salesforce (plus you’d get the other table ‘goodies’ such as filtering, searching; etc.).
