Skip to main content
To homepage To homepage

    Filter by idea status

    Filter by product

    859 Ideas

    A
    Problem Solver
    aftabpProblem Solver

    Incremental Load while landing data in BU for Enhanced Rest and OData ConnectorsSUBMITTED

    Possibility for Incremnetal Load while loading data into BU .At the moment, the Enhanced Rest provider does not support Incremental load. So while it can be turn on, it will fail with the error: Incremental LoadValidation status: ErrorMessage: Incremental load is not supported on this table.Here is the Community Post: Incremental Load in BU fails

    0
    A
    Problem Solver
    Forum|Forum|8 days ago
    D
    Starter
    dritzStarter

    Maximize Tabular Custom Measure Script Editor WindowIMPLEMENTED

    It's really annoying that the window can't be maximized or enlarged.I've asked the support for a long time, unfortunately nothing happened. It shouldn't be a big deal to change that?!

    3
    Thomas Hjermitslev
    Forum|Forum|9 days ago
    devin.tiemens
    TimeXtender Xpert
    devin.tiemensTimeXtender Xpert

    Resizing Custom MeasureIMPLEMENTED

    Hi,It seems that it is not posisble to resize the Custom Measure screen. It’s not a big deal, but still it looks like a bug. Especially when creating larger formulas it would be nice if we are able to make the screen larger.Kind regards,Devin

    2
    Thomas Hjermitslev
    Forum|Forum|9 days ago
    K
    Contributor
    KCMTContributor

    Freeze Top Pane/Row in Perspectives screen while scrollingIMPLEMENTED

    It would be nice to have the top row frozen in the Perspective screen so you can always view which Perspective you are modifying.  Now when I start scrolling I lose track of the perspectives. 

    1
    Thomas Hjermitslev
    Forum|Forum|9 days ago
    P
    Contributor
    PieterQContributor

    Add logging and cache option to Salesforce data source connectorSUBMITTED

    There is no logging option nor the cache option for the Salesforce connector. Please add.

    0
    P
    Contributor
    Forum|Forum|15 days ago
    D
    Starter
    Dror.Svartzman_1Starter

    Qlik Cloud endpoint: Create Dimension and Measure directly from Semantic layerSUBMITTED

    The introduction of the Qlik Cloud endpoint is a significant step forward. To further enhance this capability, it would be highly valuable to enable the automatic generation of Qlik master items (measures and dimensions) directly from the Delivery instance (semantic layer).Currently, it is already possible to define measures and custom fields within the semantic layer. Building on this, we propose extending the functionality by allowing additional properties to be specified for these objects, specifically for the Qlik Sense / Qlik Cloud endpoint.This would enable seamless creation and management of master items in Qlik, improving consistency, governance, and reducing manual effort.Proposed enhancement:Allow defining Qlik-specific properties on semantic layer objects: Measures: Name Description Expression Label expression   Qlik Cloud: Master Item: Meaure dialog  Dimensions / Custom fields: Field Name Description label expression  Qlik Cloud: Master Item: Dimension dialog  With this enhancement, master items could be automatically generated and maintained from within TimeXtender, eliminating the need for manual setup in Qlik and ensuring alignment between the semantic layer and the reporting layer. Measures and dimensions in Qlik are bound to a specific app. To better support this, I suggest introducing an additional Delivery instance configuration where the target Qlik app can be explicitly defined by specifying both the space name and app name.Upon deployment of this semantic layer, the system could establish a connection to the designated Qlik app and automatically create or update master items using the Qlik Engine JSON API, specifically the CreateMeasure and CreateDimension methods. The properties defined in the Delivery instance (such as name and description) would be used as input for these API calls.This approach would provide a more integrated and automated way to manage Qlik master items directly from TimeXtender, ensuring alignment between the semantic layer and the Qlik application while reducing manual configuration.  

    0
    D
    Starter
    Forum|Forum|15 days ago
    bas.hopstaken
    TimeXtender Xpert
    bas.hopstakenTimeXtender Xpert

    Expand/change the Uneven mapping optionSUBMITTED

    I use the ‘Show Uneven Mappings’ option a lot. But it is only showing the number of mappings in a table, when there is a uneven mapping in one of the columns in the tables. In some cases, I just like to see the total number of mapping in the tables, regardless if there are uneven mappings or not. 

    1
    J
    Forum|Forum|17 days ago
    erik.van.mastrigt
    TimeXtender Xpert
    erik.van.mastrigtTimeXtender Xpert

    Make Ingest data source settings (Filter Rows, Incremental Load etc.) transportableIMPLEMENTED

    In case you have similar data sources which all have the same settings ofFilter Rows Set Up Incremental Load Set Up Primary Key Override Data Types Manage Query Tablesyou have to manually enter the details one by one. When you have a lot of rules to set up, it’s quite time consuming.It would be beneficial if you can easily copy these settings to another data source on the same or a different Ingest instance. I can also think of scenario’s where it would be beneficial to copy tasks between data sources/instances.

    2
    JTreadwell
    Forum|Forum|17 days ago
    S
    Contributor
    sigsolContributor

    Alternative to TimeXtender API now that we have no JobsIMPLEMENTED

    Hello all,The TimeXtender API Endpoints are built around Jobs in TX. Now that Jobs in TX are depreciated, how do we now retain the ability to trigger execution packages via API?Please note I’m not talking about regular orchestration which can be achieved in TimeXtender Orchestration, but the cases where we need to be able to trigger TX via an API, as was possible with Jobs.

    3
    JTreadwell
    Forum|Forum|17 days ago
    P
    Contributor
    philippus.asefawContributor

    Add Incremental Load Option to CSV, Excel, JSON, and XMLSUBMITTED

    I'd like to suggest an enhancement for Timextender connectors (CSV, Excel, JSON, XML): the ability to load data incrementally. In my current setup, I receive new text files daily, and adding a new data area significantly prolongs the loading process. Since CData had it’s own way of incrementally loading text files I think it would be a great opportunity to bring a more efficient handling to the Timextender Connectors.

    4
    JTreadwell
    Forum|Forum|17 days ago
    rory.smith
    TimeXtender Xpert
    rory.smithTimeXtender Xpert

    Support for Semantic Endpoints for Qlik Cloud & improvement to Qlik Sense Enterprise endpointsIMPLEMENTED

    Copy of item in the TimeXtender Product Focus Group with some edits to summarize. In the world of BI tools, vendors are moving to SaaS solutions just as in other domains. Qlik has done the same and is focussing development on Qlik Cloud (QC). As Qlik is delivering nice improvements with respects to Qlik Sense Enterprise (QSE) and QlikView (QV) in this platform, customers are quite motivated to migrate towards this solution.Improvements of note that motivate customers to migrate are:Can host both QSE and QV apps in one solution Notifications and Alerts are included (costly expansion for QSE) Development of new features is done first here (if developments ever land in the older tools) Qlik Application Automation adds powerful features missing in the older solutions Integration of QDI features into the platformThe idea is of course that you use all the other tools in Qlik's suite and work entirely in the cloud, but you can also push data from on-prem. The options Qlik delivers on this topic are the following:Qlik Data Gateway (analogue to the Power BI Gateway). See: here . Coupled with using the correct APIs, this seems the easiest way to get support to work. This approach is also more performant than Qlik DataTransfer. Qlik Automation can expose REST endpoints that can be called from TX to do things like reload apps. Qlik DataTransfer allows you to create a DataSet in QC that can (on a schedule) reload data from a source (for instance the views created by a Semantic Model in a Datawarehouse instance's Data Area) into QC and reload an app. Qlik DataTransfer can also "watch" a folder and upload files (QVD, CSV, etc.) to the Data Files area and reload apps. Qlik DataTrasfer can also reload apps in QSE and move them to QC. Qlik APIs create/import/reload apps programmatically (with or without data) qlik-cli commandline tool to interact with Qlik APIs Qlik Sense Enterprise customers with QSE deployments can synchronise apps from on-prem to QC based on rules QlikView Publisher customers with QlikView Publisher deployements can publish apps to QC  Within our active customers and in a lot of our pre-sales discussions with prospective customers we see a large motivation to move to QC. The question that then pops up is "How will TimeXtender support / work with Qlik Cloud?". Given that there are APIs that would allow programmatic integration with the platform, we feel TimeXtender should be able to support QC as a first-class citizen. This would mean that an endpoint for QC should be implemented that allows the generation of QVD or front-end apps for:customers with only QC --> use the APIs to facilitate this customers with QSE and QC --> use the APIs or use the existing QSE endpoint and programmatically configure the synchronisation capability to synch apps with QC customers with QV Publisher --> can set up the push to QC in their environment as there is probably no API for thisThe current QSE endpoint implementation would also benefit from a review: you point TimeXtender to a QSE node (QSE deployments can consist of many nodes) and TimeXtender talks directly to the Engine Service on this node. This may overrule any load balancing defined in your QSE deployment: you might have reload nodes set up to perform heavy lifting on appropriate hardware but TimeXtender may be talking to the central node of a cluster causing reloads to happen on the wrong node.Qlik publishes APIs to programmatically work with their system and allow any rules set up in the cluster to be applied. Given that QSE can work with QC, it stands to reason that the same approach QSE takes to push apps to QC could be taken by TX.Taking this approach means customers will use Semantic Models and automate from within TimeXtender instead of setting up something manually that will likely pull data from a Datawarehouse layer instead of using a Semantic Model.One of the most powerful points of Semantic Models is being able to define them and push them to whatever tools you support. Needing to bypass Semantic Models for tools likely to be very common is unfortunate. This also makes it easier for customers to transition between BI solutions without needing to re-engineer or to feel that effort spent developing Semantic Models was wasted in retrospect. What problem is this solving?There is no direct support for QC in TimeXtender, work-arounds are much more manual than was the case before Power BI Premium Capacity support or require QSE next to QC and are therefore more costly.As Qlik fleshes out Qlik Application Automation and tools like Qlik DataTransfer, customers may decide that the added benefits of the things QC does will outweigh the automation TimeXtender would bring if you then need to manually integrate the two.TimeXtender has the (Shared) Semantic Layer as a major component of the solution, it would be strange if QC customers would then need to bypass this. And this becomes especially tricky if things like row-level security (Section Access) would then require complicated work-arounds. The current QSE implementation bypasses QSE handling appropriate for clustered environments meaning that deployments with larger Qlik installs need to change the approach and do more development in Qlik instead of in TimeXtender than would normally be required. How is this problem currently solved (inside or outside of TimeXtender)?In the case of QC: Customers would need to deploy Qlik DataTransfer to pull data to the cloud (time-consuming manual process) or monitor a folder with CSV exports (not efficient) or keep a QSE instance (costly) running to be able to push to QC.Another option is to pull data from TimeXtender into QC (potentially through Application Automation) if the database is reachable from QC. This way of integrating data is generally more robust than using Qlik DataTransfer, but does require the database being reachable from outside and needing to write or push script. How does this idea improve the business value for NEW and EXISTING customers?New customers would expect support for the current platform offered by one of the largest BI vendors. Not having to worry about the chosen BI solution or the migration between them would be a great relief.New customers with large QSE deployments would not need finicky workarounds to get their load balancing to work. Existing customers considering migration would not need to worry about how to deal with this and would be able to fulfill the wishes of business quickly. Existing customers would also not need to re-engineer parts of their implementation when they decide to work with QC instead of QSE.For QSE deployments, working with the proper Qlik APIs would make it possible to make much more use of the features provided by TimeXtender and bundle more of the orchestration there instead of needing to dive into QSE. Provide references or explain why this approach is best practiceWe have tried out the architecture where QC and Qlik DataTransfer were chained together to push data to Qlik Cloud (in PoCs). This is in no way a "pretty" process, especially compared to the ease with which you can work with the currently supported endpoints. We have also tried out the Qlik Data Gateway approach and this works well, though currently in a pull scenario.Being able to orchestrate as much of the data chain from source to end-product from TimeXtender is a great USP that should be strengthened further. 

    4
    JTreadwell
    Forum|Forum|17 days ago
    D
    Starter
    Dror.Svartzman_1Starter

    Qlik Cloud Endpoint: Add Data spaceIMPLEMENTED

    Currently, TimeXtender only supports deploying apps (.qvw) to a specified space, while QVD files are stored in the underlying “QVD folder.”It would be a significant improvement if the app deployment (.qvw) could remain unchanged, but the QVD storage location could instead be directed to a dedicated Data space, as defined in the portal’s Data space setting.This would provide better alignment with governance and data management practices.  

    1
    JTreadwell
    Forum|Forum|17 days ago
    K
    Contributor
    KajEmergoContributor

    Use Azure SQL repo with AAD & MFASUBMITTED

    Hello,We designed our TX solution in Azure and set up an Azure SQL db as our repository database with a specific Azure AD group (which contains our developers) as ‘Azure Active Directory admin’. Our organization has enforced MFA, which unfortunately makes it impossible for us to connect to our Project Repository through AAD authentication. The option is simply not available:Have you encountered this before? How can we work with this? It would be really nice to use the ‘Azure Active Directory admin’ setting instead of working with sql logins. 

    9
    FlorisW
    Forum|Forum|18 days ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Salesforce incremental loadingSUBMITTED

    I’m sure this is already on the roadmap, but we of course need the new Salesforce connector to support incremental loading.

    0
    Søren Sørensen
    Contributor
    Forum|Forum|24 days ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Salesforce table and parent table data selection rulesSUBMITTED

    We need data selection rules in our new Salesforce connector. Salesforce has “implied” relationships between e.g. quote line and quote header, and this opens up for a variation to our traditional data selection rule logic. Example…Assume the quote header table contains a country field. Our traditional data selection rule logic allows us to filter this table, e.g.:Country IN (‘AU’,’NZ’).The quote line table does not contain a country field but it’s still possible in the TX REST API to filter the quote LINE table using a quote HEADER filter. In the TX REST API, such a query would look like this:SELECT+Id,Name,CurrencyIsoCode+FROM+QuoteLine+WHERE+Quote.Country+IN+('AU','NZ')We select lines from the QuoteLine table based on a filter referring to the Quote (parent) table, and then Salesforce does the rest.

    0
    Søren Sørensen
    Contributor
    Forum|Forum|24 days ago
    D
    Starter
    Dror.Svartzman_1Starter

    Qlik endpoint: Add possibility to adjust Qlik ScriptSUBMITTED

    We suggest enhancing the script generation by allowing a customizable section before the generated LOAD script. This would provide developers with greater flexibility to insert and manage their own logic independently of the autogenerated content.  

    0
    D
    Starter
    Forum|Forum|25 days ago
    nkatlytix
    Starter
    nkatlytixStarter

    ExecutionsSUBMITTED

    In the execution view it would be nice with an extra column that shows which schedule groups the package is part ofIt would also be nice if you could you this view as a static view on a screen whitout keyboard and mouse.But when you have to many packages to be shown on a screen you cant see the last packages. So would it be possible to it automatic roll the list when there is to many to show?  

    0
    nkatlytix
    Starter
    Forum|Forum|30 days ago
    R
    Participant
    r.miltenburgParticipant

    Assign tables to an endpoint within deliver instanceSUBMITTED

    In Data Integration, it is possible to define multiple endpoints within a single deliver instance. In practice, all of our endpoints are intended to be accessed through Power BI. By assigning different roles, we can grant end users access to a specific endpoint.It would greatly benefit us if tables within a deliver instance could also be assigned to an endpoint. This would prevent the need to create a large number of deliver instances, which may also result in duplicated tables across those instances.In summary, in addition to assigning roles to an endpoint, we would like the ability to assign specific tables within a deliver instance to an endpoint.

    0
    R
    Participant
    Forum|Forum|1 month ago
    A
    Problem Solver
    aftabpProblem Solver

    Improve Error Handling in TableBuilder for TX Enhanced ConnectorsSUBMITTED

    When creating a table in TableBuilder, either by pasting JSON data or by selecting a file as the data source, any input error can cause the Data Source window to close unexpectedly. Examples include: Missing commas in pasted JSON. Trailing commas in pasted JSON. Invalid or incorrect file paths when selecting a file. Currently, when such an error occurs, TableBuilder closes the Data Source window and discards all unsaved work. This is particularly problematic when creating a new endpoint, as users can lose significant progress if their work has not been saved beforehand.Requested ImprovementTableBuilder should not close the Data Source window or discard the user's work when a data source validation error occurs. Instead, it should: Display a clear error message indicating the issue. Keep the user within the TableBuilder interface. Preserve all entered data and configuration settings. Allow the user to correct the error and continue without losing progress. Instead of writing the path to source file, there should be browser button so that correct file could be choosen. This change would significantly improve the user experience and prevent unnecessary loss of work caused by minor input mistakes.

    0
    A
    Problem Solver
    Forum|Forum|1 month ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Roll-back in TDI / v21SUBMITTED

    We need a way to roll a solution back to a prior version of Data Ingest and Data Integration. I’ve spoken to several partners, and there is a bit of “TDI upgrade anxiety” at the moment.In the olden (v20) days, I just backed the project repository up but we can’t do that in the modern cloud world … roll-back was in those days a simple matter of removing the upgraded project repository and restoring the backup.If anyone has a solution that overcomes “upgrade anxiety”, then please share 👍

    3
    rory.smith
    TimeXtender Xpert
    Forum|Forum|1 month ago
    N
    Starter
    Niels ScholtesStarter

    Auto Map Fields (Button) After Pasting SQL (e.g. from LLM / AI)SUBMITTED

    Pasting SQL (especially from AI) is pretty common, I think.When pasting queries or logic into custom views or calculated fields, mapping fields manually is repetitive. An auto mapping button could analyze the SQL and automatically match fields based on names, schema, and database, allowing users to review instead of setup mappings.For smaller queries this might not add much value (just double click the field). Not a big fan of heavy view usage myself but for views and larger transformations this could be a useful feature.If the SQL already runs without explicit mapping, the relationships are implicitly defined, so an auto‑map should in theory just surface that logic rather than change it (correct me if I’m wrong).

    0
    N
    Starter
    Forum|Forum|1 month ago
    N
    Starter
    Niels ScholtesStarter

    Structured & Automated (Suggested) Version Notes in TDISUBMITTED

    A simple text field for version control requires manual input, which leaves room for incomplete entries and adds extra effort.An automated suggestion would pre-fill release notes based on actual changes, reducing the risk of missing or low-quality input and making it easier to trace issues in deployment history. With a small set of predefined settings, versioning rules and numbering could be applied consistently. Even as a small feature, this could be very useful to rollback or distinguish between minor commits and larger changes (such as migrations), based on all changes since the previous deploy. I would expect this to look something like this, but I assume the SEs will come up with something better:Automatic draft generation: pre-filled release notes based on all changes since last deploy Editable suggestion: users can adjust before finalizing, but never start from empty Version numbering rules: configurable (e.g. incremental / semantic / date-based) Traceability: direct link between version notes and actual implemented changes

    0
    N
    Starter
    Forum|Forum|1 month ago
    andri
    Contributor
    andriContributor

    Option to accept or discard metadata changes of a data source after synchronizingIMPLEMENTED

    When you synchronize a data source and there are some problems, or the metadata changes are not to your liking (NoSql sources can be problematic), it would be good to have a choice to accept the metadata changes when you get the synchronization results before they are applied to the project. In some situations, all the tables are removed because of a data source issue and you have to close the project without saving and open it again.

    4
    JTreadwell
    Forum|Forum|2 months ago
    darrirafn
    Starter
    darrirafnStarter

    Email Notifications for Orchestration Summary Error MessagesSUBMITTED

    Hi there. Currently we get the long error messages when something fails in Orchestration executions, which tends to need some encryption at times to understand. However, in the new Portal I get this gloriously understandable error message:  Is there any chance as of now to get these new error mesages as the email notifications? Best regards,Darri 

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

    Sort Indexes in the table tree viewSUBMITTED

    As you can see in the screen shot the indexes are not sorted: And when we setup it, neither: 

    2
    rvgfox
    Problem Solver
    Forum|Forum|2 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