Build better products with our product team
Hi,The query tool incorrectly visualizes datetime fields as dates. We are using version 6346.1.The workaround for this problem is to either cast the field as a varchar, or to do the queries in SSMS.DW_TimeStamp has datatype “DateTime” but is being presented as a “Date” field in the Query tool In SSMS DW_TimeStamp is correctly presented as a “DateTime” field Appreciated if anyone had a look at this.Best,Pontus Berglund
Hi,it would be great if we could include ODX instances in a perspective. Especially in a multi-developer situations where we have different ODX instances with distinct data sources for different developers it would be really helpful. CheersKai
The new environment feature in the portal is very useful. Apart from making it visually clear which instances belong together, it also makes environment promotions a lot easier than before.There is a drawback to the current implementation though: each environment is expected to be part of a single linear chain: 1 → 2 → 3 etc. I think it would be useful to have the option to have multiple chains. You might require a separate setup for HR compared to other data but want to be able to manage them from one place.
I’m using the “Add junk dimension table” feature to create a degenerated dimension and store it the Invoice number for example.It works perfectly but it would be very useful to add in this feature the possibuility to “Add data selection rule” to filter the records to store on it.
I’ve seen that internally, TX creates tables to store the primary keys. If there are a lot off records:It would be better to create indexes on them as Azure recomends:
Add an option to generate documentation for a specific project perspective.
Hi, I was wondering if it is possible to setup Multi Environments with 2 ODXs with the newest version (6436.1) on a single server? If so, I assume that you have to create a second ODX service; one for e.g. development and one for production. In the 20.10 version you could fix this within TimeXtender via Tools -> Windows Service Setup -> Options -> Create service. However in the new version I cannot find this option.
In large environments the list of data sources in your ODX instance can get quite long. It would be nice to organize this better. For instance, I have a lot of Excel sources (which we want to get rid of, but that’s a different story) that make the list of data sources very long. Putting all of these into one folder/group would provide a much better overview of all data sources.
Rather than aggregating changes at the project level, I recommend introducing a feature that enables detailed logging at the object level, akin to the functionality of the description field.We utilize the description field to meticulously track our modifications, and subsequently, these alterations are associated with the driving DevOps Workitem and visualised in a PowerBI report.This approach not only provides a comprehensive view of impending deployments but also chronicles previous modifications. By logging the initials of the developer alongside each change, we maintain a clear record of who made each alteration and their rationale behind it. This clarity is further enhanced when the change is directly linked to the work item, as it offers additional context and background information.For a more in-depth information on this topic, I invite you to read my LinkedIn article
Whenver I install the ODX Server I get slightly annoyed that the ODX Server Configuration tool window pops to the back (at least not to the front) requiring an extra click to pull it forward. Should be an easy fix.
Hi,the data soure provider upgrade button in the TX portal is a great feature.What is not so good, is that there are sometimes dependencies between a provider version and the installed TX/ODX version at the customer site. So when a customer accidentally upgrades the provider before he upgrades the TX version there might be problems.It would be great if there was also an option to “downgrade” to an older version or if the dependencies would be shown in a popup or somewhere in the data source.The best solution would be,that an upgrade is not allowed if the customer uses an incompatible TX/ODX version, but I don’t know if the installed TX version is stored in the repository in the cloud. Cheers,Kai
I’ve detected that when I’ve a job that runs two packages:If the fist package fails it will run the second.In this case it’s not correct.There is some way to avoid it?
When upgrading v21, it would give peace of mind if it was possible to downgrade shortly afterwards.One option could be to keep the pre-upgrade repository available for e.g. a couple of weeks, allowing for an “upgrade cooling off period”.In v20 solutions, I always keep a backup of the repository before upgrading but that’s not an option in v21.
In our favorite Gantt chart the execution step is always orange and the cleansing step is blue. A table insert has a different color, purple. I think it would make sense to show a difference between a full load and an incremental load in the Gantt chart. Perhaps make one of them yellow or darker orange.Like this: This would benefit beginners that have trouble figuring out why their transformation doesn't do any thing (see this nice meme by @rvgfox ) And it would also help in spotting executions that could be incrementally loaded, and other monitoring purposes.
When setting up data source connections, especially for CData connections, there may be a large amount of settings. There is currently an index which really helps to jump down to the setting you want to change.This would be even better if the index floated on the left, so that you don't have to scroll up many pages. Similarly if you have changed a setting and want to apply it, you need to scroll all the way down to the Save button. If this floated at the top-right, this would be much easier to do.
Hi,There’s probably a bug within the Job Execution Log View. It looks like the bug happens when having 20 or more tasks (e.g. synchronize, transfer, cleaning) in 1 job. We have an example at a customer of us, but to be able to share some screenshots I just recreated the situation by adding 21 synchronize tasks of the adventure works database.When running a job with 12 tasks in it, I receive right Job Execution Log: Current job Execution log of the jobHowever, when I add in total 21 execution tasks, and execute it, I don’t get a status update in the job execution log, although that I know that it has completed successfully. This because I can see it on the execution log of the ODX. See the results below: Current job Execution log of the job Execution log of the ODX When changing the job again into 14 tasks I correctly receive a status in the Job Overview:Could you please have a look into this.Thank you in advance. Kind Regards,Devin
Hi all,in our case we are always also the implementation partner for our TimeXtender customers. Which means that I am both the admin of our own data estate in the portal, as well as the customers data estate.Right now, I have to create a new e-mail alias for each customer and add me as a company admin/data estate admin and then open the portal a second or third time in an incognito browser to work on the customers data estate.It would be really helpful, if there would be a possibilty for a “context switch” in the portal. So I switch into a customers data estate via a drop down list of or customers or something similar.This would lessen the administrative effort by much and make the development for different customers much easier.Thanks for considering the idea!Kai
When using mapping sets, is it possible to synchronize them all at once? Similar to how we can use “Synchronize with ODX” ? I noticed that changes do not show when we use “Synchronize with ODX” on mapping sets.
If you have MFA enabled, TimeXtender will not prompt you for user+pass but only for your MFA key on subsequent opening of the application. I guess the user+pass is coupled to the Windows user signed in, which is useful in most situations. If you have a machine with, for instance, local accounts (User1, User2, etc.) that are logged into by different TimeXtender Portal users they will not be able to pass the MFA challenge (someone else's key) and not be able to log out completely.Apart from the fact that this is very annoying, it should be possible to set an option to force a complete login and be possible to do a complete logout. Currently you only have MFA authentication the first time and single-factor in subsequent times at worst (depending on how people secure their on-time-pass device). This may be a hiccup that SSPs and partners can run into a bit more often than end-customers, but still something that should be smoothed out.
When promoting an instance (copying for example from dev to prod), the datawarehouse instance needs to be copied and after that, all semantic models need to be copied one by one, which is a bit of a time consuming process.It would be nice to be able to set up some kind of promotion job in which you can add multiple copy to instance actions into one job and execute it.
In the ODX management pane, all Data Source nodes are expanded by default. After each refresh, all sources are again expanded which makes the screen somewhat cluttered.It would be nice if the data sources are collapsed by default, so they can be expanded when needed (like everywhere else in the GUI).
Currently there are multiple places where you have to enter you ADF credentials. For instance:All ADF Data Sources: Storage Management Task for rolling up incremental data: Transfer ODX to DWH It would be nice to manage ADF instances/credentials on one central place, not on every single data source/task. ClientID/Secrets have a maximum lifespan of two years, which means a new secret has to be entered on multiple/many locations.
Currently, the number of choices of operators is limited when filtering rows in ODX data sources.The available options can be seen in this screenshot: It would be great to have “greater/less or equal” in here as well. It would be even better if we write our custom filtering rules, like how we can set custom data selection rules on DW tables.
I have a source database that allows NULL values in primary key columns. What happens now is that these tables fail on transfer because the ODX server does not allow NULL values in key columns.I can of course override the key for the table but it is a key provided by the source database, and this also eliminates the possibility to set up an incremental load.Also, my general incremental load rule (this database has a change date column with the same name in every table) leads to a warning every time the table with the removed primary key columns is transferred.A solution would be to set an option to allow NULL values in primary key columns, or to be able to set a default value on columns.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.