Repository navigation
[19.0][MIG] survey_sale_generation: Migration to version 19.0 - #247
Conversation
|
/ocabot migration survey_sale_generation |
Currently translated at 3.0% (1 of 33 strings) Translation: survey-15.0/survey-15.0-survey_sale_generation Translate-URL: https://translation.odoo-community.org/projects/survey-15-0/survey-15-0-survey_sale_generation/it/
Currently translated at 100.0% (33 of 33 strings) Translation: survey-15.0/survey-15.0-survey_sale_generation Translate-URL: https://translation.odoo-community.org/projects/survey-15-0/survey-15-0-survey_sale_generation/es/
- We can configure a custom mail template for the quotation. - Now it's possible to set a linked answer that acts as multiplier. TT40983
Allow to set multiple products so one question can generate several product lines
Allow to choose a quotation template
Adds the dependency to survey_result_mail
Allow to fill sale.order links from the survey answers TT47576
Now we can use a single choice question to force the template into the generated sale order. TT51297
Currently translated at 100.0% (47 of 47 strings) Translation: survey-17.0/survey-17.0-survey_sale_generation Translate-URL: https://translation.odoo-community.org/projects/survey-17-0/survey-17-0-survey_sale_generation/it/
…ompany_id When generating a quotation from a survey response, the sale order was being assigned to the company of the `create_uid`. This is incorrect in multi-company contexts, especially when the user has access to multiple companies and their default company (`company_id`) is not the active one. Instead, this commit uses `self.env.company` to retrieve the currently active company from the context, which correctly reflects the company in which the user is operating when completing the survey. This change ensures that the sale order is created in the company active in the user's session, avoiding multi-company integrity errors (e.g. trying to create a record in a company other than the one currently active). TT57057
2fedf3c to
6c06a4e
Compare
6c06a4e to
81d8c3b
Compare
|
There’s actually no issue with the tests. When I was transcribing the demo survey into the test setup, I forgot to add a field to the question about the Gold services. That field indicates whether you want to use a numeric field as a multiplier for the value of that question. Sorry for any inconvenience caused. |
Thanks for checking and clarifying! The confusion came from the 17.0 test documentation showing 1 while the actual expected behavior was 3. Thanks also for correcting it in 19.0 🙂 |
81d8c3b to
3fabb54
Compare
3fabb54 to
e7deccc
Compare
|
@pilarvargas-tecnativa, It should already cover the check you mentioned. |
|
/ocabot merge nobump |
|
Hey, thanks for contributing! Proceeding to merge this for you. |
|
Congratulations, your PR was merged at e34e9aa. Thanks a lot for contributing to OCA. ❤️ |
@Tecnativa TT64020
@pilarvargas-tecnativa @eduezerouali-tecnativa