Build better products with our product team
My client has a data source where all the string fields have data type char.They would like to change the data type to varchar for all those fields, but keep the original character length limit. I.e. char(10) → varchar(10), char(255) → varchar(255).To do it in the current version of the ODX they would either have to create one rule per data type which is not feasible, or convert the fields to a large enough varchar that all the char fields would fit which is not optimal.They would like to have a feature where they can set that char(X) → varchar(X):
In version 20.5.7.64 a tooltip showing detailed information about a conditional lookup field would show up when hovering over the CL field, see screenshot:This feature is really useful to get an overview of tables with many conditional lookups, and especially many “multiple conditional lookups”, without having to drill down inte every single field.This feature has been removed in later versions. It would be great if it could make a comeback in version 6XXX.
Hey, I use the select tables feature a lot and I find it confusing that when I add a table from the total list on the left it will show in the selection but it is not removed from the list on the left. It would be much easier to check and use if the tables that you added are removed from the list on the left
Integrate a feature that enables instant formatting of poorly structured SQL code, similar to the functionality available at https://poorsql.com/.Please refer to the following link for a resource that can assist in achieving this: http://architectshack.com/PoorMansTSqlFormatter.ashx.This enhancement would prove valuable, particularly when dealing with views and stored procedures.
Hi,It would be nice if a partner has the possibility to use the same e-mail address for logging into their own portal, and for all customers.In practical terms, you could perhaps have a drop down in the login where you choose a customer, or your own portal.It would make it easier for consultants who work with several clientsBRAnders
Dynamic perspectives are always based on data lineage. It would be great to have an option to create a dynamic perspective based on a bottom up approach (impact analysis). This way it becomes possible to create e.g. project perspectives per data source or schema.
It would be usefull to centralize both options, guard of development and guard of execution, for all tables in one screen to be quicker to enable it or disable it.
The current database cleanup wizard for DWH instances looks across all Data Areas in the instance and lists any objects that seem eligible for removal. This is useful in many scenarios, but I think it would be good to have the following enhancements:make nodes in the hierarchy for each Data Area and list items under those make it possible to run the cleanup from a Data Area only for items in that Data Area
Please make it optional to filter rows in ODX without specifying table names. In this example, I would like to filter all tables with the column “CreatedDate”: The workaround I currently use is to set the “Table operator” to “Not equal” and writing an “x” as the value, which is not the most elegant solution:
Hi,Is it possible to change the "SELECT FROM” fields in the query tool, to a script with each field on a new row, as shown below? This improves in my opinion the visibility and makes it easier to change the script. Regards,Devin
I would like to see the search result displayed with a column for the layer (ODX,Stage,DW) and the table name. A type (field, lookup, super natural key) column could be useful too for sorting/grouping the results. I also think it would be more relevant to only display fields and tables by default, and have additional checkboxes to include "Copy's", "Conditions" and other stuff.
Option to select Valid or Raw by a custom data insert on a table. If we do a Inner join (error) to a table where no custom data exists then the custom data record will not be visible. Now we have to create a custom data record also in the lookup table where we use the error join. Would be nice that we can select where we want to insert the custom data because if we choose the valid this will be visible then.
I would love to by able to enable the source table field by default for my entire project or per data area. Currently I have to enable it per table which is not optimal. So my suggestion is to add it to system fields by default just instead of adding it via the advanced table settings.
Is it possible to add a field DW_SourceTable in the default fields, so you can trace in the data were this is coming from. At a project I have database names like below: 6401 - Company 1$Appointment6401 - Company 2$Appointment6409 - Company 1$Appointment
in version 6024.1.When you are mapping tables between the ODX and a data warehouse layer we mostly use the Smart Synchonize option. You have to drag-n-drop with the Right mouse button to use the Smart synchronize. To use the Left mouse button is more intuitive but this triggers a full sunchronize. Is it possible to Smart Synchronize by default when mapping tables from ODX? And use the Left mouse button for this?
Sometimes we face issues with connectivity to Azure SQL Database during overnight executions. Sadly not all of them are reported by Microsoft, but sometimes resource health issues can be found in Azure Portal. For instance: In such cases, a typical error message in TimeXtender will say ‘Physical connection is not usable’.A transport-level error has occurred when receiving results from the server. (provider: Session Provider, error: 19 - Physical connection is not usable)Module: .Net SqlClient Data ProviderSystem.Data.SqlClient.SqlException As Microsoft also suggest, we use the retry function on TX execution packages: So when Azure SQL Database fails, I expect TimeXtender to initiate a new attempt after three minutes of delay. However, there seems no place/log where I can check if a retry actually happened. Following the execution logs, I have a strong feeling that the execution stopped after the first error. In this example we use TX 20.10.39 with Business Units and CData CSV provider 22.0.8417.Did TX actually perform a retry, and where to check?
When you create a custom view in TX that is not created from a table you have to remember to start with the CREATE VIEW [schema].[view name] AS syntax and match the view name in the syntax with the view name above. This could be 100% automated, reducing the possiblity of errors.The same situation exists with Stored Procedures.
Hey, This idea is not related to the functionality of the product but to the documentation and trainings. Many articles and training pages contain GIFs that show you how to do that what is described. I think it is great that you add visual instructions but the downside of GIFs is that you can’t pause it (at least not natively to my knowledge in Chrome). I want to follow along with the instructions but often have to wait for the GIF to finish, get to where I was stuck and hope to catch what is shown. To me it would be a lot more user friendly to have the ability to play/pause/rewind etc.Hope that you consider this feedback.Kind regards
When making major changes in a 6221.1 solution, we sometimes need to disable jobs to avoid deployment/execution collisions. It would be nice to be able to right-click a job and disable/enable it … preferably with a visual cue showing that the job is disabled when that’s the case.
I would like to be able to use the status of an ODX task as a usage condition. For example when my ODX tranfer task completed with errors, I don’t want my MDW transfer job to run. This is my use case but I expect that others might have different use cases for the same feature. Please feel free to share such use cases below.
Hi,I am reposting my conversation post as an idea instead. To give some background, I am working with TimeXtender Data Integration and trying to understand jobs better. In my trials I intentionally set up a package to fail, and first of all the monitoring view of jobs do not show any information about the error: Jobs monitoringIf I go into the execution log, I can see an error message that essentially just says that the job didn’t succeed.Execution log for test jobFor debugging that means I have to check the contents of the job (that potentially could have multiple execution packages in it) and then head over to the execution tab to check the log for the package, where I see all the details.Execution log in execution tabI would think it was nice to be able to reach the execution message(s) straight from the Jobs log. And by extension it would be super nice if this information was available by the timextender API as that allows us to create a monitoring setup for the DW.
When scheduling jobs in 6221.1, there are use cases where we need to run a job on the 10th day of the month or the second Monday of the month. It would be nice to have this flexibility when scheduling jobs … a bit like Windows Task Scheduler.(I use Windows Task Scheduler to execute TX jobs in 20.10.x for exactly this reason).
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.