Thanks for your question. We have indeed improved many aspects of our product over the last years and we keep doing so.
Regarding reporting there are a number of possibilities:
Point 4 can be done via our webservice API or via a direct connection on the database. Webservice connections are possible in all deployment options. A direct connection to the database is possible in private cloud environments. We are working on a way to connect any private and on-premise environment to our enterprise cloud dashboard. This will enable the same web UI for all deployment options.
That being said, I take the feedback in this thread very serious. I propose to do the following:
Hi Luis, Clear question that is why we developed the JasperReports API. With this API we can answer the questions of our customers.
More over the question raises that customer want to have more run-time flexibility. We are now busy with investigating/developing Ad Hoc Report Designer of JasperReport for this.
Maybe our current solution is not sufficient for your case? In that case we can discuss this so we can make improvements to our solution.
I totally agree with Luis. I recently investigated the reporting possibilities with Mendix and came to the same conclusion. Mendix provide the widget API but the current reporting widgets are not good enough. However we've build a query/reporting tool ourself within in Mendix and it's used in production by one of our biggest customers and it fulfills most of their reporting needs.
Hi Luis. You know that I agree with you on this. From a commercial point of view, it reduces one of the key advantages of Mendix vs other products which use proprietary databases.
There are lots of excellent, mature, fully-featured, drag and drop style reporting tools out there that will work on any of the databases supported by Mendix; the problem is that we can't use them in the Mendix Cloud. So we can move to on-premise, but then we lose the benefits of all the nice Cloud deployment features.
Catch 22 really.
Thank you for this write up. Important information you provide.
You're writing that "you cannot connect to an App+Db in the cloud"? Do you know why, what's the issue? And is ARS from Cape different, did they "solve" or work around those issues?
I'm very interested in this subject as I'm looking into reporting tools myself for a customer.
Thanks again. Toon
As an early Mendix adaptor (working with the platform since version 1) we couldnot agree more.
We also have lost potential customers due to not being able to fulfill their reporting requirements and it is the main reason that we still run a number of our projects on on-premise application and database servers instead of in the Mendix cloud.
Agree Luis, The mendix widget api offers enough flexibility to create a good reporting widget. A matter of priority.
One of the points that Johan made suggested developing reporting tools by using a web services connection to a public cloud based application. Has anyone tried this approach? Any thoughts on the feasibility of this and suitability to integrate with third party reporting tools in this way?