Hence a +1, especially if you want utilise the olap fucntions in the bi
component in a separate rdbms (see issue OFBIZ-6087
https://issues.apache.org/jira/browse/OFBIZ-6087)
Best regards,
Pierre Smits
*ORRTIZ.COM http://www.orrtiz.com*
Services Solutions for Cloud-
Based Manufacturing,
I have opened https://issues.apache.org/jira/browse/OFBIZ-6212 for that
Jacques
Le 25/03/2015 12:01, Jacques Le Roux a écrit :
Thanks Taher,
I agree on Birt being useful in general, and in OFBiz certainly (Jacopo at
least thinks it could be better implemented, that's another topic).
My
To Report or Not To Report, that is the question?
First:
I agree with the viewpoint that optionals in special purpose don't change
the experience of apps in the applications stack. A good example
modification to a longer existing issue regarding the field
parentCustRequestId. In such cases we
Hi Pierre,
A quick note on the pros mentioned by you: integrating BIRT to the RDBMS is
optional. You can do that or call the APIs of the entity engine and in fact
this is how reports are currently implemented (it's called scripted data
set source in BIRT). You can also fully integrate with the
Thanks Taher,
I agree on Birt being useful in general, and in OFBiz certainly (Jacopo at
least thinks it could be better implemented, that's another topic).
My question was more is it useful for existing accounting reports? Jacopo seems to say that there were already FOP implementations what
