What do you dislike about timextender?
When you are used to tools like SAP or SAS DI then this could be a downgrade in ways of possibilities.
- Logging is minimal and using your metadata to create logging is not easy.
- Working with multiple people in one environment can cause problems.
- You can't deploy a single table from DEV - TST. So when a colleague made changes in the DEV environment it's likely that those changes end up in test after a deployment. There are options for this like 'guarding' tables but it doesn't always work and it's a hassle.
The most problematic thing for me is that TimeXtender doesn't work with 'jobs' (collection of tables needed for the output of 1 FACT table for example). TimeXtender just shows all your tables and you can group/filter them by using perspectives. Perspectives are more like domains. One table can be hooked up to more than one perspective and one perspective can contain tables in all layers (staging/DSA/Integration, whatever you use). All operations visually happen on the columns in the table, there is no 'job' containment with clear oversight of different steps like joins, group by's, filtering, or custom scripts for more complex tasks (custom SQL scripts are possible). When a task gets too complex you might need a view which further complicates the visibility of what is happening where. After a year of working with TimeXtender it still feels weird.
The SSL (semantic) layer is a nice feature and they are working out small kinks with every update. Something to keep in mind is that when working with PowerBI, you need a premium workspace and a live dataset everyone has to have a premium license in order to view the reports and you have the restrictions (and benefits) of a live dataset.
Connecting to different data sources (SQL/API's/cloud works fine, except xlsx, csv and other flat files. It's possible, but it's a hassle. If your organization uses a lot of csv's, make sure this can be reduced or you will go crazy with TimeXtender. Review collected by and hosted on G2.com.