OpenERP is one of the best ERP applications I ever used.
I found that almost everything must be built from the beginning to meet the specific needs for each one including the analysis reports, but there are some basic packages already built.
Since I am new to OpenERP functionality and still haven't learned how to create reports in OpenERP, I need to know if there is any addons/extra module that provides me some basic and ready to print reports and listings for the several modules. This reports and listings will help me to better understand and learn the functional part of the application and will allow me on a future to better understand how to build reports and listings in OpenERP.
If anyone can provide me a link or repository with such information I will be greatfull.
Thank you very much
Regards
Paulo Matos
There are various ways of creating reports with openerp. They are (i've prioritized)
Webkit (for html,web designers - this will be a great utility)
OpenOffice (for any office person with minimal technical skills)
RML (Strictly for programmers :))
Jasper Report (good for people with java-reporting base)
Aeroo (Rich functionality of exporting to excel,word etc, still i am not comfortable in aeroo with openerp 7)
Pentaho Report Designer (A reporting tool from pentaho )
These links will help you in understanding better, setup environment and learn from the sample modules and reports. However you need to design what u need with one of the reporting type.
What's the best way to create a report on OpenERP
http://www.schenkels.nl/2013/02/custom-reports-in-openerp-what-will-you-use/
http://colinnewell.wordpress.com/2012/01/04/adding-new-reports-to-openerp/
https://doc.openerp.com/v6.1/developer/05_reports/
https://doc.openerp.com/6.1/book/8/8_20_Config/8_20_Config_reports/
Google more. You'll get everything u need. Good Luck!!
Reporting from Odoo / OpenERP can be very frustrating at times. We have found over the years that no single solution is great for every need.
The built in reporting mechanisms mentioned in the first answer (rml / openoffice) have been somewhat deprecated and replaced with qweb reporting which renders similarly in HTML or PDF. They can be difficult to get fine-grained control and alignment, a lot of work to achieve non-regular reporting structures and cross tab reports, but are fast and easy to use for straightforward "document" type reports (such as orders / invoices).
I cannot comment on Jasper or Aeroo, as I have not used them.
Using Pentaho Reports for Odoo can be great because they are primarily reporting engines. They can do wonderful things with data, present them in great ways.
One upside with this connector is its ability to access Data using the object layer, or SQL, or both in one report if necessary (using sub-reports for example), as well as custom methods!
One downside we have found with Pentaho Reporting is that as the code base changes for OpenERP/Odoo, the connector changes, and configuration has to be continually re-vesited.
The latest version supports Odoo version 8 and version 5.4 of Pentaho reporting engine.
Related
These are more high level questions, but our team is new to developing with APEX. We are currently a team of 3. We are using APEX 19.2, but are planning to upgrade up to 21.1
How do others handle the development flow, versioning, and releases of their projects when working in APEX?
We put majority of the business logic (validations, source sql, and process handling) in packages. So I feel it is pretty easy to version those files as they are outside of the APEX UI and can version in Git accordingly, but how do others version control all the APEX UI changes (pages, regions, items, DAs, etc...)?
I've searched and haven't really stumbled upon best practices of how teams, that use APEX, conduct their development process. One thing I'm nervous about is branching changes inside APEX UI. Sometimes we are given a requirement (say A) and we are asked to hold that release, but start working on requirement B. We may even release B before A gets final approval.
Are there any best practices, to ensure that developers working in the same workspace do not collide with others work? Luckily most of our project tasks do not overlap, but curious how others handle this
Any links or tips to this would be appreciated as we are new to APEX and trying to work these things out up front.
I'm probably not the right person to answer as my Apex team consists of 1 (one) member - me.
However:
We put majority of the business logic (validations, source sql, and process handling) in packages.
Me too, I found that to be the best option. Keep as little code on pages themselves as possible.
As of team development, did you read Managing the Application Life Cycle with Team Development?
Tracking Features might be particularly interesting for you. For example, it contains
Approval status of the feature. Indicates if the feature is to be implemented and the current progress.
which sounds like what you asked for.
I hope that someone - who really works in a team - will see your question and answer; I'd be interested in reading about their experiences and suggestions as well.
When we export application as zip , we can see there is folder structure. So in git we have to follow the same directory structure so it is easy to review and for versioning.
Thanks,
Nagaraju P
background
I have designed many tools in the past year or so that is designed to help me program for XPages. These tools include primarily helper java classes, extended logging (making use of OpenLogger and my own stuff), and a few other things that I personally feel I cannot work without. It has been discussed with my employer, and we feel that it might be a good idea to start publishing these items to openNTF. Since these tools are made up of about 3 .nsfs, all designed to use the same java code, key javascript classes, css, and even a custom control or two, I would like to consolidate key items into a plug-in that can be installed at the server and client level. I want to do this consolidation before I even think about publishing any of the work I've done so far. It would just be far too much work to maintain, not just for me, but for potential users. I have not really found any information on how to do such a thing in google searches. I also have to make sure that I am able to make use of the ExtLib libraries, openNTF Domino API, and the Notes API.
my questions
How does one best go about designing such plug-ins? Must a designer
use eclipse, or is this it possible to do this directly in the Notes
Designer?
How does a designer best go about keeping a server and client up to date while designing and updating the plug-in code? Is this why GitHub is often used?
Where is the best place to get material to get started in this direction? I sort of feel lost in the woods, knowing I need to head north, but not having a compass for that first step.
Thank you very much for your input.
In my experience, I found that diving into plug-in development is a huge PITA until you get used to it, but it's definitely worth it overall.
As for whether you can use Designer for plugin development: yes, but you will likely eventually want to not do so. I started out by using Designer for this sort of thing for a while, presumably with the same sentiment as you: why bother installing another instance of Eclipse when I'm already sitting in one all day? However, between Designer's age (it's roughly equivalent to, I think, Eclipse 3.4), oddities when it comes to working sets between the "Applications" and "Project Explorer" views, and, in my case, my desire to use a Mac app, I ended up switching.
There are two major starting points: the XSP Starter Kit (http://www.openntf.org/internal/home.nsf/project.xsp?name=XSP%20Starter%20Kit) and Niklas Heidloff's video on setting up Eclipse for XPages development (http://www.openntf.org/main.nsf/blog.xsp?permaLink=NHEF-8RVB5H). The latter mentions the XPages SDK (http://www.openntf.org/internal/home.nsf/project.xsp?name=XPages%20SDK%20for%20Eclipse%20RCP), which is also useful. In my setup, I found the video largely useful, but some aspects either difficult to find (IBM's downloads are shifting sands) or optional (debugging, which will depend on whether or not you're using Eclipse on Windows).
Those resources should generally get you set up. The main thing to worry about when setting up your Eclipse environment will be making sure your Plug-In Execution Environment is properly done. If you're following the SDK setup instructions, that SHOULD get you where you need to be.
The next thing to know about is the way plugins are structured. Each plugin you want to install in Designer or Domino will also be paired with a feature project (a feature can house several plugins), and potentially an update site - the last one is optional if you just want to import the features into an Update Site NSF. That's how I often do my normal plugin development: export the paired feature to a directory and then import the feature into the server's Update Site NSF and then install in Designer from there using Application -> Install. You can also set things up so that you deploy into the server's plugin/feature directories instead of taking the step of installing into an update site if you'd prefer. GitHub doesn't really come into play for this aspect - it's more about sharing/collaborating with your code and also having a remote storage location for your git repositories (which I highly advise).
And as for the "lost in the woods" feeling: yep, you'll have that for a good while. There are lots of moving parts and esoteric concepts to get a hold of all at once. If you mostly follow the above links and then start with some basics from the XSP Starter Kit (which is itself a plugin project that you can pair with a feature) - say, printing text in the Activator class and making an implicit global variable just to make sure it works - that should help get your feet wet.
It's best done in Eclipse. You can debug your code running on the server from there, as well as run it directly from there. The editors are also more up-to-date. You want:
Eclipse for RCP and RAP developers
XPages SDK for Eclipse RCP (from OpenNTF)
XPages Debug Plugin (from OpenNTF - basically allows you to load the plugins to the Domino server dynamically, rather than exporting to an Update Site all the time)
XSP Starter Kit on OpenNTF is a good starting point for a plugin. There are various references to the library id, which has to be unique for your plugin. Basically, references to org.openntf.xsp.starter need changing to whatever you want to call your plugin. You're also best advised to remove what you don't need. I tend to work in a copy of the Starter, remove stuff, build and if there are errors with required classes (Activator.java obviously will be required and some others), then paste them back in from the Starter.
XPages OpenLog Logger is a good cross-reference, that was built from XPages Starter Kit. It's pretty much stripped down and you'll be able to see what had to be changed. A lot of the elements of the XSP Starter Kit correspond to Java classes you'll probably be familiar with from your XPages Java development.
GitHub etc tend to be used as source control, which is useful for working out what's changed from time to time.
We need to print Business Letter for a given list with mail merge facilities.
My client is not willing to spend $$ on a paid ASP.NET control to make PDF. So I opted in for WKHTMLtoPDF and it works fine for us until one day the client tried to get a PDF of 100+ leads, resulting in complete failure of PDF generation. It works just fine with a 10-20 page PDF, but not for 100.
Are there any tips & tricks to improve performance? We are using Cloud-hosted IIS 7 with ASP.NET 4 if that matters.
PDFSharp library is really a nice one!
I have used it for quite a while now, and I find it flexible enough to fulfill your needs.
However there are some aspects of using it as a "standalone library" - e.g creating tables is a headache and there aren't much text formatting options. It is much better to mix it together with MigraDoc (an extension library for PDFSharp).
If you're looking for a really free (as in "free of worries") library, choose iTextPDF versions prior to version 4.1.7, as they state in the ByteScout blog.
From the ByteScout blog:
iTextSharp 4.1.6 DLL only: itextsharp-4.1.6-dll.zip
iTextSharp 4.1.6 Source Code (C#): itextsharp-4.1.6.zip
I'm not sure I understand your problem but couldn't you generate docx documents and get the same results?
For all, I use http://wkhtmltopdf.org/ to create HTML to PDF, my ASP.NET code generate the HtML file then I create HTML to PDF and it is done, much easier than using itextpdf's Table and td structure to get things in better space. I found it easy and fast once you get your stuff aligned properly.
library has improved since original question asked and it performs better now.
here is good tutorial http://www.codeproject.com/Articles/20640/Creating-PDF-Documents-in-ASP-NET
I am looking for a web based report designer supporting spring/hibernate. I have seen BIRTStudio but it is not free.
I came across this list http://java-source.net/open-source/charting-and-reporting which could be helpful. It might be appropriate to cookup my own small reporting engine. My core requirements:
End user should be able to specify parameters for a report
Report should be available in Excel form
Report should use the same permissions scheme as the application (ie spring security)
Report can be of two types (visual and textual) and among those types report can be of Chart or Map
I have found Pentaho to be a solution
http://community.pentaho.com/faq/waqr_faq.php
The target audience is not software developers, but it still seems a good start.
#geoaxis, try Jasper and DynamicJasper
I've written a set of tutorials for integrating Spring MVC 3 and Jasper. I've also provided a downloadable Maven build.
http://krams915.blogspot.com/p/tutorials.html
I need roadmap view, overall bug graphs, multiple pieces of information on one screen - can this work with Bugzilla? Eclipse-based plugins etc are usable... but solutions like yoxel that need access to the Bugzilla SQL DB itself are probably not workable.
Thanks
That may be a little off-course, but have you looked at Deskzilla? You can build project breakdown or roadmap using nested queries and tabular distribution. It doesn't have graphs though.
Igor
Disclaimer: I work for ALM Works, the company behind Deskzilla.