Product ideas

863 Ideas

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.

Forum|Forum|3 months ago

aftabpChampion

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.

Forum|Forum|3 months ago

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 👍

Forum|Forum|3 months ago

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

Forum|Forum|3 months ago

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

Forum|Forum|3 months ago

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.

Forum|Forum|4 months ago

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

Forum|Forum|4 months ago

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:

Forum|Forum|4 months ago

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.

Forum|Forum|4 months ago

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

Forum|Forum|4 months ago

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

Forum|Forum|4 months ago

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.

Forum|Forum|4 months ago

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

Forum|Forum|4 months ago

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.

Forum|Forum|5 months ago

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.

Forum|Forum|5 months ago

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

Forum|Forum|5 months ago

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.

Forum|Forum|5 months ago

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

Forum|Forum|5 months ago

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.

Forum|Forum|5 months ago

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.

Forum|Forum|5 months ago

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)

Forum|Forum|5 months ago

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.

Forum|Forum|6 months ago

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.

Forum|Forum|6 months ago

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.

Forum|Forum|6 months ago

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

Forum|Forum|6 months ago

Filter by idea status

Filter by product