Managing Project Tasks & Status
Let's say that I have a Projects table with a Status field where each status acts as a state that drives which Role is tasked with working on that project so that the Project can advance to the next s...
Forum Discussion
I'm not understanding why Josh can't use the native button set up by the native wizard to import the stabndatd set of temp,acted tasks. That button can be also natively configured to import unlimited levels of grandchildren.
I agree, that there is no concern about creating a whole lot if task records. They are lightweight records. You could have 100,000 of them with no performance o r space limit problems.
I agree, that there is no concern about creating a whole lot if task records. They are lightweight records. You could have 100,000 of them with no performance o r space limit problems.
- Say you use the 'native' solution. Your process would be...
I have a client, I need to make a new project.
So I go find my 'template project' in my project table. And do the copy master detail record option. Then when it is copied, I associate it with the client.
Sure its one extra step, but do it a lot...
Then you need to make sure that you account for all of those 'template' projects in your reporting because they are stored in your live tables, otherwise it can mess up your reports. So you have to add an extra filter to every single report on the project table, and every single report on the standard task table.
Now assume you have 3+ type of task list, you have to make fake projects for all of those. You also need a way to find all of those variations when it comes time to copy.
Basically, its a crutch and shouldn't be done when you want to make clean, efficient, manageable and scaleable apps. - There was no indication in the question that there were multiple sets of Tasks. Ie different Tyoes of Projects. But even if there were a small number like 6, the process would be to build 6 buttons to import he respective 6 sets if Tasks to the current project.
So you create a project and save.
Them click the button to create the Tasks. Ie you would not copy the Template record, you would import use the button to bring standard Tasks into your new Project.
That process is also smart enough to deal with Tasks which have predecessors, natively. - Josh,
I suggest that you explore the wizard located in App Management and decide if a native solution is sufficient for your needs, or if you need a scripting solution.
