Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

17.0 [MIG] fieldservice_sale #1151

Open
wants to merge 214 commits into
base: 17.0
Choose a base branch
from

Conversation

SMaciasOSI
Copy link
Contributor

osi-scampbell and others added 30 commits December 18, 2023 11:26
[IMP] Remove Duplicate Field
Added ability to link a product with FSM order template and create FSM
orders upon sale order confirmation
Added option to install fieldservice_sale module
Added support for selling recurring orders
Travis
Typo, wrong model relationship
Improved values prepation method for recurring
Updated errors on SO smart button for recurring
- Completed field service orders will now update the qty_delivered field on linked SO line
-  suggestions from reviewer comments
- This change will allow to create an FSM order for each sales order and link it to the delivery order and invoice
- Combine field service template info from sale order lines and add it to field service order
Consumable and Storable product types were not generating field services
- Was not calling super properly and FSM orders on the sale line that were not recurring orders were not being created.
- Delete unused computed field.
@SMaciasOSI
Copy link
Contributor Author

This PR requires #1150 to be merged first so the test can pass after a rebase

lambda l: l.product_id.field_service_tracking == "sale"
and not l.fsm_order_id
lambda L: L.product_id.field_service_tracking == "sale"
and not L.fsm_order_id
Copy link
Sponsor Member

Choose a reason for hiding this comment

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

Why the uppercase? Convention is to use lowercase variable names.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why the uppercase? Convention is to use lowercase variable names.

With the lowecase I got an error regarding "ambiguous variable name". I got the suggestion to change from l to L from here: https://docs.astral.sh/ruff/rules/ambiguous-variable-name/

OCA-git-bot and others added 22 commits December 28, 2023 21:58
Signed-off-by max3903
Signed-off-by brian10048
Signed-off-by brian10048
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: field-service-17.0/field-service-17.0-fieldservice_route
Translate-URL: https://translation.odoo-community.org/projects/field-service-17-0/field-service-17-0-fieldservice_route/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: field-service-17.0/field-service-17.0-base_territory
Translate-URL: https://translation.odoo-community.org/projects/field-service-17-0/field-service-17-0-base_territory/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: field-service-17.0/field-service-17.0-fieldservice
Translate-URL: https://translation.odoo-community.org/projects/field-service-17-0/field-service-17-0-fieldservice/
Currently translated at 100.0% (12 of 12 strings)

Translation: field-service-17.0/field-service-17.0-fieldservice_account
Translate-URL: https://translation.odoo-community.org/projects/field-service-17-0/field-service-17-0-fieldservice_account/it/
Currently translated at 100.0% (564 of 564 strings)

Translation: field-service-17.0/field-service-17.0-fieldservice
Translate-URL: https://translation.odoo-community.org/projects/field-service-17-0/field-service-17-0-fieldservice/es/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet