TimeXtender Desktop Q&A

Hello, TimeXtender: 20.10.31.64ODX: 20.10.31 We have a case where a customer has to move from SQL database to a OneLake Parquet as the data extraction from one of their systems. We need to find a way to get this data into TimeXtender. I could find that there is the possibility for one lake parquet connector, but it seems tied to the new version of TX as I can’t find that connector in our version of tx/odx. Is there any possibility for us to do it another way while on our version? Thank you,Victor

Hi, I'm using the TimeXtender REST Data Source (5.0) in combination with dynamic values. The API endpoint needs a filter (Period) in order to work. As you can see in the last screenshot the dynamic value query refers to a table in TX. This table contains all the yearmonth combinations of 2023: 202301, 202302, 202303 etc. When the datasource is executed in Timextender desktop it only returns the following months: 202301, 202302, 202306, 202312. It seems like the filter does not recognize all the yearmonth combinations or skips most of the months. Has anyone had the same issue or experience with this configuration? In the screenshots you can see the curent pagination and parameter configuration. I’m also using table flattening but that doesn’t seem to make a difference. Thank you. Kind regards, Joris de Leeuw

Good morning Team, The database [ODX_COL_PROD] has 2.0 TB of data, and we need tu purge it. Can someone give or send me informacion/documentation about the purge data task. Thanks for your help. Ignacio

I have a weird issue in my new TimeXtender project, where my tables in my dwh layer won't load data from the Business Unit. I have a very simple setup to start with. I have one business unit which loads a couple of tables, and the Bussines unit configured to store data on our “VMTXTD001” server in a database. The Datawarehouse uses the same database as the Bussiness Unit and should load from that Business Unit. But when I execute the DWH layer I get this message for all tables: Start Time : 4/19/2023 4:14:08 PM End Time : 4/19/2023 4:14:10 PM on server: VMTXTD001-Execute Execution Package Default 'Failed' Invalid object name 'VMTXTD001.dbo.DM_CRM_Replica_dbo__CustomAccount_DSA_dsa_test_T'. Details: SQL Server: 'vmtxtd001' SQL Procedure: 'dsa.usp_CrDM_dsa_test_CRM_dbo__CustomAccount' SQL Line Number: 12 SQL Error Number: 208 Invalid object name 'VMTXTD001.dbo.DM_CRM_Replica_dbo__CustomAccount_DSA_dsa_test_T'. To me the issue appears to be that TimeXtender created the procedure incorrect

We are trying to follow the setup guidelines so that we can get to grips with TimeXtender leveraging Fabric. We are having issues at the very beginning in trying to assign our App Registration ID to the Fabric Workspace. It just wont show as an option in the list when trying to grant membership access to the Fabric Workspace. If we specifically type in the name of the App Registration ID then we get an error below the dialog indicating that we “can’t use invalid or duplicate emails”. We are obviously missing something, anyone have any ideas?

Hi, In version 20, we have a setup with two environments, a dev and a prod, that ingests data via a business unit. We are limiting the data ingested into dev by using the “Environment name” project variable together with a date filter, much like what is described here: https://legacysupport.timextender.com/hc/en-us/articles/360032668012-Creating-Dynamic-Data-Selection-Rules-using-Project-Variables What is the equivalent of doing this in the latest version of TimeXtender? The client’s setup has one ODX and two DW instances (dev and prod). Their need is to limit the amount of data ingested into the Dev DW instance. Is this possible with the features available in version 6436.1? Best, Pontus Berglund

Hi all, I’m using the CData Connector for Parquet files and take files from a SFTP server. The files always contain the data from the last day (with some overlap). I made the following setup: Primary key Incremental Load with updates The first load is always ok, but then there is no new folder in the DataLake created? What I’m doing wrong? ThanksMichael

Hi community, I have this strange thing I cannot explain. I have a data connection that has been working properly for months. Since the beginning of May the transfer task results in a time out error, where after 1 hour the command time out is reached. I have tried everything to resolve this error; nothing is working. I tried with one really small table and 1 thread (of course setting the time out to a few minutes 😉); same error. The strange thing is; I have cloned this exact data connection and tested the transfer task running this exact similar table over 1 thread. This works without any problems. I have also added several other tables, also without any problems I fetch the rows of all tables within a few seconds. Does anybody have ANY idea what might cause this extremely weird behaviour?

Hello, My transaction journal tables unfortunately don't have a useful update/modified datetime column, only a posting date or similar. I'm looking to incrementally load these tables, since they are my biggest tables. I can do this partially based on the Posting Date column which won't change after creation, however I have some columns, e.g. BalanceDue which will mutate once an Invoice has been (partially) paid. Hence, I also can't use an offset incremental loading rule for posting date, since I won't catch these changes. Anyone got an idea to still minimize loading times on these tables?

Hello, I started seeing this error message multiple times a day in the event viewer. Does anyone know what may be causing it? Synchronize executions failed:System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK_ODX.ExecutionLogs'. Cannot insert duplicate key in object 'ODX.ExecutionLogs'. (...) Thanks

Dear Community, When I create a view in my data area MDW from a table which is in my DSA (=> I drag the table from my DSA are to the views in the MDW data area), the view auto parameterizes (which is great). I deploy the view in the MDW, read view fields and preview it. (all is still great). When I release this to my next layer (PRD) I suddenly get a erroer previewing the MDW view. When I check the view in the PRD MDW the parameterization is all gone. Have you encountered this? Is there a solution? Thanks = Daniel

I am loading a fact table from a staging table, both are regular data warehouse tables. When I create a data selection rule on the mapping table, I'm unable to select the conditional lookup fields or the system fields from the source table: TX Version is 6590.1. In legacy TX, it is possible to select the conditional lookup fields and system fields for creating selection rules: We have implemented a workaround where we create an extra field in the DSA table that has a transformation that fills it with the value of the conditional lookup field. In turn, this extra field does show up in the selection rule fields because it is a regular field. But this is not a very nice or future-proof solution. Is this an intentional change and if so, can you explain why? Or perhaps this is a bug in TX SAAS?

Hello, I can’t seem to find out how to create a variable holds the name of the data warehouse environment in new TimeXtender (6626.1). I’m thinking of the name of the environment as defined in the portal, not the name of the data area. Thanks!

Hi team, I have a table in a data-area that is filled by a single mapping set, in this case containing 7 tables. Because we discovered some differences between the fields we need from each table, I want to convert it to a normal mapping. I tried to do this via ‘Smart Synchronize’, but it is only working for fields that have not had a name change. In other words, when choosing to smart synchronize a single table onto a table with a mapping set, it seems to perform a ‘Synchronize (only existing fields)’ instead of looking at the name of the fields in the mapping. Is this expected behavior? Kind regards, Andrew

I’ve detect that some dax code doesn’t works in PBI. Are there some guide abut this?

The people before me defined certain variables in TX. One of these is [vDatabase] which is futher used in a stored procedure in ODX: Select.... FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_CATALOG = '[vDatabase]' AND RIGHT(TABLE_NAME,2) NOT IN ('_L','_M','_T', '_R', '_B') AND TABLE_SCHEMA NOT IN ('dbo','view', 'XLS') AND COLUMN_NAME IN ('modifyDate','last_update','Registrert_Dato') END The variable is also used in SQL snippets in ODX, DSA and MDW: DECLARE @sql NVARCHAR(MAX)SELECT @sql = COALESCE(@sql + ' UNION ALL', '') + ...... FROM %s'+ CHAR(10) , TABLE_SCHEMA, TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, TABLE_SCHEMA + '.' + TABLE_NAME, COLUMN_NAME, COLUMN_NAME, COLUMN_NAME, COLUMN_NAME, COLUMN_NAME, COLUMN_NAME, TABLE_SCHEMA + '.' + '[' + TABLE_NAME + ']' )FROM INFORMATION_SCHEMA.COLUMNS WHERETABLE_CATALOG = '[vDatabase]' AND RIGHT(TABLE_NAME,2) NOT IN ('_L','_M','_T', '_B') AND TABLE_SCHEMA NOT IN ('dbo','view', 'XLS') EXEC(@sql) However when i execute the table there is no data. I am

I am having some issues with the transfer step when loading incremental using direct read. The problem seems to be that the generated procedures do not utilize indices on the underlying tables, resulting in full PK scans for every run. I was especially having problems when running on azure general compute. Switching to hyperscale helped some, but the transfer step still uses approx 40sec scanning ~90m rows causing bottlenecks. When using ADO.NET I could set an index on the incremental rule-field speeding up the search to <1sec. The execution-plan generated by TX looks like this: Here we get a PK index-scan even when there is an index on dw-timestamp. Testing on a subset of the data (~10mill rows): Adding the option(recompile) to the procedure results in the procedure using the dw-timestamp index: Is there a good reason for why these procedures are generated without the recompile flag? Is it something that could be added in a later release? And is there a way to work around this other t

Hi Team, I am getting the follwing error while executing the table. Please note i do not have a column named ‘ORDER’. I have no idea what it is refering to.

Hi, I have a very regular table that is loaded from a SQL Datasource. The table has a little over 3 million records and the following definition: Nothing out of the ordinary as you can see. The table is loaded with the ODX with an incremental selection rule on te mut_dt column. The ODX load works fine; loading the table full or incremental is no problem and the data is stored in the container as expected within 1 or 2 minutes. However, when I drag the table to the DSA data area and load it there, something strange happens. Loading the table to the DSA hangs after 900.000 records are inserted into the raw table. We have tried waiting for several hours, but it just hangs there and nothing happens. Other tables from the same source load fine to the DSA. Data source version is TimeXtender SQL Source v 19.1.1.0 (but load from source to ODX works fine)ODX and TX version is 6590.1 .

Hi, I have set up a Storage Management Task with only the Rollup option ticked, and filled in the right ADF credentials. One of my source tables has been selected for this task. TX says the runs are successful and they finish in a fraction of a second, but nothing happens in the storage account. The version folders contain the full load file + all the incremental files, as before. I have tried with many different settings for min and max rollup file size. I have not specified “folder (optional)”. I have tried with and without specifying integration runtime. No pipeline run seems to show up in ADF after triggering the task.

I have a REST datasource that uses pagination with URL paramater page. Fairly simple. The next page (if there is one) is returned not as a header but as an element in the json result: So, to enable paging I have to set up something like this: And: I have two questions on this: I get an error on the XPath Value saying ‘Expression must evaluate to a node-set.’ . How do I determine the correct XPath to the json element? And my second question is how do I make sure the complete URL is replaced instead of only the /api/… part?

The DAX Snippets doesn’t works like the SQL Snippets. It doesn’t allow in the “Show Usage” section to change the snippet and change too the measures afected.

hi, i have a exclude columns made like “ exclude if schema <all” and table <all> and column contains “ plusg” for 1 table i want a specific include like include if schema <all> and table equals “plusgmoc” and column equals “plusgtest” it seems that the column isn’t added, i have done a sync and a new transfer. I look in the generated parquet file and can’t find the column. Is this expecten behaviour? how to solve?

Hello, Our team has recently started shifting from using Business Units as our data ingestion approach towards ODX server. Our project contains 3 environments (Dev, Test, Prod). All of our data providers give us 2 tables per dimension/fact (e.g. dim.user and dim.user_qa etc.) and we store them in 2 separate databases (Datastore and Datastore_qa respectively) with exactly same names (dim.user). We have a following setup in place implemented using “Environment properties”: Environment Source database Dev Datastore_QA Test Datastore_QA Production Datastore This way contents of dim.user table are loaded from Datastore_QA database on Dev and Test environments, and from Datastore database on Production environment. Is there any way to achieve the same result utilizing ODX server as data ingestion approach? Hopefully this makes sense, thank you!

Hi, we are loading a table from our source data base. A column which is part of the key, contains values that are similar but not the same. The difference is in a trailing space. Now, when TimeXtender reads this dataset, it claims a violation of uniqueness. The column is set to be VARCHAR(), which probably causes the system to trim the trailing space, resulting in a duplicate value. As the source system recognizes this as different entries, we want to keep both. How to solve this?