Skip to main content
To homepage To homepage

    Filter by idea status

    Filter by product

    863 Ideas

    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Include custom measure definitions in TDI's search functionalitySUBMITTED

    Please include custom measure definitions in TDI’s search functionality.

    0
    Søren Sørensen
    Contributor
    Forum|Forum|6 months ago
    Contributor
    jarleContributor

    Error handling timeXtender Rest Dynamic valuesSUBMITTED

    Also mentioned in this Q&AIt would be great to have functionality for handling errors in the timeXtender REST connector (and maybe other connectors as well). When using dynamic values some APIs will return 403 error when user doesn’t have access to the endpoint, or there is no record for that dynamic value. It can often be related to newly created entries, so not always easy to filter away manually.Maybe a simple checkbox to be able to go to next dynamic value upon error. Or more advanced, to be able to make a list of error codes and the handling:Error code Handling Wait 403 Continue with next record 0 sec 429 Retry 60 sec 401 Stop   404 Continue with next record 0 sec

    2
    Forum|Forum|6 months ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Inline scripts on Date tables in Fabric LakehouseSUBMITTED

    Please enable the inline script feature on Date tables in Fabric Lakehouse Prepare.I use the feature in SQL to, inter alia, calculate the number of workdays in a month and put those values on each date record for easy reference in various use cases.The workaround is an auxiliary table with an inline script, but that’s a pain in terms of object dependencies.

    0
    Søren Sørensen
    Contributor
    Forum|Forum|6 months ago
    devin.tiemens
    TimeXtender Xpert
    devin.tiemensTimeXtender Xpert

    Migration Multi environments - Remember configuration defaultSUBMITTED

    Hi,Would it be possible to set by default "Remember configuration” to on/ true. In my opinion almost everytime you need the same settings, so it would help if this setting is on by default.  

    0
    devin.tiemens
    TimeXtender Xpert
    Forum|Forum|6 months ago
    darrirafn
    Starter
    darrirafnStarter

    Read or synchronize view fields on every deploymentSUBMITTED

    Hi, is there ever a reason you would not read or synchronize view fields after deploying a view? I think every deployment of a view should simply include reading/synchronizing view fields. Just a simple idea to save a bit of time and unexpected errors (that is if a user forgets to synchronize fields). 

    0
    darrirafn
    Starter
    Forum|Forum|6 months ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Make migration from Tabular to Power BI premium endpoint in Deliver instance easier, regarding custom measuresSUBMITTED

    We have a customer that is migrating from Azure Analysis Services to the Power BI Premium/XMLA endpoint. While the custom measure syntax is still the same (DAX), all custom measures needs to be recreated and mapped to the tables/colums/measures in the ‘Power BI premium’ endpoint of the custom measure. This can be a lot of work, especially when it are a lot of custom measures. We’ve created a ticket for this as well (#29795).It would be way better if the DAX syntax can be entered in the custom measure window in a ‘DAX’ endpoint that will be mapped/deployed to both Tabular (on prem and Azure) and Power BI/XMLA endpoints.

    3
    rory.smith
    TimeXtender Xpert
    Forum|Forum|7 months ago
    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Allow Data Movement from Prepare to PrepareIMPLEMENTED

    In TimeXtender Classic you can have as many Datawarehouses as you want and move data between them. While you can add many Data Areas inside one instance in TDI, you cannot have data move from one Prepare Instance to another.The main advantage to this is that each Prepare Instance can be its own, appropriately scaled, infrastructural entity. One example is the situation where you have an implementation that starts growing horizontally: adding more subcompanies to a group, or adding more data due to acquisitions. In this case your database might not be scalable to handle the new data, or the project might be getting too large. In this case instead of scaling up a huge database to be able to handle the peak load, you can split out into smaller chunks. This also allows separating out HR data into separate hardware.

    3
    Thomas Lind
    Forum|Forum|7 months ago
    Gabriele Sangrigoli
    Starter
    Gabriele SangrigoliStarter

    Feature request: Export ticket list to CSV for reportingSUBMITTED

    I would like to submit a feature request regarding the support ticket overview/list.In larger and well-organized organizations, it is important to be able to report and analyze support activity over time - for example: where time is spent, which resources are working on which issues, the nature/category of the problems, and the timing of ticket creation and closure. To do this effectively, the underlying data needs to be easily available, sortable, and exportable.Could you please consider adding an option (e.g., a button in the ticket list view) to export the ticket/case list to CSV (or a similar format)? Ideally, the export would include as much information as possible per case, such as: ticket ID, title/summary, status, priority, category, assigned resource, requester, creation date/time, last updated, closure date/time, and any relevant tags or metadata available in the list view.This would significantly improve reporting and internal follow-up, and make it easier to maintain operational oversight of support work.  

    0
    Gabriele Sangrigoli
    Starter
    Forum|Forum|7 months ago
    erik.van.mastrigt
    TimeXtender Xpert
    erik.van.mastrigtTimeXtender Xpert

    TimeXtender PostgreSQL connectorSUBMITTED

    As CData has been deprecated/is available for additional fee, we’d like to have a native TimeXtender PostgreSQL data source connector.Our current workaround is using ODBC, but this is not the ideal solution (eg. credentials managed on server side, lots of tweaking to load bulk data etc.).

    2
    erik.van.mastrigt
    TimeXtender Xpert
    Forum|Forum|7 months ago
    Contributor
    sigsolContributor

    REST connector 500 error to trigger error instead of warningSUBMITTED

    As of today, getting 500 errors in ODX/Ingest data transfers using the REST connector does not trigger an error, only warning. This makes it almost impossible to catch. Even if 500 means that something is  wrong in the source, we must be able to catch it either to accommodate the possible source limitation (eg. downtime during certain times) or to contact the source admins. For the user, this error is just as urgent as any other.I propose to make all errors trigger an ODX error (so that the execution package fails), or at least to add an option to set this behavior.

    0
    Contributor
    Forum|Forum|7 months ago
    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Create TimeXtender Enhanced Connector for SalesforceIMPLEMENTED

    In the post-CData era, getting data from Salesforce using the Enhanced REST connector is quite painful:set up the Objects call to get the list of tables Salesforce contains, especially custom tables for each table call the describe endpoint in a REST endpoint to get the list of field (and their types) use table flattening to make the output as easy to parse as possible use local file cache to get the output you need use your favourite data-mangling tool to get the list of fields, I went with a regular expression to create what I needed turn your field XML into SOQL make REST endpoints for each table deal with pagination and any other complexity use data type overrides to deal with type scanning shortcomingsIt would be nice if there could be an Enhanced connector that does this for Salesforce, I imagine a large number of implementations need to deal with Salesforce after all. I get that at some point Blueprints could be useful for this, but custom tables and fields and some lacking functionality would still make for a painful process in my opinion. Automating the metadata fetching would be much better.

    2
    Christian Hauggaard
    Forum|Forum|7 months ago
    rvgfox
    Problem Solver
    rvgfoxProblem Solver

    Please Folders !!!SUBMITTED

    When we use a lot of objects it is necessary to group them in folders or to have them sorted at least alphabetically. For example to see the folders of External Executables, it is a madness:  

    4
    rvgfox
    Problem Solver
    Forum|Forum|7 months ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Add option to clean '_PK' tablesIMPLEMENTED

    Add option in Storage management task to clean the ‘_PK’ tables in the ODX database. I've created a topic a while ago about the ‘_PK’ tables are growing rapidly in terms of disk space. To avoid having bigger ‘_PK’ tables then ‘DATA’ tables in the ODX, it would be great this table can be cleaned. I think the storage management task would be the place to do it. You should be able to set the maximum number of batches that need to be saved in the ‘_PK’ tables.As a reference:  

    11
    Christian Hauggaard
    Forum|Forum|7 months ago
    Contributor
    juriaan.hensbroekContributor

    Import Measures in Semantic ModelSUBMITTED

    From a governance perspective, we would like all production Power BI report measures to be secured and managed in TimeXtender. At the moment, we sometimes have reports with up to 100 measures, which currently have to be retyped one by one as a measure in TX.Power BI allows measures to be exported as a JSON export, which can then also be converted to Excel.How great would it be if we could import these measures directly using the JSON file from PBI, or alternatively via a generic Excel upload function. This would save a lot of manual work.

    0
    Contributor
    Forum|Forum|7 months ago
    sten.lomme
    Participant
    sten.lommeParticipant

    Qlik Cloud Deliver endpoint release for the old classic versionsSUBMITTED

    Hi,When is Qlik Cloud Deliver endpoint estimated to be released for the classic versions?

    0
    sten.lomme
    Participant
    Forum|Forum|7 months ago
    Participant
    annfossParticipant

    Prefix Data Areas by InstanceIMPLEMENTED

    Hi, I really appreciate the ability to open different data areas across multiple instances. However, it would be helpful to see which instance each data area originates from—perhaps with a prefix or label at the top when they are open. This would reduce confusion, especially when data areas have the same name across instances (e.g., production and development environments).  

    2
    Thomas Hjermitslev
    Forum|Forum|7 months ago
    erik.van.mastrigt
    TimeXtender Xpert
    erik.van.mastrigtTimeXtender Xpert

    Copy tables between DWH instancesSUBMITTED

    It would be nice to be able to copy data between DWH instances. Currently it is not possible to copy tables from DWH instance A to DWH instance B. You can load instance A as a source into ODX/Ingest and then load it to instance B, but for large tables it consumes a lot of time and resources (compressing and decompressing parquet etc).We have two scenarios where this feature would be very useful: Make corporately cleansed data (partially) available into smaller division data warehousesOur customer wants to process and cleanse all data from their main systems in one central place. The result is stored in the corporate DWH. But also divisions have their own, smaller DWH. We would like to push data from the corporate DWH to division DWHs in the same way you can copy data between data areas. Make big data sets available for customers and auditorsWhile we can use semantic models, csv export and REST API to make data available to third parties, it sometimes is just too much data for these methods to transfer it efficiently.

    1
    Thomas Hjermitslev
    Forum|Forum|7 months ago
    darrirafn
    Starter
    darrirafnStarter

    "Word wrap" for Query toolIMPLEMENTED

    Hi there, working with Query tool would be a lot nicer if the structure was different, perhaps with a “Word wrap” feature. Working with large tables, you have to scroll all the way to the right to find what you are looking for. If the standard view would be one line for each column and even “hold ALT and press up/down arrows to rearrange” functionality… that would be really nice!Best regards,Darri 

    2
    Thomas Hjermitslev
    Forum|Forum|7 months ago
    Contributor
    luuk.boumanContributor

    REST data source option to include the relational model in nested endpointsSUBMITTED

    The idea is to add (an option to) the relation of an endpoint from the root level to nested tables when using a REST data source. Currently the normal behavior doesn't incorporate this relation. Meaning you end up with the right tables from the endpoint, but have no way to relate these tables. The CDATA connector did bring this relation. Working with Qlik it brings the relation and even the option to choose a key generation strategy. This seems like a gap in the functionality of the TX REST connector. Workarounds are available but costly in resources. Full description:When working with REST APIs that have nested endpoints my experience is that a standard setup (without for example table flattening) does not take into account the relation within the nesting hierarchy. In other words, in this way the result is 1 root level table that includes the PK and any number of lower level nested tables that cannot be related back to the main table.From what I know I either have the option to use a unnecessarily complex solution using dynamic values and query from endpoint tables. This is undesirable because in some cases I have to query the full endpoint two times and run up costs or into rate limits. The other option would be to table flatten every single nested table and carry over the PK from the root level. This is undesirable as in the past couple of cases I was querying endpoints that originally didn't need any table flattening. So something that works as easy as filling in the right parameters turns into a tedious XSLT job. Adding this functionality to the TX REST connector would help save time and/or reduce the number of necessary API calls. Even more so, it seems to be standard functionality for some of TXs competitors and other players out in the field. Vilsen, Luuk Bouman 

    0
    Contributor
    Forum|Forum|7 months ago
    Stefán Gunnar Jóhannsson
    TimeXtender Xpert
    Stefán Gunnar JóhannssonTimeXtender Xpert

    Being able to use parameters in PowerShell packagesSUBMITTED

    It would be nice to be able to use the parameter functions in PowerShell packages

    6
    Stefán Gunnar Jóhannsson
    TimeXtender Xpert
    Forum|Forum|7 months ago
    peter.jensen
    TimeXtender Xpert
    peter.jensenTimeXtender Xpert

    Add prefix to table when adding it from ingest to prepareSUBMITTED

    Hi,it would be nice if we can define a prefix (which should be added to the table name when the table is added from ingest into the prepare layer) - more or less the same as it used to work in V20 with business units.How this could work :- add a new property on the data source : prefix- when adding the table to the prepare instance add the prefix to the table.This would avoid issues when several sources have the same tables. 

    0
    peter.jensen
    TimeXtender Xpert
    Forum|Forum|7 months ago
    Contributor
    luuk.boumanContributor

    Option to use Windows authentication when conencting to a manipulation SQL server in REST data sourceSUBMITTED

    In the scenario when you set up dynamic values or pagination in a TimeXtender REST Data Source, currently the only way to login to a SQL Server instance is by using a SQL account. There are reasons why it would be preferable to use other forms of authentication such as Windows authentication. One of them being central control and management of accounts and credentials.When connecting to an Ingest SQL database storage the dropdown to select one of several types of authentication is available. Is it possible to add this functionality to the REST Data Source SQL server connection as well?Dynamic values example:Ingest instance option:Hilsen,Luuk Bouman

    0
    Contributor
    Forum|Forum|7 months ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Keep selections and mappings when changing v20 data source providerSUBMITTED

    When switching data source providers in TX Classic (v20), TX Classic should keep table/field selections, business unit lookups/parameters and mappings from the business unit to data warehouses … the metadata is there.This feature is a bit urgent because many customers will choose to switch from CData to built-in/enhanced providers before 5 March 2026.

    0
    Søren Sørensen
    Contributor
    Forum|Forum|7 months ago
    erik.van.mastrigt
    TimeXtender Xpert
    erik.van.mastrigtTimeXtender Xpert

    Gantt chart for Ingest Transfer TasksSUBMITTED

    Recently there have been some improvements with logging on the Ingest service. Some analysis are still hard to do, for instance to measure how long it takes to load a particular table/API endpoint if there are multiple tables within one Transfer Task.Prepare instances have detailled logging per table and per step, including a gantt chart. This way you can easily identify tables/steps with bad performance.Currently it can be quite time-consuming to identify slow tables/steps in an Ingest instance. A more detailled logging per step (data transfer, build parquet etc) with start- and endtimestamps, a gantt chart etc. would be a huge time saver.  Please also see  

    0
    erik.van.mastrigt
    TimeXtender Xpert
    Forum|Forum|7 months ago
    Contributor
    MaarsenContributor

    Be able to disable fieldsSUBMITTED

    I would like to disable certain fields in my tables. At the moment, I have several calculated fields that are no longer used, but the only way to remove them from the deployed table is to delete them entirely. I would prefer an option to temporarily disable these fields. They should remain visible in my TX view, but not be included in the database. This way, we can easily reactivate them in a few months if needed, without having unnecessary fields cluttering our data warehouse.Additionally, the ability to deactivate fields would be helpful when debugging certain tables.

    2
    Contributor
    Forum|Forum|8 months 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