Precisely Connect vs Qlik Compose comparison

"Precisely has the AI Act already implemented into the data catalog, which allows the integration of the European Artificial Intelligence Act into our processes."

"Using Precisely improves data quality, which can lead to a 30% increase in revenue and boost net income by 20% to 25% if implemented correctly."

"There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms."

"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good."

"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."

"The technical support is very good. I rate the technical support a ten out of ten."

"Qlik Compose is good enough; it is user-friendly and intuitive."

"I have found it to be a very good, stable, and strong product."

"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."

"I have found it to be a very good, stable, and strong product."

"Precisely works with a tool called Analyze, which has a steep learning curve due to its use of Jython, a combination of Java and Python. This could be improved to make the tool more user-friendly."

"Precisely works with a tool called Analyze, which has a steep learning curve due to its use of Jython, a combination of Java and Python. This could be improved to make the tool more user-friendly."

"It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it."

"I'd like to have access to more developer training materials."

"Qlik's ETL and data transformation could be better."

"There is some scope for improvement around the documentation, and a better UI would definitely help."

"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."

"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."

"When processing data from certain tables with a large volume of data, we encounter significant delays. For instance, when dealing with around one million records, it typically takes three to four hours. To address this, I aim to implement performance improvements across all tables, ensuring swift processing similar to those that are currently complete within seconds. The performance issue primarily arises when we analyze the inserts and updates from the source, subsequently dropping the table. While new insertions are handled promptly, updates are processed slowly, leading to performance issues. Despite consulting our Qlik vendors, they were unable to pinpoint the exact cause of this occurrence. Consequently, I am seeking ways to optimize performance within Qlik Compose, specifically concerning updates."

"There should be proper documentation available for the implementation process."

"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."

"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."

"The price of the solution is expensive."