Recently active topics

Hello,I have a TimeXtender REST data source where some loading tasks sometimes keep running infinitely. This causes issues on my pipelines where I don’t get a message/monitor from, as it doesn't error.I see that in my REST data source settings I don't have a command timeout like for SQL data sources. Is there a way I can put a command timeout? Would it be this Timeout setting in O&DQ?  

A JSON response looks like this [{"ref": 123456,"dim_1": "A","dim_2": "B","peroid": 202601},{"ref": 5E+20242959,"dim_1": "A","dim_2": "B","period": 202602}]The second ref (5E+20242959) is a problem - its neither STRING nor an INT.Ref is defined as NVARCHAR in BU, but as you can see the value is not between “”.I have tried the following approaches under, still i get the same errorInput string '5E+20242959' is not a valid number. Path '[56935]['ref.53e92a42-b13c-4062-87b4-6bd5a89547b1.1992753']', line 1, position 36741783.How do i solve this?Here are the approaches i have tried:Omitting Ref in Table FlattningIn table flattning, i have left it out. I have the other three values, but still landing returns an error:Defining the value as NULL in table flattningField transformationCondition on column ref in BUI have defined the following condition on the column, still i get the same errorCASE WHEN [ref] LIKE '5E+%' THEN NULL ELSE [ref]ENDScript ActionsI have created a script th

Connect Claude or ChatGPT to the TimeXtender MCP Server using your own Auth0 tenant as the identity provider, so users sign in with OAuth 2.1 instead of an API key.Verify your Auth0 configuration before you connect a client. Claude and ChatGPT cache the OAuth metadata they read from your server URL at organization level and do not read it again. A first connection attempt against an incomplete configuration makes that URL unusable, and recovering it requires an organization administrator. Complete every section up to and including Configure the MCP Server first.PrerequisitesAn Auth0 tenant, in any region, where you can create an API and an application. A deployed MCP Server, reachable over HTTPS at a stable public hostname. Rights to add a connector in Claude or ChatGPT. Both desktop apps use a connector created in the browser, so you need browser access for either one. Administrator access to the MCP Server host, to run the TimeXtender MCP Configurator.Under Auth0, the MCP client regi

Connect Claude or ChatGPT to the TimeXtender MCP Server using your own Microsoft Entra ID tenant as the identity provider, so users sign in with OAuth 2.1 instead of an API key.Verify your tenant configuration before you connect a client. Claude and ChatGPT cache the OAuth metadata they read from your server URL at organization level and do not read it again. A first connection attempt against an incomplete configuration makes that URL unusable, and recovering it requires an organization administrator. Complete every section up to and including Configure the MCP Server first.PrerequisitesA Microsoft Entra ID tenant you can register applications in. A deployed MCP Server, reachable over HTTPS at a public hostname. Rights to add a connector in Claude or ChatGPT. Both desktop apps use a connector created in the browser, so you need browser access for either one. The Azure CLI, installed and signed in. Run az login and select the tenant you are configuring. Administrator access to the MCP

Upgrade Timextender Data Platform Upgrades in Timextender Data Platform are rolled out on a schedule to keep the service reliable. Administrators and contacts are notified by email ahead of an upgrade and again when it is done, and administrators can take an upgrade immediately, book it for a day that suits them, or postpone one that is already booked. Cloud only. This article is aimed at cloud customers. If you are running an on-prem installation, see Upgrading Orchestration and Data Quality. The Gateway is yours to upgrade. Upgrading the cloud service does not upgrade your gateways. Each one is a Windows service on your own machine and has to be updated there, per server. See the Gateway section of the cloud upgrade article. How you are notified WhenEmailIn Timextender Data PlatformA newer release is availableNoneUpgrade available banner, for administratorsAbout 7 days before a scheduled upgradeAdvance noticeService upgrade banner, for everyoneWhile the upgrade runsNoneUpgrade in

Understanding the Schedules listGo to Orchestration > Schedules to list every schedule in the workspace. The page is laid out like the Packages page.What each row tells youColumn What it shows Frequency The schedule in plain language, for example Daily at 00:00 or Monthly on the second Tue at 00:00 Next Run When it will next fire Last Run When it last fired Status A green Enabled or grey Disabled label The Frequency column is generated from the schedule's configuration rather than entered by hand.Reading the Next Run columnFour things can appear in this column, and three of them are not dates:Next Run Meaning A date and time The scheduler has worked out the next run Calculating… You have just saved. The scheduler recomputes within about a minute Never There is no next run A dash The schedule has not reached the scheduler yet Calculating… is normal and short-lived, and is not an error. It appears after any save and resolves on its own.Never covers three

Add tasks to a scheduleThe Schedule tab decides when a schedule runs. The Tasks tab decides what it runs, and is where the work is attached to the schedule.Add a taskGo to the Tasks tab of the schedule. Select Add task. A picker opens with a category rail down the left side. Select a category, or enter text in the search box to filter the list. Select an item to add it. The item is added immediately and is removed from the list, so you can keep adding without reopening the picker. Close the picker when you are done. Select Save.The three groupsGroup Categories Data Quality Datasets, Rules Orchestration Packages Legacy Compare queries, Dimensions, Email summaries, Object groups, Processes, Queries, Reports, Test groups Each category shows how many objects are still available to add. A count of 0 means either the workspace has none of that kind, or every one of them is already on this schedule.About the Legacy group. Those eight categories are references to objects that live

Understanding schedule permissions Schedules use the same access model as packages: three ordered privilege levels, and a grant that can sit either on the workspace's Schedules node or on one individual schedule. A grant on the node covers every schedule in the workspace. A grant on a single schedule below it covers only that one. Both are configured under Access management. What each action needs ActionMinimum levelIs a grant on one schedule enough?View the Schedules listViewerYesOpen a schedule and read itViewerYesEdit fields and saveContributorYesEnable or disable from the listContributorYesAdd, remove and reorder tasksContributorYesCreateAdministratorNo. The workspace Schedules node only.DuplicateAdministratorNo. It is a create.DeleteAdministratorNo. The workspace Schedules node only.Run or Stop from ExecutionsWorkspace AdministratorNoAdministrator access on one schedule lets you edit that schedule. It does not let you create or delete others. What a read-only user sees View-

Run a schedule on demand and manage schedule groups A schedule normally fires on its own timetable, and you can also start one by hand from the Executions page. This article covers manual runs, which environment a schedule appears under, and where schedule groups are managed on a cloud tenant. Prerequisites The schedule needs at least one task assigned, and a schedule defined in ODQ Desktop. Run a schedule on demand Go to Orchestration > Executions. Select a schedule. Select Run in the details panel on the right. The row moves through Queued, Running and Finished, or Failed if one of its tasks fails, updating on its own. You do not need to select Refresh. The run appears in both Last 5 executions and Full History. You can do the same from a process map: open a schedule group's task history and select Run there. How a manual run behaves A disabled schedule can still be run by hand. Switching a schedule off stops it firing on its timetable, and does not stop you starting it you

Set the frequency and timing of a scheduleA schedule decides when work runs. This article covers the Schedule tab, where you pick the frequency and set the timing. Choosing what runs is done on the Tasks tab.To start, go to Orchestration > Schedules, select Create, and enter a name for the schedule in the header.Three fields that apply to every frequencyEnabled: a schedule that is turned off keeps its configuration and fires nothing. Execute environment: Production, Testing or Development. This decides which environment's version of each task runs. Summary: a live, plain-language description of what you have configured, in the same wording the Schedules list shows.Your instance's timezone is shown at the top of the tab, as "All times are shown in UTC+00:00 UTC, the instance timezone." Times are entered and displayed in that timezone, and the correct UTC value is stored behind the scenes, so a schedule fires at the moment you intended regardless of where the server is.The seven frequ

Packages in TimeXtender Data PlatformA package is one unit of work in an orchestration flow: refresh a Power BI dataset, run a notebook, execute a script, move a table, or trigger a pipeline. You give a package a type, tell it what to act on, and then run it, on a schedule, as a step in a process map, or by hand.All 21 package types are created and configured in TimeXtender Data Platform on cloud deployments.Cloud only. This article is aimed at cloud customers. If you are running an on-prem installation, packages are managed in ODQ Desktop.The Packages overviewGo to Orchestration > Packages to list every package in the current workspace with its type and status.Create, Duplicate and Delete sit in the toolbar. Duplicate and Delete act on the rows you select in the leftmost column, so they stay inactive until you select something. The filter bar above the grid narrows the list by keyword or by type.Choose a package typeSelect Create to open the type picker. All 21 types are grouped by

Understanding user permissions for packages Package access decides who can see a package, who can change one, and who can put one into production. This article describes the three privilege levels, where a grant can sit, and what each action requires. The three privilege levels LevelIn shortViewerRead. See the list, open a package, and read its definition.ContributorChange. Edit fields, save, and run.AdministratorCreate and destroy. Everything above, plus create, publish, duplicate and delete.The levels are ordered, so Contributor includes everything Viewer can do. Where a grant can sit A grant on a Packages node applies to every package in that workspace. Grants on a workspace, or on the Workspaces group above it, flow down the same way. A grant can also sit on one individual package. That is how you give somebody Contributor access on a single package without giving them the whole workspace. The two routes are not interchangeable: some actions accept an object-level grant, and

Create and assign a scheduleA schedule decides when work runs. You build the schedule once, then attach the packages, process maps or rules that should run on it, so the timing lives in one place instead of being repeated on every task.Schedules are managed under Orchestration > Schedules.The Schedules overviewThe toolbar has two actions, Enable and Disable. Both act on the rows you tick, which is how you stop a schedule for a maintenance window without deleting it and losing what it was attached to.Create the scheduleGo to Orchestration > Schedules and select Create. A new schedule opens, enabled, belonging to one environment. Enter a Name. Name it for the rhythm rather than the contents, for example "Nightly warehouse load" or "Hourly CRM sync". Several tasks will share it, and a name listing today's tasks ages badly. Select the Environment, which decides which environment's configuration the run uses. A schedule belongs to one environment, so use separate schedules for Develop

Configure global parametersA global parameter is a named value you define once and reuse across scripts, queries, and commands. Each parameter is referenced as a token, for example {$AppSecret}, and the execution engine substitutes the real value when a task runs.This means you change a value in one place rather than in every package that uses it, and a secret never has to be typed into a script where it can be read.Cloud only. This article is aimed at cloud customers. If you are running an on-prem installation, see Global Parameters.The token is substituted when the task runs, not in TimeXtender Data Platform. While you are editing, {$AppSecret} stays as literal text. It becomes the real value only when the package executes. A script that looks incomplete in the editor is usually correct, and a script you test by pasting the token into a terminal will fail.PrerequisitesTo manage global parameters, you need to be a global administrator or an administrator on the Workspaces group. If th

Two products ship alongside Timextender Data Platform 26.3: Xpilot Analytics, which reaches general availability, and the Timextender MCP Server, whose query engine has been rebuilt to provide more consistent and accurate results. Xpilot Analytics is part of Timextender Data Platform and is upgraded with it — there is nothing separate to install. The Timextender MCP Server runs on your own machine, so once your platform has been upgraded to 26.3, download the new version from the Downloads page in TDP and run the installer. Dive in below. Xpilot Analytics Xpilot Analytics — asking questions of your data model in plain language and getting a chart or a number back — reaches general availability in 26.3. This release is mostly about making its answers trustworthy and its reasoning visible, plus two pieces of groundwork that matter if you operate under EU rules. Agent personas You can now create personas and scope them to a workspace, then pick one at the start of a chat. A persona shapes

Create a Power BI Refresh packageA Power BI Refresh package triggers a dataset refresh. Its point is ordering: put it after the load that fills the warehouse, and the report refreshes when the data is ready rather than on a clock that assumes the load finished.The service principal must be granted access in Power BI itself. An Azure App Registration that works for other Azure types lists no workspaces here until two things are true in Power BI, neither of which is done in TimeXtender Data Platform. First, the tenant setting Allow service principals to use Power BI APIs is enabled for a security group the App Registration belongs to. Second, the App Registration is added as a member or admin of the workspace holding the dataset. The editor states it: only workspaces the data provider's service principal has been given access to are listed. An empty list is a permissions answer.PrerequisitesAn Azure App Registration data provider in the workspace. That principal granted access in Power B

Create a Microsoft Fabric Notebook packageA Microsoft Fabric Notebook package runs a notebook in a Fabric workspace as an orchestrated step.The service principal needs a role in the Fabric workspace. This type uses a Microsoft Fabric data provider rather than a plain App Registration, and the workspace list depends on Fabric permissions rather than Azure ones. The editor states it: Only workspaces the data provider's service principal has been given a role in are listed. An empty workspace list means the principal has not been added to the workspace in Fabric. As with Power BI, service principal access may also need enabling at tenant level.PrerequisitesA Microsoft Fabric data provider in the workspace. The principal given a role in the Fabric workspace holding the notebook. A notebook that can run unattended. A notebook that expects interactive input will wait indefinitely.Custom JSONBeyond the workspace and notebook, the editor accepts an optional Custom JSON payload, which is how yo

Create a Data Transfer packageA Data Transfer package moves rows from a source to a destination, with optional column mapping and merge behaviour. It is the only type in the Data movement area, and the most configurable type in the product.Use it for point-to-point movement that does not justify a full TimeXtender Data Integration pipeline: copying a lookup table between systems, landing a CSV into a table, or pushing a small extract to a partner database.Either end can be a script. Source and destination can each be PowerShell instead of a table. The editor describes the options as Select PowerShell to produce the source data from a script and Select PowerShell to hand the rows to a script instead of a table. That makes this type a general-purpose row pipe: read from an API with a script and write to a table, or read a table and hand each row to a script. It also means a data transfer in your flow may contain code, which is worth knowing when you are auditing what runs.PrerequisitesA

Create a Data Provider Command packageA Data Provider Command package runs SQL against one of the workspace's data provider connections. Use it for the database housekeeping that belongs in the nightly flow rather than in a maintenance plan: rebuilding indexes, refreshing a materialised table, or calling a stored procedure that stamps a load as complete.It reuses connections you have already defined, so there is no new credential to manage.PrerequisitesA data provider connection in the workspace, pointing at a database the command may write to. The command runs with that connection's credentials, so its permissions set the limit on what the package can do.Two modesThe editor works one of two ways, switched by a toggle:Stored procedure, the default. Select a schema, then a procedure, and the editor detects its parameters for you to fill in. Custom SQL. Write the statement yourself. The toggle description reads Toggle on to run a custom SQL statement instead of a stored procedure.Prefer

Create an Azure Synapse packageAn Azure Synapse package triggers a pipeline in a Synapse Analytics workspace, so a Synapse pipeline becomes one step in an orchestration flow rather than something scheduled separately inside Synapse.Listing pipelines needs a Synapse role as well as an Azure one. Azure RBAC gets the service principal as far as seeing the workspace. Listing the pipelines inside it needs a role granted in Synapse Studio, at minimum Synapse Artifact User. A principal with Contributor on the resource group can therefore show you a workspace and an empty pipeline list, which means the second grant is missing.PrerequisitesAn Azure App Registration data provider in the workspace. The principal able to enumerate resource groups in the subscription. Without that, the chain stops before the workspace, because Resource group is required and accepts a selection only. The principal granted a Synapse Artifact User role, or higher, in the Synapse workspace.The selection chainFive field

Create a TimeXtender SaaS packageA Timextender SaaS package runs an execution job in TimeXtender Data Integration. Where the Ingest, Prepare and Deliver types each run one stage, this type runs a job that TimeXtender Data Integration itself defines, typically several stages together.Which of the four TimeXtender Data Integration types do I want? Use Timextender SaaS when TimeXtender Data Integration already has an execution job that does what you want, and you only need orchestration to start it at the right moment. Use Ingest, Prepare or Deliver when you want the stages as separate orchestration steps, so that a failed ingest visibly stops the transform and each stage can be retried on its own. The second shape gives more detailed logs and finer retries. The first is less to maintain when TimeXtender Data Integration already owns the sequencing.PrerequisitesA TimeXtender Data Integration connection in the workspace, and an execution job defined in that instance.Create the packageGo to

Create an Azure Databricks packageAn Azure Databricks package runs an existing job on a Databricks workspace and can pass it parameters. Use it when the notebook or pipeline logic belongs in Databricks but its place in the nightly sequence belongs in orchestration.Two permission systems are involved. Azure RBAC gets the service principal as far as the workspace. Seeing a job listed inside that workspace needs permission on the job itself, granted in Databricks. A workspace that lists with an empty job list means the second grant is missing.PrerequisitesAn Azure App Registration data provider in the workspace. The principal able to enumerate resource groups. The selection chain cannot get past that field otherwise, because it accepts a selection only. The principal granted access to the job in Databricks. A job that already exists. This package type triggers jobs, it does not define them.The selection chainEach field loads the next: Data provider > Subscription > Resource group &g

Create an Azure Data Factory packageAn Azure Data Factory package triggers a pipeline in one of your data factories and waits for it to finish. Use it to put an existing Azure Data Factory pipeline into an orchestration flow, so that what happens before and after it is governed in one place.The package waits, and inherits the pipeline's outcome. The package polls the pipeline run until it completes, and reports success only when Azure reports Succeeded. Any other final state fails the package, so a downstream step in a process map does not run on a failed load. Allow for the pipeline's normal runtime when you set the package timeout.PrerequisitesAn Azure App Registration data provider in the workspace whose service principal can see the data factory. The subscription, resource group, factory and pipeline are all discovered from that provider.Selecting a Data provider loads its factories, and selecting a factory loads that factory's pipelines. If either list comes back empty, the servic

Create a PowerShell packageA PowerShell package runs a PowerShell script as a step in an orchestration flow. Use it for the small pieces of work that sit between your data tasks: calling a REST endpoint, waiting for a file to land, posting a notification, or prompting an external system.Everything the script writes to standard output is captured in the execution log, so a package is also a practical way to record what happened during a run.PowerShell or Azure PowerShell. Searching the package picker for PowerShell returns two types. PowerShell, covered on this page, runs a plain script and needs no credential. Azure PowerShell runs an Az module script inside an Azure context and requires an App Registration data provider. See Create an Azure PowerShell package.PrerequisitesPermission to create packages in the workspace. Nothing else: this package type has no data provider, no connection and no external resource to set up first. A decision about where the script should run, because it c