Fabien Pinckaers
9690685d65
Use crm.lead instead of a the crm.opportunity.report object for reporting. This allows to show more fields (e.g. tags_ids). The only field not accessible in the report is #activities, but there is a deicated report dedicated to activities. Improved the default search. Example: when reporting on leads, you want leads+opps by creation date (and not only leads) as an opportunity has been a lead created too.
33 lines
1.2 KiB
XML
33 lines
1.2 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.lead</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>
|