Skip to main content
To homepage To homepage

    Filter by idea status

    Filter by product

    859 Ideas

    S
    Contributor
    sigsolContributor

    Option to choose different transfer technology for different tables/sourcesSUBMITTED

    Hi,Today we can choose between ADO.NET and Azure Data Factory to transfer data from Ingest to Prepare in the config for the Prepare instance in the portal. However, these two have very different strengths. I would be great to be able to use ADO.NET for small tables and ADF for large ones, maybe by having an option in the configs of each of the the data sources in the portal. ADO.NET is much faster for small or incremental tables because of the substantial time it takes to start up each pipeline in ADF, while the data transfer itself is faster in ADF, and is therefore faster for larger tables.

    0
    S
    Contributor
    Forum|Forum|2 months ago
    sten.lomme
    Participant
    sten.lommeParticipant

    Please fix the Table Builder editorSUBMITTED

    The new Table Builder for the new Enhanced Data Sources is a great addition. However, the UI is extremely lacking and quite frankly not very nice to work with.The “Show XSLT” section is too small for any viable code reading and editing There is no “maximise window” to increase working space When editing the XSLT code, the UI does not support ENTER for linebreak. Instead it just closes the Table Builder.Please note we are running TX Classic v20.10.72.64

    1
    A
    Forum|Forum|2 months ago
    P
    Contributor
    Paul BridgeContributor

    Metadata Manager - Select Tables FunctionalitySUBMITTED

    TDI v6898.1HiBefore the recent upgrade that introduced the metadata manager functionality I had to limit a data source connection to specific tables for the metadata synchronisation, otherwise the sync process would attempt to read the entire schema from my Oracle JDE database which would take upwards of 50+ hours. This was straightforward to do as I could set up which tables to specifically run the synchronise step against by using the 'Select Tables' functionality to limit the sync step to just the handful of tables I wanted.However, I do not see a way to achieve this using the latest version of TDI and the metadata manager, and when the metadata manager attempts to scan the the source database we are now back to it taking an extremely long time.Can you please tell me how I can restrict the metadata manager schema synchronise step to just the tables I am interested in.Thanks

    10
    peter.jensen
    TimeXtender Xpert
    Forum|Forum|2 months ago
    wouter.goslinga
    TimeXtender Xpert
    wouter.goslingaTimeXtender Xpert

    Import XML/JSON from webservice when configuring table flatteningIMPLEMENTED

    The new TimeXtender native REST connector works very well, especially compared to the complex RSD configuration with the old CDATA connector.The tool to flatten out the XML/JSON returned by the webservice is also very handy and helpful to structure the data into the datawarehouse.At this point, we still need to use an external tool like SoapUI or Postman to fetch the XML/JSON from the webservice and paste it into the XSLT configuration tool. Since the connector already has the necessary information to get the data from the webservice, it would be nice if there is a ‘Get from webservice’-like button so the data is fetched directly instead of having to copy/paste it from another tool.

    2
    Thomas Lind
    Forum|Forum|2 months ago
    B
    Starter
    brian.brijlStarter

    Prepare Instance -> Azure SQL Database server storage type -> Authentication -> no option for 'Azure Managed Identiy'SUBMITTED

    Hi,We are setting up our TDI environment and we are surprised there is no ‘Managed Identiy’ authentication option for connecting to an Azure SQL Database in the Prepare Instance.  Since we are running TDI in Azure VM’s and are using Azure SQL Databases, we really want this option to be added. Is it possible to look into this? Or maybe the development team has already got this issue on their list?Now, we are using a Service Principal which works, but is of course not password-less :-(. Thanks,Brian

    0
    B
    Starter
    Forum|Forum|2 months ago
    B
    Contributor
    BennyContributor

    Allow views to be queried through the API semantic endpointSUBMITTED

    The title is pretty self-explaining I believe. Currently one cannot add view to a semantic API endpoint they don't show up anywhere, as I mentioned here.

    2
    peter.jensen
    TimeXtender Xpert
    Forum|Forum|3 months ago
    S
    Contributor
    sigsolContributor

    Optional batching/grouping of small ingest loadsSUBMITTED

    When loading data from Ingest to Prepare, each small table gets its own copy data activity in Azure Data Factory. These activities each come with of a lot of per-activity overhead that adds up to a lot of wasted time. Bundling together many smaller tables in the same copy data activity would probably save a lot of time.We therefore suggest to support an option to bundle multiple tables into the same ADF copy data activities.In our environment (TimeXtender SaaS + ADF + self-hosted IR + ADLS Gen2 + Azure SQL), Source → Storage account data transfer is quite fast, but Storage account → Azure SQL Server transfer in ADF is slow because of the high number of copy data activities that need to be created and started up.For example, during a busy workload, we observed a copy of 1 row / 136 bytes from ADLS to Azure SQL taking about 27 seconds in Copy activity (around 40 seconds end-to-end), while the actual transfer time reported by ADF was only about 6 seconds. This is a typical example for small tables, not an exceptional one.An optional grouping mode for small/medium ingests would likely reduce:per-activity orchestration overhead self-hosted IR CPU/process churn total elapsed ingest timeWe believe this would be useful not only for Azure SQL/ADF scenarios, but more generally for environments where many small loads are executed separately against cloud platforms.

    0
    S
    Contributor
    Forum|Forum|3 months ago
    D
    Starter
    Dror.Svartzman_1Starter

    TimeXtender Orchestration: reload qlik appSUBMITTED

    IntroductionIntroducing the Qlik Cloud endpoint is a major milestone in bridging the gap between TimeXtender and Qlik Cloud. You now have the ability to generate and refresh QVDs directly from TimeXtender. However, one crucial step is still missing to complete the end‑to‑end orchestration pipeline: the automatic refresh of Qlik dashboards.Feature RequestAdd the ability to trigger a Qlik dashboard reload directly from TimeXtender Orchestration.How?This could be implemented by allowing TimeXtender to call the Qlik Cloud Reload API as part of an orchestration step. TimeXtender would send a request to Qlik Cloud to trigger a reload of a specific app or task after the QVD generation step completes. This ensures seamless, fully automated data pipeline execution—from data ingestion to refreshed dashboards. 1. Add 'Qlik Cloud'  in 'Datasource type’ of Data ProviderParameter: 'API Key'2.  Add 'Qlik Cloud Refresh’ packageParameters:a. Space b. Dashboard 

    0
    D
    Starter
    Forum|Forum|3 months ago
    erik.van.mastrigt
    TimeXtender Xpert
    erik.van.mastrigtTimeXtender Xpert

    Ingest: SQL allow dirty readsSUBMITTED

    When source tables are heavily used and ODX Server performs a load, the process is very slow or may even fail. Using Business Unit, we have the option to 'Allow Dirty Reads' to allow TX to read tables without locking them. This option lacks in ODX Server. Currently we have to add all tables as a Managed Query, adding the WITH NOLOCK statement. Ticket #18989.

    7
    L
    Forum|Forum|3 months ago
    peter.jensen
    TimeXtender Xpert
    peter.jensenTimeXtender Xpert

    Add 'import connection profile' to TimeXtender V20.10SUBMITTED

    We’ve setup some TimeXtender Rest API connections in the TDI portal but like to implement those in the TX V20.10 project before we migrate to TDI.It would be very helpful if we had the option to import the connection profile (exported from the TDI portal) into TX V20.10 providers (Business Unit and ODX Server)Best regards,Peter

    2
    rory.smith
    TimeXtender Xpert
    Forum|Forum|3 months ago
    sten.lomme
    Participant
    sten.lommeParticipant

    Please fix the Query Tables editor in Data Source SettingsSUBMITTED

    The Query Tables editor is exremely impractical to work with. We have quite a few Query Tables and the issues are:The list of current query tables is not sorted in any way. The sorting seems totally random. Even when you create new query tables. Please allow sorting of this list. Alphatecially is 10x improvement. Please make it possible to maximize the Data Source Settings window. This would include the Query Tables editor. With larger SQL statements it is extremely cumbersome to use the tiny window. It is not even possible to make the window larger by dragging its edges. 

    2
    sten.lomme
    Participant
    Forum|Forum|3 months ago
    sten.lomme
    Participant
    sten.lommeParticipant

    Allow use of Projecte Perspecives in Execution Package Full Load Objects sectionSUBMITTED

    In execution packages we can use Project Perspectives to limit what is included or excluded in the execution package (under Included Steps and Exclude Steps). This gives incredible flexibility.Under the tab “Full load objects” however, it is only possible to select specific table objects or specific Business Units/Data Warehouses. It is not possible to use perspectives. This results in having to select every single individual object for full load.Adding this feature would increase the flexibility to select which objects are fully loaded vs not. One could use the perspectives to dynamically select the full loads.

    0
    sten.lomme
    Participant
    Forum|Forum|3 months ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    Global execution queueSUBMITTED

    We need a “global” execution queue so we can queue executions from different instances … e.g. a Prepare data warehouse update followed by a Deliver semantic model update, just like in v20.On that note, we also need the Execution Queue Log feature that we know and love in v20.(I assume this idea is relevant for all storage platforms … if not, then the idea is for Microsoft Fabric solutions)

    0
    Søren Sørensen
    Contributor
    Forum|Forum|3 months ago
    R
    Explorer
    rrnExplorer

    Execute dimensions for a single cubeSUBMITTED

    It would be great if it were possible to right click the dimensions node under a cube in the semantic layer and be able to deploy and execute the dimensions that are used in this cube only instead of having to track down each dimension and execute it individually.

    0
    R
    Explorer
    Forum|Forum|4 months ago
    Søren Sørensen
    Contributor
    Søren SørensenContributor

    TDE - Usage/limit indicatorSUBMITTED

    There is a (default?) database limit that restricts the volume of data in TDE.It would be nice with an indicator that tells how much database space has been consumed as a percentage of this limit.

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

    TDE - Default schema on new CategorySUBMITTED

    It would be nice if we could specify a default schema per category in Data Enrichment.It makes permission config a little bit easier when different business areas’ data sit in separate categories.

    0
    Søren Sørensen
    Contributor
    Forum|Forum|4 months ago
    E
    Starter
    EmilGilljamStarter

    Mapping between tables in the Data AreaSUBMITTED

    In our DSA (a single Data Area per source) we use several tables for the same data set to make transformations in steps.Each data set has at least two tables in the data area. The first we call Ingest-somthing wich is raw data mapped from the Ingest-instance.The second one is where we validate data. We do at least this before moving on to DW.However, Mapping sets only seems to be able to map between Data Areas. As in Ingest > DataArea1 > DataArea2 > ect.But i would like Mapping sets to be able to map to another table in the same Data area. As in my case Ingest > DataArea1.Table1 > DataArea1.Table2 > DataArea2

    1
    rory.smith
    TimeXtender Xpert
    Forum|Forum|4 months ago
    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|4 months ago
    J
    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
    E
    Starter
    Forum|Forum|4 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|4 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|4 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|4 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|5 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|5 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|5 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