Build better products with our product team
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'
When adding a database schema to a perspective. It does not "inherit" all tables that are attached to this schema. It only adds the schema name to the perspective. Add an option to "inherit" all tables on a database schema to add it to a perspective.
It is already possible to clone a table structure, but the lookups, data selection rules and database schema are not cloned.
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.
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.
Add feature to visualize the relation diagram in the semantic models. When selecting table in the semantic model. Just like the 'normal' tables in the ODX, DSA and MDW.
In some cases where you move the data around the staging area it would be nice to have the option to have incremental selection rules available on table inserts. Working with [Load] fields and some pre an post scripts also simulates a kind of incremental with a database but I feel this is not the most efficient way and could be achieved quite easily should this option come available.
When you run through lineage for data that involves a table insert or related table insert, clicking those does not highlight the object in the GUI. It only makes the connected tables bold in the lineage view. If you double click a default view or parameterised custom view, this does work.
It would be great to have the ability to configure TX to automatically clean execution logs older than N days/weeks, on a rolling basis. For example, a housekeeping process that is run once per day, at a time the user chooses: user choice of time would important because in my organization, we actually shut down our TX virtual machine (on Azure) for 8 hours each night. Another potentially-useful behavior configuration would be whether Successful logs should be treated differently to Failed logs. We might want to keep information about failures for longer than successes. The benefit of this automation would be to prevent TX users having to follow these steps: https://support.timextender.com/hc/en-us/articles/115004530803-Size-issues-with-your-repository-Clean-up-the-logs-and-get-more-space. The comments on that article already indicate support for this request. This is related to: https://support.timextender.com/hc/en-us/community/posts/360005494483-Repository-Cleanup, but I think it is a different request because that issue is not discussing automation, but an improved user-interface.
It would be a great help to have logging of all steps of the cleansing stored procedure (start / end time). We have tables with a lot of lookups, but sometimes some of those lookups take a lot of time. This logging would help us to identify the slow lookups and do something about it.
Add feature to copy / drag and drop data selection rules to other tables.
For versions up to 20.1.4. it is not possible to use a custom field (calculated column) in the semantic layer as a field participating in a relationship between tables. This is however supported in analysis service. This could help in development scenarios, where the model can be extended with calculated columns that participate in a relationships.
Often when doing an impact analysis, we are in fact trying to see where the table is used in any way, doesn't matter which fields. We try to mimic this by doing multiple impact analyses from key fields but this is quite cumbersome. It would be really useful if we could do an impact analysis at object level, which I imagine would result in a summarized view of datamovements (table -> table -> table) with besides the arrows or in the table boxes the fields that are affected.
How many times you ended up dragging table to the wrong table or did something else stupid you regret about? simple 'Undo' (ctrl+z) could save the (rest of your) day
When a database schema is added, tables are attached to this schema and you want to deploy the table. You get an error saying the database schema does not exist yet. It would be useful to automatically deploy this database schema it case it does not exists yet.
We have a team using Azure Data Bricks to do processing and modelling on all sorts of sensors in office buildings, and they will store output in Azure Data Lake. We want to be able to ingest this data (at least the output) and make it available in DH. Currently this is not natively possible in TX and would require something like Azure Data Factory to move files to a place accessible from TX. Could this be added?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK