<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Odoo/addons/analytic/models/analytic.py, branch 14.0</title>
<subtitle>The current checkout of upstream Odoo</subtitle>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/'/>
<entry>
<title>[MOV][IMP] analytic: reorganize addon, remove openerp tags and rename python classes</title>
<updated>2016-08-02T07:54:37+00:00</updated>
<author>
<name>fwi-odoo</name>
<email>fwi@odoo.com</email>
</author>
<published>2016-07-19T12:53:53+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=4f9c1c25f4874446719b40409e382e877255ea3a'/>
<id>4f9c1c25f4874446719b40409e382e877255ea3a</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] account_budget,analytic,project: Some display improvements</title>
<updated>2016-03-23T15:35:34+00:00</updated>
<author>
<name>Kinjal Mehta</name>
<email>kme@odoo.com</email>
</author>
<published>2016-01-13T10:49:04+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=16d993a134ba0883f1dd6cdf241934d5615dc039'/>
<id>16d993a134ba0883f1dd6cdf241934d5615dc039</id>
<content type='text'>
1/ An empty notebook was created in analytic and filled in account_budget
   That way, we had a horizontal line while the module wasn't installed yet
2/ The fields use_task and use_issue displayed on the account.analytic.account
   are just redundant information. The probable use case is to go on the project
   select the issues management on it, and it will be activated on the related
   analytic account. I don't think that anybody will come on the analytic account
   to activate the issues. So we hide them in group_no_one
3/ On the analytic account form view, display the title label only in edit mode
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
1/ An empty notebook was created in analytic and filled in account_budget
   That way, we had a horizontal line while the module wasn't installed yet
2/ The fields use_task and use_issue displayed on the account.analytic.account
   are just redundant information. The probable use case is to go on the project
   select the issues management on it, and it will be activated on the related
   analytic account. I don't think that anybody will come on the analytic account
   to activate the issues. So we hide them in group_no_one
3/ On the analytic account form view, display the title label only in edit mode
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] analytic: Replaced account_type field by active field</title>
<updated>2016-03-23T15:35:34+00:00</updated>
<author>
<name>Kinjal Mehta</name>
<email>kme@odoo.com</email>
</author>
<published>2016-01-18T11:22:13+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=a57592abe4e8ac3bac04cbd19eeac88a163aaf7e'/>
<id>a57592abe4e8ac3bac04cbd19eeac88a163aaf7e</id>
<content type='text'>
Currently there is a selection field 'account_type' on the
account.analytic.account model with 2 values : Active or Archived

Let's use an active field instead and add a Archive stat button on the
form. That way, we can remove all the domain ('account_type','=','normal')
which are implicit with the generic active field behavior
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently there is a selection field 'account_type' on the
account.analytic.account model with 2 values : Active or Archived

Let's use an active field instead and add a Archive stat button on the
form. That way, we can remove all the domain ('account_type','=','normal')
which are implicit with the generic active field behavior
</pre>
</div>
</content>
</entry>
<entry>
<title>[IMP] analytic: add tracking of customer in chatter</title>
<updated>2016-03-01T16:12:25+00:00</updated>
<author>
<name>Damien Bouvy</name>
<email>dbo@odoo.com</email>
</author>
<published>2016-03-01T16:12:25+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=150d74b6ea873f41fae4f1d4367ba2451decb21f'/>
<id>150d74b6ea873f41fae4f1d4367ba2451decb21f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] analytic: name_search with negative operators</title>
<updated>2016-02-17T09:49:00+00:00</updated>
<author>
<name>Olivier Dony</name>
<email>odo@openerp.com</email>
</author>
<published>2016-02-15T13:21:18+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=1e729c7c5af67cfea38f0135a252a6f08786177c'/>
<id>1e729c7c5af67cfea38f0135a252a6f08786177c</id>
<content type='text'>
The algorithm for matching analytic accounts based
on search term is only meant to be used for
simple, positive operators.
In other cases the results will not be what the user
expects. Falling back to the default name_search
behavior will be more useful.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The algorithm for matching analytic accounts based
on search term is only meant to be used for
simple, positive operators.
In other cases the results will not be what the user
expects. Falling back to the default name_search
behavior will be more useful.
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] analytic: _default_user</title>
<updated>2015-12-16T15:48:20+00:00</updated>
<author>
<name>Goffin Simon</name>
<email>sig@odoo.com</email>
</author>
<published>2015-12-16T13:59:09+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=c090d9992aa04adbe41a5a16c3a9b78c5e218a64'/>
<id>c090d9992aa04adbe41a5a16c3a9b78c5e218a64</id>
<content type='text'>
The "user_id" linked to the employee_id set on the sheet must be used
when editing a sheet.

opw:659647
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The "user_id" linked to the employee_id set on the sheet must be used
when editing a sheet.

opw:659647
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] analytic: workaround to re-enable the feature to close an analytic account that has been unfortunately removed by mistake in commit 2a8c077.</title>
<updated>2015-12-11T13:57:46+00:00</updated>
<author>
<name>qdp-odoo</name>
<email>qdp@odoo.com</email>
</author>
<published>2015-12-11T13:47:01+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=f6d6762dc7150076b5463b09480222db813b2cf1'/>
<id>f6d6762dc7150076b5463b09480222db813b2cf1</id>
<content type='text'>
It is using an already existing field that wasn't used anymore ('account_type') but as a lot of domains on analytic accounts were
 - wrong (still using old fields state and type that have been removed as well in the same commit),
 - or defined directly in the views
so, an update of some modules may be needed in order to avoid further problems.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It is using an already existing field that wasn't used anymore ('account_type') but as a lot of domains on analytic accounts were
 - wrong (still using old fields state and type that have been removed as well in the same commit),
 - or defined directly in the views
so, an update of some modules may be needed in order to avoid further problems.
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] analytic: fixed name_search() on analytic account. The partner_id field is not mandatory, but the previous domain was making an inner join with the partner table, which resulted in not finding the accounts matching the search criteria on name/code if they hadn't a partner set.</title>
<updated>2015-12-02T13:35:27+00:00</updated>
<author>
<name>qdp-odoo</name>
<email>qdp@odoo.com</email>
</author>
<published>2015-12-02T10:21:58+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=7909a4409afb0b2dc4ac8b4db402f8e5dd5970c8'/>
<id>7909a4409afb0b2dc4ac8b4db402f8e5dd5970c8</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] analytic: optimize name_search for large databases</title>
<updated>2015-11-24T19:00:58+00:00</updated>
<author>
<name>Olivier Dony</name>
<email>odo@openerp.com</email>
</author>
<published>2015-11-24T19:00:57+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=3b833b20397ef53e8bd2167dee87d764939a74fd'/>
<id>3b833b20397ef53e8bd2167dee87d764939a74fd</id>
<content type='text'>
On databases with a large number of res.partner entries,
the extended name_search of analytic accounts was prohibitively
slow, due to the expensive name_search on res.partner.

Restricting the search to the partner name is extremely
similar business-wise, but makes a huge difference in
terms of speed. E.g. sub-second results vs 10+ minutes
for a database with 30k analytic accounts and 600k partners.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On databases with a large number of res.partner entries,
the extended name_search of analytic accounts was prohibitively
slow, due to the expensive name_search on res.partner.

Restricting the search to the partner name is extremely
similar business-wise, but makes a huge difference in
terms of speed. E.g. sub-second results vs 10+ minutes
for a database with 30k analytic accounts and 600k partners.
</pre>
</div>
</content>
</entry>
<entry>
<title>[FIX] analytic: hide account_type</title>
<updated>2015-09-30T09:32:00+00:00</updated>
<author>
<name>Nicolas Martinelli</name>
<email>nim@odoo.com</email>
</author>
<published>2015-09-30T08:58:58+00:00</published>
<link rel='alternate' type='text/html' href='http://erp.ceuconsult.com:9000/Odoo/commit/?id=d62be727594e31fa060147cf33e4ac4fa4bc30fb'/>
<id>d62be727594e31fa060147cf33e4ac4fa4bc30fb</id>
<content type='text'>
`account_type` is probably not necessary anymore, but too late to
remove it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
`account_type` is probably not necessary anymore, but too late to
remove it.
</pre>
</div>
</content>
</entry>
</feed>
