One New Project Entry form to rule them all
Is there any way to create a form (for lack of a better or correct word) to enter in all the information for a new project? To expand on this. 1. A new project comes in and our admin clicks the Ne...
Forum Discussion
I think that you need to rethink the structure of your tables. If the data you are entering is really one for one with the Project record, then that data just belongs on a Form in separate sections, or even separate Tabs, now that we have Tabs.
If the Projects details are really child records, such as Tasks, then the best user experience will be to enable an option on the Advanced Settings for the Projects Record which say to save automatically when adding a child record.
So the user will just stat to do the data entry on the project record and when it comes time to add a true child, they will click ADD Task and the Parent Project record will save automatically. When they save the Task it will return to the Project.
If the Projects details are really child records, such as Tasks, then the best user experience will be to enable an option on the Advanced Settings for the Projects Record which say to save automatically when adding a child record.
So the user will just stat to do the data entry on the project record and when it comes time to add a true child, they will click ADD Task and the Parent Project record will save automatically. When they save the Task it will return to the Project.
I think that you're understanding my suggestion correctly.
For example if there is just one large text box for project description then that inherently belongs on the project record. But if one project has many tasks or one project has many contacts, then those two tables would be separate child l tables.
For example if there is just one large text box for project description then that inherently belongs on the project record. But if one project has many tasks or one project has many contacts, then those two tables would be separate child l tables.