[Tinyerp-users] Tree view Limit = 80
Tree views have a default Limit to display 80 Records. I am still looking for the place to change this limit. It is not in the view and the Limit of 80 I changed in product.py did not influence this. Michael ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
Re: [Tinyerp-users] Tree view Limit = 80
On 09/09/07 14:16 +0200, [EMAIL PROTECTED] wrote: Tree views have a default Limit to display 80 Records. I am still looking for the place to change this limit. It is not in the view and the Limit of 80 I changed in product.py did not influence this. You can change it in the client interface by clicking on the + -- Cédric Krier Tiny sprl Chaussée de Namur, 40 B-1367 Gérompont Belgique Tel: +32 81 81 37 00 Fax: +32 81 73 35 01 Web: http://www.tiny.be pgpkzOC2rtw6u.pgp Description: PGP signature ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Module account_account
Hello, in the modules repository of the tinyerp-server-4.2.0-rc2 I found the module account_account which aims to remove the minimal account chart. Is there a change in the accounting paradigm of connecting all Standard accounts to the minimal account chart as mentioned in the Wikipage http://tinyerp.org/wiki/index.php/DevelopperBook/I10N ? What is the sense or using of this module? Thanks Udo ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Expanding Partner fields and views
I would like to expand the fields available in the Partner for use in a specific business domain as well as the Partner Contacts. I also would like the new fields displayed in the views. I read through this post http://tinyerp.org/forum/topic4540.html?highlight=inherit%20partner which was helpful but still need some clarification. My goal is to not affect the ability to upgrade TinyERP so I am thinking that the best way to do this may be to create a custom module that would inherit and override the partner and partner contact adding the new fields and also creating new view files. Is this possible? And if so what exactly would need to be modified? Or is it better to just modify the original partner files under addons/base/res/partner? Gerry ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
Re: [Tinyerp-users] Expanding Partner fields and views
On 09/09/07 17:23 +0200, [EMAIL PROTECTED] wrote: I would like to expand the fields available in the Partner for use in a specific business domain as well as the Partner Contacts. I also would like the new fields displayed in the views. I read through this post http://tinyerp.org/forum/topic4540.html?highlight=inherit%20partner which was helpful but still need some clarification. My goal is to not affect the ability to upgrade TinyERP so I am thinking that the best way to do this may be to create a custom module that would inherit and override the partner and partner contact adding the new fields and also creating new view files. Is this possible? And if so what exactly would need to be modified? Or is it better to just modify the original partner files under addons/base/res/partner? The best way is to create your own module the inherit the objects that you want to modify. See: http://www.tinyerp.com/wiki/index.php/DevelopperBook/ObjectsInherit -- Cédric Krier Tiny sprl Chaussée de Namur, 40 B-1367 Gérompont Belgique Tel: +32 81 81 37 00 Fax: +32 81 73 35 01 Web: http://www.tiny.be pgp55FppSVxRr.pgp Description: PGP signature ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: pos
Actually, on sunday 9th, there is no file such as __init__.py in the pos package. $ ls -lR .: total 64 -rw-r--r-- 1 melodie users 213 avr 2 17:31 __init__.pyc -rw-r--r-- 1 melodie users 731 avr 26 14:25 __terp__.py -rw-r--r-- 1 melodie users 981 mai 14 17:07 __terp__.pyc -rw-r--r-- 1 melodie users 17857 avr 26 17:37 pos.pyc -rw-r--r-- 1 melodie users 520 avr 2 17:25 pos_data.xml -rw-r--r-- 1 melodie users 331 avr 26 14:25 pos_report.xml -rw-r--r-- 1 melodie users 1224 avr 2 17:25 pos_sequence.xml -rw-r--r-- 1 melodie users 11044 avr 26 14:46 pos_view.xml -rw-r--r-- 1 melodie users 471 avr 2 17:25 pos_wizard.xml drwxr-xr-x 2 melodie users 208 sep 9 18:03 report -rw-r--r-- 1 melodie users 148 avr 2 17:25 sale_wizard.xml drwxr-xr-x 2 melodie users 160 sep 9 18:03 wizard ./report: total 32 -rw-r--r-- 1 melodie users 239 avr 2 17:31 __init__.pyc -rw-r--r-- 1 melodie users 1408 avr 2 17:31 pos_invoice.pyc -rw-r--r-- 1 melodie users 1927 avr 26 15:21 pos_receipt.pyc -rw-r--r-- 1 melodie users 5257 avr 26 15:48 pos_receipt.rml -rw-r--r-- 1 melodie users 10805 avr 26 15:48 pos_receipt.sxw ./wizard: total 12 -rw-r--r-- 1 melodie users 221 avr 2 17:31 __init__.pyc -rw-r--r-- 1 melodie users 2004 avr 2 17:31 wizard_pos_payment.pyc -rw-r--r-- 1 melodie users 2158 avr 2 17:31 wizard_refund_order.pyc $ I haven't come for months now, fortunately for me I don't wait after tinyerp for my personal projects. I still think that a team working with the GPL licence and not respecting it and it's philosophy does something Bad. The documentation of a free software also must be free : why should english reading people get a manual that's half written in french, and french reading people get a manual half written in english, allowing only both languages' readers to get it all about the meaning ? Free Software and Free Manuals (http://www.gnu.org/philosophy/free-doc.html) One more day ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: Expanding Partner fields and views
greno wrote: ... the best way to do this may be to create a custom module that would inherit and override the partner and partner contact adding the new fields and also creating new view files. Is this possible? And if so what exactly would need to be modified? ... This is very much the best way. I've got some examples that I will look out and I'll post one here in the next day or so. Regards, Geoff Seath Solutions Ltd (http://www.seathsolutions.com) ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] views: adding domain to restrict result set
I have defined a view that lists partners. Now I would like to add a domain
field that will restrict the view to those partners in a certain category. How
can you do this using the domain?
record
fieldPartner/field
fieldres.partner/field
this
field[[('category')],'=','My Partners']/field
fieldtree,form/field
/record
menuitem
Gerry
___
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: Expanding Partner fields and views
Hi Geoff, Thanks, that would be great. I'm also debating whether to implement this using properties. Is there a way to group properties so that in a view you lookup one key and then all the related property fields get populated? Gerry ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: Tree view Limit = 80
This line exists in a number of files, e.g. product.py. I changed with no effect. But maybe orm.py is the one. What does orm stand for? Michael ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
Re: [Tinyerp-users] Re: Tree view Limit = 80
Object Relation(al) Mapping http://en.wikipedia.org/wiki/Object-relational_mapping On 9/9/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: This line exists in a number of files, e.g. product.py. I changed with no effect. But maybe orm.py is the one. What does orm stand for? Michael ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users -- /* Andrew Latham LATHAMA (lay-th-ham-eh) [EMAIL PROTECTED] [EMAIL PROTECTED] */ ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] properties: cannot attach external properties
I created a new module and overrode res.partner so that I could attach an
external property from my new module to it.
py:
class res_partner(osv.osv):
_name = 'res.partner'
_inherit = 'res.partner'
_columns = {
'property_mynewobject_somefield': fields.property(
'mynewobject.somefield',
type='many2one',
relation='mynewobject.somefield',
string=Some Field,
method=True,
view_load=True,
group_name=My Properties),
}
res_partner()
xml:
record
fieldproperty_mynewobject_somefield/field
field
fieldmynewobject.somefield/field
/record
The new module installs but displays this error:
Sun, 09 Sep 2007 21:09:57 ERROR:web-services:Exception in call: Traceback (most
recent call last):
File /usr/lib/python2.5/site-packages/tinyerp-server/netsvc.py, line 206,
in _dispatch
r=m(*params)
File
/usr/lib/python2.5/site-packages/tinyerp-server/service/web_services.py, line
329, in execute
res = service.execute(db, uid, object, method, *args)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/osv.py, line 111,
in execute
res = pool.execute_cr(cr, uid, obj, method, *args, **kw)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/osv.py, line 92,
in execute_cr
res = getattr(object,method)(cr, uid, *args, **kw)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/orm.py, line 764,
in read
result = self._read_flat(cr, user, select, fields, context, load)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/orm.py, line 840,
in _read_flat
res2 = self._columns[f].get(cr, self, ids, f, user, context=context,
values=res)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/fields.py, line
525, in get
return self._fnct(obj, cr, user, ids, name, self._arg, context)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/fields.py, line
600, in _fnct_read
names = dict(obj.name_get(cr, uid, filter(None, res.values()), context))
AttributeError: 'NoneType' object has no attribute 'name_get'
and the new property appears on the Properties sidetab for the Partner however
no property now receives its default
value and when you try to add/edit the new property you receive this error:
Sun, 09 Sep 2007 21:10:07 ERROR:web-services:Exception in call: Traceback (most
recent call last):
File /usr/lib/python2.5/site-packages/tinyerp-server/netsvc.py, line 206,
in _dispatch
r=m(*params)
File
/usr/lib/python2.5/site-packages/tinyerp-server/service/web_services.py, line
329, in execute
res = service.execute(db, uid, object, method, *args)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/osv.py, line 111,
in execute
res = pool.execute_cr(cr, uid, obj, method, *args, **kw)
File /usr/lib/python2.5/site-packages/tinyerp-server/osv/osv.py, line 74,
in execute_cr
'Object %s doesn\'t exist' % str(obj))
File /usr/lib/python2.5/site-packages/tinyerp-server/netsvc.py, line 92, in
abortResponse
raise Exception(%s -- %s\n\n%s%(origin,description,details))
Exception: warning -- Object Error
Object mynewobject.somefield doesn't exist
I checked the ir_model_fields table and the entry is there for res.partner.
I followed the docs but this does not appear to work.
Gerry
___
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
[Tinyerp-users] Re: views: adding domain to restrict result set
Thanks Pedro. When I change the domain line to this: nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp; nbsp;field name=domain#91;'category','=','My Partners'#93;/field I now get this error: Traceback (most recent call last): File /usr/lib/python2.5/site-packages/tinyerp-server/netsvc.py, line 206, in _dispatch r=m(*params) File /usr/lib/python2.5/site-packages/tinyerp-server/service/web_services.py, line 329, in execute res = service.execute(db, uid, object, method, *args) File /usr/lib/python2.5/site-packages/tinyerp-server/osv/osv.py, line 111, in execute res = pool.execute_cr(cr, uid, obj, method, *args, **kw) File /usr/lib/python2.5/site-packages/tinyerp-server/osv/osv.py, line 92, in execute_cr res = getattr(object,method)(cr, uid, *args, **kw) File /usr/lib/python2.5/site-packages/tinyerp-server/osv/orm.py, line 1684, in search (qu1,qu2,tables) = self._where_calc(cr, user, args, context=context) File /usr/lib/python2.5/site-packages/tinyerp-server/osv/orm.py, line 1626, in _where_calc if x[0] in table._columns: AttributeError: 'str' object has no attribute '_columns' Gerry ___ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
