We performed a comparison between CloverETL and Dundas BI based on real PeerSpot user reviews.
Find out what your peers are saying about Tableau, Qlik, Splunk and others in Data Visualization."No dependence on native language and ease of use."
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"The Layers feature organizes my work and makes it easier, instead of having to use scripting to show and hide when drilling down."
"The solution has a good drag-and-drop feature for creating dashboards."
"We have now the ability to create interactive and complex reports without the need for software developers and code."
"It was quite easy to use. The UI was basically drag-and-drop based. So, even if you were a beginner at coding software or something else, it would be easy to catch up on Dundas BI."
"We use Dundas to report on machine sensor data and create dashboards."
"With Dundas BI, you have a lot of visualization choices, and you can also do customizations by using HTML coding and JavaScript. The ease of development was one of the main factors for going for Dundas BI. The client had different reporting tools, but they wanted something that could accommodate all requirements."
"Its documentation could be improved."
"Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough."
"Needs: easier automated failure recovery; more, and more intuitive auto-generated/filled-in code for components; easier/more automated sync between CloverETL Designer and CloverETL Server."
"Lacks sufficient online support."
"It would be helpful if Dundas made the UI more user-friendly like the leading tools and decreased the learning curve. It should be simpler for a beginner to build dashboards."
"Working with the color palette is difficult in Dundas BI. They can work on different color palettes and make them organized and user-friendly. It would help a long way. Most of the time, the users face challenges in assigning colors to the fields that they have created or to the dimensions and measures in a chart."
"I cannot select a visualization and see what filters are connected to it."
"For every object, references are generated, but sometimes, there was a problem with the references overlapping each other. Everything would go off. It would stop working, and then from the admin side, people had to do something to bring it up again."
"I would love to see more functions built in inside the application, instead of being scripted. They already did some of that in the new release, version 5, like forecasting, trend lines, etc., and I would love to see more of these kinds of calculations, which we used to do it by scripts before."
Earn 20 points
CloverETL is ranked 41st in Data Visualization while Dundas BI is ranked 21st in Data Visualization with 21 reviews. CloverETL is rated 7.0, while Dundas BI is rated 8.6. The top reviewer of CloverETL writes "Provides wealth of pre-defined, customizable components, and descriptive logging for errors". On the other hand, the top reviewer of Dundas BI writes "Has a lot of integration and visualization options, but can't be easily used by business users, and working with the color palette is difficult". CloverETL is most compared with iWay Universal Adapter Framework and Talend Open Studio, whereas Dundas BI is most compared with Microsoft Power BI, Tableau, Logi Analytics, Angles Professional and Salient.
See our list of best Data Visualization vendors.
We monitor all Data Visualization reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
