GuillemCForgeFlow

[14.0][MIG]account_move_post_block: Migration to 14.0

6

Standard migration @ForgeFlow

We should also trigger the update of the Stock State when the Stock Move is assigned as there may be some updates in the `stock.quant` instances. cc @ForgeFlow

cc @ForgeFlow

[13.0][IMP]shopinvader: restrict duplicate partner emails per backend

2

Only restrict the duplicated Partner Emails per Backend. Meaning that we can have we can have two Shopinvader Partners belonging to different Websites but still having the same e-mail. cc...

Possibility to set specific Locations where to check for stock within the specified Warehouses. cc @ForgeFlow

There may be a case where the Pricelist obtained within the execution does not belong to the Company of the Backend in which we are calculating the Sale Profile. For...

[14.0][MIG]crm_lead_product: Migration to 14.0

1

Migration to v14.0: - Renamed Revenue fields (Planned and Expected to Expected and Prorated, respectively) in the `crm.lead.line` model to match the current labels in standard Odoo: https://github.com/odoo/odoo/blob/17.0/addons/crm/models/crm_lead.py#L152-L153. Also, changed...

[13.0][IMP]purchase_sale_inter_company: is intercompany fields and little improvements

2

- Add is intercompany fields for the SO, PO, Stock Moves and Transfers - Fill values for these fields in a correct way - Add corresponding filters @ForgeFlow

Removed _sql_constraints checking that there were not two partners having the same email within the same backend. Changed it for an api.constrains that will only check it for active users....

[17.0][IMP]bi_sql_editor: scheduled action periodicity settings

4

refactor `Action Settings` page to have all settings, renamed to `Settings`. Added the settings to be able to customize the periodicity of the Scheduled Action that will refresh the Materialized...