Nativo Connector for SSAS

In this article you will learn how to integrate Nativo data in SSAS without coding in just a few clicks (live / bi-directional connection to Nativo). Nativo Connector can be used to integrated operations supported by Nativo REST API..

Using Nativo Connector you will be able to connect, read, and write data from within SSAS. Follow the steps below to see how we would accomplish that.

Download Documentation

The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc.

If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started.

Connect to Nativo in other apps

Connect to Nativo in SSIS

Connect to Nativo in SQL Server

Connect to Nativo in Power BI

Connect to Nativo in SSRS

Connect to Nativo in Informatica

Connect to Nativo in MS Access

Connect to Nativo in MS Excel

Connect to Nativo in C#

Connect to Nativo in Python

Connect to Nativo in JAVA

Connect to Nativo in Tableau

Connect to Nativo in SAP Crystal Reports

Connect to Nativo in Azure Data Factory (Pipeline)

Connect to Nativo in Azure Data Factory (SSIS)

Connect to Nativo in Talend Studio

Connect to Nativo in UiPath

Connect to Nativo in PowerShell

Connect to Nativo in ODBC

Create Data Source in ZappySys Data Gateway based on API Driver

Download and install ZappySys ODBC PowerPack.
Search for gateway in start menu and Open ZappySys Data Gateway:
Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:
Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys API Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.

NativoDSN
When the Configuration window appears give your data source a name if you haven't done that already, then select "Nativo" from the list of Popular Connectors. If "Nativo" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

NativoDSN

Nativo

Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

Http [Http]

Please refer to below API Reference (External Site) link for Http [Http]

https://api-docs.nativo.com/docs/introduction

Fill in all required parameters and set optional parameters if needed:

NativoDSN

Nativo

Http [Http]

https://api.nativo.com/v2

Required Parameters
Optional Parameters
Api Key	Fill in the parameter...
Api Secret	Fill in the parameter...
RetryMode	Fill in the parameter...
RetryStatusCodeList	Fill in the parameter...
RetryCountMax	Fill in the parameter...
RetryMultiplyWaitTime	Fill in the parameter...

Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
Click OK to finish creating the data source.

Read Nativo data in SSAS cube

With the data source created in the Data Gateway (previous step), we're now ready to read Nativo data in an SSAS cube. Before we dive in, open Visual Studio and create a new Analysis Services project. Then, you're all set!

In the example below, we use Multidimensional and Data Mining Analysis Services project, but it should work with Tabular project too.

Create data source based on ZappySys Data Gateway

Let's start by creating a data source for a cube, based on the Data Gateway's data source we created earlier. So, what are we waiting for? Let's do it!

Create a new data source:
Once a window opens, select Create a data source based on an existing or new connection option and click New...:
Here things become a little complicated, but do not despair, it's only for a little while. Just perform these little steps:
- Select Native OLE DB\SQL Server Native Client 11.0 as provider.
- Enter your Server name (or IP address) and Port, separated by a comma.
- Select SQL Server Authentication option for authentication.
- Input User name which has admin permissions in the ZappySys Data Gateway.
- In Database name field enter the same data source name you use in the ZappySys Data Gateway.
- Hopefully, our hard work is done, when we Test Connection.
NativoDSN

NativoDSN
If SQL Server Native Client 11.0 is not listed as Native OLE DB provider, try using these:
- Microsoft OLE DB Driver for SQL Server
- Microsoft OLE DB Provider for SQL Server
Indeed, life is easy again:

Add data source view

We have data source in place, it's now time to add a data source view. Let's not waste a single second and get on to it!

Start by right-clicking on Data Source Views and then choosing New Data Source View...:
Select the previously created data source and click Next:
Ignore the Name Matching window and click Next.
Add the tables you will use in your SSAS cube:
For cube dimensions, consider creating a Virtual Table in the Data Gateway's data source. Use the DISTINCT keyword in the SELECT statement to get unique values from the facts table, like this:
```
SELECT DISTINCT Country FROM Customers
```
For demonstration purposes we are using sample tables which may not be available in Nativo.
Review your data source view and click Finish:
Add the missing table relationships and you're done!

Create cube

We have a data source view ready to be used by our cube. Let's create one!

Start by right-clicking on Cubes and selecting New Cube... menu item:
Select tables you will use for the measures:
And then select the measures themselves:
Don't stop and select the dimensions too:
Move along and click Finish before the final steps:
Review your cube before processing it:
It's time for the grand finale! Hit Process... to create the cube:
A splendid success!

Execute MDX query

The cube is created and processed. It's time to reap what we sow! Just execute an MDX query and get Nativo data in your SSAS cube:

Execute MDX in SSAS cube to read API data

Advanced topics

Create Custom Stored Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
Enter the desired Procedure name and click on OK:
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
```
CREATE PROCEDURE [usp_get_orders]
    @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
 AS
    SELECT * FROM Orders where OrderDate >= '<@fromdate>';
```
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
```
Exec usp_get_orders '1996-01-01';
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

Go to Custom Objects Tab and Click on Add button and Select Add Table:
Enter the desired Table name and click on OK:
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
```
SELECT
  "ShipCountry",
  "OrderID",
  "CustomerID",
  "EmployeeID",
  "OrderDate",
  "RequiredDate",
  "ShippedDate",
  "ShipVia",
  "Freight",
  "ShipName",
  "ShipAddress",
  "ShipCity",
  "ShipRegion",
  "ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'
```
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
```
SELECT * FROM "vt__usa_orders_only"
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Actions supported by Nativo Connector

Nativo Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

Read Campaign Data

[Read more...]

Parameter	Description
advertiser_id	Return campaigns only for this advertiser.

Read Advertisers Data

[Read more...]

Read Metrics

[Read more...]

Read DirectCampaign Data

[Read more...]

Read Preferred Campaign Data

[Read more...]

Read Managed Campaign Data

[Read more...]

Read Demand Campaign Data

[Read more...]

Read Auction Campaign Data

[Read more...]

Read Inventory Campaign Data

[Read more...]

Read Performance Campaign Data (Depriciated)

[Read more...]

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [Read more...]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body	Request Body content goes here
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Nativo Connector Examples for SSAS Connection

This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.

There are no examples

Conclusion

In this article we discussed how to connect to Nativo in SSAS and integrate data without any coding. Click here to Download Nativo Connector for SSAS and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Nativo Connector for SSAS Documentation

More integrations

Other application integration scenarios for Nativo

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC

Other connectors for SSAS

Amazon Ads

Amazon MWS

Amazon Selling Partner (SP-API)

Asana

Azure DevOps

Cosmos DB

DropBox

FastSpring

Google Drive

Hubspot

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

Nativo

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Stripe

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Download Nativo Connector for SSAS Documentation

Common Searches:

How to connect Nativo in SSAS?
How to get Nativo data in SSAS?
How to read Nativo data in SSAS?
How to load Nativo data in SSAS?
How to import Nativo data in SSAS?
How to pull Nativo data in SSAS?
How to push data to Nativo in SSAS?
How to write data to Nativo in SSAS?
How to POST data to Nativo in SSAS?
Call Nativo API in SSAS
Consume Nativo API in SSAS
Nativo SSAS Automate
Nativo SSAS Integration
Integration Nativo in SSAS
Consume real-time Nativo data in SSAS
Consume real-time Nativo API data in SSAS
Nativo ODBC Driver | ODBC Driver for Nativo | ODBC Nativo Driver | SSIS Nativo Source | SSIS Nativo Destination
Connect Nativo in SSAS
Load Nativo in SSAS
Load Nativo data in SSAS
Read Nativo data in SSAS
Nativo API Call in SSAS