I built a project management app. When I create a new project it requires 3 tables (objects). Which are:
Customer
User
Project.
The manual workflow is:
goto customers page
Create a customer record in the customer table
Goto user page
Create a user record in the user table
goto projects page
Create the project record in the projects table with fields that allow me to select the newly created customer and the newly created user
My first attempt at simplification was to put all those table onto a single admin page to reduce traveling to different pages. Nice but still feels clunky.
Ideally I would have a single data entry workflow that allows me to create the project, and while doing so, also select a customer or create the customer (if needed) and the same for choosing the linked users.
I can offer a solution for a 2 step flow, but not a three step.
For example, if you have a detail page for a project, you can add a linked list onto that page to show the customers that belong to that project (with ability to create a new customer). Then when you create a new customer, you can assign that customer to the related project page (current detail item). That would give you the ability to create a new customer that is assigned to the project already.
Thanks JJ, I am just getting back to reading this now. This problem went away when I integrated my CRM into my base. Now I have an external automation that uses the CRM object data to create matching records in my base that represent softr users, customers and projects.