Recently active topics

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?

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? 

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? 

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

In TX Enhanced Connector, how do one handle fields in JSON response that has the same name?In the screen-grab below, the fields in marked in red comes multiple times but the values are different.In TX Enhanced Connector, the field always grabs the value of the first occurance of the field i have marked in red.Is there a way to grab the desired value by doing somethng like this:/json/addendumValues/addendumGroups/rows[0]/json/addendumValues/addendumGroups/rows[1]/json/addendumValues/addendumGroups/rows[2]/json/addendumValues/addendumGroups/rows[3] If not, is there a way to grab everything in blue and show in one column?I can then creat a view in BU and grab each saperately The screen grabs are broek here: Understanding and using script parameters in TimeXtender Classic | Community, so i can not fuly understand the documentation

Hi, I no longer have Timextender in the Microsoft Authenticator application on my phone (after I switched phones), so I think I need to have the MFA for my account reset. Can someone please help me with this?

Can I preserve my source field names when synchronizeing my fields?I dont want spaces and periods replaces by an underscore, my current workaround is to edit the fields manually when I use the tables in my prepare instance.  

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’?

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 all,I am looking for architectural advice on designing a future-proof multi-ERP data warehouse setup in TimeXtender.We currently have multiple ERP systems feeding into one data warehouse. The goal is to create a scalable pattern that works now, but also remains maintainable when more ERP systems are added later.The main question is around where and when to create keys, especially super natural keys / business keys, and where to perform the joins between facts and dimensions. I found some scattered articles on keys and stuff, but not really an proposed best practice in TimeXtender. I understand there are multiple ways to Rome depending on the setup/preferences/performance etc. but I reckon there would be an advices standard based on TimeXtender working and fundamentals. Example simplified architecture:DSA.ERP1.Customers- CustomerID- CustomerName- DW_SourceCode- SNK_Customer = DW_SourceCode + CustomerIDDSA.ERP1.Invoices- InvoiceID- CustomerID- Amount- DW_SourceCode- SNK_Invoice = DW_S

I have followed this guide to set-up an Incremental load on a table in BU:Incremental Loading in a Business Unit (BU) in TimeXtender Classic | CommunityHowever, during the deploy i get an error:Data source Incr LoadsValidation status: ValidMessage: OKStaging Database ODXValidation status: ValidMessage: OKTable: Incr_LoadValidation status: ValidMessage: OKIncremental LoadValidation status: ErrorMessage: Incremental load is not supported on this table.Details:Data source Incr Loads ...TimeXtender.DataManager.UserErrorExceptionIt says in the guide that: When the option is enabled and the table is deployed, TimeXtender performs the following:Initial Full Load: The system fully loads the table. Setting content of the _I Table: This table records the largest incremental field value from the given load I am attachig a video of where i get an error.What am i doing wrong?

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

Today, we've published a minor release of TimeXtender Classic (v. 26.2.1.3). It adds a small but handy usability improvement to Perspectives and fixes a few issues around authentication in the Timextender Enhanced Excel data source and the Business Central 365 data source adapter, as well as an rare issue with projects upgraded from 20.10 to Classic.New & ImprovedFrozen header row in PerspectivesWhen you work with a long list of perspectives in Prepare and Deliver, the perspective name row now stays pinned in place as you scroll - just like freezing rows in Excel. Previously the names scrolled out of view, making it easy to lose track of which perspective you were editing.FixedThe Enhanced Excel data source would fail connecting to SharePoint or OneDrive, returning a "Method not found" error tied to Azure authentication. The cause was a dependency issue that has now been fixed. When loading data from multiple tenants at the same time, the Business Central 365 adapter would sometime

I have just upgraded to TX Classic 26.0.1 and i am having issues:Why do i still see ODX when i am not suppose to see it in TX Classic I havnet set up any incremental rule, so why i am getting this error? I am getting in on a table that i am not even deploying:    

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