Build better products with our product team
In the Orchestrator Desktop, the different levels or steps of a process are clearly visible, making it easy to understand and manage the structure of complex workflows. However, in the Portal, this hierarchical visibility is lacking, and users are unable to see the various steps in the process with the same level of detail.It would be highly beneficial if the Portal could also display the different levels in a similar manner as the Desktop version. This would improve transparency and usability in the Portal, helping users better navigate and manage their processes.
Is it possible to add the ability to duplicate an endpoint in the TimeXtender REST data source?It would be a nice feature to have to avoid doing repetitive work when working with APIs with multiple endpoints.
There where it is possible to filter a column on blank values in the desktop appplication of Data Enrichment module (MDM), it seems that filtering on blank values in the portal is not possible. Please add this option, because those values are mostly the ones that users should work on.
Tiny request, but should be working in my opinion. In Data Enrichment, when having a column with a checkbox datatype, when you select a box and want to undo the change by the usual bottun, it does not undo your change of checking the checkbox. For the other datatypes, the undo button works fine.
Fabric Lakehouse fields come through with underscores instead of spaces, e.g. Company_Currency.Prepare instance fields might be identical but with spaces for readability, e.g. Company Currency.When smart synchronizing a table in a Fabric Lakehouse solution, it would be great if TDI would perceive spaces and underscores as being the same character so we can avoid all the manual field mappings.
It costs a lot of time setting all format options for date, datetime and currency columns/measures correctly. In most cases, you like to use the same formatting for all date, datimetime and currency columns/measures in the same Deliver instance.It would be way easier if we have a 'general/default formatting setting’ in the Deliver instances to set some default formats for currency, date, datetime and time. Or at least show the last used format at the top of the dropdown list, this will save a lot of time scrolling through all formatting options.
If a user connects to AX 2012 using a standard SQL connector and decides to switch to the Dynamics Finance provider, the switch is implemented as a cloning. This cloning does unfortunately not “remember” the selected tables and fields in the original data source … effectively preventing the provider switch in larger solutions.It would be nice with an option to retain all metadata (including keys, incremental rules, etc.) when cloning a data source … also when it’s a standard cloning and not a provider change.
Hi, It seems that it is not possible within TX Data Quality to use User Mapping on a User group level.Would be great to have this feature.P.S. If i am wrong, and it is possible to use user mapping on a group level, please let me know.Kind Regards,Devin
After upgrading TimeXtender (TDI/TIS) to the latest version, most of the times you have to individually open all instance to upgrade them to the latest versionIn a setup with 55 instances times 3 environments (dev/test/prod) this is serious time-consuming work. Opening, confirming, waiting until the instance is loaded, close it, next, repeat. This should be way simpler.E.g. a wizard where you can select the instances (include option ‘select all’) and instantly upgrade them. It may be a window within the Execution Service Config tool.
I have a situation where a v6221.1 MDW execution step initially failed. Because of the Retry configuration, the package ultimately succeed and the MDW execution log shows Succeeded = True, which is the desired behavior.But I received two email notifications from this execution; a Fail message after the initial Fail and a Success message after the final Success.Since TX knows that it will be retrying the step, I suggest we change the subject for the first email notification to be something like “Fail/Retrying” instead of just “Fail”. I get alarmed when I see “Fail” whereas I would only be on alert if I saw “Fail/Retrying” or something like that … and when I get alarmed, I immediately jump onto the customer’s box to see what’s happening.
In the current TimeXtender CSV Data source, the Header Setup only allows the first record to be marked as the header. In some cases, files may contain one or more redundant rows, before the actual data starts:<Row> 1 Some irrelevant data 2 FieldA FieldB FieldC 3 1 A ... 4 2 B ... 5 ... ... ... In those cases, you would want to skip the top X rows and mark row x+1 as the header.
Currently, using Fabric workspaces with special characters in it (i.e. a forward slash or a space) leads to errors.
Hi, could you add the option to either trust server certificate in the TX REST API connector or specify the certificate to be trusted from the server?This setting is available in the CData REST connector, and without it my client is unable to migrate from CData REST to Enhanced TX REST:
When you have a big project with a lot of tables, it would be much easier to have the option to search and/or sort tables in the 'All Steps' pane.If you need specific tables within the packages, it can take a long time to find them. A project perspective could also be an option. However, I think having a search and/or sort feature in the Execution Package window would make it much easier.
At the moment TimeXtender creates all Fabric Items in the root of the Workspace, leading to many objects (lakehouses, fabric sql instances, notebooks, etc.) being dumped in a hard-to-manage list. As Fabric workspaces now support folders, it would be great if artifacts could be created in folders.
With the increasing complexity of data landscapes and the rise of data mesh architectures, it would be highly beneficial to introduce license-wide keystores in TimeXtender. The idea is to create a centralized key store that can be accessed and used across different project instances within the same license.Currently, encryption keys or secrets are tied to individual instances. A license-wide keystore would allow for consistent and secure management of keys across the entire organization.This feature would improve: Security, by reducing redundant key management and promoting centralized governance. Efficiency, as teams wouldn't have to duplicate keystore configurations. Scalability, especially in data mesh setups where decentralized teams still rely on shared infrastructure. Data integration, by making it easier to link and work with data from different parts of the organization using the same keystore—enabling smoother cross-domain connectivity and unified access to encrypted resources.
Currently, the Storage Management task in the Ingest Server is very limited, especially regarding the ability to remove old versions or move them to cold storage.It would be very powerful if we could move data to cold storage or archive based on defined rules—such as data older than a certain number of years, months, weeks, and so on.
Hi,Please consider adding cURL compatibility to the TimeXtender REST connector. Many devs use Postman to test API’s and it is easy to export complex API calls in a cURL format.It would be amazing if it was possible to paste the cURL into TimeXtender’s REST connector. Best,Pontus Berglund
In the Business Units section, there is an option called “When Transfer Fails: Continue with Existing Data". If this option is enabled, and the table fails to load successfully, you will not receive an error or warning notification email.The only way to notice this issue is to manually check the logs or realize that the data hasn't been updated in the reports.It would be much better if users could receive an email notification in such cases.By the way, I’m missing the option to select the product area "TimeXtender Classic/V20.10." in this idea section.Of course, this is currently only supported in Business Units.
It is already possible to clone a table structure, but the lookups, data selection rules and database schema are not cloned.
Hi there,I’d really love a quick and easy way to see which tables are being executed in the execution queue. Let’s take this example, I’m executing six tables separately: I’d like to see in which order they are being executed and which ones finished successfully. I can see which table had an error if I choose View Error of course. I know about the execution log but I think this could be much simpler and user friendly by displaying it somewhere in the queue or with a button similar to View Error.
We have some large tables source tables that need to split up for further transformation. For instance, we have a large source table containing all corporate financial transactions, that need to be divided over several divisions. To achieve more efficiency in processing, we like TX (ingest/prepare) to support the partition functionality of Fabric.https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-lakehouse-partition
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.