The task description is a text field. The task does change and is updated. When information is updated in the Project table normally it requires an email or creating a new task to inform the person it has been updated. So the idea was that one of the task would be tied to the description in the project table. This way it can remain a general summary of what needs to be done and then when the project is updated it doesn't require creating a new task or an email.
Whoever is working on then the task can update the description in the task field and when people go the project table, they will see whats been added. For example if person A has new information for the project and they add it to the project field, they then could just write in the task description that it was added, and when person B is working through their task, they can see it in the description. This works fine if one project has one task. Though, workers have multiple task, whether its a follow up call, or an email, or reviewing a document, it is still part of the same project. That is why one project can have many task. I want the action to be able to target the task description for the task that is being used as a general overview of what is being done. To prevent sending one line emails or a task to say I got the information for these fields.
If workers are making task for a follow up phone call, I do not need its task description to be changed. So like Jeff, when I use the action so that description is field modified in the project record, it is updating every description associated in the task table that is associated with its one project to many task relationship. I would like to be able to target specific records in the action. I hope this is clearer.
