Recently active topics

When you are creating custom scripts or views you can use a parameter that converts all instances of that name to what it contains and set it to what the actual name is. The bonus of this is that you can change the name of fields and tables, without having to change anything in the script. It will also make it possible to auto map custom views. If you choose to delete something that uses the view, you will get a notification about this as well. Parameters In essence you can use parameters every time you have this screen. You get that every time you do something custom. Below are a list of features that use this, or variations of this screen: Custom Views Script Actions Stored Procedures User defined functions Custom Table Inserts Custom Field transformations Custom Data selection rules Deliver Instance Custom Scripts Calculated Measures Derived Measures Script Commands Dynamic variables You can use it in many ways. Add parameters to a view or script Say you want to join two tables via

Hi, I'd like to make a new data source connection using REST to connect with our Azure storage table. Thus far I have managed to get the connection setup, however pagination remains a issue. When testing our connection and following the steps in the debug logging file I see that when a table has a next: "x-ms-continuation-NextPartitionKey” and "x-ms-continuation-NextRowKey” it will return this in the header (not the body). But if the table doesn't have this it will stop since the "x-ms-continuation-NextPartitionKey” header was not found. As I am applying these pagination parameters as query parameter I need to be able to solve this issue. Is there maybe a way to apply a default value to these variables (manipulating query doesn't work as the variable itself already won't be found) or some way to dynamically replace a URL? Example table with no NextPartition/rowkey: When variable value replaced with default: Thanks for any input someone can provide. Kind regards, Robbert

Dynamic project variables allow you to create a SQL script that returns a single value, then use that value anywhere in your project, from data selection rules to execution package conditions. In this example, we will create a variable that returns the current date. Set up a dynamic variable How to use your variable Create a Fixed GetDate() variable Add a variable in another dynamic variable script Use the Value option Apply the variable as a data selection rule Set up a dynamic variable To create a dynamic project variable, right-click on the top-level project node and select Project Variable. In the Project Variable window, click Add. Give your variable a friendly name and select Dynamic from the Type dropdown. Choose when to resolve the variable from the Resolve Type dropdown menu. There are three types: Every time: The variable will be recalculated every time it is called. This is the default value. One Time: The variable will be calculated once, the first time it is called. That v

Hello. We are working on adding PBI datasets to the Orchestration process. I have followed these instructions and up until no. 3 in the Power BI part, everything has been a success. However, I’m supposed to choose Orchestration > Packages, select New > Power Bi Refresh. But Power BI Refresh is not an option: Is there a particular reason for this? I have added Power BI Refresh to the workspace (as a member currently, does it have to be an admin? That is not specified in the instructions at least.) I’m on TimeXtender Data Governance version 24.3.0.87 Best regards.

Is it possible to add the dynamic values used in a nested call to a table flattening.In this particular case the first call gets the list of documents and feed the id as a dynamic value to the 2nd call. The response doesn't include any reference to the document and without the id we cannot link the details to a document. I've tried to add it as a static node (name: Document_ID value {id})but that only results in errors.

On 4 June, we made a hotfix release with the changes listed below. CSV Version: 23.5.3.0 (TDI) / 1.1.5 (20.10 BU) / 16.4.6.0 (20.10 ODX) Fixed issue with SharePoint when reading more than one file (Cannot access disposed object). Exact Online Version: 10.2.0.0 (TDI) Fixed an issue with the ‘Set empty fields as null’ feature where it was applying the null on the wrong dataset. Fixed an issue where datetime was parsed into local time format instead of UTC. Excel Version: 23.7.0.0 (TDI) / 1.1.5 (20.10 BU) / 16.4.7.0 (20.10 ODX) Fixed issue with SharePoint when reading more than one file (“Cannot access disposed object”). Fixed issue where Excel was now trying to process unrelated files and failing. Hubspot Version: 10.2.0.0 (TDI) Fixed an issue with the ‘Set empty fields as null’ feature where it was applying the null on the wrong dataset. Fixed an issue where datetime was parsed into local time format instead of UTC. ODATA Version: 10.2.0.0 (TDI) Fixed an issue with the ‘Set empty fields

Today, we’ve published a minor release of TimeXtender Data Integration (v. 7026.1) that contains the changes listed below. We recommend that you upgrade if you’re affected by the issues that have been fixed. Fixed Fixed an issue that caused intermittent failures when transferring tables to a Prepare instance with ADF transfer enabled. Fixed a problem affecting selection rules on Fabric Prepare instances.

TimeXtender Classic provides two ways to extract data from a source table and add that data to another table. ADO.Net. SSIS packages Requirements to run ADO.Net Most of the requirements are added here. If you have a local SQL server installation, you need SQL Express as a minimum, though you will need a Standard edition if you want to use Analysis services. Is it externally located, you will need CLR, SMO and possibly these. Requirements to run SSIS As before most requirements are added here. No matter if you have the SQL server locally, or on another server, it requires at least SQL Standard edition, though for all features SQL Enterprise edition. Here is a list of features and for what edition. Is it located on another server you will need the remote SSIS execution feature as well. TimeXtender Classic Remote SSIS Execution package Features of ADO.Net There is no deployment needed on the transfer task You can deploy without access to the data source (But not execute) You can deploy an

Note: Applies To: Version 20 and earlier. The use of SSIS is not recommended in projects with ODX Server. The original article was written for Discovery Hub version: 17.12.8. and SQL Server 2016, with some updates for later versions. This article talks about TimeXtender features related to SSIS and the configuration options. SSIS Integration Options Before considering the options, we need to clarify the related features in TimeXtender. 1. SSIS server name on Project repository The SSIS server name specified on Project repository configuration is only for synchronizing data sources that use SSIS for transfer. Once you synchronize a data source, InformationSchema SSIS packages will be created accordingly on the SSIS server. 2. Use SSIS/SSIS folder on the project level On the project level, there is only the option to select if using Integration Services or not. The SSIS server names can only be specified on the individual database if it is different from the default database server. You

This article will give a brief overview of Dynamic Data Masking and how to set this up for specific fields in a TimeXtender Classic Data Warehouse table. What is Dynamic Data Masking? Dynamic Data Masking masks sensitive data from unauthorized users. An example of this would be if a bank representative is assisting a customer; they would only be able to see a masked version of the account number with only the last 4 digits being visible. Below you will see an example showing a partial data mask: Dynamic data masking helps prevent unauthorized access to sensitive data by enabling customers to specify how much sensitive data to reveal with minimal impact on the application layer. DDM can be configured on designated database fields to hide sensitive data in the result sets of queries. With DDM, the data in the database isn't changed. DDM is easy to use with existing applications, since masking rules are applied in the query results. Many applications can mask sensitive data without modify

Symptoms When running a data transfer or execution package in TimeXtender that connects to an IBM iSeries (AS/400) data source, you may encounter intermittent timeout errors. This typically occurs during periods when a backup is running on the IBM iSeries, potentially causing table locks. The error message appears after a prolonged wait and may look like the following: Error: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Operation cancelled by user. The wait operation timed out After this error, the data source connection may lose its provider and parameters, making it difficult to edit or reconfigure the connection. Attempts to import or modify the connection string can result in the provider being set to "Unknown provider" or the loss of all connection values. Cause The timeout occurs because the IBM iSeries table is locked, often due to a backup process running concurrently with the data transfer. Changing

Symptoms When finalizing the Orchestration setup for your TimeXtender environment, you notice that DEV processes start without issues, but PRD processes do not start from Orchestration, whether scheduled or triggered manually. You are able to manually run Ingest tasks on the PRD instance without issues. After reconfiguring Execution Services (switching between single and multiple services per environment), PRD processes still fail to start from Orchestration. No errors are initially shown in the web interface, but later, error emails are received after manual attempts to start processes from Orchestration. Error: No execution lock on instance Additionally, log output may include: log4net:ERROR You have tried to set a null level to root. log4net.Core.LogException: Error in the application. Cause This issue occurs when the Execution Service does not have the required lock on the instance needed to run the process. This can happen if: Execution Services are not correctly assigned to the a

Symptoms When connecting a TimeXtender REST data source using OAuth 2.0 authentication, you successfully complete the authentication process. However, when querying an API endpoint, the request fails with an authentication error. The issue occurs because the Authorization header is sent as bearer {accessToken} (with a lowercase "b"), which some API servers (especially those following OpenAPI standards) reject. If you manually change the header to use Bearer (with an uppercase "B") in tools like Postman, the request succeeds. Error: "code": "OPENAPIVALIDATOR_ERROR", "message": "Authentication Failure filter failed" Cause The issue is caused by TimeXtender sending the Authorization header with a lowercase "bearer" instead of the required uppercase "Bearer". Some API servers are case-sensitive and expect the exact string "Bearer" as per the OAuth 2.0 specification. Using the incorrect case leads to authentication failures. Resolution In the TimeXtender REST data source setup, locate the f

Symptoms When attempting to add a user to your company in the TimeXtender portal, you encounter an error message indicating that the user already exists. This occurs if the email address you are trying to add is already associated with another company in the portal. Error: TDI user already exists Cause This issue occurs because the email address you are trying to add is already registered under a different company in the TimeXtender portal. The system does not allow the same email address to be associated with multiple companies unless a workaround is used. Resolution Remove the user with the specified email address from the other company (e.g., if the user is already added remove them from that company). Once the user has been removed from the previous company, add them to the desired company in the portal. Alternatively, as a workaround, you can add a unique identifier to the email address using the "+" symbol (e.g., user+123@example.com) to create a distinct user for each company. N

Symptoms When starting a new deliver execution package in Orchestration, the process does not begin as expected. Instead, it continuously spins and eventually times out after the set period. Other similar processes work correctly, but the affected process appears to have multiple running instances, even though only one is actually running. Running the execution package directly from TimeXtender Data Integration works without issue, but attempts to execute from TimeXtender Orchestration fail. The problem may expand to other processes, particularly new ones, while existing ones continue to function. Error: TimeXtender Data Integration task did not start within the expected time, please make sure the service running your instance is working correctly by looking at our troubleshooting guide at https://support.timextender.com/timextender-orchestration-139/troubleshooting-timextender-data-integration-in-orchestration-3218 Cause This issue occurs when a new deliver or prepare instance is crea

Symptoms Error encountered when ingesting data from an MSSQL (Navision) source to Azure Data Lake using Azure Data Factory in TimeXtender. The process failed for a specific table with the following error message: Error: { "errorCode": "2200", "message": "ErrorCode=ParquetInvalidColumnName,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The column name is invalid. Column name cannot contain these character:[,;{}()\n\t=],Source=Microsoft.DataTransfer.Common,'", "failureType": "UserError", "target": "Copy Table", "details": [] } The error indicated that one or more column names contained invalid characters for Parquet files. The user identified columns with special characters (such as hyphens and non-ASCII characters) as potential causes. The issue was specific to certain tables, while others from the same source processed successfully. Cause The root cause was a stale or inconsistent pipeline definition in Azure Data Factory associated with the failing ingest t

This article describes how to automate an import to database action in Data Enrichment (DE). Steps Create Connections in Orchestration: Create connections to your source database and your DE database as Data Providers in Orchestration. Create a Data Transfer Package in Orchestration: Create a new Data Transfer package in Orchestration. Select your source data provider as the source and select the correct table. Select your DE provider as the destination. Schedule the transfer. Use Staging Table for Data Transfer: Transfer data to a staging table in the DE database. Create a merge in the Post Execution script to move data from staging to the actual table. Truncate the staging table in the Pre Execution script. Use Custom SQL script for the source if filtering is needed. Create Execute in Orchestration Action in MDM Table: Create a new Execute in Orchestration action in your DE table. Create a connection to your Orchestration database if it doesn't exist. Select your Data Transfer packag

Symptoms Error while connecting to Microsoft Dataverse using TimeXtender OData data source. Error Message received: Error: 401 Unauthorized. Resolution To resolve the issue of connecting to Microsoft Dataverse using the TimeXtender OData data source, follow these steps: Configure the OData Data Source: Open the TimeXtender Portal and select the Ingest Instance. Define the necessary authentication settings for the data source. Provide the URL to the OData metadata discovery EDMX file. For example: https://yourorg.api.crm.dynamics.com/api/data/v9.2/$metadata. Click the Configure button to open the Metadata discovery modal. In the modal, select the endpoints and possible expansions you want to configure. Click Submit to return to the data source configurations. Authentication Setup: Ensure you have registered an app in Azure under "App Registrations". Use the following URLs for authentication: Auth URL: https://login.microsoftonline.com//oauth2/authorize?resource=https://.api.crm4.dynamic

Hi, TX ver: latest I am getting an error when import metadata or doing table flattening. This worked fine earlier, before 3 june. Works fine using Postman. Any suggestion what I am missing? “One or more errors occurred.Failed to execute request for endpoint 'Get Charge Points'.One or more errors occurred.Cannot send a content-body with this verb-type. System.AggregateException: One or more errors occurred. ---> System.Net.ProtocolViolationException: Cannot send a content-body with this verb-type. at System.Net.HttpWebRequest.CheckProtocol(Boolean onRequestStream) at System.Net.HttpWebRequest.BeginGetRequestStream(AsyncCallback callback, Object state)” /Bjørn A.