Build better products with our product team
Hi,Several clients I’ve spoken with find it confusing that tables with the “Automatic” data extraction setting have no visual cue that they are incremental when they inherit the incremental logic from their source table. Could you add the incremental I to these tables as well? The incremental I
When we are using a “Custom Insert” in a table the system fields DW_SourceCode and Source Table are filled with “Unknown”.I suggest to fill them with:DW_SourceCode = “Custom Insert”Source Table = Neme of the custom insert
Hi, it would be nice if we had a way to check for the health of the TX portal.When there are problems its hard for our customers and/or us to check if there are any known issues that are beeing worked on.Would be nice if we had some kind of health indicator, especially as one cannot develop as long as the portal doesn’t work. CheersKai
When you are applying changes in TimeXtender you often start at source-selection and then push changes forwards through DWH Data Areas into SSL. A common pattern to follow manually will then be:new field appears in a source table synchronize source (perhaps explicitly add the column to ODX) reload ODX synchronize objects add the field to DWH mapping in staging area (perhaps do some transformations on the field) map the field into subsequent Data Areas: MDW and perhaps other layers synchronize any downstream SSL edit the tables in downstream SSL to get the extra field thereWhat if TimeXtender could suggest a “push” of your changes downstream? In many cases you would want your new field to be made available downstream, and you now need to go through the manual steps listed above. Similarly to how the synchronization dialogues allow you to “help” TX by choosing mappings instead of manually performing them, you might be able to steer the generation of code and deployment and execution in one go from a simple interface dialogue. A similar functionality can be seen in coalesce.io where code changes can be propagated downstream.A more complex scenario can happen when you change a table that becomes a dimension to be historical (type 2): you probably want to reevaluate surrogate keys (or introduce them) to properly couple your fact tables into the historical data you now have available. When I build in TimeXtender I set up history before dealing with facts so I can make use of the automated “you seem to be making a conditional lookup from a history table” function. In reality you are going to run into situations where you are making the change and then having some kind of “do you also want to change lookups in this way in your downstream” functionality would be really valuable. Especially because this would push implementations into “best practice” making for more consistency across implementations. This functionality would make applying changes faster and more controlled and would also foster more “end-to-end” thinking.
Hello,We use a system that creates new Excel files every day for different services such as the Canteen, Conference, and Kiosk. Each file is named with the date it was created, like canteen_products_2023-12-27. Is it possible to set up the ODX (Operational Data Exchange) in such a way that it can connect to Excel Online and automatically select all the files that start with canteen_products_ without specifying the exact date in the file name? This way, we could automatically process all files related to canteen products regardless of the date they were created.Best regards, Marius
v21 requires sign-in at regular intervals without regard to whether a user is actively creating magic in the UI. It’s a bit annoying being signed out in the middle of something so while regular sign-ins are a great security feature, it should take recent UI activity into consideration and reset the sign-out/in timing accordingly … e.g. 6 hours after the latest UI activity.
It is currently possible to create seamless end-to-end jobs that execute ODX → DWH → SSL without needing to manually juggle the UTC / Server-time issue by using on-demand load. While this is a great feature, I find myself needing to toggle this setting to avoid loading from source when I am developing.I.e. when I am changing a staging layer, I don't need to reload from source but only from ODX. For my scheduled runs I do want to load on-demand however.I propose two changes:Make it possible to specify whether to apply on-demand in a right-click Execute and dragging onto the Execution Queue Make it possible to turn on / turn off on-demand state when promoting an ODX instance to another
Hi,Is it possible to change the order of appearance of the created display folders in the TimeXtender Data Integration?In the example screenshot, I would like to change so the folders are listed in order 1 - 2 - 3.If not currently supported, it would be great to be able to drag and drop the folders in desired order. This feature would be especially useful when having many display folders.BRMarkus
We have some datasources that have over 5000 tables. The can also have quite the amount of columns. Now when we synchronize the source, this can take up a few minutes. I thought that, when we use “Select tables..” that the synchronize would only query the tables within that those selection rules. However we do not see this in the query on the database. Is this a feature or a 🐛 ? Here is the query SELECTt.[TABLE_SCHEMA],t.[TABLE_NAME],c.[COLUMN_NAME],c.[DATA_TYPE],c.[CHARACTER_MAXIMUM_LENGTH],c.[NUMERIC_PRECISION],c.[NUMERIC_SCALE],c.[DATETIME_PRECISION],c.[ORDINAL_POSITION],c.[IS_NULLABLE],prim.[CONSTRAINT_NAME] AS [PRIMARY_KEY_NAME],t.[TABLE_TYPE]FROM [INFORMATION_SCHEMA].[TABLES] tINNER JOIN [INFORMATION_SCHEMA].[COLUMNS] c ON t.[TABLE_CATALOG] = c.[TABLE_CATALOG] AND t.[TABLE_SCHEMA] = c.[TABLE_SCHEMA] AND t.[TABLE_NAME] = c.[TABLE_NAME]LEFT OUTER JOIN ( SELECT tc.[CONSTRAINT_NAME], tc.[CONSTRAINT_SCHEMA], tc.[CONSTRAINT_CATALOG], cc.[TABLE_NAME], cc.[COLUMN_NAME] FROM [INFORMATION_SCHEMA].[TABLE_CONSTRAINTS] tc INNER JOIN [INFORMATION_SCHEMA].[CONSTRAINT_COLUMN_USAGE] cc ON tc.[CONSTRAINT_NAME] = cc.[CONSTRAINT_NAME] AND tc.[CONSTRAINT_SCHEMA] = cc.[CONSTRAINT_SCHEMA] AND tc.[CONSTRAINT_CATALOG] = cc.[CONSTRAINT_CATALOG] AND tc.[TABLE_NAME] = cc.[TABLE_NAME] AND tc.[TABLE_CATALOG] = cc.[TABLE_CATALOG] AND tc.[TABLE_SCHEMA] = cc.[TABLE_SCHEMA] WHERE tc.[CONSTRAINT_TYPE] = 'PRIMARY KEY') primON t.[TABLE_CATALOG] = prim.[CONSTRAINT_CATALOG] AND t.[TABLE_SCHEMA] = prim.[CONSTRAINT_SCHEMA] AND t.[TABLE_NAME] = prim.[TABLE_NAME] AND c.[COLUMN_NAME] = prim.[COLUMN_NAME]ORDER BY t.[TABLE_SCHEMA], t.[TABLE_NAME], c.[ORDINAL_POSITION]
Hey, in the documentation on executions/jobs I found the following information on setting up emails as notifications for succeeded and failed executions:Enter the information for the SMTP server you want to use under Mail Server. Since October 1st, 2022 Microsoft has ended basic authentication on email on online SMTP servers. To deal with this you need to add an Application (client) id for an app to use for this and the Tenant ID for your company. The app you use needs the following permissions. You need the three options, (Mail.Send, SMTP.Send and User.Read) set on your app You need a Admin to grant consent for the three settings. The user account you add as the From Email and the User name needs to run without Multi-factor Authentication. If you use GMail to authenticate, it is not possible to use email and an std password. Here you need to turn on 2-step authentication for your email account and then use the App Password in the password field. My question:We have a policy that MFA is required for every account, and we do not want to make an exception for this.“The user account you add as the From Email and the User name needs to run without Multi-factor Authentication.”Are there any plans to support for example a client secret setup, to authenticate with the App registration using a client secret? For now this means we cannot use email notifcations, which prevents us from monitoring our TX environment. Kind regards,Rutger
Dear TX development team,What would really set apart TX from other tools would be a Data Governance Module.In this module you can add extra meta data to you data warehouse on a semantic layer level.This means that you can add extra information on Dimension and Measure level explaning what this measure or dimension is all about. Here you can describe the measure in detail, technical term or functional terms. When adding this to you semantic model the end user will have access to what this measure is ‘doing' (function explination, they can see the measure that is being used and the data lineage of the fields that are beging used and where they come from with all transformations and renames listed).When also making this information ready to consume through the API it will be very easy to create a Data Governance BI App on this data giving the business extra tools in understanding what data is being used and what calculations have been used on those fields.You could already start by creating an API endpoint in which the data lineage is easily collected from the reposiloty database.Thanks= Daniel
After copying a semantic model to another (for example, promoting from dev to prod), the target semantic model points to the same data warehouse instance as the source model. This means that after promoting, the target model needs to be resynchronized with remapping and we need to change every single table to the correct table in the correct datawarehouse instance. This is a time consuming process that is also prone for errors.It would be good to be able to set a ‘default' data warehouse instance source per semantic layer, so the SSL points to the correct instance immediately after the copy to instance action.
Add an option to set the checkmark 'Send to execution queue' default turned on.
Hi, In V20 we used the project import functionality often to start a new project using a template project.In V21 we don’t have that option anymore. Can this feature be added to TimeXtender again ? (exporting an XML from an instance / importing an XML into an instance). As a partner it should be possible to do this cross-customer.Best regards,Peter
Just completing a migration from TimeXtender Classic to TimeXtender Data Integration. One feature I was excited about was the new Jobs Feature! No longer.Why can’t you combine Ingest Instance transfers and Prepare Instance Packages?One real pain in TimeXtender Classic is the lack of synchronization between ODX loads and Execution packages resulting in messy scheduling requirements between the ODX and execution packages, never mind how you handle errors in and ODX load impacting a downstream Execution Package.I was so excited, finally a great solution. A Job where I can schedule both in one area.But no! You can either schedule Ingest Transfers, or Prepare Instance Package Executions, but not both in one job. Why? A real missed opportunity!Please make this an enhancement to the Jobs sub system.
Hi, It would be really nice if could automate the project Environment Transfer using command-line or API
When the ODX Server originally came out, there was a really nice documentation feature in the portal that allowed you to define and add tags to ODX Sources based on:source schema table fieldYou could also upload the metadata from your repository into the TX cloud and generate simplified documentation for your whole implementation including the impact of GDPR/confidential data. Having this feature in the new release is becoming more and more important due to larger customers needing to be compliant with internal and external policies. In 20.10.x you can at least tag BU → DWH → SSL or DWH → SSL if you use the ODX, but in the new release this is more fragmented.The main advantage of the prioroption was being able to grant access to a DPO who could then input all the tagging without needing to understand how TimeXtender itself works. While there may not have been much use back then, I think having all of this within the scope of TimeXtender makes for a unique selling point. You can technically do this in Purview (and this is what I am doing in a few situations) but that is not a viable solution across the board.In the current situation you can add tags to DWH instances but there is no end-to-end documentation. The tagging is also only field-based and mostly hidden from sight.
It would be very useful for us if you publish a TimeXtender icon pack to be used in our diagrams.
One reason for downloading a previous version is, if a customer running on an older version and encounter a problem, i would like to install the exact same version to check if i can recreate the problem, in order to find the solution of the problem.
It’s not possible to use snippets in aggregate tables, only regular transformations.Please add snippet functionality to aggregate tables in both v20 and v21.(And please also look at the “current field in snippets” idea put forward by others over time)
Please consider adding the feature to remove tables from Ingest instance storage that have been deleted in the desktop, similar to how the “SQL Database cleanup tool” works for the DW.Let’s take the use case of when SQL Storage is used for the Ingest instance.The “Remove unused object” option does not drop tables.The “Storage Management Task” is good of course, but we can’t use it for deleted data sources.Let’s say I have transferred a large table hundreds of times into my Ingest instance and then deleted the data source. Currently I can’t drop them from TimeXtender Data Integration and the workaround is that I drop the tables manually in SSMS.The feature could work in similar ways for other Ingest instance storages. For example with ADLS Gen2 the feature could delete the files from storage etc.Best,Pontus Berglund
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.