OneDrive and SharePoint — Attachments Stored in Microsoft 365

OneDrive and SharePoint — Odoo attachments in Microsoft 365

Odoo attachments live in Odoo. The company's documents live in SharePoint. In between, someone copies things over — and that someone forgets.

Also searched as: OneDrive Odoo, SharePoint Odoo, Microsoft 365 Odoo, Microsoft Graph Odoo, SharePoint attachments Odoo, cloud storage Odoo, OneDrive connector Odoo 19, Microsoft documents Odoo Community.

One folder per record, following a folder structure you decide. {modele}/{annee}/{enregistrement} by default, and the tokens can be rearranged. Names are sanitized before upload: characters Windows rejects, reserved names — CON, NUL — and path traversal attempts are neutralized, rather than letting the upload fail with an obscure message.

The refresh token expires, and the module says so. This is the case connectors handle poorly, because it is rare in testing and certain in production. Here, the connection switches to the “token expired” state, displays the reason returned by Microsoft with its date, stops the queue for that connection — tasks stay pending, none is lost or marked as failed — and waits for human action. No retry loop: hammering a dead token does not revive it, and eventually gets the account locked.

Rate limiting is respected, not suffered. On a 429, the module reads the Retry-After header, pauses the connection until that time and puts the task back in the queue. It is the module's only automatic retry, and it is justified: on a 429, we know the call did nothing.

Deletion is your decision, never ours. Three policies, selectable per connection: keep the remote file — this is the default —, move it to the trash, or delete it permanently. Removing a duplicate in Odoo is not the same as deciding the fate of a company's supporting document.

No network call in a process that serves a page. Uploading a document only writes a record: sending happens from the cron job or from a “now” action. A call attempted from a computed field is refused — this is a safeguard verified by a test, not a guideline.

An orphaned task is flagged, never retried. A task whose process died mid-upload may have succeeded. Running it again would create a duplicate in SharePoint that would have to be tracked down by hand. It is marked, counted, and awaits a decision.

Nothing is sent until you have named something. No model is tracked by default.