Skip to main content
To homepage To homepage

    Filter by idea status

    Filter by product

    863 Ideas

    andri
    Contributor
    andriContributor

    Allow multiple jobs to be run concurrentlySUBMITTED

    The current design in TX v21 doesn’t allow more than one job to run at a time per execution service. In many environments, either with multiple instances or with data sources that require frequent updates this is quite a limitation as jobs will constantly be added to a queue with the waiting state. There shouldn’t necessarily be a need to have multiple VM’s with a separate execution engine just be able to run jobs simultaneously.When using exMon for orchestration and as a tool for business user to run executions on-demand it can also give the user a false pretence that the job has started when it is actually waiting in queue. If it has to wait too long the exMon package will get a timeout failure when there is no failure. The package will eventually start and finish successfully but the user will not know about it.This limit also makes the current concurrency options for the execution packages quite useless.

    8
    JTreadwell
    Forum|Forum|1 year ago
    andrew.gebhard
    TimeXtender Xpert
    andrew.gebhardTimeXtender Xpert

    Manage Job QueueSUBMITTED

    Hi team, An issue that I am running into relatively often is that a job fails to fail or complete, staying in the ‘running’ state indefinitely. Sometimes cloud services can experience transient issues, which may cause these anomalies. More importantly, however, there is no way to clear the queue, stop existing jobs, or force a job to restart when it's already running. Furthermore, there is no timeout on jobs, so they can continue to run forever.Example: this job has been in the running state for about 30 hours. It runs a number of Ingest Transfer and Cleanup tasks:Job MonitorIn the ODX Execution Queue I can see that there are no ODX tasks waiting or running, so I cannot cancel anything from there: Ingest Instance Execution QueueStarting the job manually or via eXmon does not work, I get the message failed to run message from eXmon: “The TimeXtender job 'ODX - OneLake and FTP - Transfer + Cleanup' is already running”. If this was a prepare or deliver job, it would now be blocking the other prepare or delivery jobs from running. -- The only way to reset the jobs is by stopping the ODX Service and restarting it. This causes all ODX tasks (also outbound) to fail instantly, which is far from ideal in an environment where data is constantly being loaded, and lengthy reloads may be running outside of work hours. It's also difficult to explain to a client that they may need to do this periodically to keep their environment running. We should have more control over the how jobs run, fail, and cancel. Jobs waiting or running in the queue should be able to be removed without restarting a service and a large unplanned impact to the platform. Kind regards,Andrew

    0
    andrew.gebhard
    TimeXtender Xpert
    Forum|Forum|1 year ago
    Roy V
    Problem Solver
    Roy VProblem Solver

    Multiple running Prepare jobs in one execution serviceSUBMITTED

    HelloI see two tickets for it not being possible to have multiple jobs running at the same time. The answer was that it is not posibble within one execution service (only for ssl now).With more and more organisations moving to more real time analysis, timextender is the ideal tool to have multiple job schedules during the day (even with extract data on demand to have it combined with data ingestion). But then you are limited, that for one instance, it can only have one job running and other jobs have to wait. I just don’t understand how that matches with the filosofy of the tool?I hope that based on the related tickets a solution to this issue is one of high priority.The wo tickets: If not high on the priority list can you please let me know how we can solve this in the meantime (of course without using the development or acceptance execution service for production jobs).For example : one job runs each hour and one each two hours. When the 2-hour job is running the job which needs to run each hour will not run while the two hour job is busy (and runs for an hour and a half). I don’t want a technical limit on these times, it needs to be based on the business needs.

    4
    Roy V
    Problem Solver
    Forum|Forum|1 year ago
    wouter.goslinga
    TimeXtender Xpert
    wouter.goslingaTimeXtender Xpert

    Automatically detect parametersSUBMITTED

    In custom table inserts, views, custom transformations and custom measures (in deliver instances) we create parameters that point to fields or tables, to create dependencies, lineage and catch column or table renaming.Currently, we have to drag and drop these parameters every time. It would be very nice if the editor had a ‘detect parameters’ button that automatically creates parameters based on the code written.

    1
    rory.smith
    TimeXtender Xpert
    Forum|Forum|1 year ago
    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Improve synchronizing Prepare Instance with Ingest InstanceSUBMITTED

    In the 6xxx release when you synchronize your Prepare instance with an Ingest instance there are two things that may happen:TimeXtender automatically handles changes, no input is required. TimeXtender cannot automatically deal with the changes and user input is required to tell TimeXtender how mappings should be set up.In both cases, there are significant improvements to be made (or deficiencies handled). I will list my issues and suggestions for each in the following sections:Changes can be handled automaticallyIt is usually great that TimeXtender handles things for you, but there is currently no way of seeing the changes that were applied. In the 20.10.x BU setup, a source synch would show you what changes were applied. In my opinion what should be available is the following:a synchronize which can be auto-resolved should show the proposed (additions, removals, mutations) changes. It only applies them if the user agrees it should be possible to review the current mapping state in its totality the interface showing all mappings should be sortableChanges cannot be handled automaticallyWhen TimeXtender cannot handle changes, it shows a dialogue with all mappings (one line per table, followed by all field mappings). You need to scroll through a potentially huge list of mappings to find any that are problematic. This dialogue will not accept empty (None) mappings and give you a warning. What we need here is the following:the interface showing all mappings should be sortable (to quickly sort on tables with errors) it should be possible to collapse and expand tables (start with everything collapsed) so that fields can be hidden for a shorter list it should be possible to select None as a mapping. If a field is removed from source, there is no reason why None is not a valid mapping to DWH. It is fine to mark the field visually, but if I want a field without a mapping that is not always an error it should be possible to filter the interface so I can focus on the problems only instead of needing to scroll through thousands of mappings with pgdn to try and find one problematic mapping it should be possible to review the current mapping state in its totalityI am not sure how mapping sets are currently visualised (if they are at all), but those rules should be reachable from the general mapping interface.

    1
    andrew.gebhard
    TimeXtender Xpert
    Forum|Forum|1 year ago
    Participant
    thzmanParticipant

    Add instance name to tabs in the GUISUBMITTED

    It would be helpful if you add the instance name in the GUI, to the tabs for DSA and MDW, just like you have done for the Execution tab. See the attached picture.The right DSA tab is for production and the left DSA tab is for DEV, but there is no way to visually tell them apart.  

    0
    Participant
    Forum|Forum|1 year ago
    rogier.helmus
    Problem Solver
    rogier.helmusProblem Solver

    Supporting STRING_AGG in aggregationsIMPLEMENTED

    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.

    4
    rogier.helmus
    Problem Solver
    Forum|Forum|1 year ago
    anders.e.jonsson
    Contributor
    anders.e.jonssonContributor

    Anonymization in Timextender REST ConnectionSUBMITTED

    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

    1
    Participant
    Forum|Forum|1 year ago
    wouter.goslinga
    TimeXtender Xpert
    wouter.goslingaTimeXtender Xpert

    Add semantic model instance to data warehouse perspectiveIMPLEMENTED

    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.

    4
    Christian Hauggaard
    Forum|Forum|1 year ago
    Employee
    Greg LennoxEmployee

    Make sure Data Selection Rule and Field Validation are disabled for incremental load tablesSUBMITTED

    TDI UI Improvement idea - Make sure Data Selection Rule and Field Validation are disabled when incremental load is applied to a table.

    1
    rory.smith
    TimeXtender Xpert
    Forum|Forum|1 year ago
    Contributor
    dsvartzmanContributor

    Add Undo featureSUBMITTED

    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 

    3
    devin.tiemens
    TimeXtender Xpert
    Forum|Forum|1 year ago
    coen.donders
    TimeXtender Xpert
    coen.dondersTimeXtender Xpert

    Automatically deploy table and view securitySUBMITTED

    ​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.​

    1
    JTreadwell
    Forum|Forum|1 year ago
    anders.e.jonsson
    Contributor
    anders.e.jonssonContributor

    Best Practice Analyzer for Prepare and Deliver instancesSUBMITTED

    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

    2
    anders.e.jonsson
    Contributor
    Forum|Forum|1 year ago
    devin.tiemens
    TimeXtender Xpert
    devin.tiemensTimeXtender Xpert

    Create Exmon Process Map TemplatesSUBMITTED

    Hi, Is it possible to create your own Exmon Process Map Templates?If so, how to save them as a template. Regards,Devin

    2
    devin.tiemens
    TimeXtender Xpert
    Forum|Forum|1 year ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Add table partitioning for SSAS Tabular modelSUBMITTED

    Add feature to enable table partitioning in SSAS tabular models.

    13
    bas.hopstaken
    TimeXtender Xpert
    Forum|Forum|1 year ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Check compatibility data source connections with installed version of TimeXtender Data IntegrationSUBMITTED

    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. 

    1
    Christian Hauggaard
    Forum|Forum|1 year ago
    rvgfox
    Problem Solver
    rvgfoxProblem Solver

    New screen to manage environmentsIMPLEMENTED

    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:  

    1
    Christian Hauggaard
    Forum|Forum|1 year ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Add option to copy/clone a instance in the portalIMPLEMENTED

    Add option to copy/clone instances in the Portal. Just like the clone option for Data Sources that can be used in the portal. 

    2
    Christian Hauggaard
    Forum|Forum|1 year ago
    wouter.goslinga
    TimeXtender Xpert
    wouter.goslingaTimeXtender Xpert

    Show more deliver instances in the TimeXtender Portal Migrations sectionIMPLEMENTED

    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.

    2
    Christian Hauggaard
    Forum|Forum|1 year ago
    Bitmetric_Maarten
    Contributor
    Bitmetric_MaartenContributor

    ODX mapping question after promoting Prepare instanceIMPLEMENTED

    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. 

    2
    Christian Hauggaard
    Forum|Forum|1 year ago
    andrew.gebhard
    TimeXtender Xpert
    andrew.gebhardTimeXtender Xpert

    Closing instance should not force environment folders to expandIMPLEMENTED

    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

    3
    Christian Hauggaard
    Forum|Forum|1 year ago
    Dirk Meert
    Explorer
    Dirk MeertExplorer

    Reverse data Area .. refiningSUBMITTED

    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.

    3
    Christian Hauggaard
    Forum|Forum|1 year ago
    Starter
    p.laadStarter

    Partial release - Deploy single/multiple component between environments instead of promoting the whole instanceSUBMITTED

    As of now we need to deploy the whole project from one environment to another. This requires a lot of effort. Let’s say is there is defect in TEST environment in a single component, then we need to do the fix in DEV and TEST manually only for that component. As TX doesn't allow to migrate only a single or multiple components. It has to be the whole project. It also causes a lot of dependencies if multiple teams are working on the same project.

    2
    Christian Hauggaard
    Forum|Forum|1 year ago
    andrew.gebhard
    TimeXtender Xpert
    andrew.gebhardTimeXtender Xpert

    Clone (custom) measure in Deliver instanceSUBMITTED

    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

    2
    andrew.gebhard
    TimeXtender Xpert
    Forum|Forum|1 year ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Create TimeXtender API connectorSUBMITTED

    I would be great if there is a standard connector to the TimeXtender API available in the standard data connectors list.

    1
    Christian Hauggaard
    Forum|Forum|1 year ago

    Filter by product

    • All products
    • TimeXtender Data Integration
    • TimeXtender Data Integration Portal
    • TimeXtender Data Enrichment
    • TimeXtender Orchestration & Data Quality
    • TimeXtender Classic
    • Data source providers
    • Exmon
    Terms and ConditionsAccessibility statement