Wednesday, November 20, 2024
6 changes
2 changes
Enhancements to existing features
The Twitter/X integration now reflects X's stricter privacy rules for likes, so users can still see like counts but no longer see who liked a post or retrieve posts liked by a specific user. Existing social streams will avoid crashing when X returns empty like details, and duplicate feed items stay consistent when a user likes a post.
Original PR description
The X platform announced that they were updating their policy on likes. These changes also impacts their API, this commit updates the social_twitter module to handle this change.
The API has been changed so that when accessing the Likes lookup endpoints, the resulting response will contain data about the accessed posts if it belongs to the authenticated user.
It is still possible to fetch the like_counts for all posts, but not the details of each like.
This disables any user to evaluate who is liking its posts. This also blocks any attempt to retrieve the posts liked by a specific user.
If a user tries to access these endpoints the resulting response will be:
```
{
"meta": {
"result_count": 0
}
}
```
These responses aren't considered errors so exisiting streams using this endpoint will not crash.
But they will not contain any fresh post and won't be able to be refreshed.
task-3986158Studio users can now configure whether records can be duplicated from form and list views. This gives businesses more control over user actions and helps prevent unintended record copies where duplication should not be allowed.
Original PR description
This PR adds the 'duplicate' property to forms and list views. It's true by default and when set to false will add the `duplicate="true"` attribute, when true the attribute is removed Task ID: 4286087
4 changes
Enhancements to existing features
Users can now re-import exported chart of accounts spreadsheets that include company-specific account code mappings without import failures. The update also improves account code uniqueness checks so Odoo proposes valid, available account codes more reliably across companies.
Original PR description
When exporting a CoA in Excel format, the user can export the code mapping for all the companies via the `code_mapping_ids/company_id` and `code_mapping_ids/code` columns. However, importing these…
When exporting a CoA in Excel format, the user can export the code mapping for all the companies via the `code_mapping_ids/company_id` and `code_mapping_ids/code` columns. However, importing these values fails because the import transforms these values into `CREATE` commands on `code_mapping_ids`, which are currently not handled. With this commit, we catch those CREATE commands in `account.account` `create` and `write` methods and modify the account's code in the relevant company. In addition, we take the opportunity to correctly rewrite the `_ensure_code_is_unique` check method. In https://github.com/odoo/odoo/pull/181352, we relaxed the constraint that prevented accounts from being mapped to an account code in a company the account doesn't belong to, if there already exists an account in that company that already has that code. However, the `_ensure_code_is_unique` wasn't rigorously rewritten, and it didn't apply the check in a consistent manner. We now rewrite it and provide tests for it. We also modify the `_search_new_account_codes` method accordingly, such that it proposes the first non-reserved account code. Enterprise PR: https://github.com/odoo/enterprise/pull/71910 task-4247869
Indian localization settings now clarify which HSN code length applies based on business value thresholds. Companies below 5 crore use 4-digit HSN codes, while those above 5 crore use 6-digit HSN codes, helping users follow reporting requirements more clearly.
Original PR description
Modified HSN display format based on crore thresholds: - 4-digit HSN for values below 5 crore. - 6-digit HSN for values above 5 crore. This update enhances clarity by providing distinct formats for HSN codes based on value thresholds. > Task: 4252228
Restaurant point-of-sale users can now return to the floor plan without waiting for a background server update to finish. This makes navigation feel quicker and removes an unnecessary notification when moving to the ticket screen.
Original PR description
- We don't wait anymore the server's response (from the call to `sync_from_ui`) when going to the floorplan. - Remove useless toaster notification when going to the ticket screen. task_id: 4329314 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Account imports now support accounts shared across companies by making the account code optional and allowing accounts to be matched by company-specific code, external ID, or database ID. Users can also import company-specific code mappings, helping multi-company setups maintain different account codes accurately.
Original PR description
We adjust the account import mechanism to the new reality that accounts can now be shared between companies, and have different codes in different companies. - The `code` column is now no longer required. Users can reference an account by its code in the current company (in which case only the account with that code that belongs to the current company will be matched), but can also reference an account by its external ID or database ID. - The user can import a code mapping for accounts via the `code_mapping_ids/company_id` and `code_mapping_ids/code` columns. We add a check that both of these columns must be simultaneously present. Community PR: https://github.com/odoo/odoo/pull/183695 task-4247869