This pattern comes up more and more, so I thought I’d build a simple example.
We already know that you can copy rows using the “add rows to another table” action. But sometimes we want our end user audience to provide some input first. The attached app shows a simple way to do this.
At its most basic, the design has an “extra” table whose only real purpose is to allow data entry of a single row of info. This info could then be used when calling the “Copy” action.
So… in our fictitious example, an event planner wants to be able to add line items to an event. They have a library of line items, and they have a list of clients who have events.
In the menu, we have provided “step 1” and “step 2”. (This could all be done on a dashboard as well).
Step one is that the event planner picks which event they want to work on, and step two allows them to add line items to that event:
It only has one single action in it. Enjoy and best regards.