Build better products with our product team
I know this post is a little bit different of the conventional post on this forum.But I am noticing a lot of posts with massive up-votes or a myriad of posts on the same topic indicating an urgent request from the community.However it seems these posts are not getting any attention from TimeXtender for quite some time now..., yet posts with 0 or 1 vote are being answered... Is it because you guys are planning on a massive engine overhaul or something else. Feedback on these topics would be appreciated.
Add an option to clone a Semantic Model. (just like the Qlik Models in the Qlik tab)
As many requests are allready in place to sort various lists (which are not affected by sorting the perspective) When adding a table insert, the list is unsorted, it's also not the order they are created it's just random and when the list is long, you have to visually scroll to find the object you need. When selecting a column in the table insert, the list is not sorted. And allthough you can type the first letter, but that only works for the first items with that letter, when they are down the list again with the same letter they are not found. There are more, Ill try to add them later on'.
Provide an option to set display folders on Dimension or Fact level.Each time someone adds an hierarchy, measure, attribute we have to tick the correct display folders. In most cases a display folder is used for an entire fact or dimension and not for one attribute.
There's already a description box for all fields in the semantic model. They could be deployed as an attribute description in the model so it can be viewed when hovering over them in Power BI. There could be a checkbox on the endpoint configuration to have it enabled/disabled. Having a "Copy description from the source field" button for the semantic field description dialog could also be useful for a simple propagation of description.
When exporting data using the CSV export we are now forced to export the CSV using a single name. However, sometimes you don't want to export the full table, but just a new increment (for example an hourly export of the new records of that hour) to enable the target system to easily load incements of data instead of the full set. We can create that behaviour with a custom selection rule, but the file name will be the same for each export. The suggested feature would allow you to define a custom naming pattern so that for example you could enumerate the exports or incorporate the date and time of the export.
You can create master items in a Qlik Sense Endpoint by adding custom measures to the semantic model. It would be nice to be able to also add a description to the master item so that our front-end users can be guided as to how to use the master item. My suggestion would be to add the TX description to the Master item's description. In the same vein adding Tags in TX could translate to labels in the QS master item.
We have a data source (Afas "Profit", Dutch ERP system) that we can only access through a SOAP API. This API allows you to do a call and receive a table in XML format. Calling this SOAP API is quite easy from powershell, however it is not possible to run the powershell code from SQL Server (xp_cmdshell is not an option for us) Besides this, having code outside of TX is a path we don't we to go, as it puts us back in the world of manually deploying files. It would be great if we could deploy and run powershell scripts from TX. This would make sense as an option in "Script Actions", e.g. in the right click menu there are 3 options: * Add Custom Step * Add FTP Source * Add Powershell script (Of course, even better would be if TX supported Afas Profit out of the box)
I would like to see an option added to perform a "Differential Execution". So if I have some changes to push to a new environment, I could easily deploy the differences and then only execute those objects. Currently, the only way to do that is to do a differential deploy, make a note of all the objects deployed and then manually execute each of them in the queue. Note that I edited my original post as it actually seems to be a bug that I'm working on replicating now and will submit to Support. The post now reflects another suggestion that was at the bottom of the original post, so the comments below may not make sense.
TimeXtender appears to force you to always define a decimal field with scale 38. decimal(38,xx). Unfortunately this isn't always going to work for us as there are times where we have to have decimal fields with a precision of up to 16 decimal places. Since SQL Server has a maximum "length" of 38, we're losing accuracy that we have to have in order to apply precise calculations when doing math operations, such as computing a quotient. We would really like to define some of our decimal fields as decimal(22,16). Please see the attached example of an issue we're experiencing when we're not allowed to modify the scale. You can see how the repeating 6's are limited to only 6 decimal places and not the full 16. It would really be nice to have this as an added feature in a future release of TX. Thanks!
Add functionality to copy / clone a measure in the semantic model. Including mapping of parameters ofcourse.
There are different windows where I would like to have a 'select all' checkbox. For example in the History settings. When I have a big table I have to click each field one by one and this will take a lot of time.
I'm really excited about the Syntax Highlighting and Autocompletion option for transformations, custom table inserts and data selection rules in the newest version of TimeXtender. But unfortunately, this is not working in the Query Tool. Please add this functionality in the Query Tool!
Add indicator/icon on the tables where a custom script is used. The only way to check whether a custom script is used is to right-click the table --> advanced --> Set Pre- and Post Scripts'
Upgrading a SQL Snippet that is used in many objects is a tedious task.Having checkboxes with a "select all" option for the SQL snippets upgrade would be great.
Add an option to enable on project level to execute all executions to the execution queue by default.
We often have quite some script actions in our project. When we are on a table and we see that a script action is involved, we have to start scrolling back-and-forth. It would be great that we could have an option ‘Go To Script Action’ or ‘Open Script Action in new Window’. Similar as we now have a ‘Go To Source Table’ / ‘Open Source Table in New Window’ option.
Add an option to make it easier to execute an Incremental table using a full load. At the moment you need to go to 'review tasks' set the checkboxes and then execute the table. It would be much easier if you can directly execute a full load on a table. This way it might also not be necessary to save the project as a deployed version.
Again requesting to add the option to sort display folders in this window instead of showing them in order of creation. Can you guys please make the reflex to add this functionality by default...The number of feature requests to have alphabetically sorted lists in this forum are almost beyond counting. Also implement this on other levels as well, it is so tiring scrolling up and down lists just to find the thing you need.
In my projects, it often happens that I get spreadsheets from Excel and need to transpose them first. At the moment I do this over a complex T-SQL Script. A simplification feature would be very desirable.
It would be great that unpivoting tables can be automated. At the moment I need to do it using a Custom Table Insert. For example: Select fields on a table that need to be unpivotted and Discovery Hub will automatically create the stored produre(s) and the output table.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.