TimeXtender Desktop Q&A

I've made a simple semantic model and configured an Analysis Services (Tabluar) endpoint in Azure. There is one perspecive containing a few fields and measures. The model deploys and executes without any issues.However, the perspective is not visible when connecting to the model from Power BI Desktop. Also, when I connect to the model from Management Studio, I can only browse the whole cube and again the perspective is not there. I can script the AS database to a new query window and the perspective is not mentioned in the script.Is this an issue with TimeXtender? Or as AAS config issue perhaps? I'm using a PPU license but I don't think that's relevant since the perspective cannot be used in Management Studio either.TimeXtender version is 20.10.37.64.Thanks!

Hello, I have built a data model in Timextender and with a Power Bi endpoint. In the Power Bi report I see certain fields summarized by ‘Sum’. In the SSL layer I only get the option to change te name and I am missing the 'Summarize by’ and the ‘Sort by’ option. What am I doing wrong?   

I have table A with history enabled, all columns SCD type 2 except the PK and a record is marked as deleted when deleted in the source (with a seperate record).In the next data area / data warehouse (DSA) i want to create an incremental table B based on table A, but I do not want to have deleted records from A in table B.When follwing the incremental rule wizzard the incremental selection rule can be set based on the incrementaltimestamp but deletes can not be handled because table A has no deletes (is thomstone =1).How to solve this the easiest? I can only think of taking along the Isthombstone field to table B and delete the records in a post script but this should be possible musch easier I would say.Suggestions? 

Hello, i use Semantic layer as an endpoint to analyze the data through Microsoft Excel. In my model i have Calendar table (auto generated by TX) which dates from 2015 up to 2030. Fact in my dataset has values only up to year 2026.When i open analysis services endpoint through Excel and want to filter values based on Calendar, i can see the empty row in filter. I assume this is due to the reason that Calendar dimension has values up until 2030, and the fact - up until 2026:Is there anyway to not show empty values coming from dimensions (that do not have matches within the fact) in the analysis services from semantic layer? Thanks!

The ODX server stopped (per 25/8) synchronizing it's job status with the portal.Restarting the ODX Server does not solve the issue. Any tips?

Is it normal when loading fact table incrementally with new data, that it can take up to one hour?Are there any tips to have this incremental load to perform better?Moving records from staging table to fact tablefact table is 140 million records, new load is around 500 thousand records with new timestamp here is the execution log overview  the table is not that complex.17 fields are moved over, from staging to fact table1 field is from keystore3 fields are have custom value script table settings are..

I’m using Azure Analysis Services as a SSL  Is it possible to resume and pause using powershell in a job?Do you have some examples of configuration? 

Hello Today I get this error, wenn I want to add new Job. We didn’t change the version and use TimeXtender 6143.1.  We updated all of data sources but doesn’t change. Firstly, I want to understand why I am receiving this error. If I encounter this message in the future, I want to comprehend what I should do. There is a similar topic, but since there is no version change, I want to reopen it. Xpilot recommends that we should use the new version. Is it correct?

Hi Community,After creating a simple semantic model (one table) and deploying it to Power BI Premium I get an error for the connection to the source database. It says it cannot connect to the source database because of the credentials (we use SQL Authentication on our Azure SQL database in this case).Would be nice if we could configure that from within TimExtender (and perhaps there is a way?).After manually fixing this authentication issue. we are able to execute this endpoint.This is confirmed by checking the Refresh History. Now we try to add the created (and tested) execution package to a job. That is not possible because the execution package is greyed out in the Job and therefore to able to be added.What could be reason why we are not able to add Semantic Model execution packages to a Job?Thanks in advance. Kind regards, Eric  

Hi team!  I am contacting you because I am trying to transfer data from MariaDB to ODX and I received the following errorfailed with error:System.FormatException: The DateTime represented by the string is not supported in calendar  Any suggestion to solve it? Regards Ignacio 

New fields from source are not showing in the Data Movement pane.New fields are added to the source database, the new fields and data are in the ODX, I can see the new fields in the parquet files, but the fields are not showing in the Data Movement pane.I have tried to run the function in ODX “Synchronize Object”I have tried to run the “Synchronize” task in the odxI’m Running Timextender Version 6346.1

Hi All, Is it possible to use an SAP Theobald Extractor with incremental load and that just for 1 table ( or more, but not all the tables? We tried is on one table and we got an error message saying we needed to change all the tables into incremental load.Kind regards, Eric 

Hi,We have different instances for the development, test and production environments at a customer. Both MDW and SSL.After copying the instances from one environment to another, it would be nice if you could easily switch source for the target SSL to the MDW in the same environment. Under Synchronize with remapping, one must change the instance, data area, schema and table for each table in the model. it would have been smoother if you could switch instances for the entire model with one change.The easiest would have been if you could choose whether these settings in an SSL should be overwritten or not when copying.BRAnders

Dear Support,I'm having a problem with adding a new column from MDW area to the semantic model (tabular).I synced the model, I see the new column in Data Movement on the right side, but when I try to add the new column to the table it belongs to in the semantic model I don't get a 'plus’ symbol. It is a column I want to add to a fact table.I tried to reboot the server, but that didn't solve it. I opened another semantic model and tried to add a new column to a table and that worked. But for some reason in this model it won't. Can you help me?TimeXtender version 6143.1  

Dear all,I'm trying to set up a completely new ODX Server. I've installed the ODX server and made all the required configuration. When th ODX Server needs to connect to its instance i'm getting this error:I've checked all the firewall settings and I've done all the checks in this document: Configu

Hi,I have seen clients use Supernatural key fields to create keys between the fact and dimension tables, usually when the logical key is a combination of fields. I have seen these two methods used:The Supernatural field key is created in both the fact and dim table, using the same key store The Supernatural key is created in the dim table, then mapped to the fact table with a conditional lookupIs there a difference in performance here? Is there a best practice to advocate for? 

Hi Support, We first raised this problem/bug back in Feb 2022. It seems that the incremental rules are not working correctly. The client Xandor had removed these incremental rules from their Live system some time ago but re-introduced them this month, and have failed. The problem seems to be related to using multiple incremental rules e.g. 'MODIFIEDDATETIME > (Last Max Value) - 3600 seconds & TRANSDATE > (Last Max Value) - 15,552,000 seconds.  Please see attached document for further information on this. The client is currently on version 20.10.30.64 and have TX configured to use SSiS for data transfers.  Do you know if there is a solution to this issue please? Thanks,Kashif 

Hi team I have the following tableAnd I have to create this transformation on incidentGroup Column  CASE    WHEN [incidentTypeID] >= 100 AND [incidentTypeID] <= 199 THEN '1XX-Fire'        WHEN [incidentTypeID] >= 200 AND [incidentTypeID] <= 299 THEN '2XX-Overpressure, Explosion, Overheat(no fire)'        WHEN [incidentTypeID] >= 300 AND [incidentTypeID] <= 399 THEN '3XX-Rescue & Emergency Medical'        WHEN [incidentTypeID] >= 400 AND [incidentTypeID] <= 499 THEN '4XX-Hazardous Condition(No Fire)'        WHEN [incidentTypeID] >= 500 AND [incidentTypeID] <= 599 THEN '5XX-Service Call'        WHEN [incidentTypeID] >= 600 AND [incidentTypeID] <= 699 THEN '6XX-Good Intent Call'        WHEN [incidentTypeID] >= 700 AND [incidentTypeID] <=

Hi team,Are there any documents about the naming convention on the TX project? About Table, View, schemas, etc. The client requests that on the project. RegardsIgnacio   

Hi team I am beginning work with a new client, I created environments development, UAT, and Prod, and after I created Global DataBases DSA and MDW for now.My question is, How I have managed the projects on Global DataBases? Only can I create one project when using Global DataBases or Can I create a lot?Thanks for your helpIgnacio

We are running an environment on two servers. One DEV and one PRD server. The instances are copied from the DEV to PRD server, both ODX and MDW. Apparently the jobs are also copied. After refreshing the list I'm adding jobs to run the production ODX. As we can see below I can choose between both the DEV and PRD ODX's : However. If I select the ODX Just Brands Production / JB NAV / Full Load NAV. It jumps back to ODX Just Brands / JB NAV / Full Load NAV, running the DEV ODX. Why is this?

Our machine runs in UTC+2.00, whilst our Azure databases (by default) run on UTC time. Now when we schedule an ODX Transfer task, the interface let's us schedule these tasks in UTC time. The Execution logs of a transfer task are also in UTC time. However, schedules for execution packages are in local time, UTC 2.00, and therefore there logs are also in UTC 2.00.  I guess my question is, why is this the case? Both the ODX & Execution service are services on the same machine with UTC 2.00. Both the ODX as well as the MDW and the project repo are azure db's in UTC.  Why would one use the machine time and the other the azure db timezone? And is there a way to make them the same other than resetting the machine time to UTC? Version 20.10.37

Hello!I want to experiment a little and check if changing my Max Threads setting can improve execution times. I have one big package which includes multiple other packages as Steps.If I change the Max Threads setting in the main package, do the packages from the included steps inherit this setting, or do I have to manually change the setting for each included step?Side question; I have plenty of data for execution times at 4 threads. My plan is to do three runs at 3, 5 and maybe even 6 threads and compare the averages. Is that a good setup? Thanks.

TX: 6284.1Is there a reason why Lineage generated from the Data Source Explorer in the ODX Server includes the downstream stuff in a DWH instance whereas generating Lineage from a field in a Data Area in the DWH instance does not show the ODX part of the lineage?

Is it absolutely necessary to perform a transfer between environments after an upgrade?Dev, QA and Prod are all sitting on their own server. I have upgraded all 3 to the latest TimeXtender version and all Deployed and executed perfectly. Would I still have to do the “Multiple environment Transfer” or is this not necessary?Upgrade Dev - Deploy, Execute, & Validate all is working.  Upgrade Test - Deploy, Execute, & Validate all is working. Transfer Dev -> Test - Deploy, Execute, & Validate Test to ensure all is working. Upgrade Prod - Deploy, Execute, & Validate all is working. Transfer Test -> Prod - Deploy, Execute, & Validate Prod to ensure all is working