Unanswered questions

Hiwhen I try to test the connection I get this error message:Exception Type: ODX.Model.Exceptions.DataSourceExceptionMessage: The connection 'EXT_EXACT_NL' uses a version of the provider that is not compatible with this version of TimeXtender Ingest Service. Upgrade the data source connection in the Portal and try again.But I cannot upgrade the provider. Has anyone the same issue?

I’ve got a customer with approx. 200 orchestration packages in TDP 26.3.I need to update retry settings for the vast majority of these packages … manually, that’ll take close to forever.We should have a bulk-update feature based on the existing multi-select feature, which currently only works for deletions:  enable/disable retries and, if enable, set the retry interval to e.g. 60 seconds for all selected packages.Notifications are also relevant from a bulk-update perspective.

Hello,My Azure SQL ERP source does not have a lastmodified datetimestamp on the tables. We’re investigating the options to enable change data capture (CDC) or change tracking (CT) on the biggest tables.How would I proceed with further setting this up with TimeXtender? I can't find any related manuals, blogs or sources for this.Thanks in advance! 

I have just checked the excution on a clients Orchestration site and it seems to have dropped history and I am not sure if scheduled executions are happening. Is there an issue with your Orchestration tool?I just had a look at the history package in a production process and process map that runs every hour and the history on that item shows it executing this morning at 8:57 (over 3 hours ago) and then before that August 5th! It has definitely been running consistently, so I am not sure what has happened that you no longer have history why and the process executions do not appear to be taking place as scheduled.  

Hi,We have a Contact Centre based on MS Teams (quite a new solution for us) and now they want to start gathering data and follow up the number of calls per operator and such. The only option that the service provider provides for us to get a hold on that data is to set up an Azure SQL database that they can send the data into.Since we have all our other databases locally, I was looking into how to set up a connection to such a database in the portal but didn’t find any specific option for that. Should I just use a “regular” SQL connection with the Azure server name and database name with Entra authentication or how do I go about this?Anyone who has done this before?Any information is appreciated. :)

Hello, I have submitted the following question to TimeXtender support. I wanted to post the question here to see if there are other people that have build or are trying a similar solution to monitor the executions. We are currently implementing a monitoring and orchestration framework based on the TimeXtender Meta Collection data.According to the TimeXtender documentation, Meta Collection metadata is exported once every 24 hours to the data lake. We have also observed this behavior in our environment. The documentation states that metadata is exported once every 24 hours and the exported files overwrite the previous export. Our use caseWe are using the following Meta Collection entities to monitor the execution status of our data platform:Ingest_ExecutionTasks Ingest_ExecutionLogs Ingest_Tasks Ingest_TaskVersions Ingest_DataSourceVersionsThe objective is to determine:Which tasks were executed Whether the execution was successful Whether warnings or errors occurred Which datasource and

I have encountered an issue after upgrading the TX Enhanced REST Connector from version 1.10.2 to version 1.15.0.The problem did not occur when using version 1.10.2.Our environment consists of a single TimeXtender server hosting both DEV and PROD environments.Since upgrading to version 1.15.0, i am no longer able to create new Data Sorce using TX Enhanced REST Connector v. 1.15.0 in PROD (DEV works fine). However, creating connections with version 1.10.2 continues to work without any issues in both PROD and DEVI am a bit reluctuent to re-/uninstall 1.15.0 because i have a datasource in DEV with 15 endpoints that use 1.15.0. 

I am experiencing an issue that I have encountered a few times before in TimeXtender Classic. Previously, the problem was resolved either by restarting TimeXtender or by recreating the affected tables. However, this time I have spent a few hours troubleshooting without success.I have two tables in ODX (BU) that need to be copied to corresponding tables in DSA.The situation is as follows:The source tables in ODX/BU are populated with data. The tables are correctly mapped in DSA. When I perform a Deploy (or Execute and Deploy), the tables are generated in DSA as expected. However, no data is transferred to the DSA tables. The tables are created, but they remain empty. Neither the BU tables nor the DSA tables are guarded on Deploy or Execution.I have verified the mappings and deployment configuration, but I have not been able to identify the cause of the issue.Have you seen this behavior before, or are there any logs or settings you would recommend checking?

Incremental Load Strategy for Data Warehouse Layer (Prepare Views → DW Hi everyone,We’re working on a project for a TPA that provides property and casualty services to smaller P&C companies. The architecture connects to multiple disparate sources that ultimately feed into a standardized data warehouse.Here’s our current setup:Architecture:We’re creating a raw schema in Prepare for each data source, then using views to abstract the transformation logic. The DW maps from those views. So the flow is: Source → Ingest → Prepare (raw) → Prepare (views) → DW.What’s working:Incremental loads are running well from Source to Ingest and from Ingest to Prepare raw — no issues there.The challenge:The DW layer currently runs as a full load every time. We’re moving roughly 200M rows per company. Load times are about 1:45 hours, which is manageable, but we’d like to bring that down with incremental loads. It would also reduce the vCore demand — we’re currently on 8 vCores Premium Series with memor

Hi,Is it possible to connect to a Microsoft Fabric OneLake using a specific data source in TimeXtender version 20.10.74.64?We have tried using a SQL Database connection, but are encountering authentication errors, as the connection depends on Microsoft Entra ID authentication.

Hello,I have a TimeXtender REST data source where some loading tasks sometimes keep running infinitely. This causes issues on my pipelines where I don’t get a message/monitor from, as it doesn't error.I see that in my REST data source settings I don't have a command timeout like for SQL data sources. Is there a way I can put a command timeout? Would it be this Timeout setting in O&DQ?  

A JSON response looks like this [{"ref": 123456,"dim_1": "A","dim_2": "B","peroid": 202601},{"ref": 5E+20242959,"dim_1": "A","dim_2": "B","period": 202602}]The second ref (5E+20242959) is a problem - its neither STRING nor an INT.Ref is defined as NVARCHAR in BU, but as you can see the value is not between “”.I have tried the following approaches under, still i get the same errorInput string '5E+20242959' is not a valid number. Path '[56935]['ref.53e92a42-b13c-4062-87b4-6bd5a89547b1.1992753']', line 1, position 36741783.How do i solve this?Here are the approaches i have tried:Omitting Ref in Table FlattningIn table flattning, i have left it out. I have the other three values, but still landing returns an error:Defining the value as NULL in table flattningField transformationCondition on column ref in BUI have defined the following condition on the column, still i get the same errorCASE WHEN [ref] LIKE '5E+%' THEN NULL ELSE [ref]ENDScript ActionsI have created a script th

I run into this error while loadning csv-files from our s3 bucket.The issue is that the number of fields differs from time to time. We would like to ignore that and read these fields if they exists and otherwise not.Is there a way to do this or is this just an exception in CsvHelper-lib that isnt accessible for me to configure? The error:Executing table [csv].[VOF_UTF_Planeradebesok__aggregated]:failed with error:CsvHelper.MissingFieldException: Field with name 'Planerat besök - konfidentiellt' does not exist. You can ignore missing fields by setting MissingFieldFound to null.IReader state:   ColumnCount: 21   CurrentIndex: -1   HeaderRecord:["Användare - ID2","Användare - personnummer","Användare - profession","Avbruten/inställd","Brukare - ID2","Brukare - personnummer","Planerad resurs - namn","Planerat besök - dubbelbemanning","Planerat besök - ej utfört (anledning)","Planerat besök - sluttid","Planerat besök - starttid","Planerat besök - typ av brukare","Planerat besök - utfört","P

Hi,I have created an endpoint in my TimeXtender OData Data Source (provider version 1.4.1). I am currently using TimeXtender version 20.10.74.64.The endpoint supports incremental loading by applying a filter such as lastModifiedDateTime gt .... For the input variables, I use a Dynamic Value SQL query.We have three separate environments,Development, Test, and Production, hosted on different servers. The current environment is available through the TimeXtender variable vEnvironment.Is it possible to use a dynamic variable, such as vEnvironment, in the connection string to select the appropriate server?For example something like this?  Server = $(vEnvironment);Initial Catalog = ODX;Persist Security Info = ...  

Hi,I have two Execution Package chains ("Run Packages...") configured as follows:Chain 1:1a) Revenue 1b) Revenue Trigger 1c) Morning 1d) Morning TriggerChain 2:2a) Store 2b) Store TriggerThe requirement is that 2a) Store and 2b) Store Trigger must not run concurrently with 1c) Morning or 1d) Morning Trigger.I have configured this restriction in the Concurrent Packages section under Edit Execution Package. However, the restriction does not currently seem to be enforced as expected.Could this be because 1a) Revenue and 1b) Revenue Trigger are allowed to run concurrently with 2a) Store and 2b) Store Trigger?In other words, when Execution Packages are part of a chain, do the concurrency restrictions need to be configured for every package in the chain? Or should the restriction between 1c/1d and 2a/2b be sufficient to prevent those specific packages from running at the same time?

Hi all,We have regular ODX loads that periodically fail because of schema changes in Business Central (e.g. a new column added). The fix is straightforward: sync the metadata and rerun.I'm considering just adding the metadata sync step before every ODX load to avoid these failures altogether. Is there any downside to syncing every time? Could it cause unexpected behavior, longer run times (probably only a few minutes?), or anything else worth watching for?My instinct is that it's still better than having a load fail over a single new column, but wanted to check if this should be standard practice or if there's a reason this isn't already standard practice.Interested to hear your thoughts.