Build better products with our product team
I would like to have the option to aggregate strings in the TimeXtender Aggregate functionality as can be done in SQL via a STRING_AGG() function. I’m currently doing this with views.
Hello,it would be great if you could do anonymization and the like in Timextender's REST Connection.You can do that in Cdata's REST connection.BRAnders
In the legacy version of TX, it was possible to check one or more semantic models in a project perspective. If the perspective is dynamic, it would then automatically select all tables required for that semantic model in the perspective.In the new TX version, semantic models are separate instances and can therefore not be selected in the data warehouse Perspectives. So now we have to select all tables manually and maintain the selection if tables are added to a semantic model.It would be very helpful if we are able to select a semantic model in a data warehouse perspective.
TDI UI Improvement idea - Make sure Data Selection Rule and Field Validation are disabled when incremental load is applied to a table.
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
Hi,This is related to post:The suggested solution is to use 'Review Tasks’ to deploy the changed table/View together with security. But than you have to deselect ALL other tables and views you do not want to deploy/execute. This is not a workable solution when you have hundreds of tables you need to deselect each time you need to deploy a table with security. It is also not directly clear for developers which tables are used in security rules. This would mean that every time you change a table or a view you have to do a differential deployment on data warehouse level.Please make sure that table/view security is automatically deployed when a table and/or view is changed. Make sure that users don't have to manually add security to the production environment each time after a environment transfer.
Hello,wouldn't it be good with a best practice analyzer for Prepare and Deliver instances.A BPA can start on a modest scale and develop over time. There will certainly be suggestions on what needs to be checked in the Community.The same applies to the functionality. You can start with a report that lists possible areas for improvement, with suggestions for action.The next step could be for Timextender to provide an interactive proposal where the proposals for measures are listed with checkboxes so that you can choose which ones you want Timextender to implement.If a BPA is to be implemented in the portal or application, I leave it open.BRAnders
Hi, Is it possible to create your own Exmon Process Map Templates?If so, how to save them as a template. Regards,Devin
Add feature to enable table partitioning in SSAS tabular models.
At the moment. It is is possible to install/update data source connectors to the newest version. While in some cases, the new version of the connector is not compatible with the installed version of TimeXtender. This means you have to install a older version of a data source connector, or you need to update TimeXtender Data Integration to the newest version.It would be way easier if only the data source connectors were shown in the portal that are compatible with in installed TimeXtender Data Integration version. Or at least, a pop up/warning is visible that is showing the compatible versions for the selected connector.
In the new version from yesterday 02/04/24 we haven’t enought space to see the SSL instances:It would be nice to be able to create something like Power Bi Pipelines to define the sequence DEV->PROD for each group of instances because it would be more clear and more safe:
Add option to copy/clone instances in the Portal. Just like the clone option for Data Sources that can be used in the portal.
Currently, when you open the Environments page in the portal, the Semantic Models are shown per two items with scroll buttons. We have customers with around 20 semantic models, so you need to click around a lot to go to the model you need. Also, when you click it to copy it to another instance, the UI switches back to the first two items so you have to click your way back again to the next one.It would be nice if the portal shows more Semantic Models at once, perhaps around 10. There is space enough. Even better would be if you can choose the amount of models shown.
As mentioned in this post :It is currently necessary to manually map all tables whenever a new promotion of a Prepare instance is done. This makes the use of multiple environments for DTAP tedious and unnecessary a lot of work. With each new release the amount of fields/tables could grow, leading to more overhead work for mapping. Since only 1 ODX could run per server isn't it a simple solution to just get a pop-up which asks if we would like to use the same Ingest instance or choose one? It can then automatically remap based on the new Ingest instance. Whenever a table or fields name doesn't match it could give us the same remapping table in which we can manually correct these or take other actions.Please look into this, since I cannot see how the current process should work as it does.
Hi team, Currently I am working in a project with 60+ instances, across three environment folders. There are certain actions in TimeXtender Data Integration that trigger all of the folders to open. This is frustrating, as it makes it easy to open an instance from a different folder in the list by mistake. Closing an instance, for example, causes all folders to expand. Kind regards,Andrew
I love this feature, as it can also be used to quickly incorporate datawarehouses made when TimeXtender was not used yet. I gather that it was created because the Export/ Import feature from version 20.10 is no longer (or not yet?) available.However, when taking a database, created with TimeXtender, it unfortunately simply also takes in the raw tables, Log and Message tables (as the gif in your article clearly shows). This means actually that you need to clean up a lot of “ingested” tables from the solution and remove all the system fields, like DWID, because the deploy just doesn’t work otherwise. If it wouldn’t take too much work, it would be great to have an option to Choose a Schema to import. If best practices are followed, then only the Valid schema should be enough.. and it would allow to import a Staging area only, or a Final area only have a check box to remove any fields which would conflict .. and thus not scripting any of the system fields which TimeXtender will add again.Until this is made, I’ll work on with a custom solution because I believe this feature offers the opportunity to refrain from re-inventing the wheel over and over again, but to inject template sets of tables and views to gain even more time.
Hi community,Often, multiple versions of the same measure are made with only slight differences. Being able to clone a measure, including its parameters, would speed up this process and is relevant for all endpoints.Kind regards,Andrew
I would be great if there is a standard connector to the TimeXtender API available in the standard data connectors list.
At this moment it is not possible to use Azure AD Integrated Authentication on MDW instances. You can select this setting in the portal but it is not working in the Desktop Client.More and more customers want to use AD integrated authentication (MFA) in their applications. Azure Active Directory enables you to have single place for user management instead of different SQL accounts for each SQL server/database. It is also recommended by Microsoft to use AD Integrated Authentication. One reason is that this makes it possible to trace different user activity on the SQL server. This is not possible when all developers use the same SQL account when connecting to the SQL server. Please make it possible to use Azure AD Integrated Authentication on data warehouse instances.
Hi,The new feature in 6429 to group instances in environments is excellent. Copying in the portal also works well. Especially with the ability to select data warehouse instance mapping when we transfer semantic models.This brings up a couple of new possibilities.The first concerns semantic models. it would be an advantage if you could choose to keep the roles you set up in an instance. They often become different in the environments. A little check box in the transfer dialog that gives the choice to keep roles and row level security setup in the destination instance.The second idea concerns the application. It would be great if you could choose which environment you want active and visible in the application.BRAnders
I can’t see it’s possible to set up instance specific data area roles where some end users can access the PROD data warehouse and other end users can access the DEV data warehouse.The feature is available (and very useful) in v20 but I can’t see it in v21.
Hi team, For some of our clients it would save time and administration if we could create our own roles to assign to users, instead of individually assigning access to instances in a solution. For example, some business users might want to be able to check logic in our ‘test’ SSL (deliver) instances, but need no access to the data warehouse or other SSL instances in ‘dev’ or ‘prod’. When there are many instances, it would be much faster to define a role, select the instances that the role has access to one time, and then assign the role to users as needed. Currently, we would need to open each instance in the portal and add each user. The user list for each instance is managed independently. Kind regards,Andrew
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.