Nicolas Martinelli
aa65a46fc5
The new settings model loads by default all settings. In the case of non-admin user having the 'Settings' access rights this can lead to access errors. This commit deals with the multi-company issues on a standard installation. If the admin is in Company A and the other user in Company B, accessing the settings is pretty much impossible because of records rules. This fixes the master or demo data to avoid setting a company by default. Note that it only fixes a standard installation: if the settings are later customized, there is no guarantee that it will still work. Problematic fields: `auth_signup_template_user_id` `crm_default_team_id` `leave_timesheet_task_id` opw-801210
33 lines
1.3 KiB
XML
33 lines
1.3 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<record id="sales_team.team_sales_department" model="crm.team">
|
|
<field name="use_opportunities">True</field>
|
|
<field name="use_leads">True</field>
|
|
<field name="alias_name">sales</field>
|
|
<field name="dashboard_graph_model">crm.opportunity.report</field>
|
|
<field name="company_id" eval="False"/>
|
|
</record>
|
|
|
|
<!--default alias for leads-->
|
|
<record id="mail_alias_lead_info" model="mail.alias">
|
|
<field name="alias_name"></field>
|
|
<field name="alias_model_id" ref="model_crm_lead"/>
|
|
<field name="alias_user_id" ref="base.user_root"/>
|
|
<field name="alias_parent_model_id" ref="model_crm_team"/>
|
|
</record>
|
|
|
|
<!-- opportunities' lost causes -->
|
|
<record id="lost_reason_1" model="crm.lost.reason">
|
|
<field name="name">Too expensive</field>
|
|
</record>
|
|
<record id="lost_reason_2" model="crm.lost.reason">
|
|
<field name="name">We don't have people/skills</field>
|
|
</record>
|
|
<record id="lost_reason_3" model="crm.lost.reason">
|
|
<field name="name">Not enough stock</field>
|
|
</record>
|
|
</data>
|
|
|
|
</odoo>
|