Build better products with our product team
I found that I can’t choose to do a LEFT JOIN instead of INNER JOIN when I create a conditional lookup field. I understand that it can be dangerous to explode a table but there should be an option to do it. The current solution of creating a custom view to do this is cumbersome in my opinion
Hey, we are currently developing BI reports for our clients. We are working with DEV, TST and PROD versions of the dashboards. In TX I’m developing in our DEV data area. Once these developments are stable and approved we want to duplicate this data area to our TST data area. That way we can have a stable TST layer and continue new developments on the DEV layer again. To request is basically to be able to duplicate a data area into new or existing data area.
Now that there is a certification for pre-sales professionals, there should also be a badge for those of us trying to “catch ‘em all”
I’ve a store procedure that I’m using as template:It would be useful to be able to copy and paste and maintaint the parameters to create a new one based on the template.
Many data platforms require hierarchical data. There are quite complex ways of dealing with this kind of data that often require recursive CTEs with usually bad performance..But SQL Server has had a specific data type for this since SQL 2008. It would be good if TimeXtender supported the hierarchyid field so we could use this.See: https://learn.microsoft.com/en-us/sql/relational-databases/hierarchical-data-sql-server?view=sql-server-ver16
When you use roles in the Deliver instance, it is not possible to sort and search the list of role members. If you have a long list of users, it is hard to find a user when you are not able to search or sort in the list of role members.
Hey all,When developing a data warehouse one of the most time consuming tasks is which tables contains which data and how are the tables hooked up to each other. luckily, most databases nowadays have there PK and FK metadata set up correctly. In the BU of TimeXtender it is possible to ‘Add sugessted constraints’. Which will put PK's and FK on the tables. With some creative work it is possible to see which tables have a relation with what tables and it's easy to create you're model. Except, you have to load the tables first before you can do this. In the new version with the ODX server I believe this possibility is somewhat gone.My suggestion is: Within the ODX server => would it be possible to have a ‘Source ERD’ option. Where you Sync the source, you get this data and then create the ERD overview. Would be really cool to have an extra function when you select a table it would highlight the tables it has a relation with and then with a simple selection you can add it to the tables you want to load. When working with Qlik Compose I saw a functionality like this. Very helpful. Maybe take a look there.ps. If there is software out there that already does this and I've clearly missed this: Please let me knowThank you= Daniel
Hi All,For some clients I have to load aggregated tables from a datalake. So these tables do not have a timestamp to be incrementally load on. This feature would work on all tables from all sources which do not fit in the usual incremental load format.What I would do when not using TX is whenever I load the data I would load the data from the current month or current year, then union this data the the data which was already loaded but filter this whichout the current month or current year.This would be great to have a a feature in TimeXtender.
In the Syncchronize with Remapping window:Sort the options alphabeticaly:
This week I tried to create an incremental selection rule to load every table incremental based on the timestamp column. Except for some tables, those table needs to be fully reloaded.An option could be to create multiple transfer tasks, but in this case, it is hard to schedule. The reload is scheduled to run every 5 minutes and it is not possible to run 2 ODX tasks at the same time.I’ve contacted our Solution Specialist and we could not find a way to reload all tables incrementally, except a few. We tried to create multiple Incremental Load Rules, using the 'Not Contains' operator. But this operator is only exception 1 table as input. So we created multiple rules for each table that do not need to be incrementally loaded. This doesn’t work because if you create multiple rules, it is an OR instead of an AND. I think this could be solved to add a new operator called ‘Not in list’ or ‘Not Contains in list’. Or add an option to handle multiple incremental selection rules as an AND condition, instead of an OR condition.
I noticed that the find functionality on project level is not scanning the project variables. (Tested this in TX v. 20.10.40)Looked for : var_Analysis_Server_DEVResult : emptyBut actually the variable is used in another variable :Variable : var_Current_Analysis_ServerValue :SelectCASEWhen '[var_Environment]' = 'DEV'THEN '[var_Analysis_Server_DEV]'When '[var_Environment]' = 'PRD'THEN '[var_Analysis_Server_PRD]'ENDI think the Find functionality should also scan the project variables.
It would be nice to get diferent color icons for the guard options: Depending on the selection: For example:Orange icon: Guard on execution Yelow Icon: Guard on deployment Red Icon: Guard on execution and deployment.
I’d like to pitch for the addition of an “In list” option for the table / schema / column selection in the Incremental Load screen in ODX Server. As an example I have the following use case: For this data source there are 10+ tables for which the MODDTE field can be used as the incremental timestamp. Since the table names differ it’s not possible to use the “contains” option, so each table has to be configured separately. This could be improved by adding an “In list” option.TX version: 20.10.40
Make it easier to see the source table where the aggregate table is based on. The only way to see it at the moment is when you edit the aggregate table. It would be way easier if this is visible when you hover over the aggregate table name.This is working great for supernatural key fields, when you hover over a supernatural key field, it shows the key store and the business keys.
It would be very useful if we could setup a project variable which refers to the Execution Id (same setup as for e.g. the environment) - so without having to query the TimeXtender Repository DB.We need this ‘Execution Id’ since we’re calling an ADF pipeline to extract data into a Landing Zone DB. We want to pass the Execution Id to the ADF pipeline as a parameter (through a record in a parameter table), so the ADF pipeline can add the ‘execution ID’ as an extra column in the extracted data.Like this we’re sure that during execution of the TX execution package only the data requested by this package is being loaded from the Landing Zone DB.
When executing a table in a DWH instance that will copy data from Azure Data Lake Storage through Azure Data Factory it would be more optimal to drop any indexes on the raw table before bulk transfer.If you look at a running pipeline, ADF will also give you this tip.I think this should always be applied; I don't think there is a situation where inserting into a raw table with indexes active is required. Same goes for non-ADF transfers I would expect.
Dear community,For my client i'm looking into the option if you can pull data directly into your MDW from an Azure data lake. The data is already being extracted and cleaned through different tools. I need to get this cleaned data and push it towards the MDW. To me it would be a waste of resources and time to first load the data (again) in the ODX and then be able to get it to my MDW.If seen this idea and that would be great: Is there a possibility?Thank you!
The ODX Server UI needs to be improved in many ways. In this idea I’d like to pitch that an option gets added for a “In list” filter for table filtering. Imagine this use case from the business unit:We have a table that contains a filter on 19 field values. If we would have to replicate that in ODX server we would have to enter each filter 19 times and for each value we would have to: 1) input the table 2) input the filter field 3) input the filter value.At the client of this screenshot this table is loaded from 10+ source databases that need to have the same filter applied. An action that would take me 5 minutes in the business unit will take me hours in ODX server.
_PK tables are used for handling deleted source records when incrementally loading data. There’s no need to keep anything but the latest set of primary keys … we should truncate the _PK table when using SQL Server as the ODX … or potentially let the Storage Management task handle prior _PK loads.
Keeping lookup values updated is all or nothing … and that can be very expensive performance-wise in a table with many lookups of which only few really need to be checked.It would be nice with an option to select which fields should be included. It can of course be achieved by editing the data cleansing SP but then the SP gets locked and won’t capture future changes to the table.
I would like to have an option to sort or filter (e.g. tables with no primary key) the tables in the Primary Keys screen in ODX server. It’s impossible to find a table with large databases.
Hi,To be honest, it is not a "major” improvement, but still handy if we are able to drag Semantic models and Perspectives into the Execution Queue. By means of this, we could e.g. execute one table in the DSA, MDW and update the SL in a row.Kind regards,Devin
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.