openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #04711
Re: tests/feedbacks for the new reporting
On 01/29/2014 01:08 PM, Joël Grand-Guillaume wrote:
> May be this new qweb engine html -> pdf can be use to print out the pdf
> of the current list view !?
May be, but it's not our focus for now on. We will mostly focus on
fixing bugs on reports, rather than adding new features.
>
>
> On Wed, Jan 29, 2014 at 12:19 PM, Mantavya Gajjar <mga@xxxxxxxxxxx
> <mailto:mga@xxxxxxxxxxx>> wrote:
>
> Hello Simon,
>
> The only one major difference between chrome and firefox is
>
> firefox : you will be able to see the header (Table Header) and
> footer (totals) on each page which is a Table Header / Footer
> chrome: you will get a exact same report exclude the header and
> footer (total) on each page as webkit does not support
>
> Rest I don;t think its a big problem, like firefox support a
> configuration of where to put what information in term of header and
> footer, while chrome does not allow you to configure those options.
>
>
> Mantavya Gajjar
> Director
> Tiny ERP Private limited
> 16 & 17 IT Tower-I
> Info City, Gandhinagar
> Pin code: 382009
> Gujarat, India
>
> Phone : +91 79 40 500 100, Ext. 202 <tel:%2B91%2079%2040%20500%20100%2C%20Ext.%20202>
> Website: http://www.openerp.com <http://www.openerp.com/>
> Twitter: @mantavyagajjar
>
>
>
>
>
>
>
> On 29-Jan-2014, at 3:49 pm, Simon Lejeune <sle@xxxxxxxxxxx
> <mailto:sle@xxxxxxxxxxx>> wrote:
>
>> Hello Mantavya,
>> I will test your css improvement, thanks for sharing it.
>> But i'm pretty sure that the same page printed by chrome will look
>> horribly bad, because of chrome print engine (sad) lack of support
>> of repeating thead/tfoot and correct table break...
>> So maybe it's not a good direction to go if the only browser able
>> to print it correctly is firefox.
>> But anyway, i will try it.
>>
>> Thanks!
>>
>>
>> On Wed, Jan 29, 2014 at 10:34 AM, Joël Grand-Guillaume
>> <joel.grandguillaume@xxxxxxxxxxxxxx
>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>> wrote:
>>
>> Hi Mantavya, Simon
>>
>>
>> Thanks for sharing the .css ! That's what we want for dynamic
>> report based on group by views.
>>
>> @Simon, could you integrated that one in the new qweb-report
>> branch ? I mean, if someone inside OpenERP has already make
>> the work of improving the layout of the @media print browser
>> function, it would be nice to include it here for everyone
>> don't you think ?
>>
>> For the layout of the sale and invoice, that's an interesting
>> point as well. Happy to see that. But it won't apply in a
>> "generic" way for every model. It's a good features for some
>> people for sure though.
>>
>> But having the group by printed properly serve another purpose
>> : you suddenly have access to unlimited possibilities of
>> reports in standard ! that would be amazing.
>>
>> Regards,
>>
>> Joël
>>
>>
>>
>>
>> On Wed, Jan 29, 2014 at 10:23 AM, Simon Lejeune
>> <sle@xxxxxxxxxxx <mailto:sle@xxxxxxxxxxx>> wrote:
>>
>> @Joel:
>> Hello,
>> You should try the sale_layout module. It allows you to
>> create categories and to assign a sale line into a
>> category. The sales lines will be ordered by their
>> category's sequence in the listview. It is a groupby.
>>
>> Instructions: Create a quotation, then insert some order
>> lines. When you insert one, just fill the "layout
>> category" field (the first one). When you click on save to
>> validate all your order lines, the order will be updated
>> and will be the same when printing the sale order.
>> (This module applies only to sale order and invoice)
>>
>>
>>
>> On Wed, Jan 29, 2014 at 10:02 AM, Mantavya Gajjar
>> <mga@xxxxxxxxxxx <mailto:mga@xxxxxxxxxxx>> wrote:
>>
>> sorry forget to attached file each time, use this
>> media print function
>>
>>
>>
>> Mantavya Gajjar
>> Director
>> Tiny ERP Private limited
>> 16 & 17 IT Tower-I
>> Info City, Gandhinagar
>> Pin code: 382009
>> Gujarat, India
>>
>> Phone : +91 79 40 500 100, Ext. 202 <tel:%2B91%2079%2040%20500%20100%2C%20Ext.%20202>
>> Website: http://www.openerp.com <http://www.openerp.com/>
>> Twitter: @mantavyagajjar
>>
>>
>>
>>
>>
>>
>>
>> On 29-Jan-2014, at 2:29 pm, Mantavya Gajjar
>> <mga@xxxxxxxxxxx <mailto:mga@xxxxxxxxxxx>> wrote:
>>
>>> Also take the css we wrote quickly just to solve few
>>> problem, may help you.
>>> Mantavya Gajjar
>>> Director
>>> Tiny ERP Private limited
>>> 16 & 17 IT Tower-I
>>> Info City, Gandhinagar
>>> Pin code: 382009
>>> Gujarat, India
>>>
>>> Phone : +91 79 40 500 100, Ext. 202 <tel:%2B91%2079%2040%20500%20100%2C%20Ext.%20202>
>>> Website: http://www.openerp.com <http://www.openerp.com/>
>>> Twitter: @mantavyagajjar
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 29-Jan-2014, at 2:05 pm, Joël Grand-Guillaume
>>> <joel.grandguillaume@xxxxxxxxxxxxxx
>>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>> wrote:
>>>
>>>> Hi Fabien,
>>>>
>>>> Yes, I know, but look at the following print (tested
>>>> on qweb-report branch), you see that columns are
>>>> scraped, total of group by aren't here so in the end
>>>> it isn't usable.
>>>>
>>>> That's very sad, cause honestly, it'll be a sooo
>>>> amzing feature to have proper report this way :)
>>>>
>>>> No ?
>>>>
>>>> Joël
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jan 29, 2014 at 9:23 AM, Fabien
>>>> Pinckaers <fp@xxxxxxxxxxx
>>>> <mailto:fp@xxxxxxxxxxx>> wrote:
>>>>
>>>>
>>>> > I just though about something :
>>>> >
>>>> > * Would it be that difficult to be able to
>>>> print the current list view,
>>>> > respecting the filter and 'group by' currently
>>>> used ?!
>>>> >
>>>> > I mean, it's not the first time we talk about
>>>> that idea. It'll introduce
>>>> > then thousands of possible reports out of the
>>>> box, without any
>>>> > additional work required.
>>>> >
>>>> > That could be really an amazing one, what do
>>>> you think ?
>>>>
>>>> It's the print feature of the browser.
>>>> We already worked to make it quite clean (but it
>>>> could mbe improved with
>>>> just a few CSS lines)
>>>>
>>>> >
>>>> > Regards,
>>>> >
>>>> > Joël
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Tue, Jan 28, 2014 at 12:12 PM, Simon
>>>> Lejeune <sle@xxxxxxxxxxx <mailto:sle@xxxxxxxxxxx>
>>>> > <mailto:sle@xxxxxxxxxxx
>>>> <mailto:sle@xxxxxxxxxxx>>> wrote:
>>>> >
>>>> > Hello everyone,
>>>> >
>>>> > @ Nicolas:
>>>> > I will soon write a little guide about
>>>> report writing.
>>>> > Simple idea is, as the report is a
>>>> webpage, behind it you have an
>>>> > http controller that is associated to an
>>>> url and a qweb template.
>>>> > All report's url follow the form
>>>> /report/module.report_name(/ids).
>>>> > For simple reports (for instance, only
>>>> displaying fields), you won't
>>>> > have to write any python code because you
>>>> will use the generic http
>>>> > controller. Just write the Qweb template
>>>> and access your objects
>>>> > with 'o.fields'.
>>>> > If your report need additionnal method to
>>>> preprocess data, you will
>>>> > have to write your own controller
>>>> overriding the report url:
>>>> > /report/yourmodule.yourreportname.
>>>> >
>>>> > @ Axel:
>>>> > Some documentation could be written in a
>>>> few weeks, but for the
>>>> > moment i have nothing to bring you.
>>>> > By looking at the sale order report, you
>>>> can have an overview of
>>>> > almost all functionalities needed in
>>>> reports : t-field to display
>>>> > the field a browse record, t-if,
>>>> t-foreach/t-as, t-call to call
>>>> > another template, t-set to assign a
>>>> variable and the groups
>>>> > attribute to hide the tag where it is applied.
>>>> > If you are familiar with the jinja2
>>>> syntax, you won't have any
>>>> > problems as this one is even simpler.
>>>> >
>>>> > @ Ashok Dudla: pull the branch and have a
>>>> look at a 'simple' module
>>>> > like sale. Report is under the 'views'
>>>> folder. Don't forget to
>>>> > declare the report in a
>>>> modulename_reports.xml on the root folder.
>>>> >
>>>> > @ Fedinand and Jeff: nice (and logic)
>>>> remark. It is done in rev9491:
>>>> > when the address of delivery and shipping
>>>> are the same, they're
>>>> > printed only once. Thanks.
>>>> >
>>>> > @ Joel:
>>>> > * In the delivery slip (printed from a
>>>> delivery order), note
>>>> > written at the bottom aren't printed on
>>>> the report. That's sad and
>>>> > not difficult to fix.
>>>> > &&
>>>> > * The invoice seems not to have the
>>>> proper / same header (with
>>>> > logo) than other. It seems to me that some
>>>> report doesn't have the
>>>> > same header and footer at all. For
>>>> example, Receipt and delivery
>>>> > slip header are different from SO / PO.
>>>> Invoice has no logo, etc...
>>>> > You should verify that all docs are
>>>> printed with a same header/look
>>>> > and feel
>>>> > >> It is because most of the stock related
>>>> reports are not converted
>>>> > to QWeb report, they're still RML. Stock
>>>> has gone through major
>>>> > changes in another branch and i'm waiting
>>>> a merge to convert them.
>>>> > Sorry for not saying this before.
>>>> >
>>>> > * How could we move a block or field, for
>>>> example, the payment term
>>>> > in the SO before the lines, is that possible ?
>>>> > >>> Go to customize, HTML Editor and chose
>>>> report_saleorder. You
>>>> > will see that the payment terms bloc is at
>>>> the end of he document
>>>> > and declared as <span
>>>> t-field="o.payment_term"/>. Just cut and paste
>>>> > this block before the sale lines and it's
>>>> done (line 113).
>>>> >
>>>> > * IMO the tax report should not display
>>>> the line with 0 (this is
>>>> > also a trouble on current version though,
>>>> but would be nice to fix
>>>> > it in the meanwhile)
>>>> > >>> I will add a boolean in the wizard to
>>>> let the user chose to hide
>>>> > the zero lines.
>>>> >
>>>> > * On the General Ledger, you may have a
>>>> performance trouble. Not
>>>> > sure, but without any entries, it still
>>>> take around 45 sec to print
>>>> > ! May be something strange here...
>>>> > >>> I will have a look, thanks. RML report
>>>> takes about 15 secs.
>>>> >
>>>> > Thanks for your remarks!
>>>> >
>>>> >
>>>> > On Tue, Jan 28, 2014 at 10:35 AM, Joël
>>>> Grand-Guillaume
>>>> > <joel.grandguillaume@xxxxxxxxxxxxxx
>>>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>
>>>> > <mailto:joel.grandguillaume@xxxxxxxxxxxxxx
>>>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>>> wrote:
>>>> >
>>>> > Hi,
>>>> >
>>>> >
>>>> > A few remarks after testing the report
>>>> it-self:
>>>> >
>>>> > * In the delivery slip (printed from
>>>> a delivery order), note
>>>> > written at the bottom aren't printed
>>>> on the report. That's sad
>>>> > and not difficult to fix.
>>>> >
>>>> > * How could we move a block or field,
>>>> for example, the payment
>>>> > term in the SO before the lines, is
>>>> that possible ?
>>>> >
>>>> > * The invoice seems not to have the
>>>> proper / same header (with
>>>> > logo) than other. It seems to me that
>>>> some report doesn't have
>>>> > the same header and footer at all. For
>>>> example, Receipt and
>>>> > delivery slip header are different
>>>> from SO / PO. Invoice has no
>>>> > logo, etc... You should verify that
>>>> all docs are printed with a
>>>> > same header/look and feel
>>>> >
>>>> > * IMO the tax report should not
>>>> display the line with 0 (this
>>>> > is also a trouble on current version
>>>> though, but would be nice
>>>> > to fix it in the meanwhile)
>>>> >
>>>> > * On the General Ledger, you may have
>>>> a performance trouble. Not
>>>> > sure, but without any entries, it
>>>> still take around 45 sec to
>>>> > print ! May be something strange here...
>>>> >
>>>> >
>>>> > Good luck !
>>>> >
>>>> > Regards,
>>>> >
>>>> > Joël
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Tue, Jan 28, 2014 at 9:33 AM, Joël
>>>> Grand-Guillaume
>>>> > <joel.grandguillaume@xxxxxxxxxxxxxx
>>>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>
>>>> >
>>>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx
>>>> <mailto:joel.grandguillaume@xxxxxxxxxxxxxx>>> wrote:
>>>> >
>>>> > Hello Fabien,
>>>> >
>>>> > Thanks for that answer, I do now
>>>> understand more the purpose
>>>> > ! That is really welcome, and if
>>>> the right management check
>>>> > is made before save event, that
>>>> would perfectly fit
>>>> > everybody's need !
>>>> >
>>>> > Great devs in any case, thanks !
>>>> >
>>>> > Regards,
>>>> >
>>>> >
>>>> > Joël
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Mon, Jan 27, 2014 at 8:07 PM,
>>>> Fabien Pinckaers
>>>> > <fp@xxxxxxxxxxx
>>>> <mailto:fp@xxxxxxxxxxx> <mailto:fp@xxxxxxxxxxx
>>>> <mailto:fp@xxxxxxxxxxx>>> wrote:
>>>> >
>>>> > Joel,
>>>> >
>>>> > * When I edit a report, I
>>>> edit both the template
>>>> > and the current SO (e.g.
>>>> SO00007). I don't know
>>>> > which of my modifications
>>>> will appear on all reports
>>>> > and which will only apply
>>>> on my current editing SO.
>>>> >
>>>> > That is a problem. Wee
>>>> need to know which part we're
>>>> > editing : the template of
>>>> all SO, or only this SO ?!
>>>> > In term of right
>>>> management as well, I want my
>>>> > salesman to print good SO
>>>> for my customer, but I
>>>> > don't want them to change
>>>> my template layout...
>>>> >
>>>> >
>>>> > The goal of this branch is
>>>> certainly not to have
>>>> > salesman to edit reports in
>>>> OpenERP. It's an alternative
>>>> > to RML, Office Report
>>>> Designer, Jasper Report, Webkit
>>>> > reports, ... It's more for
>>>> partners to quickly create or
>>>> > customize reports like sales
>>>> order, invoices, delivery
>>>> > orders, ... They can use the
>>>> edit inline feature, but
>>>> > they will certainly use the
>>>> HTML Editor feature from the
>>>> > Customize menu.
>>>> >
>>>> > Having said that, the system
>>>> is so simple and powerful
>>>> > that it actually works for
>>>> salesman to edit reports too:
>>>> > - it follows access rights:
>>>> the salesman will not be
>>>> > able to change the design of a
>>>> report, only products
>>>> > related fields (it can be
>>>> improved in a way so that zone
>>>> > are not even accessible,
>>>> currently the check is at the
>>>> > save only)
>>>> > - it shows a yellow border
>>>> when you edit a record, no
>>>> > yellow border when you edit
>>>> the design of the sale order
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > I don't know how, but I
>>>> strongly suggest :
>>>> >
>>>> > * to have various level
>>>> of editing possibility
>>>> > related to the user's
>>>> right: an admin will be able
>>>> > to edit the template where
>>>> a salesman will only edit
>>>> > the current SO
>>>> > * to have a visual way to
>>>> identify what belong to
>>>> > the template and what
>>>> belong to the current report
>>>> > while editing
>>>> > * If it is not possible,
>>>> better to ensure all the
>>>> > modification are only for
>>>> the current report to save
>>>> > headache to people ;)
>>>> >
>>>> > Keep up the good work !
>>>> >
>>>> >
>>>> > Regards,
>>>> >
>>>> > Joël
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Mon, Jan 27, 2014 at
>>>> 11:16 AM, Simon Lejeune
>>>> > <sle@xxxxxxxxxxx
>>>> <mailto:sle@xxxxxxxxxxx> <mailto:sle@xxxxxxxxxxx
>>>> <mailto:sle@xxxxxxxxxxx>>> wrote:
>>>> >
>>>> > Hello everyone,
>>>> > I'm working on the
>>>> reporting part of OpenERP and
>>>> > i need your help. I'm
>>>> now at a development phase
>>>> > where mass testing of
>>>> this feature can be
>>>> > (really) appreciable.
>>>> >
>>>> > Big idea is that the
>>>> reports are now complete
>>>> > webpages, so they are
>>>> customizable using html
>>>> > code. Inside your html
>>>> code, you can use a
>>>> > simple 'magic' syntax
>>>> to display fields of a
>>>> > browse record, etc. I
>>>> encourage you to check the
>>>> > sale order report for
>>>> a speaking sample.
>>>> >
>>>> > The first thing you'll
>>>> see when testing the sale
>>>> > order is a pdf result.
>>>> How can you modify it ?
>>>> > by displaying the html
>>>> version of this report.
>>>> > Two way of doing this:
>>>> > 1) activate the
>>>> technical feature and go to
>>>> > settings > reportings
>>>> > reports > search for
>>>> > sale.order and replace
>>>> report's type from
>>>> > 'qweb-pdf' to 'qweb-html'.
>>>> > 2) just edit the url from
>>>> >
>>>> /report/pdf/report/sale.report_saleorder/7 to
>>>> >
>>>> /report/sale.report_saleorder/7
>>>> >
>>>> > I think you now get
>>>> the idea : qweb-pdf is the
>>>> > printed qweb-html.
>>>> >
>>>> > To customize the pdf
>>>> result you can set
>>>> > paperformat records in
>>>> >
>>>> settings>technical>reporting>Paper Format and
>>>> > set one by default on
>>>> your company and/or
>>>> > explicitely associate
>>>> a report to a paper
>>>> > format. You can define
>>>> dpi, margin-top etc on them.
>>>> >
>>>> > Known issues:
>>>> > Header and footer of
>>>> the resulting pdf: you have
>>>> > to define your header
>>>> in a <reportheader> tag
>>>> > and footer in a
>>>> <reportfooter> one. But the
>>>> > secund thing to define
>>>> is the margin of your
>>>> > header ; if you put
>>>> text or image too big to be
>>>> > displayed under this
>>>> margin, then you will have
>>>> > some hidden text or
>>>> even a crash of the pdf engine.
>>>> >
>>>> > Beware that if you use
>>>> the internal/external
>>>> > layouts that i have
>>>> set, there is a
>>>> > data-report-margin-top
>>>> attribute on the html
>>>> > root tag that is
>>>> prioritized over the margin-top
>>>> > set in paperformat. So
>>>> it is this margin-top
>>>> > that you must edit!
>>>> >
>>>> > Notes:
>>>> > - Branch is named
>>>> 'trunk-qweb-report' and is
>>>> > available
>>>> at http://runbot.openerp.com/.
>>>> > today's branch is
>>>> >
>>>> http://trunk-qweb-report-28555-all.runbot.openerp.com/
>>>> > - 'website' module is
>>>> mandatory to dislay the
>>>> > reports. So, either
>>>> you use 'all addons' when
>>>> > connecting to the
>>>> branch on runbot or you
>>>> > install 'website'
>>>> module on base-install.
>>>> > - It's not possible to
>>>> directly access the xml
>>>> > code of views
>>>> (webpages) from the reporting >
>>>> > reports menu. If you
>>>> want to edit it, just use
>>>> > the html view of the
>>>> page. To access the views:
>>>> > technical > user
>>>> interface > views.
>>>> >
>>>> > I'm sure you all know
>>>> that the report engine is
>>>> > a tricky part of any
>>>> software, so please be
>>>> > patient as it's likely
>>>> to be buggy at start.
>>>> > That's also why your
>>>> help and feedback are
>>>> > appreciated.
>>>> >
>>>> > Feedbacks can contain:
>>>> > - traceback (critic issue)
>>>> > - no traceback but the
>>>> datas shown are wrong
>>>> > (critic issue)
>>>> > - ugly reports/ulgy
>>>> html code
>>>> > - ideas to simplify
>>>> this module
>>>> > - wanted new features
>>>> or comments
>>>> >
>>>> > Thanks in advance,
>>>> > Simon
>>>> >
>>>> >
>>>> >
>>>> _______________________________________________
>>>> > Mailing list:
>>>> >
>>>> https://launchpad.net/~openerp-community
>>>> > Post to :
>>>> >
>>>> openerp-community@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>>>> >
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>>
>>>> > Unsubscribe :
>>>> >
>>>> https://launchpad.net/~openerp-community
>>>> > More help
>>>> : https://help.launchpad.net/ListHelp
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> > *camptocamp*
>>>> > INNOVATIVE SOLUTIONS
>>>> > BY OPEN SOURCE EXPERTS
>>>> >
>>>> > *Joël Grand-Guillaume*
>>>> > Division Manager
>>>> > Business Solutions
>>>> >
>>>> > +41 21 619 10 28
>>>> <tel:%2B41%2021%20619%2010%2028>
>>>> > www.camptocamp.com
>>>> <http://www.camptocamp.com/> <http://www.camptocamp.com/>
>>>> >
>>>> >
>>>> >
>>>> >
>>>> _______________________________________________
>>>> > Mailing
>>>> list: https://launchpad.net/~openerp-community
>>>> > Post to
>>>> : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>>>> >
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>>
>>>> > Unsubscribe
>>>> : https://launchpad.net/~openerp-community
>>>> > More help
>>>> : https://help.launchpad.net/ListHelp
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> > *camptocamp*
>>>> > INNOVATIVE SOLUTIONS
>>>> > BY OPEN SOURCE EXPERTS
>>>> >
>>>> > *Joël Grand-Guillaume*
>>>> > Division Manager
>>>> > Business Solutions
>>>> >
>>>> > +41 21 619 10 28
>>>> <tel:%2B41%2021%20619%2010%2028>
>>>> > www.camptocamp.com
>>>> <http://www.camptocamp.com/> <http://www.camptocamp.com/>
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> > *camptocamp*
>>>> > INNOVATIVE SOLUTIONS
>>>> > BY OPEN SOURCE EXPERTS
>>>> >
>>>> > *Joël Grand-Guillaume*
>>>> > Division Manager
>>>> > Business Solutions
>>>> >
>>>> > +41 21 619 10 28
>>>> <tel:%2B41%2021%20619%2010%2028>
>>>> > www.camptocamp.com
>>>> <http://www.camptocamp.com/> <http://www.camptocamp.com/>
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> > *camptocamp*
>>>> > INNOVATIVE SOLUTIONS
>>>> > BY OPEN SOURCE EXPERTS
>>>> >
>>>> > *Joël Grand-Guillaume*
>>>> > Division Manager
>>>> > Business Solutions
>>>> >
>>>> > +41 21 619 10 28 <tel:%2B41%2021%20619%2010%2028>
>>>> > www.camptocamp.com
>>>> <http://www.camptocamp.com/> <http://www.camptocamp.com/>
>>>> >
>>>> >
>>>>
>>>>
>>>> --
>>>> Fabien Pinckaers
>>>> CEO OpenERP
>>>> Chaussée de Namur 40
>>>> B-1367 Grand-Rosière
>>>> Belgium
>>>> Phone: +32.81.81.37.00 <tel:%2B32.81.81.37.00>
>>>> Fax: +32.81.73.35.01 <tel:%2B32.81.73.35.01>
>>>> Web: http://openerp.com <http://openerp.com/>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *camptocamp*
>>>> INNOVATIVE SOLUTIONS
>>>> BY OPEN SOURCE EXPERTS
>>>>
>>>> *Joël Grand-Guillaume*
>>>> Division Manager
>>>> Business Solutions
>>>>
>>>> +41 21 619 10 28
>>>> www.camptocamp.com <http://www.camptocamp.com/>
>>>>
>>>>
>>>> <Selection_027.png>_______________________________________________
>>>> Mailing list: https://launchpad.net/~openerp-community
>>>> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>>>> Unsubscribe : https://launchpad.net/~openerp-community
>>>> More help : https://help.launchpad.net/ListHelp
>>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> *camptocamp*
>> INNOVATIVE SOLUTIONS
>> BY OPEN SOURCE EXPERTS
>>
>> *Joël Grand-Guillaume*
>> Division Manager
>> Business Solutions
>>
>> +41 21 619 10 28
>> www.camptocamp.com <http://www.camptocamp.com/>
>>
>>
>>
>
>
>
>
> --
>
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Joël Grand-Guillaume*
> Division Manager
> Business Solutions
>
> +41 21 619 10 28
> www.camptocamp.com <http://www.camptocamp.com/>
>
>
--
Fabien Pinckaers
CEO OpenERP
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com
References
-
tests/feedbacks for the new reporting
From: Simon Lejeune, 2014-01-27
-
Re: tests/feedbacks for the new reporting
From: Fabien Pinckaers, 2014-01-27
-
Re: tests/feedbacks for the new reporting
From: Joël Grand-Guillaume, 2014-01-28
-
Re: tests/feedbacks for the new reporting
From: Joël Grand-Guillaume, 2014-01-28
-
Re: tests/feedbacks for the new reporting
From: Simon Lejeune, 2014-01-28
-
Re: tests/feedbacks for the new reporting
From: Joël Grand-Guillaume, 2014-01-29
-
Re: tests/feedbacks for the new reporting
From: Fabien Pinckaers, 2014-01-29
-
Re: tests/feedbacks for the new reporting
From: Joël Grand-Guillaume, 2014-01-29
-
Re: tests/feedbacks for the new reporting
From: Simon Lejeune, 2014-01-29
-
Re: tests/feedbacks for the new reporting
From: Joël Grand-Guillaume, 2014-01-29
-
Re: tests/feedbacks for the new reporting
From: Simon Lejeune, 2014-01-29
-
Re: tests/feedbacks for the new reporting
From: Joël Grand-Guillaume, 2014-01-29
