[18.0][MIG] hr_expense_widget_o2m

[TheerayutEncoder]

Standard Migration

Hi @kittiu, @Saran440
Relate to

• [16.0][MIG] hr_expense_widget_o2m #232
• [IMP] base: remove groups_id from ir.ui.view odoo/odoo#98551
• [IMP] base: uniform "groups" in back-end view odoo/odoo#95729

on version 18.0 groups_id also removed from ir.ui.view
That means we cannot configure it to use O2M widget by groups; we can only enable this feature by installing or uninstalling it.

[Saran440]

Code Review 👍

[Saran440]

/ocabot migration hr_expense_widget_o2m

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[Saran440]

Step to test:

1. Create hr.expense.sheet and add a line
2. Change quantity or Total > Save
3. Click in each line > edit price > Save
4. Click from smart button expense

Result:
The price still shows the old value.

I think this behavior may be related to the widget implementation in Odoo 18 and the way the x2many state is handled.

To simplify the user experience, I created an alternative module using the standard Odoo behavior with open_form_view:
#342

What do you think?

[TheerayutEncoder]

Step to test:

1. Create hr.expense.sheet and add a line
2. Change quantity or Total > Save
3. Click in each line > edit price > Save
4. Click from smart button expense

Result: The price still shows the old value.

I think this behavior may be related to the widget implementation in Odoo 18 and the way the x2many state is handled.

To simplify the user experience, I created an alternative module using the standard Odoo behavior with open_form_view: #342

What do you think?

Yes, it's better to just use standard odoo like open_form_view.