Skip to content

[MIG] base_export_async: Migration to 17.0#894

Open
StephaneMangin wants to merge 62 commits into
OCA:17.0from
acsone:17.0-mig-base_export_async
Open

[MIG] base_export_async: Migration to 17.0#894
StephaneMangin wants to merge 62 commits into
OCA:17.0from
acsone:17.0-mig-base_export_async

Conversation

@StephaneMangin

@StephaneMangin StephaneMangin commented Feb 11, 2026

Copy link
Copy Markdown

--Needed to monkey patch the env of request during data parsing as the export mechanism uses it under the hood and leads to ACLs exception while searching for currencies--

Reimplementing a part of the Export to avoid calling request which fails.
A patch on Odoo is planned.

apineux and others added 30 commits February 11, 2026 11:00
Currently translated at 100.0% (19 of 19 strings)

Translation: queue-12.0/queue-12.0-base_export_async
Translate-URL: https://translation.odoo-community.org/projects/queue-12-0/queue-12-0-base_export_async/de/
Currently translated at 100.0% (19 of 19 strings)

Translation: queue-12.0/queue-12.0-base_export_async
Translate-URL: https://translation.odoo-community.org/projects/queue-12-0/queue-12-0-base_export_async/zh_Hans/
The UI still send it to the current user, but it will allow
reusing the module for other purposes: plan a regular export
to users.

Setting the recipient_ids instead of the email_to in mail.mail means
that we can still send the email, it will stay in the failed emails,
allowing to correct the user.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: queue-12.0/queue-12.0-base_export_async
Translate-URL: https://translation.odoo-community.org/projects/queue-12-0/queue-12-0-base_export_async/
@StephaneMangin StephaneMangin force-pushed the 17.0-mig-base_export_async branch 5 times, most recently from 1a2ec34 to 91c5bc7 Compare February 18, 2026 15:55
@yvaucher

Copy link
Copy Markdown
Member

/ocabot migration base_export_async

@OCA-git-bot OCA-git-bot added this to the 17.0 milestone Feb 19, 2026
@OCA-git-bot OCA-git-bot mentioned this pull request Feb 19, 2026
8 tasks
@StephaneMangin StephaneMangin force-pushed the 17.0-mig-base_export_async branch 17 times, most recently from 7f59164 to 0ac5649 Compare February 19, 2026 16:45
@StephaneMangin StephaneMangin force-pushed the 17.0-mig-base_export_async branch from 0ac5649 to 4f73e1b Compare February 19, 2026 16:54
@github-actions

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 28, 2026

@hbrunn hbrunn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with your changes an async excel export will look slightly differently from what you get without async, I don't this this should be the case.

In my opinion, the excel export changes should go to another module that applies these changes in a way that's independent of base_export_async, and the migration keep the contract of: do the same as in sync case, but asynchronously.

And please refrain from reformatting xml files without need, that makes the diff more noisy than necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.