TimeXtender Desktop Q&A

I have a transaction table in odx with the following fields (simplified)Key,Value, transactiondate Example100, V100, 2023-01-01100, V100A,2023-01-31 09100, V100B,2023-01-31 10 Each day there are multiple transactions added , of course with  another transaction date.Note in the example I  have only shown the date part (not hours, minutes, seconds) What I need is a table with the latest update in DSAI created the same table. Set primary key to KEY and added an incremental selection rule on transactiondate . Added history settings to update the Value and transaction date based on the keyWhere it goes wrong is if we get in one day multiple transactions 100, V100A,2023-01-31 09100, V100B,2023-01-31 10I traced down the cleansing procedure and Tx detects that there are twice the same key. So far so good.Next it puts the ID of  the latest transcation into <table>_L  and only processes the ID’s that ar not in <table>_LThe result is that I get  100, V100A,2023-01-31 09 which is incor

Dear Community,I like to build my data estates with supernatural keys but in lager datasets the data cleansing starts to take very, very long. Do you happen to have the same issues? Is there a way to make the supernatural keys load faster? Even with incremental loading it begins to be super slow:I've ran a test on 435,397 records. This is on a Azure SQL with 10 vCores1. is a full load on the table with 7 supernatural keys.2. is a full load on the same table without the supernatural keys.1 has data cleansing of 1 second. 2 has a data cleansing of 104 seconds!Second I've done a test on the same tables but now incremental loads:1. incremental load with 7 supernatural keys2. incremental load without supernatural keys1 has a data cleansing time 1,6 seconds and 2 a data cleansing of a whopping 129 seconds!I'm not so sure I want to keep using the supernatural keys. What do you guys do? Take care= Daniel

Hello,I'm working on a project (new license model) where we want to use the Azure Data Factory for Data Movement. I've installed the TX 6143.1 version but got the message “Data Factory source is out of date”. Looking at the release notes this version of TX doesn't support ADF Data Movement at the moment:“Warning: The new version does not support the data source providers that move data using Azure Data Factory (e.g. "Azure Data Factory - SQL Server (11.0.0.0) 64 bit").”I've decided to downgrade to TX version 6117 but I'm getting the message as shown below (screenshot). It looks like there is another Repository from both installations.How can I solve this and remove one of the repositories. I want to use the ADF Movement so the repository for version 6117 is needed.Thanks in advance!VinceVicta B.V.

Hi, I have a list that maps product_codes to product_ID's.What I would like to create is a Key Store that, when fed a product_code from the list, produces the same product_ID and when fed a new code (so not in list) produces a supernatural_key as usual. Is it possible to force the keystore to create the ID's as shown above? 

Hi,I have the following setup in my Dev/Prod environments:ODX Shared, all on my live environment DSA / MDW separate for each environmentA daily refresh starts with ODX and on success moves to DSA. So far so good.On the ODX step, there's a Usage condition for Environment (project variable) = ‘Prod’.I added this because I don't want to start 2 refreshes of the same ODX from both Prod&Dev.However, the Dev environment goes straight into the DSA refresh because the ODX ‘starts’ and finishes instantly. Meaning the DSA only gets a few thousand rows from the still-refreshing ODX (largest table has 2000 rows where I'd expect 2million+).Is my assumption correct in using the Usage condition? How can I use the same Execution packages for Dev/Prod while still using the same ODX ?Thanks for any help!

The setup phases are confusing, can anyone explain where exactly they run? The Pre script runs previously to insert the records in the valid table, it’s correct in my case, but the post script that must be run after the records inset, doesn’t run.My script it’s: 

When adding a job I see a checkbox 'Hide objects that can't be added’.  After I uncheck this checkbox I see that my execution schedules for both the data warehouse and the semantic layer can't be added to the job. Could you please tell me what might be causing this?And in general I'd like to know when an object can't be added to a job.

Hi, I am trying out the new TimeXtender version and just set up my environment. Now when I use a transfer task I receive the following error: System.AggregateException: One or more errors occurred. ---> System.Exception: Error validating data storage version. The version is empty   at DataStorageEngine.SQL.SQLHelper.GetDataStorageVersion(SqlCommand command)   at DataStorageEngine.SQL.SQLStorageEngine.ValidateStorage(SqlCommand command, Boolean tryTakeOwnership, Boolean throwIfInvalidOwner)   at DataStorageEngine.SQL.SQLStorageEngine.TransferData(IDataSourceEngine dataSourceEngine, ExecutionTaskModel taskModel, List`1 tableModels, Boolean forceFullLoad, SecurityExecutionModel securityExecutionModel)   at ExecutionEngine.Action.StandardAction.Execute()   at ExecutionEngine.Action.ExecutionAction.<.ctor>b__9_0()   at System.Threading.Tasks.Task.Execute()   --- End of inner exception stack trace ------> (Inner Exception #0) System.Exception: Error validating data storage versio

I'm reading XML files from a folder using cdata XML provider. This is working fine and using incremental loading also works. The issue I'm having is that there is an attribute defined in my rsd file that is not always present in the XML files. When ODX starts reading the folder and the first file it parses doesn't have this field it skips the field for all following files. Similarly if the first file does have the attribute all the rest is parsed ok. Is this a bug or is there a setting I'm not aware of? Or maybe a definition in rds that could help?

It would be great if in the Multi Environment Transfer Step it would be possible to refresh the Data source as well.Currently I have to add new tables in Dev en Prod environment on a weekly basis (chaning ERP systems).It happens that a table is added in Dev, but that table is not yet avialable in Prod. So when I transfer the project and deploy I do not get a warning that the table does not exists. So after deployment, the schedule will run in morning and it will fail on the missing table.Only after a refresh of the Data source the project recognises the missing table and gives a warning. Now I have to in Dev transfer project and deploy to Prod and then open the Prod environment itself to refresh data source in order to check if all tables are available or not.

Does anyone know whether or not the rules you put in the over ride data types area are applied sequentially like they would be in a SQL case statement (i.e. once a field evaluates to TRUE it ignores the subsequent logic)?

I would like to run a job only if the number of records in the raw table it’s diferent of the number of records in the valid table wit a condition.How can I do it?

Hi, We are running on MS SQL Server 2019, but all of the DBs created from TX  are still on compatibility level 120. Will changing the compatibility_level impact the TX solution?   br,Sturla

Hi Guys,  I had an ODX connection to a SAP ByDesign instance that suddenly stopped at the end of last week and spit out the below error log. I am looking for any ideas on the direction to go. From how I am reading the error, I am assuming its originating at the ByDesign end, and I need to find a location to whitelist DiscoveryHub. (doesn't explain why it was working then suddenly not working without any other changes).   Thanks for any help.     If you need assistance, please submit this with your ticket. Service request failed: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> rds190C.vX: HTTP protocol error. 401 Unauthorized. ---> rds190C.vX: HTTP protocol error. 401 Unauthorized. ---> rds190C.IX: HTTP protocol error. 401 Unauthorized.at rds190C.ERZ.q(String , String , FR , ERk , String , Boolean , String )at rds190C.ERZ.o(Boolean )at rds190C.FZZ.K(WDn )at rds190C.WaZ.q(Wg , WDt )at rds190C.WaZ.A(Wg , Wan )--- End of

Data in the context of GDPR or sensitive to stock markets require attention in the datawarehouse with regard to securing the data, in some cases this also to the people developing the datawarehouse. We have been looking into several options, and now plan to do a proof of concept on transparent data encryption.   Anybody experience with securing sensitive data in the datawarehouse, either with this setting or in other ways?

Hello!!Please help to figuer out this error "The given value of type String from the data source cannot be converted to type nvarchar of the specified target column" while pulling data from source to stage.Anyone Who Can Help!!!

I’ve a job like this:The Job’s schedule it’s: When the job finishes the execution log it’s wrong, there’re several tasks, but no one with schedule start type and without details:  

Hi, When executing and deploying a project it does every single table and change, not just the changes I have made since the last deployment. In other projects, it only deploys the selected tables or changes made. But in our biggest project (deployment takes roughly 15 minutes each time) it does all or nothing.Even when in a perspective it still does every other table that exists in the entire project.Other projects don't do this and I can't seem to find the setting that changes this for the big project. Does anyone know how to set this up?Thanks!

The autoindexes doesn’t created in the physical table 

The services of 6117.1 worked fine, but after upgrading to 6143.1, I'm not able to start the TimeXtender Execution service. Receive the error:Windows could not start the TimeXtender Execution 6143.1 service on Local ComputerError 1064: An execption occured in the service when handling the control request.In the Event log not more info then the error above.Anyone an idea what is causing this and how to solve this?

Hi, My source database contains over 300 tables, from which only 30 are relevant for our purposes. Instead of manually searching and checking the required tables, Is it possible to define a list of objects of interest(text)  and let TX pick it from there? Kind regards, Dror Svartzman

Did anyone notice that these functions do not seem to work directly on a field? I always have to create a new one to use trim function on the original filed. Am I missing something?I would like to avoid the repetitive process of manually creating additional fields when I have a table which needs TRIM.

Hi.I have a question for you all:I have a table for example link thisfiled_name:FormatProduct_id: IntegerDelivery_metod: varchar(50)Inventory_id: IntegerInventory_Entries: JSONInventory_entries can contain one or several entries in JSON format like this:[{"SKU":"A","Price":"100"},{"SKU":"B","Price":""00"}]Instead off one line with the json entries nested into one single field i would like to Normalize the tabel into several lines, one for each SKU.Any ideas?

It would be really beneficial if functionality was added to the Semantic layer, such that SSAS Tabular partitions could be defined within the tool.Ideally, one would be able to right click on a table within the semantic model and choose partitioning, which would allow you to pick a field, like a Date field and configure it so that partitions on say Year, or Quarter, or Month, or Week would be dynamically created with each deployment of the tabular model. Additionally, it would also be great if once TX had visibility of the metadata of the partitions it has created, it would be extremely beneficial if we could then decide which partitions are executed in a given execution package.A little background for this request, we are in the middle of a major AX and data warehouse project, and we are building out quite a few SSAS tabular models to be consumed by Power BI.  Unfortunately, with the current setup of the semantic layer, we are having to consider managing tabular models outside of Time

Hello! I'm trying to resolve an issue where OLAP fails to execute during ETL processing due to a canceled transaction attempting to acquire a lock.  This is occurring on a QA instance hosted on a dedicated server that doesn't have any other ETL jobs processing.  I'm seeing a pattern of failures occurring on particular days of the week.  However, the error message sent in the ETL email isn't specific to the root-cause.  Also, I've perused 3 online resources that give explanations on the causes and remedies for such an issue, as I've gained understanding thereby that this matter occurs due to insufficient "timeout" settings.  But those tactical solutions pertain to remediation via the traditional SSAS development capacity, and such do not apply to the TX DWA software  For I don't see a way within TX DWA to change the settings for CommitTimeout and ForcedCommitTimeout.  Does anyone have any insight on how to rectify this issue? Your input would be greatly appreciated.  Thanks and have a g