Zum Inhalt springen
Menü
Sie müssen registriert sein, um mit der Community zu interagieren.
Diese Frage wurde gekennzeichnet
1032 Ansichten

I'm encountering an issue when importing timesheet data into Odoo 16. The problem arises when multiple projects have tasks with the same name (e.g., "Task 001" exists in Project A, Project B, and Project C).

  • Project names are correctly captured during the import, and the timesheet data does associate with the right project.
  • However, when tasks are imported, they are automatically categorized under the same project (in my case, Project C) regardless of which project they actually belong to.
  • This seems to be because Odoo matches tasks based solely on the task name, without taking the project into account.

I need a solution that minimizes manual adjustments after import. Ideally, Odoo should match tasks based on both the project and task name during the import process, rather than grouping tasks with the same name under a single project.

I've already tried checking the structure of the import file, and while project names are included, the task-project relationship seems to be missing or not being enforced during the import.

How can I adjust Odoo's import logic to ensure tasks are correctly assigned to their respective projects without manual intervention after each import?

import from ..

8069/web#action=616&model=account.analytic.line&view_type=list&cids=1&menu_id=439

Avatar
Verwerfen
Verknüpfte Beiträge Antworten Ansichten Aktivität
2
Mai 25
1342
0
Mai 25
913
4
Mai 25
5068
1
Apr. 25
1057
1
Aug. 24
2349