[tryton] default cost and list price

2018-04-21 Thread Francisco Maria Moyano Casco
Hi,
  I am trying to put a default cost and list price, but had no success.

  The code am working on is the next one: 
 

   @staticmethod
   def default_list_price():
   return 1.0
..

   I know that both fields are Property fields, and that is why my code doesn't 
work.

   I am inventoring all my assets, and I need to have some defaults values on 
the product.template

   Regards.
   Francisco

-- 
You received this message because you are subscribed to the Google Groups 
"tryton" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton/709b280d-f3a1-4951-984f-f27f10f0efa7%40googlegroups.com.


Re: [tryton-dev] import_data and model account with account_account_type (RESEND)

2018-04-21 Thread Richard PALO

Le 20/04/2018 à 20:22, Richard PALO a écrit :

Le 20/04/2018 à 20:15, Richard PALO a écrit :



Thanks, I'm finding the correct account.account.type instance now with
the following simplified snippet:

md, = ModelData.find(['fs_id', '=', data[-1]])
at, = AccountType.find(['template', '=', md.db_id])
   


But import_data() still balks...

Doesn't seem to like either at.id nor str(at.id)

Looked a bit at the code, which suggests that .rec_name should be used,
but that fails as well


data[-1] = at.rec_name
Account.import_data(header, [data], Account._config.context)



The exception message, which is for a type 'provisions_charges',
the first record in my file, gives:

trytond.exceptions.UserError: ('UserError', ("Relation not found: 'Plan de types de 
compte (France)PassifProvisionsProvisions   >pour charges' in 
account.account.type", ''))

The updated 'data' record is as follows:

['158200', 'Provisions pour risques et charges litiges', 'True', '158200', 
'other', '158', '', '', 'True', 'Plan de types de compte
(France)\\Passif\\Provisions\\Provisions pour charges']


I'm wondering if it's a quoting problem returned from rec_name?

Any suggestions?



BTW, It's choking in import_data's get_many2one()



Unless I'm missing something, this can not work currently.

The query generated to lookup 'rec_name' uses the simple 'name' :
'SELECT "a"."id" AS "id", "a"."balance_sheet" AS "balance_sheet", "a"."company" AS "company", "a"."create_date" AS "create_date",  
"a"."create_uid" AS "create_uid", "a"."display_balance" AS "display_balance", "a"."income_statement" AS "income_statement", "a"."name" AS  
"name", "a"."parent" AS "parent", "a"."sequence" AS "sequence", "a"."template" AS "template", "a"."write_date" AS "write_date",
"a"."write_uid" AS "write_uid", CAST(EXTRACT(%s FROM COALESCE("a"."write_date", "a"."create_date")) AS VARCHAR) AS "_timestamp" FROM   
"account_account_type" AS "a" WHERE "a"."name" = %s))) AND ((("a"."company" IN (%s) ORDER BY "a"."sequence" ASC NULLS FIRST,   
"a"."id" ASC LIMIT 2'


but get_rec_name() returns the hierarchy of names when there is a parent type,
case not treated for but which is *always* the case for account_account_type.

If I set on the header 'type:id', then the lookup seems to expect the 
identifier of
the account_account_type_template and not the instance of it in 
account_account_type
as it invokes ModelData.get_id() much like Sergi mentioned (and must be 
specified
like 'account_fr.provisions_charges'

This seems to imply indirectly what I feared in that the simple name *must* be 
unique
else the supporting code must know about treating for hierarchical names
and/or know about treating the instantiated template tables
and/or have a means to stipulate that the db 'id' is supplied for relations
(something like 'type:dbid').

cheers,
--
Richard PALO

--
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/d5cfeb94-ff1e-9875-1236-6f9e38d06f01%40netbsd.org.


Re: [tryton-dev] import_data and model account with account_account_type (RESEND)

2018-04-21 Thread Cédric Krier
On 2018-04-21 09:09, Richard PALO wrote:
> but get_rec_name() returns the hierarchy of names when there is a parent type,
> case not treated for but which is *always* the case for account_account_type.

Indeed, it will be good to customize the search_rec_name like in
party.category.

> If I set on the header 'type:id', then the lookup seems to expect the 
> identifier of
> the account_account_type_template and not the instance of it in 
> account_account_type
> as it invokes ModelData.get_id() much like Sergi mentioned (and must be 
> specified
> like 'account_fr.provisions_charges'

Yes ':id' suffix works only for XML id because they are the only unique
ID valid on different databases.


The script openerp2tryton is just a starting skeleton and the CSV import
is not the most powerful tool. It was used in openerp2tryton for simple
case. But it is still more powerful to write proteus script instead.

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

-- 
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/20180421082321.GA18860%40kei.


Re: [tryton-dev] import_data and model account with account_account_type (RESEND)

2018-04-21 Thread Richard PALO

Le 21/04/2018 à 10:23, Cédric Krier a écrit :

On 2018-04-21 09:09, Richard PALO wrote:

but get_rec_name() returns the hierarchy of names when there is a parent type,
case not treated for but which is *always* the case for account_account_type.


Indeed, it will be good to customize the search_rec_name like in
party.category.


If I set on the header 'type:id', then the lookup seems to expect the 
identifier of
the account_account_type_template and not the instance of it in 
account_account_type
as it invokes ModelData.get_id() much like Sergi mentioned (and must be 
specified
like 'account_fr.provisions_charges'


Yes ':id' suffix works only for XML id because they are the only unique
ID valid on different databases.


The script openerp2tryton is just a starting skeleton and the CSV import
is not the most powerful tool. It was used in openerp2tryton for simple
case. But it is still more powerful to write proteus script instead.



I tried adding the method search_rec_name() on account_account_type
but it doesn't seem to get called during import_data().  missing glue?

re: ':id', this is fine and preferred.
The point is that only the template classes have this (directly getting the 
dbid),
the instantiated classes need to reference that via template=dbid

So I'll just update account_account_template instead of account_account and do 
so
prior to creating the chart of accounts.. should have thought of that sooner:-/

WRT proteus script, I guess I don't understand, openerp2tryton seems to me a 
proteus
script as it *is* using proteus... how could it not be?

cheers,
--
Richard PALO

--
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/9bfd1cb1-5170-c0c5-3ab8-3622500bf459%40netbsd.org.


[tryton-dev] Un-assigned Tryton issue tracker requests

2018-04-21 Thread Tryton issue tracker
Created ID   Activity   Title
===
 bug
3 days ago  7365 yesterday admin account login error 
 bug
1 month ago 7232 2 weeks ago segv in client
 bug
12 months ago 6470 1 month ago Old migration to rename packing to shi ...

To view or respond to any of the requests listed above, visit the URL

   https://bugs.tryton.org/

and click on "Show Unassigned". Do NOT respond to this message.

-- 
You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton-dev/20180421222302.2A1411180246%40moretus.b2ck.com.