Tryton Technical Training

Transcription

1 Tryton Technical Training N. Évrard B 2CK September 18, 2015 N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

2 Overview and Installation Outline 1 Overview and Installation Tryton Overview Prerequisites Initializing tryton 2 A basic module 3 Some more advanced features 4 Additional topics N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

3 Overview and Installation Tryton Overview Global overview A general purpose application platform Web shop Insurance software GNU Health Traditional ERP Covers lot of fields Accounting Sales Management Stock Management... Free Software GPL-3 Tryton foundation TU* N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

4 Overview and Installation Tryton Overview Technical Overview Written in Python Three tiers architecture PyGTK client (tryton) and a JavaScript client (sao) in its infancy Application Server (trytond) dbms, usually PostgreSQL but you can use SQLite or even MySQL Modularity of business functionalities N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

5 Overview and Installation Prerequisites Python good practices (pip & virtualenv) pip is THE tool for installing and managing Python packages. virtualenv is THE tool used to create isolated Python environment. create isolated Python environments Do not mix different version of your libraries / applications Installation of packages in the user $HOME pip install virtualenv (or your distro package manager) virtualenv --system-site-packages.venv/trytond source.venv/trytond/bin/activate hgnested is a mercurial extension. The tryton project use it to easily apply the same command on nested repositories. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

6 Overview and Installation Prerequisites Configuring mercurial In order to activate both the hgnested and MQ extensions of Mercurial we will need to add those lines to your.hgrc [extensions] hgext.mq = hgnested = N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

7 Overview and Installation Initializing tryton Installing trytond $ hg nclone -b 3.4 $ cd trytond $ pip install -e. $ pip install vobject N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

8 Overview and Installation Initializing tryton Setting up a trytond config file Here is a minimal example of a configuration file. You should save it in $HOME/.trytond.conf [database] path = /home/training/databases We will set the TRYTOND_CONFIG environment variable $ export TRYTOND_CONFIG=$HOME/.trytond.conf N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

9 Overview and Installation Initializing tryton Initializing a minimal trytond database $ touch ~/databases/test.sqlite $./bin/trytond -d test -u ir res trytond will ask you for the admin password at the end of the installation process. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

10 Overview and Installation Initializing tryton Adding a new modules In this tutorial we will use a MQ repository in order to progress step by step. $ cd trytond/modules $ hg init training $ cd training/.hg $ hg clone -b 3.4 patches N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

11 A basic module Outline 1 Overview and Installation 2 A basic module A minimal module Defining some object / tables Different fields Defining a tree and a form view Default values and on_change calls 3 Some more advanced features 4 Additional topics N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

12 A basic module A minimal module A minimal trytond modules A minimal trytond modules needs two files: init.py the usual file needed by all python modules tryton.cfg the file that helps tryton glue together model and view definitions N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

13 A basic module A minimal module The content of tryton.cfg [tryton] version=0.0.1 depends: ir res N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

14 A basic module Defining some object / tables Creating a model A trytond model is a python class inheriting from Model. To enable the SQL persistence the model must inherit of ModelSQL. from t r y t o n d. model import ModelSQL a l l = [ O p p o r t u n i t y ] c l a s s Opportunity (ModelSQL ) : Opportunity name = t r a i n i n g. opportunity N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

15 A basic module Defining some object / tables Register the model In order for your object to be "known" by trytond they must be registered into the pool. from trytond. pool import Pool from. o p p o r t u n i t y import def r e g i s t e r ( ) : Pool. r e g i s t e r ( Opportunity, module= t r a i n i n g, type_= model ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

16 A basic module Defining some object / tables Adding fields to a model c l a s s Opportunity (ModelSQL ) : Opportunity name = t r a i n i n g. opportunity _rec_name = d e s c r i p t i o n description = fields. Char ( Description, required=true ) s t a r t _ d a t e = f i e l d s. Date ( S t a r t Date, required=true ) end_date = fields. Date ( End Date ) party = f i e l d s. Many2One ( party. party, Party, required=true ) comment = fields. Text ( Comment ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

17 A basic module Defining some object / tables fields arguments string A string for label of the field. required A boolean if True the field is required. readonly A boolean if True the field is not editable in the user interface. domain A list that defines a domain constraint. states A dictionary. Possible keys are required, readonly and invisible. Values are pyson expressions that will be evaluated with record values. This allows to change dynamically the attributes of the field. The whole list in trytond/model/fields/field.py N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

18 A basic module Different fields fields.char In a tryton module: description = fields. Char ( Description, required=true ) In the interface: In SQL: d e s c r i p t i o n VARCHAR NOT NULL N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

19 A basic module Different fields fields.date In a tryton module: start_ date = fields. Date ( Start Date, required=true ) In the interface: In SQL: s t a r t _ d a t e DATE NOT NULL N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

20 A basic module Different fields fields.text In a tryton module: comment = fields. Text ( Comment ) In the interface: In SQL: comment TEXT N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

21 A basic module Different fields fields.many2one In a tryton module: party = fields. Many2One ( party. party, Party, required=true ) In the interface: In SQL: p a r t y integer NOT NULL, FOREIGN KEY( p a r t y ) REFERENCES p a r t y _ p a r t y ( i d ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

22 A basic module Different fields Other relation fields fields.one2many fields.many2many fields.one2one N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

23 A basic module Defining a tree and a form view Displaying data To use the presentation layer your model must inherit from ModelView c l a s s Opportunity (ModelSQL, ModelView ) : You must also add the xml presentation file in the tryton.cfg configuration file xml: opportunity.xml N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

24 A basic module Defining a tree and a form view Defining a view View objects are normal tryton objects (trytond/ir/ui/view.py) Two kind of view: Tree view a list of record Form view a view for editing/creating one record N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

25 A basic module Defining a tree and a form view A tree view < r e c o r d model=" i r. u i. view " i d =" o p p o r t u n i t y _ v i e w _ l i s t "> < field name=" model ">training. opportunity</ field > < f i e l d name=" t y p e "> t r e e < / f i e l d > < field name="name "> opportunity_ list < / field > < / r e c o r d > < t r e e s t r i n g =" O p p o r t u n i t i e s "> < f i e l d name=" p a r t y " / > < field name=" description " / > < f i e l d name=" s t a r t _ d a t e " / > < field name=" end_date " / > < / t r e e > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

26 A basic module Defining a tree and a form view A form view <record model=" ir. ui. view " id=" opportunity_view_form "> < field name=" model ">training. opportunity</ field > < field name=" type ">form< / field > < field name="name ">opportunity_form</ field > < / r e c o r d > <form s t r i n g =" O p p o r t u n i t y "> < l a b e l name=" p a r t y " / > < f i e l d name=" p a r t y " / > < l a b e l name=" d e s c r i p t i o n " / > < field name=" description " / > < l a b e l name=" s t a r t _ d a t e " / > < f i e l d name=" s t a r t _ d a t e " / > <label name=" end_date " / > < field name=" end_date " / > < s e p a r a t o r name=" comment " c o l s p a n =" 4 " / > < field name="comment " colspan="4" / > < / form> N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

27 A basic module Defining a tree and a form view Gluing them together <record model=" i r. action. act_window " i d =" a c t _ o p p o r t u n i t y _ f o r m "> < field name="name ">Opportunities</ field > < field name=" res_model ">training. opportunity</ field > < / r e c o r d > < r e c o r d model=" i r. a c t i o n. act_window. view " i d =" a c t _ o p p o r t u n i t y _ f o r m _ v i e w 1 "> < field name=" sequence " eval="10 " / > < f i e l d name=" view " r e f =" o p p o r t u n i t y _ v i e w _ t r e e " / > < f i e l d name=" act_window " r e f =" a c t _ o p p o r t u n i t y _ f o r m " / > < / r e c o r d > < r e c o r d model=" i r. a c t i o n. act_window. view " i d =" a c t _ o p p o r t u n i t y _ f o r m _ v i e w 2 "> < field name=" sequence " eval="20 " / > < field name=" view " ref=" opportunity_view_form " / > < f i e l d name=" act_window " r e f =" a c t _ o p p o r t u n i t y _ f o r m " / > < / r e c o r d > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

28 A basic module Defining a tree and a form view Adding menu entries <menuitem name=" T r a i n i n g " i d =" m e n u _ t r a i n i n g " / > <menuitem parent=" menu_training " a c t i o n =" a c t _ o p p o r t u n i t y _ f o r m " id=" menu_opportunity_form " / > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

29 A basic module Default values and on_change calls Adding default values Create a method in the object with the name s t a t i c m e t h o d def d e f a u l t _ s t a r t _ d a t e ( ) : pool = Pool ( ) Date = pool. g e t ( i r. d a t e ) return Date. t o d a y ( ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

30 A basic module Default values and on_change calls Reacting to user input: on_change Tryton provides a way to react on the user input by changing the value of other fields. This mechanism is call the on_changes. They come in two flavours: on_change_<field name> When a field is changed a list of value is sent to the server. The server sends the new values of some fields on_change_with_<field name> A field value is computed when any field in a list of fields is modified. The computation occurs on the server. In both case the list of fields sent to the server is specified thanks to the N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

31 A basic module Default values and on_change calls f i e l d s. depends ( p a r t y ) def on_change_party ( s e l f ) : a d d r e s s = None i f s e l f. p a r t y : a d d r e s s = s e l f. p a r t y. a d d r e s s _g e t ( type = i n v o i c e ) return { a d d r e s s : a d d r e s s, } N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

32 A basic module Default values and on_change calls f i e l d s. depends ( s t a r t _ d a t e ) def on_change_with_end_date ( s e l f ) : i f s e l f. s t a r t _ d a t e : return self. start_ date + datetime. timedelta ( days =7) return None N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

33 Some more advanced features Outline 1 Overview and Installation 2 A basic module 3 Some more advanced features Workflows More beautiful views Function fields Wizards Extending pre-existing tryton objects 4 Additional topics N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

34 Some more advanced features Workflows Adding workflow to object Your object should inherit from Workflow c l a s s Opportunity ( Workflow, ModelSQL, ModelView ) : It must have a state field: s t a t e = f i e l d s. Selection ( [ ( o p p o r t u n i t y, O p p o r t u n i t y ), ( c o n v e r t e d, Converted ), ( l o s t, Lost ), ], S t a t e, r e q u i r e d =True, r e a d o n l y =True, s o r t = F a l s e ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

35 Some more advanced features Workflows Defining a workflow A workflow is composed of def s e t u p ( c l s ) : super ( O p p o r t u n i t y, c l s ). s e t u p ( ) c l s. _ t r a n s i t i o n s \ = s e t ( ( ( o p p o r t u n i t y, c o n v e r t e d ), ( o p p o r t u n i t y, l o s t ), ) ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

36 Some more advanced features Workflows Defining transition method Each transition must be linked a t r a n s i t i o n ( c o n v e r t e d ) def c o n v e r t ( cls, o p p o r t u n i t i e s ) : pool = Pool ( ) Date = pool. g e t ( i r. d a t e ) c l s. w r i t e ( o p p o r t u n i t i e s, { e n d _ d a t e : Date. t o d a y ( ), } ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

37 Some more advanced features Workflows Adding buttons in view Now we need to add buttons in the view <button name=" convert " string =" Convert " icon=" tryton go next " / > The method must be "button decorated" to be callable and def s e t u p ( c l s ) :... c l s. _ b u t t o n s. u p d a t e ( { c o n v e r t : {}, l o s t : {}, t r a n s i t i o n ( c o n v e r t e d ) def c o n v e r t ( cls, o p p o r t u n i t i e s ) :... N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

38 Some more advanced features More beautiful views Making the view more beautiful Let s add the state and the buttons to the opportunity view. There is also a way of grouping widgets <group co l =" 2 " colspan =" 2 " id =" s t a t e "> < l a b e l name=" s t a t e " / > < f i e l d name=" s t a t e " / > < / group > <group c o l =" 2 " c o l s p a n =" 2 " i d =" b u t t o n s "> <button name=" lost " string =" Lost " icon=" tryton cancel " / > <button name=" convert " string =" Convert " icon=" tryton go next " / > < / group > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

39 Some more advanced features More beautiful views Adding dynamicity in the form Of course sometimes you want to make fields readonly/invisible/required under certain conditions. This behavior can be implemented using the states attribute of fields: start_ date = fields. Date ( Start Date, required=true, s t a t e s ={ r e a d o n l y : Eval ( s t a t e )!= o p p o r t u n i t y, }, depends =[ s t a t e ] ) end_date = fields. Date ( End Date, readonly=true, s t a t e s ={ r e q u i r e d : Eval ( s t a t e ). i n _ ( [ c o n v e r t e d, l o s t ] ), }, depends =[ s t a t e ] ) pyson is used to encode statements that can be evaluated. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

40 Some more advanced features More beautiful views Adding dynamicity to buttons pyson expression can also be used on buttons to hide def s e t u p ( c l s ) :... c l s. _ b u t t o n s. u p d a t e ( { c o n v e r t : { i n v i s i b l e : ~ Eval ( s t a t e ) \. i n _ ( [ o p p o r t u n i t y ] ), }, l o s t : { i n v i s i b l e : ~ Eval ( s t a t e ) \. i n _ ( [ o p p o r t u n i t y ] ), }, } ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

41 Some more advanced features Function fields Defining a simple function field A function field is a field that is computed into python its data is not persistently store into the database. d u r a t i o n = f i e l d s. F u n c t i o n ( f i e l d s. I n t e g e r ( D u r a t i o n ), g e t _d u r a t i o n ) def get_duration ( self, name=none ) : i f not s e l f. s t a r t _ d a t e or not s e l f. end_date : return None return ( s e l f. e n d _ d a t e s e l f. s t a r t _ d a t e ). days Any tryton type can be used. Note also that since this signature is the same as the one of an on_change_with then the same function can be used for both. Of course a setter and a searcher can also be defined in order to modify or search corresponding data. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

42 Some more advanced features Function fields Defining a function field operating by batch The previous example makes one call per record. Tryton provides a way to compute the values by batch. In order to do so the getter must be a classmethod and it must return a dictionary mapping the id to the function value. d e s c r i p t i o n _ l e n g t h = f i e l d s. F u n c t i o n ( f i e l d s. I n t e g e r ( D e s c r i p t i o n Length ), g e t _ d e s c r i p t i o n _ l e n g t h def get_ description_ length ( cls, opportunities, name ) : cursor = Transaction. cursor ( ) o p p o r t u n i t y = c l s. t a b l e ( ) query = o p p o r t u n i t y. s e l e c t ( opportunity. id, CharLength ( opportunity. description ) ) c u r s o r. e x e c u t e ( query ) return d i c t ( c u r s o r. f e t c h a l l ( ) ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

43 Some more advanced features Wizards Adding actions to model Sometime you want to add functionalities to a model that do not suite the use of a button. For this kind of use case the wizard is your solution. A wizard is composed of two things: A set of views that represent the form to gather the user input A "state machine" that define what should be done N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

44 Some more advanced features Wizards Wizard views Those are standard ModelView, you can define on_change, on_change_with and default values on them. c l a s s C o n v e r t O p p o r t u n i t i e s S t a r t ( ModelView ) : Convert Opportunities name = t r a i n i n g. o p p o r t u n i t y. c o n v e r t. s t a r t N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

45 Some more advanced features Wizards Wizard "state machine" This is a class that inherits from Wizard. You ll be able to define different states on it. from trytond. wizard import Wizard, StateView, S t a t e T ra n s i t i o n, Button c l a s s C o n v e r t O p p o r t u n i t i e s ( Wizard ) : Convert Opportunities name = t r a i n i n g. opportunity. convert s t a r t = StateView ( t r a i n i n g. o p p o r t u n i t y. c o n v e r t. s t a r t, t r a i n i n g. opportunity_ convert_ start_ view_ form, [ Button ( Cancel, end, t r y t o n c a n c e l ), Button ( Convert, c o n v e r t, t r y t o n ok, d e f a u l t =True ), ] ) convert = S t a t e T r a n s i t i o n ( ) def t r a n s i t i o n _ c o n v e r t ( s e l f ) : pool = Pool ( ) O p p o r t u n i t y = pool. g e t ( t r a i n i n g. o p p o r t u n i t y ) opportunities = Opportunity. browse ( T r a n s a c t i o n ( ). c o n t e x t [ a c t i v e _ i d s ] ) O p p o r t u n i t y. c o n v e r t ( o p p o r t u n i t i e s ) return end N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

46 Some more advanced features Wizards Activating the wizard <record model=" ir. action. wizard " id=" act_ convert_ opportunities "> < field name="name ">Convert Opportunities</ field > < field name=" wiz_name ">training. opportunity. convert</ field > < field name=" model ">training. opportunity</ field > < / r e c o r d > < r e c o r d model=" i r. a c t i o n. keyword " i d =" a c t _ c o n v e r t _ o p p o r t u n i t i e s _ k e y w o r d "> < field name=" keyword ">form_action</ field > < field name=" model ">training. opportunity, 1< / field > < field name=" action " ref=" act_ convert_ opportunities " / > < / r e c o r d > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

47 Some more advanced features Extending pre-existing tryton objects Extending models Sometimes you want to extend existing objects to add miscellaneous information. Doing so is just a matter of (tryton) inheritance: from t r y t o n d. model import f i e l d s from trytond. pool import PoolMeta a l l = [ P a r t y ] m e t a c l a s s = PoolMeta c l a s s Party : name = p a r t y. p a r t y opportunities = f i e l d s. One2Many ( t r a i n i n g. o p p o r t u n i t y, p a r t y, Opportunities ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

48 Some more advanced features Extending pre-existing tryton objects Extending existing views Modifing existing view is done by adding record in the XML files that specify an xpath and what to do with the resulting node. <record model=" ir. ui. view " id=" party_view_form "> < field name=" model ">party. party</ field > < field name=" inherit " ref=" party. party_view_form " / > < field name="name ">party_form</ field > < / r e c o r d > < d a t a > <xpath expr=" / form / notebook / page accounting ] " p o s i t i o n =" a f t e r "> <page name=" o p p o r t u n i t i e s " c o l =" 1 "> < s e p a r a t o r name=" o p p o r t u n i t i e s " / > < field name=" opportunities " / > < / page > < / x p a t h > < / d a t a > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

49 Additional topics Outline 1 Overview and Installation 2 A basic module 3 Some more advanced features 4 Additional topics Reporting proteus Table Queries N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

50 Additional topics Reporting Adding a report To add a report you must create an odt template that is compatible with relatorio ( This report engine allows you to create opendocument files from templates. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

51 Additional topics Reporting Making trytond aware of the report You must define a python class that will register a report object from trytond. r e p o r t import Report c l a s s O p p o r t u n i t y R e p o r t ( Report ) : pass You might want to overload the parse method to define a specific behavior. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

52 Additional topics Reporting Creating the report object < r e c o r d model=" i r. a c t i o n. r e p o r t " i d =" r e p o r t _ o p p o r t u n i t y "> < field name="name ">Opportunity</ field > < field name=" model ">training. opportunity</ field > < field name=" report_name ">training. opportunity</ field > < field name=" report ">training / opportunity. odt< / field > < / r e c o r d > <record model=" i r. action. keyword " i d =" r e p o r t _ o p p o r t u n i t y _ k e y w o r d "> < field name=" keyword ">form_print</ field > < field name=" model ">training. opportunity, 1< / field > < field name=" action " ref=" report_ opportunity " / > < / r e c o r d > N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

53 Additional topics proteus Using proteus to script tryton You might want to script your tryton server. For this there is the proteus library. It will allow you to interact with it in a python way. With models you will be able to use the find, edit, delete and create objects You will also have the possiblity to use the wizards. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

54 Additional topics proteus Setting up proteus To set up proteus, you first need a connection to a Tryton server: either through xml-rpc using the set_xmlrpc method or on the same compute using the set_trytond method The latter will use the possibility to import trytond to create and set up an internal trytond server. N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

55 Additional topics proteus An example of proteus i m p o r t csv i m p o r t d a t e t i m e i m p o r t s y s from proteus import config, Model d e f main ( a r g s ) : P a r t y = Model. g e t ( p a r t y. p a r t y ) Opportunity = Model. get ( training. opportunity ) c s v _ f i l e = csv. D i c t R e a d e r ( open ( a r g s [ 1 ], r ) ) f o r l i n e i n c s v _ f i l e : p a r t i e s = P a r t y. f i n d ( [ ( name, =, l i n e [ P a r t y ] ) ] ) i f n o t p a r t i e s : p a r t y = P a r t y ( name= l i n e [ P a r t y ] ) p a r t y. s ave ( ) e l s e : party = p a r t i e s [ 0 ] l i n e _ d a t e = d a t e t i m e. d a t e t i m e. s t r p t i m e ( l i n e [ Date ], %d/%m/%y ). d a t e ( ) new_opportunity = O p p o r t u n i t y ( p a r t y = party, description=line [ Description ], start_ date =line_ date ) new_opportunity. save ( ) i f name == main : c o n f i g. s e t _ t r y t o n d ( password = admin, database_name = t r a i n i n g ) main ( s y s. argv ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56

56 Additional topics Table Queries Creating a view object table_query allows you to define a sql-query to use as source of the records. c l a s s OpportunityByParty (ModelSQL, ModelView ) : O p p o r t u n i t i e s by P a r t y name = t r a i n i n g. opportunity_ by_ party party = fields. Many2One ( party. party, Party, readonly=true ) opportunity_count = fields. Integer ( Opportunity count, readonly=true def t a b l e _ q u e r y ( c l s ) : pool = Pool ( ) o p p o r t u n i t y _ t a b l e = pool. g e t ( t r a i n i n g. o p p o r t u n i t y ). t a b l e ( ) columns = [ Min ( o p p o r t u n i t y _ t a b l e. id ). as_ ( i d ), Max( opportunity_ table. create_uid ). as_ ( create_uid ), Max( o p p o r t u n i t y _ t a b l e. c r e a t e _ d a t e ). as_ ( c r e a t e _ d a t e ), Max( o p p o r t u n i t y _ t a b l e. w r i t e _ u i d ). as_ ( w r i t e _ u i d ), Max( o p p o r t u n i t y _ t a b l e. write_date ). as_ ( write_date ), opportunity_ table. party, Count ( o p p o r t u n i t y _ t a b l e. id ). as_ ( o p p o r t u n i t y _ c o u n t ), ] group_by = [ o p p o r t u n i t y _ t a b l e. p a r t y ] return opportunity_ table. select ( columns, group_by=group_by ) N. Évrard (B 2 CK) Tryton Technical Training September 18, / 56