Syncing from upstream odoo/odoo (tmp.saas-18.1) #34155
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
__Issue:__ Condition used for MOs triggered under the `pbm_sam` manufacturing flow only checks the start of the group name, not the whole name, which could fail in case triggered by reordering rules where the origin might be a compound string such as: "OP/00001,WH/MO/00001" __Steps to reproduce:__ 1.) Install sales; inventory; manufacturing 2.) Enable multi-step routes 3.) Unarchive MTO 4.) Set warehouse manufacture steps to: Pick components, manufacture, then store products (3 steps) (manufacture_steps == 'pbm_sam') 5.) Create product A-bom (enable manufacture and mto routes) 6.) Create product B (enable manufacture) 7.) Add Product A as bom for product B 8.) Add a reordering rule (manufacture) for product B 9.) run SA Procurement: run scheduler Error: duplicate key value violates unique constraint opw-4866263 bug found: [#c50cb9d][1] [1] : c50cb9d closes #217417 X-original-commit: c604235 Signed-off-by: William Henrotin (whe) <[email protected]> Signed-off-by: Verina Gad (vega) <[email protected]>
This PR adds the reference field on the partner as Tax Office to the partner tax information sent to Nilvera, as required by GİB. This is a temporary fix until a new module is added later that handles GIB tax office information, which will add a tax office m2o field to the res.partner model. Task-4886128 closes #217621 X-original-commit: 99016b3 Signed-off-by: Ali Alfie (alal) <[email protected]> Signed-off-by: Khumam Alzagim (alkh) <[email protected]>
…table in po
Steps to Reproduce:
1. Navigate to Purchase → Create a new Purchase Order.
2. Add a Vendor → Add a Product with description or enter one using the ☰ widget.
3. Save and Confirm the order, Try to edit the description.
Issue:
- The product description becomes non-editable after confirming the PO.
- Previously, the description was separated in view.
Cause:
- Since product_id is readonly, the name (description) field also does not allow
to edit.
- e.g. In SO, the description is editable if the product_id is hidden and only
name (description) field is visible.
Since product_id is readonly in states ('purchase','to approve','done','cancel')
the description field also becomes read-only, as they are combined.
By hiding the product_id, we can edit the description, as it is not.
Solution:
- Added optional="show" to product_id in the XML view to allow toggling
discription editability. When product_id is hidden, name field becomes editable.
Steps to Verify:
1. Open same confirmed PO and hide the product_id column.
2. Make sure name (description) field is visible and now it is editable.
opw-4892063
closes #217278
X-original-commit: b48e1e2
Signed-off-by: William Henrotin (whe) <[email protected]>
Signed-off-by: Khushi Srivastava (khsr) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bt_gitbot