Elabore/odoo-usability
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove account_hide_analytic_line (replaced by the module account_analytic_no_lines from OCA/account-analytic)

Browse Source
This commit is contained in:
Alexis de Lattre
2018-02-02 17:13:47 +01:00
parent 72f7235c18
commit 782f1fdb92
3 changed files with 0 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
account_hide_analytic_line/__init__.py
View File

@@ -1 +0,0 @@
# -*- coding: utf-8 -*-

30
account_hide_analytic_line/__manifest__.py
View File

@@ -1,30 +0,0 @@
# -*- coding: utf-8 -*-
# © 2016 Akretion (Alexis de Lattre <alexis.delattre@akretion.com>)
# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
{
'name': 'Account Hide Analytic Lines',
'version': '8.0.1.0.0',
'category': 'Accounting & Finance',
'license': 'AGPL-3',
'summary': 'Hide analytic lines',
'description': """
Account Hide Analytic Lines
===========================
This module hides analytic lines. If you don't use timesheets, you should
not use analytic lines at all. Instead, you should only use
account move lines with the analytic account field (technical name: *analytic_account_id*).
Why ? Because, when you change the analytic account on an account move line,
the analytic line is not updated by Odoo. So, if you use the report available in *Reporting > Accounting > Analytic Entries Analysis*, as this report is based on analytic lines, the results will not take into account the changes of analytic account that you made on some account move lines.
This module has been written by Alexis de Lattre from Akretion
<alexis.delattre@akretion.com>.
""",
'author': 'Akretion',
'website': 'http://www.akretion.com',
'depends': ['account', 'base_usability'],
'data': ['account_view.xml'],
'installable': False,
}

63
account_hide_analytic_line/account_view.xml
View File

@@ -1,63 +0,0 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
© 2016 Akretion (Alexis de Lattre <alexis.delattre@akretion.com>)
License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
-->
<openerp>
<data>
<record id="account.account_analytic_journal_entries" model="ir.ui.menu">
<field name="groups_id" eval="[(6, 0, [ref('base_usability.group_nobody')])]"/>
</record>
<!-- Chart of analytic accounts -->
<record id="account.menu_action_analytic_account_tree2" model="ir.ui.menu">
<field name="groups_id" eval="[(6, 0, [ref('base_usability.group_nobody')])]"/>
</record>
<record id="account.next_id_40" model="ir.ui.menu">
<field name="groups_id" eval="[(6, 0, [ref('base_usability.group_nobody')])]"/>
</record>
<record id="account.account_analytic_journal_values" model="ir.values">
<field name="value" eval="False"/>
</record>
<record id="view_move_line_form" model="ir.ui.view">
<field name="name">account_hide_analytic_line.account_move_line_form</field>
<field name="model">account.move.line</field>
<field name="inherit_id" ref="account.view_move_line_form"/>
<field name="arch" type="xml">
<page groups="analytic.group_analytic_accounting" position="attributes">
<attribute name="invisible">1</attribute>
</page>
</field>
</record>
<record id="view_account_entries_report_search" model="ir.ui.view">
<field name="name">account.entries.report.search: add groupby</field>
<field name="model">account.entries.report</field>
<field name="inherit_id" ref="account.view_account_entries_report_search"/>
<field name="arch" type="xml">
<group expand="1" position="inside">
<filter name="account_groupby" string="Account" context="{'group_by': 'account_id'}"/>
<filter name="analytic_account_groupby" string="Analytic Account" context="{'group_by': 'analytic_account_id'}"/>
</group>
</field>
</record>
<!-- Natively, this action is based on analytic.entries.report
We switch that to account.entries.report with good context value to
have a similar result -->
<record id="account.action_analytic_entries_report" model="ir.actions.act_window">
<field name="res_model">account.entries.report</field>
<field name="context">{'search_default_thisyear': 1, 'search_default_analytic_account_groupby': 1}</field>
<field name="search_view_id" ref="view_account_entries_report_search"/>
<field name="domain">[('analytic_account_id', '!=', False)]</field>
</record>
</data>
</openerp>