Recently active topics

Hi, I’ve got a Prooblem with a Datefield. Within the datasource it is defined as DateTime Offset. The source is connected via Rest API (ODATA) and I use table flattening before importing it into ODX. Alle Date fields arrive as DateTime2 when loading MetaData except this one field. It is imported as nvarchar. When looking into it, ist looks like a Boolean. True ist set when the field is filled. The rest is just empty.I’ve already checked if this field has the same datatype as all of the other fields- the set up ist the same.When I try to set a default value within the table flattening, the source isn’t recognized anymore and I have to reconnect. When I try override Data Types  I get the error “... Exception occurred when converting value '' for column name 'd-Istmenge_Enddatum' from type 'String' (precision:-1, scale:-1) to type 'DateTime' ...” The same error occurs when I try converting it in stage with set custom transformation to replace empty field with a default date. Maybe some on

Hello,After Snowflake enabled behavior change bundle 2026_04 on our production account, our execution packages began failing. TimeXtender generates the "SCD Surrogate Hash Key" column as a virtual (computed) column with a NOT NULL constraint.As of bundle 2026_04, Snowflake rejects NOT NULL/CHECK constraints on virtual columns at DDL time, so the CREATE TABLE statement for the TX-generated temporary staging table now fails. The same project ran fine until the bundle was enabled, and runs fine again after we temporarily disabled the bundle.The failures occur only on tables that have History (SCD) settings enabled. Tables without history are unaffected, which is consistent with the surrogate hash key being generated specifically for the history/SCD code path.Environment- TimeXtender Data Integration, product/portal version: 7158.1- Data storage: SnowflakeError messageJavaScript execution error: Uncaught Execution of multiple statements failed on statement "CREATE TABLE ...#<temp>...

Microsoft Dataverse is the underlying data platform for Dynamics 365 applications, including Sales, Customer Service, and other CRM modules. When you connect to Dataverse, you get direct access to CRM entities such as accounts, contacts, leads, and opportunities. This guide walks through setting up that connection using the TimeXtender Classic OData provider with OAuth 2.0 client credentials authentication.This guide uses client credentials (app-only) authentication. No user account is involved at runtime — access is granted to a registered Azure AD application, which is then mapped to a Dataverse application user. This is the recommended approach for service integrations.Prerequisites Register an Azure AD Application Register the app in Azure Portal Grant Dataverse API permissions Create a client secret Configure an application user in Dataverse Create the OData Data Source in TimeXtender Classic Add a new OData data source Set the base URL Configure OAuth 2.0 authentication Te

SymptomsError while executing TDI transfer task for TimeXtender Excel data source. Error messages received:Errors:Input string was not in a correct format.The given value of type String from the data source cannot be converted to type nvarchar of the specified target column.CauseThese errors occur due to the incorrect format of the input string when the data types are inferred from the Excel file. This issue can arise if the "number of rows to infer data types" setting is not configured correctly.ResolutionChange the "number of rows to infer data types" setting to 0 (i.e., scan all rows to determine data types).   Execute the import metadata task for the data source in TDI desktop. Execute the transfer task for the data source in TDI desktop.If the issue persists:Ensure that no data type overrides or changes are applied to the data source in TimeXtender Data Integration. Confirm that the data source is pointing to the correct file. Verify the data types in the data source explorer for

SymptomsWhen setting up mail notifications in the Process Orchestration tool, you notice that administrators receive failure notifications automatically, but there is no clear option to configure notifications for successful executions at higher object levels such as Object Groups or Processes. Attempts to use the "email on completion" feature are limited to the lowest level objects.CauseThe Process Orchestration tool currently lacks built-in support for sending success mail notifications at higher object levels (Object Groups or Processes).ResolutionUse the Email Parameter for Success Notifications on the Package level: You can start a process with the email parameter on the last package in the process sequence or object group to receive notifications upon completion. Add a dedicated email-sending Package at the end of your Object Group or Process sequences: Configure it to send on Success. Submit a Product Idea for Enhanced Notification Features: If you require success notification

SymptomsAn "Out of Memory" error is received while running a TDI package in TimeXtender Orchestration. The package may have completed successfully, but an following error is received in Orchestration.Error: Exception of type 'System.OutOfMemoryException' was thrown.CauseThe issue is typically caused by a process stuck in the "running" state, which leads to memory exhaustion on the application VM. When multiple scheduled packages or processes run concurrently and overlap, the combined memory load can exceed the available resources.Resolution Check TimeXtender Orchestration Execution History Open TimeXtender Orchestration and review the execution history to identify any packages or processes still showing a "running" state. Look for executions with start times that correspond to when the error occurred. Check for Updates Ensure that you are using the latest version of TimeXtender. Check the release notes for any relevant fixes related to execution visibility and memory issues. Monit

SymptomsHigh CPU consumption by the TimeXtender repository database. Error Message received:Error: High CPU consumption by repository database.CauseHigh CPU consumption is can be caused by indexing on the repository tables.ResolutionTo address the high CPU consumption, you can add or modify indexes in the repository tables. However, there are a few considerations to keep in mind:Adding or modifying indexes may improve execution and reduce CPU consumption. The changes might be overwritten every time the table is deployed. There is a risk that the changes could cause errors when using or running the table or project.Warning: Always backup your TimeXtender Classic repository before making these types of changes. We do not recommend altering the TimeXtender Classic repository database manually, as it can lead to unforeseen issues.Steps to add a non-clustered index:Backup your databases before making any changes to avoid issues if the changes do not work as expected. Execute the following S

SymptomsError while executing PowerBI Premium endpoint in a Deliver instance. The error message received is:Error: A connection could not be made to the data source with the Name of 'MDW'.DM_GWPipeline_Gateway_DataSourceAccessError -> A connection could not be made to the data source with the Name of 'MDW'.A task was canceled.. The exception was raised by the IDbCommand interface.A connection could not be made to the data source with the Name of 'MDW'.CauseThe issue is related to the Power BI gateway used to connect to the data source rather than TimeXtender.ResolutionInvestigate and fix the gateway configuration used to connect to the data source. Ensure that the gateway is properly set up and operational.Reference Ticket32083

We are getting a bad request error when we are using the timextender odata data source.  When we use the endpoints that we previously selected during metadata discovery, they still work normally. So why is the discovery metadata at the moment not working (it worked the first time). Thank you in advance!   

Hi,In one of my CData connections i have a RSD file for an endpoint with the follwing code for startPeriod and endPeriod <api:set attr="out.TodayDate" value="[dummy | CURRENT_DATE()]"/><api:set attr="out.StartPeriodYear" value="[out.TodayDate | year()]"/><api:set attr="out.StartPeriod" value="[out.StartPeriodYear | insert(4,01)]"/><api:set attr="out.EndPeriod" value="[out.StartPeriodYear | insert(4,12)]"/> This i refer to in POST statement in { "fromValue": "{startPeriod}", "restrictionType": ">=", "columnName": "period", "relDateCrit": "" }, { "fromValue": "{endPeriod}", "restrictionType": "<=", "columnName": "period", "relDateCrit": "" }Is this the correct way - instead of hard coding?  Name Value todayDate CURRENT_DATE() startPeriodYear year(todayDate) startPeriod insert(startPeriodYear, 4, '01') endPeriod insert(startPeriodYear, 4, '12')  And then, in the

This release strengthens two parts of the TimeXtender AI offering: the MCP Server that securely connects TimeXtender to your data, and Xpilot Analytics, the conversational analytics experience built on top of it. The MCP Server work makes secure on-premise deployment work end-to-end and returns more trustworthy query results. The Xpilot Analytics work makes the chat experience accurate, readable, and correctly isolated per workspace. TimeXtender MCP ServerIn shortThis update makes secure (HTTPS) deployment work end-to-end, returns trustworthy query results, and keeps the service running through reboots. Previously, enabling HTTPS was blocked by a series of separate problems; an administrator can now stand the server up over HTTPS, on a standard port, with the cloud relay, and change or revert that setup later, entirely from the configurator without editing files by hand. Before and after Area Before In 2.0.1 Saving an HTTPS setup Saving an HTTPS configu

Use deliver instance endpoint name variable, in combination with data selection rules, to perform different data selections for different endpoints in the same deliver instance. This way, each department can get their own endpoint with a subset of data relevant to their division. This can help improve load performance, report performance and help manage costs by keeping individual models smaller. This also helps avoid creating multiple deliver instances for different departments.How to filter use data selection rules for specific endpointsCreate a Deliver instance with multiple endpoints Close all instances in TimeXtender Data Integration and then open the Deliver instance in TimeXtender Data Integration and click Tools > Instance Variables. Then click Add, and add an instance variable of type Destination Scope, setting the Value Filter to Endpoint and setting the Value to Name. Then click OK and close. Right-click the table you would like to create filter on and select Add Data S

I believe I have read the documentation, in case I missed something. My bad. Im trying to load csv files from the root of a S3 bucket. The 'test connection’ in the portal turns green but when trying to synchronize in timextender it tells me I have to enter a value for ‘path’.I have tried these so far: /.mybucketname/inbound/s3://mybucketname/inbound/But timextender keeps throwing errors saying the directory does not exist. I can succesfully connect to it and download the csv's via Python so Im quite sure the setup is correct.  Does anyone know what to fill in for ‘path’?

OverviewAssigning privileges to Entra ID groups is a good way to ensure access to TimeXtender Data Platform is maintained in a single location in the organization.This requires single sign-on to be registered.One-paragraph explanation: an Entra-backed role in TDP grants its privileges to anyone who is a member of a chosen Entra security group, with no need to maintain membership in two systems. See User Management in TDP for general role behaviour. Note: prerequisite is that the customer has SSO with Azure AD already configured — link back to article 1930. Creating a role backed by an Entra groupOpen Settings → User permissions → Roles in TDP. Click Create role.   Choose Group type: Entra group. Click Browse to open the picker. The picker authenticates the admin via a Microsoft popup (using the existing SSO session) and lists the Entra groups in the tenant. Search by name and select the group. Assign privileges (Workspace / Datasets / Rules / Process Maps / etc.) — see User Management

After upgrading to Ingest 7313.1 I updated my REST API provider version to 12.1.0.0. Now some of my REST endpoints have started failing.Running “Import metadata” works fine, but when it tries to extract values from the JSON, it fails with errors like: Failed to execute callback for endpoint 'Get Charge Points':Column 'data_id' does not belong to table charge-points.System.ArgumentException: Column 'data_id' does not belong to table charge-points. But it should be able to parse it.The structure of the JSON is like this (just showing top of file):{  "data": [    {      "id": 1096237,      "teamId": 449574, Any tips? 

I have en endpint with multiple parameters:CaseHandling/External/Cases/GetCases?exportFields=CaseID&exportFields=Closed&exportFields=Position&exportFields=ProjectLevel&exportFields=Anonymous&Key is always exportFields Values are differentIn CData i have no issues getting values in the columns.In TX Enhanced Connection, when i define multiple parametes with key-anme exportFields and different value, only the last is shown: This is how i have defined in TX Endpoint I have tried the whole endoint in Path, which gived empty table  

 Changes in TDP 26.2Previously, syncing a TimeXtender Data Integration (TDI) Data Provider created one package per environment per unique TDI package. A workspace with 18 unique TDI packages across three environments (Development, Testing, Production) would result in 54 package entries in Orchestration & Data Quality (ODQ). This caused confusion and added maintenance overhead.With this release, sync deduplicates packages by their unique package GUID. The same TDI package, regardless of how many environments it appears in, is now represented by a single entry in ODQ. The correct environment (and its associated TDI instance) is resolved at execution time.Before: 18 packages × 3 environments = 54 ODQ package entriesAfter: 18 packages × 1 = 18 ODQ package entries  TDI Data Provider — TDP OnlyThe TDI Data Provider configuration dialog is only available in the TimeXtender Data Platform (TDP) web interface.If you open a TDI Data Provider in the desktop application, you will see an "Open i

Installed data integration and ingest services 7361.1 I cannot start the Timextender execution services also not after I download the config file and replaced it

See the below screenshot.  I’ve installed Classic 26.2.1.1 and if I just put in the License Key, it tells me I need to have an activation file.  Never had to do this with 20.10.Went to download the activation file, and there is not an option for v26.  If I try a 20.10 activation file, it says it’s the incorrect version.Using the Alithya partner key starting with: 3c67…. 

Today, we've published a minor release of TimeXtender Data Integration (v. 7387.1) that includes two fixes, one for an Execution Service startup issue introduced in 7376.1 and one for Snowflake deployments using history.We recommend that you install this hotfix if you’re using the Execution Service or if you’re using history on Prepare tables on Snowflake storage. There are no changes to the Ingest Service and it remains at version 7376.1.FixedAfter upgrading to 7376.1, the Execution Service could fail to start with a Windows service error (‘Error 1067: The process terminated unexpectedly’). The cause was a token refresh issue that has been resolved. Deploying a table with history enabled to a Prepare instance on Snowflake instance would fail during the raw table structure step. This affected tables using SCD Type I regardless of column types or hashing algorithm configuration.

Hello,Since about a month ago, I am not able to connect to Sharepoint Lists anymore. When I test the connection, I get the error message as seen in the image below. Authentication wise, I use Auth scheme AzureAD end the Sharepoint edition is Sharepoint Online. I do not use OAuth and I am able to login to the Sharepoint site with the account I use. Is anyone experiencing the same issue or does someone know how this can be solved? 

Hi,We are currently using TX 20.10.80.64 in combination with TX Data Enrichment. TX DE is exposed as a source in the ODX.When we modify a Custom SQL query via Table Designer → Actions → Source, it appears that the data is not refreshed in Home afterwards. Old columns or outdated row counts are still displayed.We have configured primary keys (PKs) to define the columns in the Table Designer.Therefore, we suspect that when we call the ODX source TX DE within TX 20.10.80, the data is not being refreshed from TX DE.What are we doing wrong?

SymptomsError: The TimeXtender Execution Service 7376.1 service terminated unexpectedly.Error: Windows could not start the TimeXtender Execution Service 7376.1 service on Local Computer.Error 1067: The process terminated unexpectedly.CauseBug in TDI 7376.1 execution service which will be fixed in the upcoming TDI version The issue was a mismatch between some DLL versions in the configuration file, which would silently cause the authentication to not automatically refresh, and hence cause the service to fail when the token expired.ResolutionLocate the TimeXtender.Job.Execution.exe.config file in "C:\Program Files\TimeXtender\TimeXtender Data Integration 7376.1\TimeXtender.Job.Execution.exe.config" Unzip the attached zip file, and replace the TimeXtender.Job.Execution.exe.config file with the attached file Run the execution service config and click save Restart the execution service