Solved

Hi, Is it possible to connect to several databases that are on the same SQL server with one data source connection? We have tried to connect to multiple databases on the same SQL Server using the provider “TimeXtender SQL Data Source 17.0.1.0”. We tried leaving the Database parameter blank, putting in *, and writing a comma-separated list of databases, but neither way works. Has anyone had any success doing this with this connector or another? We’re using version 6221.1. Thanks!

After connecting successfully to my SQL server and adding the tables & rows I am able to preview the data by Select Tables. The Synchronize task also completed successfully. However, when I execute the Transfer task it fails with 2 errors (see attachments). I can’t figure out the reason why it fails though but the error message suggests something that (The specified path does not exist). I tried to remove the File Container in Azure and sync+transfer again, but it does’nt make a difference.

We have 2 jobs Job 1 runs at 11pm and normally runs 1 hour. Job 2 runs at 1am and must run after Job 1 completes, this job usually runs for 6 hours. On occasions Job 1 runs 3 hours and this causes job 2 to miss it start window. How can I adjust the schedule so that Job 2 has 2 criteria? 1-Job 1 completes 2-Has to start after 1am

Hi community, I created a role in the MDW and added Grant permission on one specific database schema. This schema contains some tables and some Stored Procedures. This role need to be able to select data in the tables and execute the stored procedures. I created my Object Security Setup using these settings: When I login using SSMS (using the user in the role), I see the correct tables and I'm able to select data in the tables. But I'm not able to see the stored procedures. When I check the permissions on the ‘ExcelAddin’ database schema. Only the ‘select’ permission in granted. Is it possible to grant permission for ‘execute’ as well? Using TimeXtender?

I have an Excel sheet with percentages (11 decimals). The decimal sign is comma. See example below. Year Period CostPercentage2020 1 0,018001882020 2 0,016852519 But when I read the data in TX then I see the below result: I have tried to use the culture feature see below but no success. Find a screen dump below Why does TX / Cdata not read the data as is? The “,” is interpreted as a Thousand separator. Any help will be appreciated. When I have a file with a “.” (dot) as a decimal sign I convert the data to numeric precision 38,scale 11 and that works.

Hi, I need it for a customer. I think i have seen something, but can’t find it now. BR Anders

Hi, Can we only download TX 20.10.x on the Legacy support page? https://legacysupport.timextender.com/hc/en-us I can't find it through the new Support.timextender.com site under Product updates, there I can just find the new SaaS solution. Thanks.

Is it possible to connect to an Amazon Timestream database (https://aws.amazon.com/timestream/) with the ODX?

Hi, I am using a REST API (CData source) to get source data. Is it possible to specify that you want to do a POST rather than GET in a CData source? If so is there any Guide?

Are there any best practices regarding the management of rsd files (and the like) in a multiple developer / multiple environments setting. We are currently manually distributing the files, and considering linking the locations to a git controlled repo to have some sort of control, but we do not want to complicate things if it is not necessary. Note: Using legacy version

I am trying to get data using REST API Data Source: ODX Provider: CData 2022 Authentication: OAuth Format: JSON OAuth Grant Type: Client Authorize OAuth Successful Test Connection getting below error: RSSBus.RSBException.HTTP Protocol error. 400 bad requests

Hi, We are currently migrating cubes from Power BI report Server ( On-premises) to Power Bi premium.Those cubes are not maintained in TX & refreshes are triggered through a SSIS package called by TX at the end of the ETL execution process. In the new implementation (where the tabular models are still not maintained in TX), we will be using XMLA endpoints & would like to trigger partitions refresh from within TX without using a SSIS package. What would be the best approach to tackle this, taking into account we’re running on an Azure platform (so TX VM and Azure SQL DB for DWH) ? We were thinking of using an ADF pipeline or use REST api calls, but this isn’t supported by TX version 20.10.x. Any ideas on possible alternatives ? Thanks Peter

Dear Support, I'm running into a weird error when I try to load customer data from the customer table of Navision. The error is: The numerical value is too large to fit into a 96 bit decimal. I use a query table to only get the columns I need. In this query table I use a where clause in which I exclude some customernumbers. But now I found out that I also need these numbers in my customer dimension. But when I clear the WHERE clause, the error comes up again. If I execute the same query in SQL Management studio it runs good and I don't see some strange values in one of the columns. Do you have any idea?

Hi team how to run data bricks script from TX

Hi I am just testing our V21. I have started with something simple, a 2 column CSV file with an integer key field and a text group code field. There are 18 rows. I can load it into the ODX fine (running on local SQL Server db) and I can preview the contents in the ODX “Select Tables” Pane. I can drag it to a Data Warehouse Data Area and it creates and maps the table fine with appropriate field settings. When I deploy the table in the Data Area that works fine. When Executing I get an error on the transfer which does not tell me what is happening. The error I get returned is as follows: Transfer table failed Details: Transfer table failedModule: timeXtenderSystem.Exception at TimeXtender.DataManager.StepTransferExecute.DoDataWarehouse(IStepSetup stepSetup, List`1 mergeODXTransferInfromation, VariableResolveObject dynamicResolveObject) at TimeXtender.DataManager.StepTransferExecute.DoAbstractStep(IStepSetup stepSetup) That means nothing to me and I cannot determine what I can do to corre

I am curious why system fields like SCD is Current & SCD is TombStone are datatype bigint. Is there a way to change them to tinyint? As far as I know they can only be 0 or 1.

I am setting up a table relation where the tables join based on a date range (see screenshot below) In setting this up in TimeXtender, I noticed that I can only set this up on the lookup field and not as the default relation between the tables. Does anyone know of a way this can be setup on the default table relation? Or can we had as an enhancement for TX? (NOTE: I have edited the table names and columns for this post)

Hello, I am currently trying to integrate Exact data using the TX Exact Online connector. I need to integrate data from a bunch of different divisions; I was wondering if the only way to do so was to individually add each division as a new data source or if there was another way ?

In my DSA I have my Business Partner Master Data. I want to add a field that named Intercompany that shows ‘Intercompany’ when BP Group Code = 104 or 109 and else show Extern. BP Group Code has a smallint datatype. I added a custom field with the CASE WHEN statement. However, the extra field does not show the right results. When executing the CASE statements SMSS everything works fine, but when I implement it in my DSA, it does not work correctly. I tried all kinds of CASE statements with e.g. Like,OR statements, strings, however it does not show the desired result, but rather tons of nulls. The screenshot below shows the intercompany field with the Nulls and some tests CASE statements.

Hello everyone, After the odx transfer task for API, when I click on the preview, I get the “invalid column name” error. This warning also occurs while executing in the data warehouse and stops execute. What should I do? I wanted to use aliases but I have 575 columns. I tried to re-deploy the table with differential deployment disabled. Version: 6143.1 My column name example is below: it is very long ‘properties_parameter_WS10M_RANGE_202109’ Thanks Best Regards

Hi all, Too many parameters in nasa api data available year and month. I changed their name via RSD file because and have only one table like below; I have to change this columns in this dataset from this station WS10_MAX201901 WS10_MAX201902 WS10_MAX201903 ….. WS10_MIN201901 WS10_MIN201902 WS10_MIN201903 …... to this station MM.YYYY WS_10_MAX WS_10_MIN How can I do it? I tried Custom Table Insert but doesnt work. I tried also Junk Dimension but I had to clone my dataset 12 time to be able to print for example 12 months 2019 data consecutively.

I'm following the steps explained on this page (https://legacysupport.timextender.com/hc/en-us/articles/360034695651-Connect-to-a-REST-API), but I can't figure out. Situtation: I have to get for all station weather data from DW. An example for stationnummer 10184 like this: https://s3.eu-central-1.amazonaws.com/app-prod-static.warnwetter.de/v16/forecast_mosmix_10184.json You can find the all station list here: https://www.dwd.de/DE/leistungen/met_verfahren_mosmix/mosmix_stationskatalog.cfg?view=nasPublication&nn=16102 What I did? first I set up a dataset for the sample station 10184 and got the ‘days.rsd’ file. Then I made some changes in ‘days_changed’ file(it doesnt work). And I coudnt generate it.

While talking to TimeXtender, other people, and upgrading TimeXtender a lot of different numbers are thrown around. For some of those the definition and messaging is clear, but others less so. While upgrading the latest patch I encounter: Software (build?) version: 6221.1 Instance version: 2.0.0.0 (I assume something like Cloud Repository structure version?) TimeXtender Next Gen (in articles on the community) API version (if your ODX Server and TimeXtender desktop mismatch) To avoid going down the path that IBM or Microsoft took with a flurry of different numbers that you all need to understand and be careful about, it would be nice to have a place in the Community that lists all these things. This makes it much easier to triage issues and create a “common parlance” between partners, customers and TimeXtender.

When associating instances to an Execution Server in 6221.1 I noticed that the message displaying locked instances has a slight grammar mistake: “The following instances that currently locked by another machine” should probably be something like “The following instances are currently locked by another machine”.

Hi community, I have a client attempting to load a postgres database into ODX Server (TX version 20.10.x). The table contains a field with dates that are invalid for SQL but valid in Postgres, for example 20011/01/01. Upon transfer, the task completes with errors that it is unable to parse datetime value. All datetime fields have been converted to VARCHAR(MAX) using Override Datatypes and this is confirmed by looking in the ODX Storage in SQL Server Management studio. Since the error still presents itself, it seems likely that the error is coming a step earlier, during the CDATA conversion. Unfortunately, it seems that there is no way to generate RSD/schema files from the CDATA Postgres provider. Normally I would change the datatype there in these situations, since it seems to be going wrong in CDATA somewhere. How can I load this table? Kind regards,Andrew - E-mergo