Recently active topics

In this release, we’ve implemented Federal Information Processing Standards (FIPS) support for SSL connections, ensuring that all cryptographic operations used by the CData Virtuality Server and JDBC driver can be performed using a FIPS-approved provider and FIPS-compatible keystores (you’ll need to enable it as described in our documentation).On the Server side, we’ve upgraded the embedded PostgreSQL used for the configuration database to v17 and significantly improved the structure of the Git repository (which means that it’s incompatible with the old version). Here’s what changed: we’ve improved the storage of recommended indexes, schedules and jobs, foreign functions, users and their roles and changed some other storage locations. Job owner, executor, and "enabled" flag are now saved in the same file as the job itself, materialized tables are stored together with their recommended optimizations (which are now stored in separate files), materialization jobs are located in the "jobs"

How can I get this Sql Server dbQuery to work? The INSERT is completing fine, but I need to get the inserted identity PK and Arc is not picking it up.<arc:set attr="db.query"> insert into table (...) values (...); select SCOPE_IDENTITY();</arc:set><arc:call op="dbQuery" in="db" out="results"> ...Is there a better way to get the identity? (I have to use ArcScript, the upsert connector is not an option)

AI-driven analytics can be slow and costly when LLMs repeatedly rebuild schemas and relationships across multiple data sources. Derived Views with CData Connect AI eliminate that overhead, reducing token usage while making multi-source analytics faster and more reliable at scale.Read the full article here: https://www.cdata.com/kb/articles/connect-ai-derived-views-performance.rst

Configuring SAML-Based Single Sign-On (SSO) with Microsoft Entra ID for CData Sync With SAML-based Single Sign-On (SSO), users can seamlessly authenticate through their organization’s identity provider (IdP), enabling secure, centralized access and just-in-time user provisioning at the time of login. This guide explains how to configure Microsoft Entra ID (formerly Azure Active Directory) as the SAML 2.0 identity provider for CData Sync, providing a unified, enterprise-grade authentication experience. Configuring Microsoft Entra ID SSO Authentication in CData Sync: Step 1: Create an Enterprise Application in Microsoft Entra ID  Log in to the Azure Portal: https://portal.azure.com  Navigate to:   Microsoft Entra ID > Enterprise applications > New application  In the Create your own application window:  Name: Sync SAML (or a name of your choice)  Option: Integrate any other application you don’t find in the gallery (non-gallery)  Click Create   Step 2: Configure SAML as the Sig

Private key certificates are used in AS2 and other MFT protocols to allow for secure elements of MFT transfers – notably, data encrypted with the matching public key certificate can be decrypted with the private key certificate, and messages signed with the private key certificate can be verified with the matching public key.   In any protocol that uses private and public key pairs, both parties to the transaction will need to be updated if a certificate is replaced, because trading partners that exchange messages with the owner of the private key will need to obtain and install the matching public key from the partner.   One thing that you will notice with certificates issued this way is that they have a built-in expiration date:   While, in theory, this validity period can be any validity period chosen by the issuer, in practice it is common to issue a certificate in the range of 1 to 5 years, depending on the security policy of the issuer.   When it comes time to replace your privat

Can you pull a trial balance into excel which will included historic month end balances. the standard trial balance query only seems to pull in the current trial balance as reflecting in xero.

The CData Salesforce connectivity solutions make it easy to synchronize data with Salesforce by enabling seamless UPSERT operations using External IDs. An External ID allows you to match records from your source system with corresponding Salesforce records ensuring accurate updates, preventing duplicates, and simplifying data integration workflows.In this article, you’ll learn how to: Create and configure an External ID field in Salesforce Connect to Salesforce using the CData Salesforce Driver Perform an UPSERT operation using the External ID for record matching To learn more, read: How to Use an External ID to Perform an UPSERT Operation against Salesforce