Currently, when tasks are created in Plans using the provided CSV template, uploading an updated version of that CSV creates entirely new tasks instead of updating the existing ones.
This makes it difficult to manage schedules or task lists externally because even when the task name and information remain the same, every reimport generates duplicates. Deleting the previous tasks does not fully resolve the issue either, since newly created tasks continue from the last internal task ID rather than restarting the numbering.
It would be helpful if the CSV template included a permanent Task ID or External ID that could be used to match imported rows with existing tasks.
When reuploading the CSV, the system could:
- Update tasks when a matching Task ID is found.
- Create a new task only when no matching ID exists.
- Optionally flag tasks that were removed from the CSV instead of automatically deleting them.
- Preserve the task’s history, assignments, relationships, progress, and existing references.
This would make the CSV workflow useful not only for the initial bulk creation of tasks, but also for ongoing schedule maintenance and coordination. It would also prevent duplicates and reduce the need to manually update large numbers of tasks inside the platform.
