TimeXtender Desktop Q&A

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)Howev

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

One of our client's has a problem with the version mismatch between odx and desktop application. They are running on 6645.1 odx but some of the desktop versions are still on 6626.1 they get an error that the odx version is locking them on 6645.1 but it's expecting 6626.1. Is there a workaround for this or a fix? or is this a bug? I know the ‘easy’ solution is that all the desktops versions should be updated at the same time for everyone ones you also update the odx but that's not always possible.

Hi all,I need to extract data from a huge table in SAP (KONV) based on a subquery from another extracted table (VBRK). Any ideas on how to solve this using the XtractIS? I can’t use quey tables on this type of connector and I tried to put the subquery in the filter rows filter for “in list” which also didn’t work either. Any more ideas how to solve this? Many thanksKai

Hello,TimeXtender: 20.10.40.64ODX: 20.10.31We have an issue on certain source where transfer tasks result in “completed with error” or “failed” in the ODX.This lead to the question if there is anyway to capture this without going into the ODX and manually checking every transfer, as there is no way to set up any notificaiton.We need to someone capture this, as the loads within TX will run as usual without failing but not get new data from the sources in most cases. Has anyone found a solution to streamline this? Within Timextender or with a external solution?Thank you,Victor

I have been playing around with the on-demand load and set up some SQL Sources to use this. When I right-click Execute a table in MDW that loads from an on-demand source (TimeXtender SQL Source, ADO.Net transfer) I do not see any new extract to ODX - so I decided to run a Job: I subsequently right-clicked a Job that reloads my MDW layer and chose Execute. If I try to Execute again I get a message “The job xxx is already queued”, it does not ever seem to Execute the job however.Is there somewhere where I can see the job queue?

I am working in a project and the execution is to mach slow,  It has take 35 minutes for 5 tables, that all of them has 10000 rows.    

When promoting a Semantic Model (copy to instance), are the Roles and especially the users/groups within the role in the model also copied to the other environment? In legacy TX we were able to grant a role to different users/groups per environment, but in the new TX it seems to be the case that we have to change that after promoting?

Hello, I am using ODX server 20.10.47. I would like to limit the amount of records loaded by implementing following filtering rule on column [perakt] among others:LEFT ([perakt],2) > 20I am trying to achieve this in following way using “Filter Rows” options on data source but it does not work:Also if i click OK and load the data, the 2 upper filters are not applied, just because the 3rd filter does not work.Are there any ways of achieving this through “Filter rows” functionality? Or the only option is to create a custom query table?Thank you!

Good Day,  We are receiving the following error messasge: Finished executing project 'COMPANY' Execution Package 'Client execution'Execution failedStart Time : 5/24/2024 7:57:22 AM End Time : 5/24/2024 7:57:22 AM on server: NAME-Execute Execution Package Client execution 'Failed'    The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.        Details:        SQL Server: 'NAME'    SQL Procedure: ''    SQL Line Number: 1    SQL Error Number: 242        The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value.    Module: .Net SqlClient Data Provider    System.Data.SqlClient.SqlException       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)       at System.Data.SqlClient.TdsParser.TryR

In my source table, I have a column called [lastSync] that is varchar.In my history table I have last_sync as datetime.Currently the only way that I know of how to solve this is to eitherCreate new Custom field [last_sync] in my source table that includes TRY_CAST([lastSync] as DATETIME) The problem here would be that I would need to change my Source table from Simple mode. I would like to keep the simple mode table. Data redundancy as this specific column is stored twice. Create a new Custom field [lastSync] in my history table to accomodate the data before [last_sync] uses Custom Field Transformation to cast to datetime. The problem here would be redundancy as I’m storing the same column twice over a long period. Of the two I would prefer option 1.Is there no way to do this on the fly, so that data is converted when transferring data from the Source Table → History Table?  I’m Using TimeXtender Business Units 20.10.32.64

Hi, Since we upgraded to 6626.1 our TimeXtender SQL Data Source (18.0.1.0) type data source has been failing. We believe it is because 6626.1 expects a TimeXtender SQL Data Source (20.0.1.0). This either is a bug that needs to be fixed, or in the product update log / in the portal there should be some warning about this. If this was mentioned somewhere in a product update please share the link to the article.   

Good morningYesterday on the development vm I created a job to be executed on a production vm (which has the related instance marked  in the execution server). However it did not run last night.Is it necessary to log in in TimeXTender desktop in the production vm for the job to become active on that vm?