Prepare

Case:In the DSA I have two tables (Employee and Employee Addresses).The fist table has history in it from the source system (so no TX  history active).On the second table we have TX History active (Type II) . It is not privided by the source system. When joining the tables to a dimension, the timelines must be combined.In what way can this be achived in TX? Emp_ID RegistrationNumber ExpDate ValidFromDate ValidToDate SCD Is Current       109030 39935270430 4-7-2020 1-01-00 1-10-24 0       109030 39935270430 4-7-2029 2-10-24 31-12-99

Hi all,I'd like to start a discussion about the batch cleansing option. You can find this option in: Table Settings → Performance → Enable batch data cleansing. This option is disabled by default. I'm looking for best practices when you should use it and how to determine the best batch cleansing size.I normally enable it on big tables (5.000.000 + rows), this reduces the disk space used for logging. But in some cases it also improves performance. It can result in faster loading of a table. However, I'm always struggling determining the correct batch size. I know the answer will be ‘it depends’. But I'm trying to find some best practices for this option.For now I start at 250.000 rows for batch cleansing and increase with 250.000 rows. I write down the timings and pick the best setting. This setting depends on the number of rows and number of transformations in the table. I'm curious if there are any practices or tips and tricks for this?

Hi,I updated our TX version to the newest 6814.1 I have added many tables in TimeXtender Ingest Server with incremental load. Why do I have to change all incr. tables in "desktop app" to explicit incremental load, can't you use “Automatic” anymore? Error msg: when executing with automatic on a table with incr setup from the datasource I get this type of error “Invalid object name 'shema.table_I'.” Something I haven't done right... regards,Bjørn A.

I am deploying a project to Snowflake.On a table I get the following error:Object reference not set to an instance of an object.As read in another ticket I did a ‘Save and reload' but unfortunately that did not solve the issue.It;s on deploying the data cleansing script however it does not show me the script in the deployment log, I only see the error message. Is there an easy  way i can see what lookup column is causing the issue ? 

Hi!Getting this error when I try to open the Dev instance. Test and Prod is OK.I could open an earlier version of the project but after I made some changes and tried to save and deploy, I first got a warning that said that this was not the latest version. When I chose to save anyway, I got the same error. Is there some way to “force save” to make this earlier version the latest one and get rid of the error?

Hi,I was wondering  if it's possible to use multiple ODX instances for different enviroments (DEV/ACC/PRD).I know that at 20.10 you could only use a single ODX as after multiple enviroment transfer all mapping to ODX would be lost when using multiple ODX instances Is this still the case? Is this issue solved in next-gen?  

This is the first time that I see it: What it is?

I am deploying a project to Snowflake and see a lof of tables are skipped.Then we get the messages below (as an example) Apparantly the tales are skipped as key stores / supernatural keys  are not supported .Is this a feature to become available on short notice as our entire datawarehouse uses these?Besides that, is there a way I can see what any other unsupported feautures we have?

HiI have an issue whereby I get the following message when running the ‘Report / Errors’ menu option in one of my data areas. However, when I click OK I do not get any further information to help me identify the issue. Please advise what I need to do to troubleshoot this further.TimeXtender Data Integration version 6745.1Thanks

Dear all,When synchronizing the mdw with the odx through right mouse click on the odx and selecting “Synchronize (...)”, the error messages as attached always show up. “Synchronize with Remapping (...)” only leads to complete removal of the field mappings in the subject tables.As there are other ways to sync the mdw with the odx, it’s still possible to work with the subject tables in the mdw. Nevertheless i wonder what causes the error messages and would like to eliminate them along with the risk of having to redo all work on the tables in a later stage.

Hi,We are migratring i customer from version 20 to 21. In version 20 they use a system variable to limit the amount of data loaded into certain DSA tables in the development environment.is there any way to accomplish this in V21 - setting a variable that only affects one instance?BRAnders

I have a table which loads incremental in the ODXIn the datawarehouse the table is on Automatic and in simple mode.The setting to keep fields up to date is off.Will the incremental records from the ODX do inserts and updates, but update only on the fields with no transformations/lookups or will no updates be made at all when an updated existing record is retrieved from the source?As we don’t have any transformations in that part I was hoping we could skip the RAW table and that records get updated if newer versions come by.The documentation only mentions what the ‘keeping fields up to date’  does for lookup fields , transformation fields and so on, not what exactly happens when that box is not checked 

I am working with a solution that delivers 3 end pointsThe first end-pointhttps://data.mysystem.com/86fb92b5-ae9cData from this end-point is aleady in the DVHid is the unique id for the attached document:{ "Type": "images", "fileName": "some_file_name.pdf", "id": "3de1cef70101", "mimeType": "application/pdf" }The second end-pointTo reterive the document the endpoint ishttps://data.mysystem.com/attachment/<id>This gives the output as ANSI%PDF-1.7%����1 0 obj<</Type/Catalog/P

Hi there. I‘m having trouble with a three tables in my project. What they have in common is that they are tables that I created specifically (that is not with a mapping to ODX) and populate with a Custom Table Insert.The problem seems very similar to this one: Data Clensing results in time out | Community (timextender.com)For example, I deployed and executed one of my tables yesterday evening (not a large one, about 20.000 rows). And these are the results:

HelloDon’t know if this is a bug or a deliberate choice, but when you want to add a transformation on a field in a table that was opened in ‘new window (CTRL+W shortcut), then the section for Field Transformation is not available.I have included a picture.When your table is in the DSA/MDW node and you do right-mouse click, then you can choose Field Transformation.When your table is in a separate window, then this particular option is missing

Dear Support,I have encountered a strange phenomenon with the history settings and need urgent support.Situation:Records which were once flag as new records from the ERP system show up as SCD Is Current is 0. These orders were canceled in the ERP as a next step and flagged correctly in the history raw table table as a type II change (which is correct). However, they do not get inserted into the valid table as new record. Today we realized even more records are missing in the valid table. TX Version: 20.10.40.64.Please advise on how to proceed. This is causing us major issues in our month end closing reporting. It used to be fine and we only experienced it this week. Thank you.Oscar

Hi guys,Somehow I am unable to create a job for my semantic models or my datawarehouse/ data area. I can’t select the model when I’m trying to add a new job.  

Good morningI am deploying a specific table with history (mostly type2) to Snowflake.However in the generated script the semicolumn is not placed correctly (after the ; some additional ‘and’ clauses are added). This results in an error creating the data cleansing procedure. I added the script in the attachment.Can you please have a look.

This problem arrived after the issue with SNK is resolved. I am not sure if the two cases are related in any way but that was the last change made in TX.I am trying to figure out why data clensing is taking so much time. It ultimately ends in time out:Error during Data Processing for Table: DSA.FACT_TABLE_A at: DSAExecution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.Operation cancelled by user.Warning: Null value is eliminated by an aggregate or other SET operation.The wait operation timed outStored Procedure: [DSA].[usp_FACTABLE_Clean]Parameters:@version = 2177Line number: 0Details:SQL Server: 'TEST-SQL-SERVER'SQL Error Number: -2The total number of rows in ODX are 9

Hi Team,We have a data provider for which we need to connect to MySQL. We want to incrementally bring data from the source, but the problem is that all the columns in the table are of the string data type. This prevents us from setting any incremental logic on the date column, which is currently stored as a VARCHAR(8). I tried casting the column to a date format, which works in the query tool, but when I try to add the query table, the option is disabled. I am using Mysql 5.1 client data source.Could you please suggest how I can achieve this?

Is it possble to create a table based on CTE in timextender, or how would you do it? 

Hi everyone, back again with another issue.  We have now setup our ODX with storage account as storage layer. refreshing it sometimes breaks though. I'm getting 404 error, path can't be found. This happens with transfer all option. When I run the set of tables one by one, everything seems to be fine. I saw 1 more post like this for oracle, where the connector got updated. We're using an older version so I suppose can update the cdata connector and try again. However: the weird thing is that this also happens with ODX to DSA. Any clue how this is possible? Path does not exist, but I can find it in the storage account. 

Dear all, We have tx instaled on Azure and on premise. The version we are using is 20.10.52.64. how is it possible that on the onpremise we can use the custom data selection rule and on Azure this screen is not appearing in the DSA?The issue we are facing is that we want to limit that data we want to load in the odx when the raw table is being executed. Therefore we want to set a customized data selection tule on the mappings.Why this option is not in Azure but it is there on the on premise?We want to load / keep all data in the odx server and make a data selection rule in the DSA..Imagine we are migrating from on premise and we want to show only 15 months of data instead of  10 years. Only if the customer is asking for it we will load it.  This is working on the on premise perfectly.Now that we are migrating from on premise to azure we are missing the most used data selection rule. And the advised work around

See the screenshot. in the mapping you can see all odx sources with the correct name (ODX(BEBOO1): bronze.blueyonder_wms.DSCMST. However when I go the the field mapping The name for each source is now called local host????For trouble shooting purposes when missing a mapping. It will create a work around for us, because we have to click on the table to see all mappings on the right side then you have to go on be by one.  why the name have changed on a the field mapping? possible to have a fix for this? 

Hi all, I'm looking at making the right keys in our database model. I've been reading some topics on the forum but haven't found a shared opinion on the best practice. Super natural keys Advantage: Easy to use.   Disadvantage Huge performance impact. According to some topics reloads can increase in time from 3 till 30 minutes.  Their are relations in reloading the tables in the correct sequence. TX will calculate this sequence, however their is an increased change of circle references. Hashed Keys Advantage: Easy to use.  Should be faster than SNK. It doesn't need a look up to the keystore.  Disadvantage: Change on duplication of keyus is limited to a minimum Source: https://stackoverflow.com/questions/297960/has