Trello is a popular project management platform used by teams worldwide to organize tasks, track progress, and collaborate on projects. Many applications and tools need to integrate with Trello data for reporting, analytics, and business intelligence. Using Zappysys ODBC Driver for Trello, you can easily query card data, lists, and board information from Trello using standard SQL queries without writing custom code.

This tutorial demonstrates how to connect to Trello via ODBC and extract card and board data for use in your applications, databases, and reporting tools.

Prerequisites

1. A Windows or Linux system with an ODBC driver manager installed.
2. An ODBC-compatible application (Excel, Power BI, Tableau, database tool, etc.).
3. A Trello account with at least one board and list created.
4. Finally, install the ZappySys ODBC Driver.

Steps

Generate Trello API Key and Token

1. Go to the Trello Power-up page and log in to your account.
2. Create a new App and fill in the form.
   

   Trello – Create a new App

3. Inside your new App, click the API key, then generate a new API Key.
   

   Trello – API key page

4. In the API Key section, click the Token link to generate an access token.
   

   Trello – API key and Token link

5. Choose the token’s expiration time (Recommended: 30 days for security).
6. Review the permissions and click Create Token.
7. Copy the generated token and store it securely.
8. You now have both your API Key and Token. Keep these credentials confidential.

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

 Configure the Connection and API Settings

1. In the Base URL field, enter the URL:
   

   https://api.trello.com/1/members/me/boards?key={{TrelloApiKey}}&token={{TrelloToken}}

   For more examples:
   GET /boards/{boardId}/cards — Retrieve all cards from a specific board
GET /boards/{boardId}/lists — Retrieve all lists from a specific board
GET /cards/{cardId} — Retrieve details of a specific card

2. In the Request Method, use GET
3. You can use the Array filter to get the object you need.
4. Test the connection to check everything is working fine
   

   Trello – ODBC configuration

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   Trello – ODBC final result

Conclusion

Connecting to Trello via ODBC with the Zappysys ODBC Driver simplifies integrating project management data into your applications, databases, and reporting tools without custom development. By following the steps outlined in this tutorial, you can build reliable data connections that allow you to query Trello data using standard SQL and access it from Excel, Power BI, Python, SQL Server, and many other tools. Whether you need to track project progress, analyze team productivity, consolidate data from multiple teams, or create executive dashboards, Trello integration via ODBC provides a flexible and powerful solution.

Explore the full capabilities of the ZappySys ODBC Drivers to optimize your data access and integration strategy. You can extend this solution to include periodic data synchronization, real-time dashboards, and advanced transformations using your preferred analytics platform.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post How to extract data from Trello appeared first on ZappySys Blog.

Introduction

Claude.IA is a powerful cloud-native intelligence and automation platform that offers REST APIs for accessing AI models, data processing pipelines, and automation workflows. In this guide, we will demonstrate how to connect to Claude using the Zappysys ODBC Driver for REST APIs with API key authentication.

Whether you are using Claude for intelligent document processing, data enrichment, or automated workflows, you will learn how to configure ODBC connectivity without writing custom code. Zappysys ODBC REST driver handles all the complexity, allowing you to query Claude APIs using standard SQL and connect from any ODBC-compatible application.

Prerequisites

1. Windows operating system (32-bit or 64-bit).
2. Claude’s account has API access enabled.
3. Finally, do not forget to install ZappySys ODBC PowerPack.

Steps

Generate an API Key in Claude

1. Log in to your Cloude.IA account settings.
2. Navigate to Settings > API Keys.
3. Click Create Key.
4. Enter the workspace name (optional).
5. Enter a descriptive name for the API key.
6. Press Add to generate the token Key.
7. Save the API key in a secure location; you won’t be able to view it again.
   

   Cloude- Generate Token

8. Set Up Billing (required): add a payment method via the Billing Settings page.

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

 Configure the Connection and API Settings

1. In the Base URL field, enter:
   

   https://api.anthropic.com/v1

2. Select HTTP as the connection type, then click it to configure it.
3. Select Static Token/API Key as the Authentication Type.
4. Enter your Claude API key in the API Key field.
5. In the Header Name, enter x-api-key.
6. In the OAuth Scheme, use none.
7. Click OK to save the configuration.
8. Set up the HTTP Request Method to POST.
9. Use this JSON as the body:
   

   {
     "model": "claude-sonnet-4-6",
     "max_tokens": 1024,
     "messages": [
       {
         "role": "user",
         "content": "{YOUR-Message}"
       }
     ]
   }
10. In the Body content type, select 

    JSON(application/json)

11. Inside the header, add:

    anthropic-version: 2023-06-01

12. You can use the Array filter to get the object you need, and you can use

    $.messages[*].content

      to get only the message.
13. Test the connection to check everything is working fine
    

    Claude – JSON ODBC Driver configuration

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   Claude – JSON ODBC Driver result

Conclusion

You now have a secure and reliable ODBC connection to Claude. API Key authentication provides a simple and secure way to connect using the Zappysys ODBC Driver for REST APIs. With this connection configured, you can build powerful data extraction, transformation, and integration workflows using Claude’s intelligence and automation capabilities from any ODBC-compatible application without writing custom code.

Explore the full capabilities of the ZappySys ODBC PowerPack to optimize your data integration tasks. By applying this pattern, you can extend your solution to include additional data sources and create unified reporting across multiple cloud-based APIs.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post ODBC Tutorial: How to connect Claude to ODBC appeared first on ZappySys Blog.

This tutorial walks you through the process of extracting blog posts and comments data from Blogger using the REST API and Zappysys ODBC connectors. In this guide, you will learn how to authenticate with the Blogger REST API, configure a Zappysys ODBC data source, and query extracted data using ODBC. This approach eliminates the need for custom code and provides a standard interface for managing complex API integrations.

Zappysys provides a powerful ODBC connector that simplifies the integration of cloud-based APIs. We will demonstrate a practical pattern using ZappySys ODBC JSON Driver to extract data from Blogger APIs through any ODBC-compatible application.

Prerequisites

Before you begin, make sure you have the following:

• Windows operating system with ODBC Data Source Administrator available
• Access to a Blogger blog with appropriate permissions to read public posts and comments
• Finally, do not forget to install ZappySys ODBC PowerPack.

Steps

Create/Select a Project in the Google API Console

1. Navigate to the Google API Console.
2. Click on the Project Dropdown at the top bar and either select an existing project or create a new one by clicking CREATE PROJECT.
   

   Google Console – Create or select a project

3. Once the project is set, click ENABLE APIS AND SERVICES.
4. Search for the Blogger API v3 and click ENABLE.
   

   Google Console – Enable Blogger API

5. Return to the main screen and click on the OAuth Consent Screen tab.
6. Select the External user type and click CREATE.
7. Provide the application name, user support email, and developer contact information, then click SAVE AND CONTINUE.
8. Click through the remaining scopes and summary pages (no additional scopes are required for this tutorial), and click SAVE AND CONTINUE on each.
9. Move to the Credentials tab.
10. Click CREATE CREDENTIALS in the top bar, choose OAuth Client ID, select Desktop App as the Application Type, and click Create to obtain your Client ID and Secret.
    

    Google Console – Create credentials

11. Download the credentials JSON file and save it in a secure location on your development machine.

Creating a new ODBC DSN using ZappySys JSON Driver

1. Search for ODBC in the Windows Start menu and open the ODBC Data Source Administrator.
   
2. In the User DSN or System DSN tab, click Add to create a new data source.
3. In the ODBC Data Source Setup window, select the ZappySys JSON Driver and click Continue.
   

Configuring the ODBC connection for Blogger

1. Set the API Base URL to the Blogger API endpoint:
   https://www.googleapis.com/blogger/v3/blogs/{{Blog_ID}}/posts
2. Select OAUTH as the connection type, then click it to configure it.
3. Configure the authentication and provide the Client ID and Client Secret
4. Enter the Blogger Scope: https://www.googleapis.com/auth/blogger
5. Generate the token and test the connection
6. Click OK to save the connection
7. Set the HTTP method to GET.
8. Select the object you want to use in the Array Filter.
9. Test the connection by clicking Test Connection to verify your credentials and API access.
10. Save the configuration and name your ODBC DSN (e.g., “BloggerAPI”).
    

    ODBC JSON driver – Blogger connection

Preview the data

1. Once your ODBC DSN is configured, go to the preview tab.
2. Select the table you want to use.
3. Press the Preview data button to see the result.
   

   ODBC JSON driver – Blogger final result

Conclusion

You have successfully learned how to use Zappysys ODBC connectors to extract data from the Blogger
platform using the REST API. With ZappySys ODBC PowerPack, connecting Blogger to any ODBC-compatible application becomes
straightforward and reliable. By configuring the JSON ODBC driver for Blogger, you can access blog data from Excel, Power BI, Tableau, and other business intelligence tools.

Explore the full capabilities of the ZappySys ODBC PowerPack to optimize your data integration
tasks. By applying this pattern, you can extend your solution to include additional data sources and create unified reporting across multiple cloud-based APIs.

Need Help?

If you encounter any issues, our support team is here to help:

1. Live Chat — Use the chat widget (bottom-right corner of this page)
2. Email — support@zappysys.com
3. Support Center — Visit the ZappySys Support Portal

The post ODBC tutorial: How to connect Blogger to ODBC appeared first on ZappySys Blog.

OpenAI, the creators of ChatGPT, provide both a web interface and an API for seamless integration of their tools into applications. This article provides a comprehensive guide on how to establish a connection with the OpenAI API in SSIS using ZappySys JSON Source, enabling seamless data integration and retrieval.

Prerequisites

Before we perform steps listed in this article, you will need to make sure following prerequisites are met:

1. SSIS designer installed. Sometimes it is referred as BIDS or SSDT (download it from Microsoft site).
2. Basic knowledge of SSIS package development using Microsoft SQL Server Integration Services.
3. Make sure ZappySys SSIS PowerPack is installed (download it).
4. Optional (If you want to Deploy and Schedule ) – Deploy and Schedule SSIS Packages

Step-by-step guide to making a ChatGPT Rest API call

How to get an OpenAI API Key for ChatGPT

First, obtain your API key from OpenAI. This key is required for authenticating your requests.

To access the services, you will be required to set up an account with OpenAI. Click here to create your account. Once your account has been successfully created, proceed to log in to your OpenAI account.

You can find the API key by following these steps:

1. Navigate to the top right corner of the screen.
2. Click on your account name.
3. From the drop-down menu, select “API Keys.”
4. Alternatively, you can directly access the API Keys section by clicking here.

To generate a new secret key, please follow these steps:

1. Go to the API Keys page.
2. Look for the “Create new secret key” button.
3. Click the button to generate a new secret key.

Generate a new key

Upon generation, your API key will be visible on the screen. It’s crucial to copy the key and store it in a secure location immediately, as it will not be displayed again for security purposes.

The new key

Now that you have your API key, you can begin utilizing it to make calls with your components. A preliminary example involves retrieving a list of all available models in OpenAI. For detailed instructions, please refer to the API documentation available here.

ChatGPT Rest API call using JSON Source

1. Drag and Drop the SSIS Data Flow Task from the SSIS Toolbox.

Drag and drop Data flow task

2. Double-click on the DataFlow task to see the DataFlow designer surface.

3. From the SSIS toolbox drag and drop ZS JSON Source on the dataflow designer surface.

Drag and drop a JSON source

4. We will use this on the URL path:

https://api.openai.com/v1/models

5. In the HTTP headers grid add the following values by clicking Raw Edit button :

Authorization: Bearer YOUR_OPENAI_API_KEY
OpenAI-Organization: org-YQ9qpxxxxxxxxxxxxgoPi

6. Select your preferred Array Filter, simply click the “Select Filter” button. for this API call we need to select the

$.data[*]

7. Final step: Click ‘Preview’ to initiate the ChatGTP Rest API call. You will also find a demonstration within our component, along with the resulting output from the call, below.

ChatGPT call

That’s it the configuration for the ChatGPT Rest API call has been completed successfully.

Load ChatGPT data in SQL Server using Upsert Destination (Insert or Update)

ZappySys SSIS PowerPack makes it easy to load data from various sources such as REST, SOAP, JSON, XML, CSV or from other source into SQL Server, or PostgreSQL, or Amazon Redshift, or other targets. The Upsert Destination component allows you to automatically insert new records and update existing ones based on key columns. Below are the detailed steps to configure it.

Step 1: Add Upsert Destination to Data Flow

1. Drag and drop the Upsert Destination component from the SSIS Toolbox.
2. Connect your source component (e.g., JSON / REST / Other Source) to the Upsert Destination.

SSIS - Data Flow - Drang and Drop Upsert Destination Component

Step 2: Configure Target Connection

1. Double-click the Upsert Destination component to open the configuration window.
2. Under Connection, select an existing target connection or click NEW to create a new connection.
   • Example: SQL Server, or PostgreSQL, or Amazon Redshift.

Step 3: Select or Create Target Table

1. In the Target Table dropdown, select the table where you want to load data.
2. Optionally, click NEW to create a new table based on the source columns.

Configure SSIS Upsert Destination Connection - Loading data (REST / SOAP / JSON / XML /CSV) into SQL Server or other target using SSIS

Step 4: Map Columns

1. Go to the Mappings tab.
2. Click Auto Map to map source columns to target columns by name.
3. Ensure you check the Primary key column(s) that will determine whether a record is inserted or updated.
4. You can manually adjust the mappings if necessary.

SSIS Upsert Destination - Columns Mappings

Step 5: Save Settings

• Click OK to save the Upsert Destination configuration.

Step 6: Optional: Add Logging or Analysis

• You may add extra destination components to log the number of inserted vs. updated records for monitoring or auditing purposes.

Step 7: Execute the Package

• Run your SSIS package and verify that the data is correctly inserted and updated in the target table.

SSIS Upsert Destination Execution

Conclusion

In this article, we explored the seamless process of establishing a connection with ChatGPT in SSIS and integrating data effortlessly, all without the need for coding. Interested in trying it out yourself? Feel free to Download ZappySys SSIS PowerPack by clicking here and experience the simplicity firsthand. Should you have any lingering queries, please don’t hesitate to ask by clicking here or initiating a conversation with our experts via the live chat icon at the bottom-right corner of this page.

The post Call ChatGPT REST API in SSIS appeared first on ZappySys Blog.

Imagine this situation, you or users of your product wants to consume some REST API in ETL / BI / Programming Tools using ODBC / JDBC Driver interface but there are no ODBC / JDBC Driver available for that API and you dont even know coding? If you are in a situation No Problem !!! In this post you will learn how to create a custom ODBC Driver for API (i.e. REST / SOAP / OData) without writing code… and access in most BI / ETL / Reporting tools using Industry Standard such as ODBC Interface….. Yes you heard it right… 🙂

Generally speaking, creating an ODBC Driver requires a lot of coding effort and that’s why most vendors don’t invest in providing ODBC Driver and let you consume their API using code only. They assume that your company / team has really sharp C# / JAVA / C++ coders available 🙂 …. but we all know that coding is not cheap and not easy to maintain in long run.

Basically, the approach mentioned in this article requires you to create an XML File (or call it Connector File) and then consume it using API Driver (ODBC) So let’s get started!

API Connector File – The Concept

ZappySys has developed a highly flexible API Connector Framework which you can use to build API Connector Files which can be used by API ODBC Driver in different apps. This API Connector Framework is so flexible that it can handle pretty much any API out there.

Here are a few example connector files we built using the same framework. Don’t worry about various parts in those connector files for now, you might not need to implement all those. We will start simple and explain to you advanced use cases later.

Example Connector Files

• Youtube
• Stripe
• Jira
• Shopify

Basic Example of API Connector File

Here is a very simple example of some API to read Customers and Orders. Keep in mind most features are omitted for simplicity.

Below connector file shows few concepts which we will discuss later in this article. Such as API Base URL (i.e. Service URL), Authetication, Pagination, EndPoints, Metadata, Parameters, Templates, Tables so on.

1. Open Notepad
2. Copy / Paste below XMl in notepad and save as NorthwindConnector.xml
3. Then you can Create a new ODBC DSN as mentioned here and use our connector file for Testing (Use Saved Connector File Option on new DSN wizard).

NorthwindConnector.xml

<?xml version="1.0"?>
<ApiConfig Name="Northwind" Slug="northwind-api" Desc="Sample connector for Northwind OData Service" Logo="https://www.odata.org/assets/ODataLogo-96.png">
  <ServiceUrls>
    <ServiceUrl Name="V3_API" Url="https://services.odata.org/V3/Northwind/Northwind.svc"/>
    <ServiceUrl Name="V4_API" Url="https://services.odata.org/V4/Northwind/Northwind.svc"/>
  </ServiceUrls>


  <!-- Implement supported way to Authenticate API calls -->
  <Auths>
    <Auth Name="ApiKeyAuth" Type="Http" TestEndPoint="get_customers" ConnStr="CredentialType=Token;TokenAuthHeader=X-APIKEY;Password=[$ApiKey$]">
      <Params>
        <Param Name="ApiKey" Label="Enter your API  Key" Secret="True"/>
      </Params>
    </Auth>  
  </Auths>

  <!-- Reusable Templates (i.e. API Pagination Properties) -->
  <Template>
    <EndPoint Name="PaginatedCall">
      <Params>
        <Param Name="NextUrlAttributeOrExpr" Type="Property" Value="$.['odata.nextLink']"/>
      </Params>    
    </EndPoint>
  </Template>

  <!-- EndPoints -->
  <EndPoints>
    <EndPoint Name="get_customers" Template="PaginatedCall" Url="/Customers?$format=json" Filter="$.value[*]" Method="GET">
      <OutputColumns>
        <Column Name="CustomerID" Label="Id" DataType="DT_WSTR" Length="20"/>
        <Column Name="CompanyName" DataType="DT_WSTR" Length="100"/>
      </OutputColumns>
    </EndPoint>

    <EndPoint Name="get_orders" Template="PaginatedCall" Url="/Orders?$format=json" Filter="$.value[*]" Method="GET">

      <OutputColumns>
        <Column Name="OrderID" Label="Id" DataType="DT_I4"/>
        <Column Name="OrderDate" DataType="DT_DBTIMESTAMP"/>
        <Column Name="CustomerID" DataType="DT_WSTR" Length="20"/>
        <Column Name="Notes" DataType="DT_NTEXT"/>
      </OutputColumns>
    </EndPoint>
  </EndPoints>

  <!-- Tables (with SELECT, LOOKUP UPDATE, INSERT, DELETE operations. For Demo we have used just SELECT EndPoint) -->
  <Tables> 
    <Table Name="Orders" SelectEndPoint="get_orders"/>
    <Table Name="Customers" SelectEndPoint="get_customers"/>
  </Tables>
</ApiConfig>

Using API Connector File in Apps

Once API connector file is created

Use in ODBC Apps

Click here to see an example – Using API connector file in ODBC Apps (ODATA). For other popular apps check this page and click on desired app.

Here is how it may look like if we import the previous connector file in API Driver UI. Notice how we selected the V3 Base URL as API. Also, see how various connector file elements translated to Driver UI…. very cool right ?

Using Custom API Connector File – New ODBC DSN – ZappySys API Driver

Using Custom API Connector file in ZappySys API ODBC Driver

Here is the output from Preview Tab

Preview Data from Custom API Driver – Using ZappySys API Driver

Use in JAVA Apps

Click here to see an example – Using API connector file in JAVA based Apps (It uses ZappySys Data Gateway as Bridge rather than direct ODBC call in Java becuase JAVA doesnt support ODBC directly)

Use in SQL Server (T-SQL code)

Click here to see an example – Using API connector file in SQL Server (It uses ZappySys Data Gateway as Bridge rather than direct ODBC call in SQL Servr becuase of some known issues of direct ODBC)

Use in SSIS Package

Click here to see an example – Using API connector file in SSIS Packages. It uses native API Source / API Destination components.

Create / Edit Connector file using Wizard from API Driver UI

If you like to edit your file previously created using Wizard then you can do the following steps.

1. Assuming you have already setup ODBC DSN for API Connector File we previously created.
2. Open Odbc UI (search for “ODBC” in the start menu and select “ODBC Administrator”)
3. Double-click on the Data source you like to edit
4. On the Properties Tab > Go to Advanced Tab
5. Click on Customize – Current Connector File (If you wish to create a new API connector file then you can click on Create New Connector File Button instead)

Create / Edit Custom API Connector File – From API ODBC Driver UI

Create Connector file from SSIS JSON / XML Source UI Settings

If you are an SSIS user and you have configured JSON Source or XML Source then you convert those UI settings into a basic API connector file by going on API Template and clicking on Create New Connector File button like below.

Create a new Custom API Connector File – From SSIS JSON / XML Source UI

Create API Connector file from scratch

So far you have understood the basic ideas about connector files. Also explored creating / editing API Connector File using Wizard in ODBC / SSIS.

Now let’s look at concepts of creating connector file in detail.

Basic Properties (Name, Slug, Logo)

Coming Soon

Service URL (API Base URL)

Coming Soon

Authentication

Coming Soon

Templates

Coming Soon

Parameters

Coming Soon

EndPoints

Coming Soon

Metadata / OutputColumns

Coming Soon

Tables

Coming Soon

Contact Us – We will build Custom API Driver for you

If you are still not sure how to use all these on your own or you do not have time/experience… no worries. Contact us and we will provide you an estimate for building a custom API Driver / connector.

In the contact form above provide us following details (or as much as you can provide)

• Which connector do you like to build?
• How are you planning to consume that data (i.e. which apps e.g. Power BI, Tableau)?
• Your use case (e.g. read customer data from Zoho Invoice System)
• Include table / data feed names you prefer to read from (e.g. Read Invoices, Read/Write Customers)

Conclusion

In this article, we explored how easy it is to create your custom ODBC Driver for API using a powerful API Connector Framework. Download ODBC PowerPack and build your own API Driver in a few clicks.

The post How to create custom ODBC Driver for API without coding appeared first on ZappySys Blog.

In this blog post you will learn how to use Infor Compass JDBC driver in ODBC Apps (i.e. non-JAVA apps) such as Power BI, Excel, Informatica and many more listed here using JDBC-ODBC Bridge Driver. In other words, if you like to use Infor Compass data in your App / Programming language and App doesnt support using JDBC Driver Infor Provides then this article is for you. ZappySys has created a Bridge Driver which can translate ODBC calls to JDBC making it possible to call any JDBC driver in non Java Apps (i.e. ODBC Apps) written in languages like C++ / C#  / Python etc.

So lets get started.

Download Infor Compass JDBC Driver and ionapi file

Check below links to download and configure Infor Compass JDBC.

1. Download Infor Compass JDBC Driver (*.jar file)
2. Extract Driver files to local folder
3. Download and Configure *.ionapi file – Infor Compass JDBC Driver.ionapi file (Placed in same directory where JDBC driver is saved)

Setup JDK (Java Runtime)

Before you start using ZappySys JDBC Bridge Driver, we need to install JAVA Runtime (JRE) or Java Development Kit (JDK).

We recommend installing JDK21 or higher (other JRE / JDK version(s) might work too).

There are several ways to get Java Runtime Installer, but we recommend from following link. Skip below steps if you have JAVA Runtime already installed.

1. Download JDK 21 (i.e. Amazon Corrento OpenJDK distribution). Listed here
   Direct Download Link:  amazon-corretto-21-x64-windows-jdk.msi
2. Run the downloaded msi installer file
3. After it’s installed, you can confirm Java version by running the following command line. It will show
   

   java.exe -version

   Sample Output
   

   openjdk version "21.0.7" 2025-04-15 LTS
   OpenJDK Runtime Environment Temurin-21.0.7+6 (build 21.0.7+6-LTS)
   OpenJDK 64-Bit Server VM Temurin-21.0.7+6 (build 21.0.7+6-LTS, mixed mode, sharing)

Download Infor JDBC Driver / Generate ionapi Credentials File

To access infor Data using their official JDBC Driver you will need to do 2 things

1. Download Infor JDBC Driver locally
2. Create ionapi file locally

Read this link for more information

Here is the video Tutorial

Create ODBC DSN for Infor Compass JDBC Driver

In this section, you will learn how to Configure ODBC DSN. Later on, this DSN can be used to use ZappySys Driver. ODBC DSN can be stored at Machine Level (for all users) or the Current User Level. In this case, we are going to load data into Microsoft Excel from PostgreSQL Storage using ZappySys JDBC Bridge ODBC Driver.

1. Type odbcad32.exe in your search box and launch the DSN Config utility.
   
2. If you want access for yourself then stay on User DSN Tab. If you want to grant access to other users, then go to the System DSN tab. For SQL Server Integration go to the System Tab and add a new System DSN rather than User DSN. Click the New button.
   
3. From the Driver list Select ZappySys ODBC Driver. For this example, select [ZappySys JDBC Bridge Driver].
   

Configure ODBC DSN for Infor Compass Connectivity

Once you downloaded / extracted JDBC (*.jar) and *.ionapi files and saved them to the local disk you can configure ZappySys JDBC Bridge Driver like the below

1. Create a folder e.g. C:\Infor_Datalake
2. Extract jdbc driver files in that folder, keep ionapi file in the same folder too (v1.7 will look ionapi file under this folder)
3. Make sure do not rename ionapi file. It must be named as “Infor Compass JDBC Driver.ionapi”
   
   If you are getting this error (Infor Compass JDBC Driver.ionapi file is not found) then we suggest you copy ionapi file in the below locations too. If you are not planning to use Data Gateway / Linked Server then you can skip ionapi file copy to 3rd location (i.e. ZappySys.TdsServer.WindowsService folder).
   

   C:\Program Files (x86)\ZappySys\ZappySys ODBC PowerPack\JdbcBridgeDriverX64
   C:\Program Files (x86)\ZappySys\ZappySys ODBC PowerPack\JdbcBridgeDriverX86
   C:\Program Files (x86)\ZappySys\ZappySys ODBC PowerPack\ZappySys.TdsServer.WindowsService

4. Open ODBC DataSource UI by double clicking the DSN (you created in the previous section).
5. Enter JDBC Connection String as per this format
   

   jdbc:infordatalake://TENANTNNAME

6. Enter Driver class (Optional).
   

   com.infor.idl.jdbc.Driver

7. Enter User ID and Password is optional so keep it blank unless required by driver. Click Test Connection
   

   Using Infor Compass JDBC Driver in ODBC Apps via ZappySys JDBC Bridge Driver

8. Now you can go to Preview Tab and select Table from the dropdown and write query to preview data

Video Tutorial – ODBC-JDBC Bridge Driver

Connect Infor Compass Datalake in SQL Server (Linked Server)

So in our previous section, we saw how to connect using ODBC Driver but if you like to access Infor Datalake data in SQL Server then you have to use the Data gateway approach. Click here to learn more.

In Data Gateway Driver UI is pretty much the same as ODBC UI except few differences. You also need to configure the Linked server which requires extra steps. The above link is for a generic JDBC Driver but follow Infor Datalake JDBC-specific steps mentioned in the ODBC setup section in this article.

Troubleshooting Known Errors

Here in this section, we will discuss some known errors and its workaround.

The Infor Compass JDBC Driver.ionapi file is not found

If you get this error you can review this solution

Data Lake is not available /  Unable to verify trust for server certificate chain

If you get the following error then check this link for possible workarounds

JBR error: java.sql.SQLException: Data Lake is not available

at com.infor.idl.jdbc.Driver.connect(Driver.java:422) 
at DbConnection.Init(DbConnection.java:45) 

.......... 
.......... 
Unable to verify trust for server certificate chain [CN=mingle-ionapi.inforcloudsuite.com, CN=pa-trusted-ca.noble.loc, CN=noble-SUBCA-CA, DC=noble, DC=loc, CN=ROOTCA-CA, CN=ROOTCA-CA] .......... at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) 
.......... 
..........

Test Connection Hangs

This happens if you have not installed the latest Java version (i.e. Java 21 or higher) and you are using the latest JDBC, which doesn’t support Java8 (i.e. infor-compass-jdbc-2025.06.05.jar)

To fix this issue, uninstall the  older version of Java and install the new Java (e.g. v21 or higher) from here

Using Infor Compass ODBC-JDBC connection in various apps (e.g. Power BI, Excel, Informatica, SQL Server)

Once you create ODBC DSN you are ready to test that in any ODBC-compliant apps listed here

If your app is not listed in the above link, then no worries just find the Option to connect to ODBC in your App and use DSN we created in an earlier section.

ZappySys ODBC Drivers built using ODBC standard which is widely adopted by industry for a long time. Which mean the majority of BI Tools / Database Engines / ETL Tools already there will support native / 3rd party ODBC Drivers. Below is the small list of most popular tools / programming languages our Drivers support. If your tool / programming language doesn't appear in the below list, which means we have not documented use case but as long as your tool supports ODBC Standard, our drivers should work fine.  

BI / Reporting Tools Integration	ETL Tools Integration	Programming Languages Integration
Microsoft Power BI Tableau SSRS (SQL Reporting Services) QlikView /Qlik Sense MicroStrategy Google Sheet Microsoft Excel Microsoft Access Oracle OBIEE Many more (not in this list).....	Informatica PowerCenter (Windows) Informatica Cloud SSIS (SQL Integration Services) SQL Server Talend Data Studio Pentaho Kettle Oracle OBIEE Many more (not in this list).....	Visual Studio C# C++ JAVA Python PHP PowerShell T-SQL (Using Linked Server)

 

Conclusion

In this post we saw how easy it is to use the Infor Compass JDBC driver in any non-JAVA app in a few steps. Click here to download ZappySys JDBC Bridge Driver.

The post Connect to Infor Compass using JDBC Driver in ODBC Apps (e.g. SQL Server, Power BI, Excel, Informatica) appeared first on ZappySys Blog.

In this section, we will discuss how to register OAuth App to call Salesforce API using Client ID / Secret rather than using your User Id / Password. Once you follow these steps below to register your Salesforce App (OAuth App), at the end you will get a Client ID (sometimes referred to as App Id) and Client Secret (or App Secret). These two pieces can be used later on to call Salesforce API using OAuth. So let's get started.

Register Salesforce App (OAuth)

1. Login into your account and go to Setup as shown below (click on gear icon at the top right corner):
2. Then in the search bar input "app" and open App Manager:
3. Then click New Connected App to create a new OAuth App: NOTE: In some version, it may say New External Client App

   Look for one of the following buttons:

   • New Connected App (Classic name)

   • New External Client App (Lightning name)

   
4. Give your App a name and: - Enable OAuth Settings - Set callback URL to following two URLs (one in each line) https://login.salesforce.com/services/oauth2/success https://zappysys.com/oauth - Add an OAuth scope you want or simply add "Full access". - Add "Perform requests on your behalf at any time (offline_token)" scope to get a refresh token so that you don't have to re-authenticate each time requesting an access token: IMPORTANT: You can use "Access and manage your data (api)" if you do not like to grant full permission to this app but make sure you request same permission from the caller app too  (Example on ZappySys Salesforce Connection UI -> Advanced Tab -> Set scope as "api offline_access" rather than "full offline_access"
5. Click "Save".

Get Client Id and Client Secret for Salesforce Connected App

Once the App is created, we need to find out the App Id / Secret so we can use it for API calls.

1. Go to App Manager
2. Find out the recently created App and click View (click on the small arrow to the right)
3. Once App page is loaded you can Copy Consumer Key and Consumer Secret (click on reveal to see). Also copy anyone Call back URL (We will need this for OAuth Connection > Advanced Tab > Call Back URL or Redirect URL property depending on which ZappySys Product / Driver you are using)
4. That's it, you can now use these 3 pieces to ZappySys OAuth connection UI or on Salesforce Connection UI (new version with OAuth support). The above screenshot shows where to enter these 3 pieces in the New Salesforce Connection. For the OAuth Connection, the redirect URL goes to the Advanced Tab > Callback URL textbox.

Get Client Id and Secret for Salesforce External Client App

If you created a new App by clicking on the New External Client App button, then your App may not be visible in the App Manager Screen. In that case, find it below way. [caption id="attachment_11637" align="alignnone" width="1222"] Get Client Id, Client Secret - For New External Client App[/caption]

Enable Client Credentials Grant (Non-Interactive Run-As)

If you like to enable Non-Interactive mode, just like UserId / Password Authentication, but without actually passing a real UserId or Password on the Connection UI, then you can enable Client Credentials Flow as below. NOTE: Only the New version of ZappySys Salesforce Connection supports Client Credentials Grant. Version released after Nov 1, 2025 supports this grant type. [caption id="attachment_11639" align="alignnone" width="419"] Enable Salesforce Client Credentials Grant (Run As)[/caption]

(OPTIONAL) Configure Salesforce OAuth refresh token validity

By default, Salesforce Refresh Token doesn't expire once you generate. If you want to change the default behavior, follow these steps.

1. Go to "Manage Connected Apps" menu item and press on your App name:
2. Click "Edit Policies" to configure refresh token validity:
3. Set "All users may self-authorize" and "Refresh token is valid until revoked" options:
4. Click "Save".

Using Salesforce Connection with OAuth App in SSIS / ODBC

Once you have Client ID / Secret, you can use it in the Salesforce Connection in SSIS Connector / ODBC Driver for Salesforce like below (Only the new version will have OAuth option)

Troubleshooting Known Issues

Let’s look at some common issues with Salesforce Connection and how to fix them.

OAuth Error: Missing Required Code Challenge

When you click Generate Token button, you may get an error like the one below.

Salesforce OAuth Generate Token Error – Missing Required Code Challenge

Solution

Here is how to fix it.

For Salesforce Connection UI: Go to Advanced Tab => Check Enable PKCE Code Verifier option
–OR–
For OAuth Connection UI: Go to OAuth2 Grant Options Tab => Check Enable Code Verifier Option

Enable PKCE code verifier option – OAuth Connection for Salesforce.

The post How to register Salesforce App and obtain Client ID / Secret (for API Call / OAuth) appeared first on ZappySys Blog.

Downloading Gmail Attachments in SSIS is always a little more difficult than working with simple text or numeric columns. If you are not an SSIS expert, doing it for the first time may be challenging. That is why we created this article for you. This is a common request we receive, so we are bringing this article to you.

Gmail is the most popular email service in the world, and it can be helpful to automate and get valuable information from it. We will connect to Gmail with the REST API. For that, if you are not an experienced user of the REST API, do not worry. This article is for you. We will provide simple steps for the connection.

Requirements

To do it, we will need the following components:

1. SSDT for SSIS must be installed on your computer
2. ZappySys SSIS Powerpack should be installed. This Powerpack Plugin includes connectors to Gmail via the REST API.

Getting Started

Creating the connection

1. First of all, in SSDT, create a new SSIS project
2. To create a connection in SSDT, open the Connection Manager and select New Connection.
   

   Create a new connection

3. Select the ZS OAuth connection. This is a special connection included with the ZS.
   SSIS PowerPack installer that we will use to connect to Gmail.
   

   Select ZS-OAuth connector
4. In the ZS OAuth connection, select the Google API OAuth Provider and specify the following credentials and scope permissions:
   

   SSIS Gmail connection

   https://mail.google.com/
   https://www.googleapis.com/auth/gmail.modify
   https://www.googleapis.com/auth/gmail.readonly
   https://www.googleapis.com/auth/gmail.addons.current.message.readonly
   https://www.googleapis.com/auth/gmail.addons.current.message.action

Creating the package to download Gmail attachments in SSIS

1. First of all, drag and drop the Data Flow Task from the SSIS Toolbox and double-click it
   to edit.
   

   Drag and Drop SSIS Data Flow Task from SSIS Toolbox

2. Secondly, in the Data Flow, we will use the JSON Source to connect to Gmail and get the attachments. JSON Source is a ZappySys component used now only to connect to JSON files, but also to connect to REST API Servers that support JSON. In this case, Gmail REST API can send information in JSON Format. Use the connection created before.
3. Basically, we need to specify the URL of the Gmail attachment. In Gmail, the email attachment is inside the message. Then you need to specify the message-id and the Gmail attachment-id like this:
   

   Zappysys JSON source Gmail attachments configuration

   https://www.googleapis.com/gmail/v1/users/me/messages/{{User::email_id}}/attachments/{{User::attachment_id}}

4. Now, in the go-to columns tab, set the data type to DT_IMAGE and increase the length of the other columns’ DT_WSTR fields by 1000 and 1500. We set

   contentBytes

   to the

   DT_IMAGE

     datatype, it’s like

   varbinary(MAX)

   

   JSON Source Columns Tab – attachment datatype

5. Next, we will use the derived column to set the path to the local folder where the attachment will be stored. The derived column will be used to set the local path for the attachment. Make sure to specify valid paths with double backslashes, since backslashes are special characters. The derived column is a special transformation component that creates new columns. SSIS expressions.
   

   Derived columns – Gmail attachment file path

6. Also, we will require the Export column to download into a file. This component is specially used to get images or binary files into the file system.
   

   Export columns transformation – Gmail attachment

7. Finally, we will use the Trash destination to get the attachment and finish the flow. This one is also a ZappySys component ubiquitous.
8. Your package should be something like this:
   

   Final Result – Gmail attachment

9. The next step is to run it and test it.
10. If everything is fine, we will be able to see the file in your system.

Conclusion

In conclusion, we learned how to download Gmail attachments in SSIS. Basically, you need to use the ZappySys JSON Source to connect to Gmail via the REST API, then use the derived column component to specify the path to store the attachment. The next step is to use the Export column component to export the attachment. Finally, the ZS Trash destination is the attachment’s destination. If you liked this article, do not hesitate to continue testing and using ZappySys PowerPack for SSIS.

API Connector

Here are a few examples with our API connector for Gmail

API connector – Gmail get message attachments

API connector – Gmail download message attachments

The post Download Gmail Attachment in SSIS appeared first on ZappySys Blog.

In the previous article, we learned how to get data from AdWords in SSIS and basically control your AdWords account programmatically, outside the dashboard. In this one, we will continue on how to download AdWords report by using Google Ads API, ODBC, and ZappySys XML Driver. Let’s not waste our time and cut to the chase!

Prerequisites

1. Google Ads account up and running.
2. ZappySys ODBC PowerPack installed.

Step-by-Step – Download AdWords report

Get Developer Token

The first important step to access any Google Ads Account is to request a developer token. Click this link for step by step information. Watch a short video to get an overview of the entire process to access data via API.

Get Client Customer Id

Login into a non-manager account at https://ads.google.com and get your Client Customer Id:

Getting Google Ads (formerly AdWords) Client Customer Id

Copy it to a notepad, we will use it later.

Open ODBC Data Sources Manager

Search for "odbc" in your start menu and click on ODBC (64 bits). If you can't find this then you can also go to Start Menu > ZappySys > ODBC PowerPack > Click on ODBC Data Sources (64-Bit).

Open ODBC Data Source

Create ODBC Data Source based on ZappySys XML Driver

Select tab User DSN if you want to create a data source only for your user, or select System DSN to create a data source for all users or for OS services (e.g. SQL Server Agent):

Creating ZappySys XML Driver based data source

Configure authentication in the ODBC data source

Let’s authenticate first:

1. Select OAuth in Connection Type property.
2. Click Click to Configure link.
3. In OAuth Provider property select Google.
4. Then either select Use Default OAuth App or Use Custom OAuth App. For the latter, you will need to create a Google OAuth App yourself. It’s perfectly safe to use the default application, but if your company policy does not allow it, you may consider creating it yourself.
5. In Scopes enter:
   https://www.googleapis.com/auth/adwords
6. Then hit Generate Token and hit allow once asked.

Download AdWords report – Configuring authentication in ODBC data source

Proceed with HTTP request configuration

Then go on with configuring the data source:

Configuring HTTP request in ODBC data source to download an AdWords report

1. Give your data source a name
2. Then input this URL to download the report:
   https://adwords.google.com/api/adwords/reportdownload/v201809
   If the above URL does not work, get the working one from Google’s documentation.
3. Input POST as HTTP Request Method.
4. In Body enter this text:
   __rdxml=<reportDefinition xmlns="https://adwords.google.com/api/adwords/cm/v201809">
<selector>
<fields>CampaignId</fields>
<fields>Impressions</fields>
<fields>Clicks</fields>
<fields>Cost</fields>
<predicates>
<field>CampaignStatus</field>
<operator>IN</operator>
<values>ENABLED</values>
<values>PAUSED</values>
</predicates>
</selector>
<reportName>My Campaign Performance Report</reportName>
<reportType>CAMPAIGN_PERFORMANCE_REPORT</reportType>
<dateRangeType>LAST_7_DAYS</dateRangeType>
<downloadFormat>XML</downloadFormat>
</reportDefinition>
   This will display the data of CAMPAIGN_PERFORMANCE_REPORT report (campaign Id, impressions, clicks, and cost) for the last 7 days, for all campaigns that are enabled or paused. Make sure to visit the Google documentation page, which contains the information about how to download a different kind of report, how to configure predicates, etc.
5. In Body Content Type property select Form (application/x-www-form-urlencoded) option.
6. In HTTP Headers enter your developerToken and clientCustomerId retrieved in previous steps.

Select data filter in ODBC data source

Then hit Select Filter button and select row node, so that Array Filter is set to $.report.table.row[*]

Filtering on AdWords report data

If asked whether you want to treat the row element as an array, click “yes”. You can also go to the Xml Array Handling tab and see if the element row is specified there.

The Results

To view the results press Preview tab and then click Preview Data:

Previewing AdWords report data

Now you can use this data source and get the data into an Excel sheet, Power BI report, SQL Server (would need to create a data source in ZappySys Data Gateway instead) or elsewhere.

Reusing the data source

If your client application supports, you can override data source settings, such as HTTP body, in SQL query using WITH clause. In that case, you won’t need to create multiple data sources for different kind of reports; e.g.:

SELECT * FROM $ (RequestData='@c:\files\report-definition.txt')

SELECT * FROM $ (RequestData='__rdxml=<reportDefinition xmlns="https://adwords.google.com/api/adwords/cm/v201809">
<selector>
<fields>CampaignId</fields>
<fields>Cost</fields>
</selector>
<reportName>My Campaign Performance Report</reportName>
<reportType>CAMPAIGN_PERFORMANCE_REPORT</reportType>
<dateRangeType>LAST_7_DAYS</dateRangeType>
<downloadFormat>XML</downloadFormat>
</reportDefinition>')

Build a SQL query using the Query Builder:

Use Query Builder to construct SQL query and override data source properties

Conclusion

In this article, we learned how to download AdWords report using ODBC PowerPack and Google API. We created an ODBC data source based on XML Driver, then configured the OAuth authentication, HTTP request and data filtering without a single line of code. Then we previewed AdWords “Campaign Performance Report” data and finally, considered how to reuse the data source we created. Visit https://zappysys.com/blog/category/odbc-powerpack/odbc-app-integration/ for examples of how to integrate data sources based on ZappySys Drivers into applications.

References

https://developers.google.com/adwords/api/docs/guides/reporting

https://developers.google.com/adwords/api/docs/appendix/reports

https://developers.google.com/adwords/api/docs/appendix/reports/campaign-performance-report

The post Download AdWords report using Google Ads API, ODBC, and XML Driver appeared first on ZappySys Blog.

In our previous few posts we saw how to call various google apis in SSIS.  In this post lets learn how to call Google Search Console API in SSIS or other ODBC Compatible Apps such as Power BI, Informatica, SSRS using API Drivers for ODBC

About Google Search Console API (Google Webmaster API)

If you are new to Google Search Console API (i.e. Webmaster API) then start from this link. You can also check API Explorer here to test API requests.

Search API can be called by supplying either API key in URL  or use OAuth

Search Console V3 Covers following APIs (May add more in future)

Search Console API Call Example

Here is simple example of Search Console API call. Below example returns all sites you added under your search console account.

Request

GET https://www.googleapis.com/webmasters/v3/sites?key={YOUR_API_KEY}

Response

{
 "siteEntry": [
  {
   "siteUrl": "https://my-google-search-api-1.com/",
   "permissionLevel": "siteOwner"
  },
  {
   "siteUrl": "https://www.my-google-search-api-1.com/",
   "permissionLevel": "siteOwner"
  },
  {
   "siteUrl": "https://my-google-search-api-2.com/",
   "permissionLevel": "siteOwner"
  },
  {
   "siteUrl": "https://www.my-google-search-api-2.com/",
   "permissionLevel": "siteOwner"
  }
 ]
}

Step-By-Step – Call Search Console API in SSIS

Now lets look at very simple API call to list search console sites

1. Open SSIS Package
2. Drag and drop ZS REST API Task from SSIS tool box
   

   Drag and Drop ZS REST API Task from SSIS Toolbox

3. Now double click REST API Task and configure (Skip Step 5 if you use API Key instead of OAuth).
4. Enter API URL you like to call. For This example we will use simple URL as below
   OAuth based Authentication
   

   https://www.googleapis.com/webmasters/v3/sites/

   API Key based Authentication
   

   https://www.googleapis.com/webmasters/v3/sites/?key={YOUR_API_KEY}

5. If you want to use OAuth based credentials then perform the following steps
   1. Select URL from Connection 
   2. Click New ZS-OAUTH connection from Dropdown
   3. On the OAuth UI select Google as Provider
   4. Enter Scopes as below
      

      https://www.googleapis.com/auth/webmasters
      https://www.googleapis.com/auth/webmasters.readonly

   5. Click Generate Token. When you get Login Prompt enter your Google Account information and click Accept
   6. Click OK to Save OAuth UI
6. This is how it will look like if you use OAuth Connection
   

   Call Google Search Console API using SSIS REST API Task (OAuth Authentication)

7. Now click Test Request / Response to check if its working. You should get response like below

Read from Search Console Analytics API (query)

Now let’s look at how to call Search Console Analytics API (i.e. query) for Specified Site and extract data in tabular format using ZS JSON Source. In below example we will obtain search Impression, clicks, position etc for specified site. We will aggregate this over date and country (dimensions).

In this section you will learn how to use JSON Source Adapter to extract data from JSON file (In this case its Web URL).

1. Firstly, You need to Download and Install SSIS ZappySys PowerPack.
2. Once you finished first step, Open Visual Studio and Create New SSIS Package Project.
3. Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox.
   
4. Double click on the Data Flow task to see Data Flow designer surface.
5. From the SSIS toolbox drag and drop JSON Source on the Data Flow designer surface.
   
6. Double click JSON Source and configure like below
   1. Enter URL as below. Notice two things, first we used <<somedata,FUN_URLENC>> placeholder function to encode : and // in the URL so it become %2F %3A. We use

      --dont-escape--

        suffix at the end.
      For OAuth based Credentials
      

      https://www.googleapis.com/webmasters/v3/sites/<<https://mysite.com,FUN_URLENC>>/searchAnalytics/query--dont-escape--

      For API Key based Credentials
      

      https://www.googleapis.com/webmasters/v3/sites/<<https://mysite.com,FUN_URLENC>>/searchAnalytics/query/?key={YOUR_API_KEY}--dont-escape--

   2. Check Use Credentials and select OAuth connection (created earlier) (if you are using API key in URL then skip this step).
   3. Select POST as HTTP Method
   4. Enter Body for Query. Here are some examples for various queries you can use. For our case we want to group by date and country so use below
      

      {
      "startDate": "2019-01-01",
      "endDate": "2019-01-10",
      "dimensions" : ["date","country"]
      }

   5. Select Content Type as

      application/json

        from Content Type drop down.
   6. Select Filter or enter as 

      $.rows[*]

   7. Now go to Extract Multiple Arrays Tab and Check Array Flattening Option (on older version it was on the different Tab)
7. Click Preview and you will see your Google Search Console API data as below.
   

   Read from Google Search API Console (Analytics Query Endpoint) – JSON Source

Loading Google Search Console API data into SQL Server / Other Target

ZappySys SSIS PowerPack makes it easy to load data from various sources such as REST, SOAP, JSON, XML, CSV or from other source into SQL Server, or PostgreSQL, or Amazon Redshift, or other targets. The Upsert Destination component allows you to automatically insert new records and update existing ones based on key columns. Below are the detailed steps to configure it.

Step 1: Add Upsert Destination to Data Flow

1. Drag and drop the Upsert Destination component from the SSIS Toolbox.
2. Connect your source component (e.g., JSON / REST / Other Source) to the Upsert Destination.

SSIS - Data Flow - Drang and Drop Upsert Destination Component

Step 2: Configure Target Connection

1. Double-click the Upsert Destination component to open the configuration window.
2. Under Connection, select an existing target connection or click NEW to create a new connection.
   • Example: SQL Server, or PostgreSQL, or Amazon Redshift.

Step 3: Select or Create Target Table

1. In the Target Table dropdown, select the table where you want to load data.
2. Optionally, click NEW to create a new table based on the source columns.

Configure SSIS Upsert Destination Connection - Loading data (REST / SOAP / JSON / XML /CSV) into SQL Server or other target using SSIS

Step 4: Map Columns

1. Go to the Mappings tab.
2. Click Auto Map to map source columns to target columns by name.
3. Ensure you check the Primary key column(s) that will determine whether a record is inserted or updated.
4. You can manually adjust the mappings if necessary.

SSIS Upsert Destination - Columns Mappings

Step 5: Save Settings

• Click OK to save the Upsert Destination configuration.

Step 6: Optional: Add Logging or Analysis

• You may add extra destination components to log the number of inserted vs. updated records for monitoring or auditing purposes.

Step 7: Execute the Package

• Run your SSIS package and verify that the data is correctly inserted and updated in the target table.

SSIS Upsert Destination Execution

Import Google Search Console API data in Reporting / other ETL tools (ODBC Usecase)

There will be a time when you dont want to use SSIS connector like mentioned in previous sections but extract Google Search API data in Reporting Tools / Other ETL Platform.  Good news is you can use ZappySys ODBC Driver for JSON / REST API in ODBC Apps. See few popular ODBC Apps below.

• Power BI connection for Google Search Console API
• Excel connection for Google Search Console API
• Informatica connection for Google Search Console API
• MS Access connection for Google Search Console API
• C# , PowerShell, VB.net connection for Google Search Console API

Preview / Generate Query in JSON Driver / XML Driver

Load Google Search Console API in SQL Server without any ETL

Now let’s look at even more interesting integration scenario. If you have SQL Server and like to load Google Search Console API without any ETL then you can use Data Gateway

Read this article to learn how to load REST API in SQL Server without any coding (Use just T-SQL) .

You can write query like below to load data inside SQL Table.

SELECT * FROM OPENQUERY([MY_LINKED_SERVER]
, 'SELECT * FROM $
WITH(
	 Src=''https://www.googleapis.com/webmasters/v3/sites/<<https://mysite.com,FUN_URLENC>>/searchAnalytics/query/?key={YOUR_API_KEY}--dont-escape--''
	,Filter=''$.rows[*]''
	,RequestData=''{
"startDate": "2019-01-01",
"endDate": "2019-01-10",
"dimensions" : ["date","country"]
}''
	,RequestContentTypeCode=''ApplicationJson''
	,Header=''cache-control: no-cache || Accept: */*''
	,RequestMethod=''POST''
	,EnableArrayFlattening=''True''
)')

SSMS Output – Query REST API via Linked Server OPENQUERY statement (Connect to ZappySys Data Gateway)

Conclusion

So in this post we saw how easy it is to achieve total REST API integration in SSIS using JSON Connector. We also saw how to use ODBC Drivers to query REST API data inside Apps like Excel, MS Access, Informatica and other ODBC Apps using ODBC JSON / REST API driver. If you are SSIS User download SSIS PowerPack and try for FREE and if you don’t have SSIS in house and want to try more generic approach then Download ODBC PowerPack Drivers for FREE Trial.

The post Get data from Google Search Console API in SSIS and ODBC Apps appeared first on ZappySys Blog.