hello every one im beginner of opnerp i have create a module total part is over but report part is there please tell the procedure how to generate reports
On 28 January 2014 11:51, Fabien Pinckaers <[email protected]> wrote: > > > Sent from my iPad > > On 28 Jan 2014, at 04:27, "jeff.wang" <[email protected]> wrote: > > Hi Fabien, > > For the sales order report, I have a concern about the addresses, both > for 7.0 and new qweb design. > > We know we have a option on menu Setting->Configuration->sales called > "Allow > a different address for delivery and invoicing" > > With this option check, user can select other address for shipping and > invoicing than the customer address itself. > > Problem is when this option isn't selected. it's so strange to the end > user that the printed sales order output customer address 3 times, you know > those are three 5 lines big blocks. > > > good feedback, we will fix. > > Solution should be compare the shipping address and invoice address > with customer main address, only print them out when there is diference. > > > No, it's much easier then this. The new report engine is based on simple > ir.ui.view exactly like form views. So, we can use the same feature than in > form views to hide data (e.g. groups="...") on the two extra fields > > > > Looking for everybody's feedback. > > ------------------ > Jeff Wang | [email protected] | 18016291663 | 02158980787 > @OpenERP_Jeff "As simple as possible, As complex as needed" > <http://www.osbzr.com> > Maintainer of Open ERP china community > http://www.openerp-china.org > > > > ------------------ Original ------------------ > *From: * "Fabien Pinckaers";<[email protected]>; > *Date: * Tue, Jan 28, 2014 03:13 AM > *To: * "Joël Grand-Guillaum"<[email protected]>; > *Cc: * "openerp-community"<[email protected]>; "Simon > Lejeune"<[email protected]>; > *Subject: * Re: [Openerp-community] tests/feedbacks for the new reporting > > To all, > > We are looking for feedback on the reports themselves because we rewrote > most reports: sales order, invoices, delivery orders, ... but also: balance > sheet, aged trial balance, P&L, pricelist print,... > > Feedback on the report designer is less interesting as this system is > designed to be used by partners through the HTML Editor or through code in > their modules. What's really important is to test if all reports of OpenERP > are still working like in v7. > > We had to rewrote the code of 70 reports, that's why it's important to > test. We are not sure we did not integrated a regression. > > Thanks, > > > Fabien > > > On Mon, Jan 27, 2014 at 8:07 PM, Fabien Pinckaers < <[email protected]> > [email protected]> 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 < <[email protected]> >>> [email protected]> 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/>http://runbot.openerp.com/. >>>> today's branch is >>>> <http://trunk-qweb-report-28555-all.runbot.openerp.com/> >>>> 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> >>>> https://launchpad.net/~openerp-community >>>> Post to : <[email protected]> >>>> [email protected] >>>> Unsubscribe : <https://launchpad.net/~openerp-community> >>>> https://launchpad.net/~openerp-community >>>> More help : <https://help.launchpad.net/ListHelp> >>>> 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 >>> >>> >>> >>> _______________________________________________ >>> Mailing list: <https://launchpad.net/~openerp-community> >>> https://launchpad.net/~openerp-community >>> Post to : <[email protected]> >>> [email protected] >>> Unsubscribe : <https://launchpad.net/~openerp-community> >>> https://launchpad.net/~openerp-community >>> More help : <https://help.launchpad.net/ListHelp> >>> https://help.launchpad.net/ListHelp >>> >>> >> > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
