Warning found in logs:
2026-01-15 15:18:52,281 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;div&gt;</tt></b> are displayed, but they depend on the field <b><tt>bank_account_id</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “bank_account_id” is accessible for groups: &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;<br/>- element “&lt;div class=&#34;d-flex&#34; invisible=&#34;not bank_account_id&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 15:18:52,281 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>is_trusted_bank_account</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “is_trusted_bank_account” is accessible for groups: &#39;hr.group_hr_user&#39;<br/>- element “&lt;button title=&#34;Untrust Bank Account&#34; class=&#34;icon-button button-on&#34; icon=&#34;fa-solid fa-toggle-on fa-lg&#34; type=&#34;object&#34; name=&#34;action_untrust_bank_accounts&#34; invisible=&#34;not is_trusted_bank_account&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 15:22:34,851 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:22:55,357 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;div&gt;</tt></b> are displayed, but they depend on the field <b><tt>bank_account_id</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “bank_account_id” is accessible for groups: &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;<br/>- element “&lt;div class=&#34;d-flex&#34; invisible=&#34;not bank_account_id&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 15:22:55,358 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>is_trusted_bank_account</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “is_trusted_bank_account” is accessible for groups: &#39;hr.group_hr_user&#39;<br/>- element “&lt;button title=&#34;Untrust Bank Account&#34; class=&#34;icon-button button-on&#34; icon=&#34;fa-solid fa-toggle-on fa-lg&#34; type=&#34;object&#34; name=&#34;action_untrust_bank_accounts&#34; invisible=&#34;not is_trusted_bank_account&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 15:23:38,313 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:25:42,448 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;field name=&#34;l10n_be_ambulatory_insurance_notes&#34;/&gt;</tt></b> are displayed, but they depend on the field <b><tt>l10n_be_has_ambulatory_insurance</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “l10n_be_has_ambulatory_insurance” is accessible for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39;<br/>- element “&lt;field name=&#34;l10n_be_ambulatory_insurance_notes&#34; string=&#34;Additional Information&#34; invisible=&#34;not l10n_be_has_ambulatory_insurance&#34;/&gt;” is shown in the view for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39; | &#39;dtg_hr_contract.group_hr_contract_user&#39;
2026-01-15 15:25:42,448 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;field name=&#34;l10n_be_hospital_insurance_notes&#34;/&gt;</tt></b> are displayed, but they depend on the field <b><tt>has_hospital_insurance</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “has_hospital_insurance” is accessible for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39;<br/>- element “&lt;field name=&#34;l10n_be_hospital_insurance_notes&#34; string=&#34;Additional Information&#34; invisible=&#34;not has_hospital_insurance&#34;/&gt;” is shown in the view for groups: &#39;hr_contract.group_hr_contract_employee_manager&#39; | &#39;dtg_hr_contract.group_hr_contract_user&#39;
2026-01-15 15:27:00,751 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:28:11,479 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:28:26,110 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:28:47,252 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:28:54,483 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:28:58,587 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:23,018 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:27,168 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:29,491 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:32,824 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_ui_view: <b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;div&gt;</tt></b> are displayed, but they depend on the field <b><tt>bank_account_id</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “bank_account_id” is accessible for groups: &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;<br/>- element “&lt;div class=&#34;d-flex&#34; invisible=&#34;not bank_account_id&#34;/&gt;” is shown in the view for groups: &#39;base.group_system&#39; | &#39;hr.group_hr_user&#39; | &#39;dtg_hr.group_hr_employee_dtg_user&#39;
2026-01-15 15:29:36,172 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:39,724 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:44,124 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:45,703 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:45,956 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:47,772 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:49,061 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:51,121 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:51,472 43 WARNING 04394-18-0-all odoo.addons.base.models.ir_model: Two fields (employee_department_id, department_id) of res.users() have the same label: Department. [Modules: None and hr] 
2026-01-15 15:29:53,019 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:55,118 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it 
2026-01-15 15:29:56,069 43 WARNING 04394-18-0-all odoo.fields: Field bad.debt.sequence.data.invoice_id: unknown parameter 'unique', if this is an actual parameter you may want to override the method _valid_field_parameter on the relevant model in order to allow it