ssrs Archives | ZappySys Blog

Import Google Analytics data into SQL Server / Reporting / ETL

ZappySys — Sat, 25 May 2019 19:17:14 +0000

Introduction

In our previous article we saw how to read Google Analytics data using SSIS. But what if you don’t use SSIS and you still like to Import Google Analytics data into SQL Server or Read inside other Reporting / ETL Apps (e.g. Excel, Power BI, MS Access … and many more). Not all BI tools comes with native driver / connectivity for Google Analytics. Sometimes they do offer Google Analytics connectivity but don’t offer feature you looking for (e.g. Sort, Segment Filter). In such case you have to look for solution outside.

Well not to worry we will show you how simple it is to connect to Google Analytics using ZappySys JSON Driver (For REST API / Files) in few mins. This driver is one of the best REST API drivers you can find in the market. It is so generic that it can virtually access any REST API you may find internally or on public sites (e.g. Facebook, Salesforce, Azure, AWS). Check these articles to see many more use cases of JSON Driver.

At the end of this article you will learn how to Query Google Analytics data in SSMS like below (Yes that’s correct .. Pretty Awesome!!! ).

Import Google Analytics Data into SQL Server Table (using T-SQL Code)

Requirements

This article talks about few tools and techniques in order to load API data in SQL Server. Please make sure following prerequisites are met.

Download and Install ZappySys ODBC PowerPack (This includes XML / JSON / REST API and few other drivers for SQL Server and ODBC connectivity in tools like Excel, Power BI, SSRS)
Make sure you have access to SQL Server Instance. If you cant find one still want to try what is mentioned in this article then install FREE SQL Express Edition
Confirm that you have SSMS Installed. If you don't have then you can download from here.

Testing Google Analytics API

If you are new to Google Analytics API then read little bit about Google Analytics REST API here. Google also offers a really good way to test Analytics API using Query Explorer Tool here. So please check that and understand how to craft correct REST API URL which will be used in the next section.

Using Google Analytics Query Explorer Tool – Create REST API Url (Dimension / Metrics Selection Browser)

Sample Google Analytics API Response

Behind the scene here is how API Request and Response Looks like for Google Analytics REST API. Notice that Authorization Header in below request is automatically added by ZappySys Driver or Query Testing tool above. Also notice nextLink attribute in response, its used to fetch more data. By default each response contains upto 10000 rows.

Request

GET https://www.googleapis.com/analytics/v3/data/ga?ids=ga:185737326&start-date=30daysAgo&end-date=yesterday&metrics=ga:avgSessionDuration&dimensions=ga:date
Authorization: Bearer ya29.GlwUxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Response

{
    "kind": "analytics#gaData",
    "id": "https://www.googleapis.com/analytics/v3/data/ga?ids=ga:123456789&dimensions=ga:date&metrics=ga:avgSessionDuration&start-date=30daysAgo&end-date=yesterday",
    "query": {
        "start-date": "30daysAgo",
        "end-date": "yesterday",
        "ids": "ga:123456789",
        "dimensions": "ga:date",
        "metrics": ["ga:avgSessionDuration"],
        "start-index": 1,
        "max-results": 1000
    },
    "itemsPerPage": 1000,
    "totalResults": 30,
    "selfLink": "https://www.googleapis.com/analytics/v3/data/ga?ids=ga:123456789&dimensions=ga:date&metrics=ga:avgSessionDuration&start-date=30daysAgo&end-date=yesterday",
    "nextLink": "https://www.googleapis.com/analytics/v3/data/ga?ids=ga:123456789&dimensions=ga:date&metrics=ga:avgSessionDuration&start-date=30daysAgo&end-date=yesterday&start-index=10001&max-results=10000",
    "profileInfo": {
        "profileId": "123456789",
        "accountId": "33445566",
        "webPropertyId": "UA-33445566-3",
        "internalWebPropertyId": "454545454",
        "profileName": "All Web Site Data",
        "tableId": "ga:123456789"
    },
    "containsSampledData": false,
    "columnHeaders": [
        {
            "name": "ga:date",
            "columnType": "DIMENSION",
            "dataType": "STRING"
        },
        {
            "name": "ga:avgSessionDuration",
            "columnType": "METRIC",
            "dataType": "TIME"
        }
    ], "totalsForAllResults": {
        "ga:avgSessionDuration": "49.3779488037477"
    },
    "rows": [ 
		["20190425", "401.38912133891213"], 
		["20190426", "512.49723756906077"], 
		["20190427", "11.53488372093024"], 
		["20190428", "432.148648648648646"], 
		["20190429", "234.650735294117645"],
		.......
		.......
		.......
		.......
		["20190525", "74.123435294117645"]
	]
}

Creating Google API Project (Obtain Client ID / Secret)

Very first step to call any Google API including Google Analytics is to create Google API Project and register OAuth App to obtain Client ID and Client Secret. If you dont want to go through this hassle and start easy way then ZappySys offers Inbuilt Default App on OAuth Connection UI but we strongly recommend you create your own app rather than using Default App because in Default App API call limit is shared by many. Your data is never shared with ZappySys in any case even you use Default App.

Here is how to create API Project to call Google API. Once you create Google API Project make sure you enable Google Analytics API.

So once you have Client ID and Client Secret we can move forward to the next step.

Loading Google Analytics data into SQL Server

In our previous article we saw in depth general idea on how to import REST API data in SQL Server (T-SQL Script) without relying on any ETL tools. Now lets look at step by step on how to load Google Analytics data into SQL Server.

In this example, our goal is to extract a Google Analytics report which shows average session duration and new users count by date (For last 30 days).

Setup ZappySys Data Gateway

Very first step to access any REST API Data inside SQL Server is to configure ZappySys Data Gateway. We covered this in previous article. But here are high level steps for initial setup of Data Gateway.

Search for Gateway in Start menu and Select ZappySys Data Gateway
Open ZappySys Data Gateway
Create new User in Data gateway on Users tab. Enter username and password (we will use this when we create Linked Server) . Check Admin Option
Add Data Gateway User

Setup Google Analytics API Data Source in Gateway / ODBC

Once gateway user is setup, now lets create a new Data Source for Google Analytics API. In this section we will talk how to create data source in gateway but most instructions can be used to create data source in ODBC too. At the end of this article we explained how to Launch ODBC Datasource UI. Step#1 and 2 are only different, all other steps same in ODBC DSN creation.

Click Add Data Source option (Select Native – JSON Driver )
Add Gateway Data Source (Native JSON Driver)
Click Edit to configure data source
Edit Gateway Data Source Settings
Now lets configure Driver settings. Click on Load Connection String button.
Load ZappySys Driver ConnectionString to configure UI

Enter the following ConnectionString to get started with predefined settings.
Change ids (111223344 to your own Profile ID in DataPath URL). Other URL Parameters explained in next section.

DRIVER={ZappySys JSON Driver};
DataPath='https://www.googleapis.com/analytics/v3/data/ga?ids=ga:11223344&start-date=30daysAgo&end-date=yesterday&metrics=ga:avgSessionDuration,ga:newUsers&dimensions=ga:date';
DataConnectionType=OAuth;
ScopeSeparator='{space}';
Scope='https://www.googleapis.com/auth/analytics https://www.googleapis.com/auth/analytics.readonly';
ServiceProvider=Google;
Filter='$.rows[*]';
ArrayTransformType=TransformSimpleTwoDimensionalArray;
ArrayTransColumnNameFilter='$.columnHeaders[*].name';
RequestMethod='GET';
NextUrlAttributeOrExpr='$.nextLink';
ClientId='xxxxxxxxxxxx';
ClientSecret='yyyyyyyyyyyyyy';
UseCustomApp='True'

URL used in DataPath is most important (parameters explained below) . You can use Query Explorer Tool here to build same URL.
```
https://www.googleapis.com/analytics/v3/data/ga?ids=ga:11223344&start-date=30daysAgo&end-date=yesterday&metrics=ga:avgSessionDuration,ga:newUsers&dimensions=ga:date
```
Parameters Explained

Here is some required parameters used in above REST API URL.
ids=ga:11223344
This is your Profile ID which you like to extract. Read more
start-date=30daysAgo
This can be yyyy-MM-dd or some other some predefined date keywords (e.g today, yesterday 10daysAgo). Read more.
end-date=yesterday
Same as above
metrics=ga:avgSessionDuration,ga:newUsers
This can be comma separated list of metrics you like to extract (max 10). Read more.
dimensions=ga:date
This can be comma separated list of metrics you like to extract (max 7). Read more.
Now its time to configure OAuth settings. Click on Configure Connection. Enter Client ID and Client Secret Obtained in the previous section (see here) and then click Generate Token as below.
Configure Google API Data Source / DSN (Google Analytics API Example)

Thats it now can click on Preview Tab and run sample query like below.

select * from $

–OR–
(Select Table name from dropdown and generate default query and then you can add alias , remove unwanted columns)

SELECT 
"ga:date" date, 
"ga:avgSessionDuration" avgSessionDuration,
"ga:newUsers" newUsers
FROM "rows"

–OR–
(Type custom query with your own URL generated from here, Change Profile ID – from 11223344 to your own id)

SELECT * FROM $
WITH(
	 Src='https://www.googleapis.com/analytics/v3/data/ga?ids=ga:11223344&start-date=30daysAgo&end-date=yesterday&metrics=ga:avgSessionDuration,ga:newUsers&dimensions=ga:date'
	,IncludeParentColumns='False'
)

Create Linked Server in SQL Server using T-SQL Script

Once our Gateway Data Source is configured we can now move to SQL Server Part to define Linked Server.

Here is how you can define linked server to access Google Analytics Data inside SQL Server. There are two ways to create Linked Server (1) via T-SQL script (2) via SSMS UI)

Here is how to create using Script.

USE [master]
GO

--drop existing linked server for same name if already found
EXEC master.dbo.sp_dropserver @server=N'GOOGLE_ANALYTICS_LS', @droplogins='droplogins'
GO

EXEC master.dbo.sp_addlinkedserver 
	@server = N'GOOGLE_ANALYTICS_LS', 
	@srvproduct=N'', 
	@provider=N'SQLNCLI', 
	@datasrc=N'localhost,5000', --this is host name and port number where  ZappySys Data Gateway is running
	@catalog=N'ZS-GA' --this must be same name as defined on Data Source tab Grid on ZappySys Data Gateway

EXEC master.dbo.sp_addlinkedsrvlogin 
	@rmtsrvname=N'GOOGLE_ANALYTICS_LS',
	@useself=N'False',
	@locallogin=NULL,
	@rmtuser=N'SOME-GATEWAY-USER', -- user name created on ZappySys Data Gateway
	@rmtpassword='SOME-GATEWAY-PASSWORD' -- password for ZappySys Data Gateway user
GO

Create Microsoft SQL Server Linked Server using SSMS UI

Once you configured data source in Gateway, we can now setup Linked Server in SQL Server to query API data.

Assuming you have installed SQL Server and SSMS. If not then get both for FREE from here: Get SQL Server Express and Get SSMS
Open SSMS and connect to SQL Server.
Go to Root > Server Objects > Linked Servers node. Right click and click New Linked Server...

Add Linked Server in SQL Server
Now enter linked server name, select Provider as SQL Native Client
Enter data source as GatewayServerName,PORT_NUMBER where server name is where ZappySys Gateway is running (Can be same as SQL Server machine or remote machine). Default PORT_NUMBER is 5000 but confirm on Data gateway > General tab incase its different.
Enter Catalog Name. This must match name from Data gateway Data sources grid > Name column

Configure Linked Server Provider, Catalog, Server, Port for ZappySys Data Gateway Connection
INFO:
- For SQL Server 2012, 2014, 2016, 2017, and 2019, use the SQL Server Native Client 11.0 as the Provider.
- For SQL Server 2022 or higher, use the Microsoft OLE DB Driver for SQL Server as the Provider.
Click on Security Tab and select last option "Be made using this security context". Enter your gateway user account here.
Optional: Under the Server Options Tab, Enable RPC and RPC Out and Disable Promotion of Distributed Transactions(MSDTC).

RPC and MSDTC Settings

You need to enable RPC Out if you plan to use EXEC(...) AT [MY_LINKED_SERVER_NAME] rather than OPENQUERY.
If don't enabled it, you will encounter the 'Server "MY_LINKED_SERVER_NAME" is not configured for RPC' error.

Query Example: EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]

If you plan to use 'INSERT INTO...EXEC(....) AT [MY_LINKED_SERVER_NAME]' in that case you need to Disable Promotion of Distributed Transactions(MSDTC).
If don't disabled it, you will encounter the 'The operation could not be performed because OLE DB provider "SQLNCLI11/MSOLEDBSQL" for linked server "MY_LINKED_SERVER_NAME" was unable to begin a distributed transaction.' error.

Query Example:
```
Insert Into dbo.Products 
EXEC('Select * from Products') AT [MY_LINKED_SERVER_NAME]
```
Click OK to save Linked Server

In SSMS execute below SQL query to test your connectivity.

SELECT * FROM OPENQUERY( MY_LINKED_SERVER_NAME, 'SELECT * FROM $')

--OR--

SELECT * FROM OPENQUERY( MY_LINKED_SERVER_NAME, 
'SELECT * FROM $
 WITH (Src=''https://services.odata.org/V3/Northwind/Northwind.svc/Customers?$format=json''
 ,Filter=''$.value[*]''
 ,DataFormat=''OData''
)');

Here is the preview after you run some REST API query in SQL Server. Notice that you can override default configuration by supplying many parameters in WITH clause (second query example in screenshot).

SSMS Output - Query REST API via Linked Server OPENQUERY statement (Connect to ZappySys Data Gateway)
You can wrap your queries inside View or wrap inside Stored procedure to parameterize. Here is an example of create view which calls REST API queries. Below View can be consumed like a normal table from any Tools or Programming Language which supports connectivity to SQL Server.
```
CREATE VIEW dbo.vwApiInvoices 
AS 
/*Call REST API inside SQL Server View*/
SELECT * FROM OPENQUERY( LS , 
'SELECT * FROM $
WITH (Src=''https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json''
	 ,Filter=''$.value[*]''
	 ,DataFormat=''OData''
)');

GO
```
Notice in above approach if you parameterize Stored Procedure then check this article to understand Dynamic Metadata.
That's it. We are now ready to move forward with more interesting things in next section.

Import Google Analytics Data into SQL Server Table (T-SQL Code)

Now lets see how to run sample query to import Google Analytics Data into SQL Server. Notice that how we have escaped quotes in OPENQUERY.
NOTE: Change id 11223344 with your own Id (use this tool to create URL)

select * into GaApiLoad from OPENQUERY([GOOGLE_ANALYTICS_LS] ,
'SELECT * FROM "rows"
WITH 
 (
   SRC=''https://www.googleapis.com/analytics/v3/data/ga?ids=ga:11223344&start-date=30daysAgo&end-date=yesterday&metrics=ga:avgSessionDuration,ga:newUsers&dimensions=ga:date''
  ,IncludeParentColumns=''False''
 )
')
select * from GaApiLoad

Import Google Analytics Data into SQL Server Table (using T-SQL Code)

Expose Google Analytics Data as View

To make it simple you can expose above query as SQL Server views so you can access them from any Reporting / ETL Tools.

CREATE VIEW vw_Google_Analytics_BounceRate_PageViews_Last30Days
AS
--change ids to your own Profile ID
select * from OPENQUERY([GOOGLE_ANALYTICS_LS] ,
'SELECT * FROM "rows"
WITH 
 (
   SRC=''https://www.googleapis.com/analytics/v3/data/ga?ids=ga:11223344&start-date=2019-04-01&end-date=2019-04-30&metrics=ga:bounceRate,ga:uniquePageviews&dimensions=ga:date''
  ,IncludeParentColumns=''False''
 )
')
GO

Making things Dynamic using Stored Procedure with Parameters

Now let’s make few things dynamic. We will change above query so we can pass Id, Dimensions and Metrics as parameters.

Run below script to Create a stored proc and fetch google analytics data in SQL Server.

use MyDatabase
go
create proc usp_GoogleAnalyticsData
	@ids varchar(1000),
	@startDate varchar(50)='30daysAgo',
	@endDate varchar(50)='yesterday',
	@metrics varchar(200)='ga:avgSessionDuration,ga:newUsers',
	@dimensions varchar(200)='ga:date'	
as

declare @sql varchar(4000)

set @sql='select * from OPENQUERY([GOOGLE_ANALYTICS_LS] ,
''SELECT * FROM "rows"
WITH 
 (
   SRC=''''https://www.googleapis.com/analytics/v3/data/ga?ids=ga:' + @ids 
   +'&start-date='+ @startDate 
   +'&end-date='+ @endDate 
   +'&metrics='+ @metrics 
   +'&dimensions='+ @dimensions 
   +'''''
  ,IncludeParentColumns=''''False''''
 )
'')'

print @sql
execute(@sql)

go

--Example: query google analytics data
exec usp_GoogleAnalyticsData 
	@ids='11223344',  --Change this ID - Obtain from here https://ga-dev-tools.appspot.com/query-explorer/
	@startDate ='30daysAgo',  --or like this 2019-04-01
	@endDate   ='yesterday', --or like this 2019-04-30
	@dimensions='ga:date', 
	@metrics   ='ga:bounceRate,ga:uniquePageviews'

Insert Google Analytics Data into table (Save Stored Procedure Output)

Now what if you like to save Stored Proc output into a table? Well for that you must create table with same structure as stored proc output and then use INSERT INTO sql like below.

--import google analytics data in a table
if(object_id('GaDataLoad') is not null)
	drop table GaDataLoad
create table GaDataLoad([Date] date, BounceRate numeric(10,5), PageViews numeric(10,5))  

insert into GaDataLoad
exec usp_GoogleAnalyticsData 
	@ids='11223344',  --Change this ID - Obtain from here https://ga-dev-tools.appspot.com/query-explorer/
	@startDate ='30daysAgo',  --or like this 2019-04-01
	@endDate   ='yesterday', --or like this 2019-04-30
	@dimensions='ga:date', 
	@metrics='ga:bounceRate,ga:uniquePageviews'

select * from GaDataLoad

Performance Tips / Handling data errors due to missing rows

By default ZappySys API Drivers sends minimum 2 API requests. First one to fetch metadata and second, third… for Data. There will be a time when you wont have any data and it may throw error about no records found because it fails to parse metadata. You can avoid such issue by supplying metadata before hand so you can avoid expensive API calls. Check this article see how you can supply cached metadata in your SQL Query as below. This will avoid Metadata call and speedup significantly. It will also avoid errors due to no rows found for specified criteria.

select * from OPENQUERY([GOOGLE_ANALYTICS_LS] ,
'SELECT * FROM "rows"
WITH 
 (
   SRC=''https://www.googleapis.com/analytics/v3/data/ga?ids=ga:11223344&start-date=30daysAgo&end-date=yesterday&metrics=ga:bounceRate,ga:uniquePageviews&dimensions=ga:date''
  ,IncludeParentColumns=''False''
  ,Meta=''[ 
     {"Name": "ga:date","Type": "String", "Length": 16 },
     {"Name": "ga:bounceRate", "Type": "String", "Length": 36 },
     {"Name": "ga:uniquePageviews", "Type": "String", "Length": 10 }
    ]''
 )
')

ODBC Connection – Google Analytics Data in Other Apps (e.g. SSRS / Power BI / Excel / Tableau)

So far we have talked accessing data inside SQL Server using Data Gateway Approach but what if you like to access in other apps ? Well you have three options.

Use Microsoft SQL Server Driver to call Linked Server Queries (OPENQUERY approach we saw earlier)
Access Google Analytics Data using ODBC connectivity
Use Microsoft SQL Server Driver to send direct SQL queries to Gateway (Bypass Linked Server – Use inner SQL query without OPENQUERY in this case)

Method-1 : Linked Server Approach

First approach most likely works in all cases because most apps will support connecting to SQL Server using OLEDB / ADO.net / ODBC / JDBC Drivers. So calling SQL Queries which uses Linked Server (i.e. OPENQUERY statement) is advisable.

Method-2 : ODBC Driver Approach

However in some cases this may not be possible (e.g. You don’t have SQL Server inhouse or you don’t want to rely on SQL Server to access API). In such case you can use ODBC connectivity in your app. Since ODBC is widely adopted standard most app out there (Except JAVA apps) should support ODBC Drivers. If you like to use this approach then create ODBC DSN rather than Data Gateway Data source and use it in your Reporting / ETL / Custom Apps.

Open ODBC Data Sources (Create DSN)

ODBC User DSN Tab: Add new Driver Screen

Method-3 : Direct connection to Data Gateway (By pass Linked Server)

Last option we suggest for cases like JAVA Apps / Linux / Mac machines where you cannot install ZappySys ODBC Drivers and you dont have option to use SQL Server Linked Server either. In such case you can try to send SQL Queries to Gateway directly using Microsoft SQL Server Compatible Drivers (i.e. ODBC /JDBC). See this example how we called API Queries inside JAVA Apps.

Google Analytics / REST API Integration in various apps

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 article we explored many ideas of JSON / API integration in SQL Server. We saw how to create OAuth App for Google API and import Google Analytics data into SQL Server Table without doing any ETL using pure T-SQL code (Query / Views /Stored Procs). You can Download FREE Trial of ODBC PowerPack and try yourself see how easy it is to query any API inside SQL Server and avoid expensive ETL processes.

The post Import Google Analytics data into SQL Server / Reporting / ETL appeared first on ZappySys Blog.

Read JIRA data in SSRS Reports (SQL Server Reporting Services)

ZappySys — Thu, 27 Dec 2018 13:04:45 +0000

Introduction

UPDATE: ZappySys has released a brand new API Connector for Jira Online which makes it much simpler to Read/Write Jira Data in ODBC compared to the steps listed in this article. You can still use steps from this article but if you are new to API or want to avoid learning curve with API then use newer approach.

Please visit this page to see all Pre-Configured ready to use API connectors which you can use in SSIS API Source / SSIS API Destination OR API ODBC Driver (for non-SSIS Apps such as Excel, Power BI, Informatica).

In our previous blog we saw how to read rest api in SSRS reports. We recommend you go through that article first. In this post we will look at specific example on How to read JIRA data in SSRS Reports (SQL Server Reporting Services), along with few other topics such as how to generate an API Token using Atlassian Account for JIRA REST API Call, how to read all Issues data from JIRA using our ODBC Driver and load it into the SSRS reports.

We will go through the steps to read data from JIRA and Load into SQL Server using JSON Driver of ODBC PowerPack

In nutshell, this post will focus on how to call JIRA API using ODBC PowerPack and how to create SSRS Report.

So let’s get started.

Requirements

Make sure you have SSRS designer installed (You can download SSDT BI for Visual Studio).
Finally, make sure to have ZappySys ODBC PowerPack installed.

What is JIRA

JIRA is Atlassian’s popular project- and issue-tracking platform used by development and technical support teams to get more work done and faster.

It combines:

issue tracking – a software application that allows to record and follow the progress of every problem or “issue” that user identifies until the problem is resolved.
agile project management – an iterative approach to planning and guiding project processes. customizable workflow, and a pluggable integration – integrates with Freshdesk, GitHub, Zendesk, Zapbook, Asana and so on.

Getting Started

First of all, we will see several examples. ZappySys includes an SSIS JSON Source Connector that will help you to call JIRA API, read various data from JIRA with SSIS and do many more actions using REST API. To learn more about JIRA API check this help file.

Generate API Token

To access JIRA data using REST API call you need to generate an API Token in your Atlassian account. Follow the steps mentioned below to generate API Token:

you can directly login to the JIRA Atlassian Cloud site with your credentials, and redirect to the JIRA Atlassian Cloud Account's Profile Page for generating an API Token.
Click API tokens, then Create API token.

Generate API Token - Step - 1
Create API Token - Give Label name to your API token which you are generating now

Generate API Token - Step - 2
Use Copy to the clipboard, and paste the token into your or elsewhere:
Note: * For security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token. * You should store the token securely, just as for any password.

Generate API Token - Step - 3
If you forgot API token, then you can Revoke your old API token and create new API token OR you can create multiple API tokens too.

Generate API token - Step - 4

Now we have successfully generated an API token. Let´s start with an example. In this example, we will show how to read Tasks/Issues data from JIRA and store that data into a SQL table with SSIS.

About JIRA REST API

JIRA On-premises and Cloud Version both offers REST API. Here are some examples of JIRA REST API. For reading JIRA REST API data we will use JIRA REST API Search method which returns data in JSON format. Search API support use of JQL Syntax to filter issues. If you don't specify JQL parameters in /search endpoint then all issues will be returned. Check this link to learn how to build JQL for JIRA REST API Call. If you don't have JIRA hosted instance yet but still want to try REST API Examples on public JIRA Server then try below URL (Its official JIRA site which lists their own issues). For example, try to copy below URL in a browser and hit enter.

https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER

Step-by-Step: Import JIRA data using REST API

Now once you have API token in the JIRA Atlassian Cloud website we can move to ODBC JSON Driver Configuration Part. For this example purpose you can use the following URL:

https://YOUR-DOMAIN.atlassian.net/rest/api/2/search?startAt=0&maxResults=100&jql=project=MYPROJECT

hence, your-domain is your Atlassian Cloud account’s domain name (we are using zappysys2.atlassian.net). Therefore startAt is the index of the first item returned in the page of results. And another maxResults is the maximum number of items that can be returned per page. Above all, each API endpoint may have a different limit for the number of items returned, and these limits may change without notice. (For more See this JIRA API Documentation for Pagination)

Configure Data Source in Gateway (ZappySys JSON / REST API Driver Example)

Now let's look at how to configure ZappySys Data Gateway. This feature acts as a bridge between Client App and ZappySys Drivers. Using data gateway you can use ZappySys Drivers inside applications / operating systems where ZappySys drivers may not be available directly for some reason (e.g. You don't have access to Server for Installation or System does not support ODBC drivers like JAVA programs). Click here to read more on various use cases of Data Gateway.

Configure Data Gateway User / Port

Now let's look at steps to configure Data Gateway after installation. We will also create a sample data source for ODATA API (i.e. JSON based REST API Service).

Assuming you have installed ZappySys ODBC PowerPack using default options (Which also enables Data Gateway Service)
Search "Gateway" in your start menu and click ZappySys Data Gateway

Open ZappySys Data Gateway
First make sure Gateway Service is running (Verify Start icon is disabled)
Also verify Port on General Tab

Port Number setting on ZappySys Data Gateway
Now go to Users tab. Click Add icon to add a new user. Check Is admin to give access to all data sources you add in future. If you don't check admin then you have to manually configure user permission for each data source.

Add Data Gateway User

Configure Data Source

After user is added, go to Data Sources tab. Click Add icon to create new data source. Select appropriate driver based on your API / File format. You can choose Generic ODBC option to read data from ODBC DSN or use Native Driver option.
```
NOTE: Whenever possible use native driver option for better performance / security and ease of use.
```
Add Gateway Data Source (Native JSON Driver)
Now it's time to connect with JIRA. Let's use JSON Driver Data source with the following URL. Change domain with your own domain.
```
https://{yourdomain}.atlassian.net/rest/api/2/search?startAt=0&maxResults=100
```
ODBC JSON Driver: Enter Request URL
It is time to configure the Other Settings. Select HTTP Connection Type from the Connection Type drop-down and Click on Click to Configure Link to Configure the Connection Manager.
[caption id="attachment_5596" align="alignnone" width="1245"] JIRA REST API Connection - Use ZappySys JSON Driver HTTP Connection[/caption] JIRA REST API Connection - Use ZappySys JSON Driver HTTP Connection
Now, we are going to set Pagination related configurations for JIRA Search request. Page number indicator must be startAt and maxResults value in URL must match with Increment By (i.e. 100)
ODBC JSON Driver - JIRA request Pagination Configurations Settings
After adding pagination parameters let's add JQL= search parameter to get specific data. Here we are searching the data by Project name and status. You can find more information about JQL on this link: Search JIRA like a boss with JQL Here is example JQL search query for Public JIRA site. Replace jira.atlassian.com and project JRASERVER with your own values.
```
https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER
https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status=Open
https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status in (Open,Done)
https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER AND status=Open order by lastViewed DESC
```
Search using JQL parameter
Click on Select Filter to set the Filter.
ODBC JSON Driver for JIRA API: Select Filter
You are done with the Configurations, Click on Test Connection to test the Connection.
ODBC JSON Driver - Test Connection
After that select the table from where you want to get data.
JSON Driver: Create Query of JSON data
Click on the Preview Data button to preview the data.
Preview issues table data
And that’s it, Now we will move forward to the next Phase.

Build your Own JQL Search queries for JIRA Issue

In previous sections we saw some basic JQL queries to search JIRA Issues using API call. Now lets look at how to build such queries using online UI (Think like a query builder). from JIRA.

JIRA has its own public Issue repository which you can browse any time by going here https://jira.atlassian.com/issues/
Now try to change filter settings for search criteria (E.g. change Project, Status etc)
You will notice when you make change your URL keeps changing too. From that URL you can extract ?jql=xxxxxxx part and use it as template for your own JIRA API search queries.

For more information check how to build JQL for JIRA REST API Call.

Create and configure new SSRS Reports (Using ODBC Connection)

Let’s create a new SSRS project.

In SSRS, in a new Reporting Service Project, add a new Data Source:
Add SSRS data source
Also, specify a name for the data source and in type select ODBC. Press Edit to select the ODBC connection for JSON and REST API and select the ZappySys Data Source name that we created before.
Add ODBC JSON Data Source
Now let’s create a new SSRS report which uses the API data source we created in the previous section.
Right-click on the Reports node and click Add New Report (Wizard mode)
Add new SSRS report
In New report, wizard window clicks on next button until you reach the step of query builder like below screen. Now Press the query builder button.
Note: You can also copy and paste the query directly into the Query string box which we created in the previous phase.
```
SELECT * FROM "issues"
```
Query builder
Now, press the Add table icon and go to Views. Select issues(DATA) and press Add.
SSRS Add Table
Now remove DATA. prefix from the query so that our query look’s like as below and Click Ok button:
```
SELECT issues.* FROM issues
```
Now press Next Button and select Tabular Report Type and go to next in the following option until the completing wizard and specify a name for the report and finally press the Finish button.
Now click on the Preview a report. It shows the report and exports the REST API data to Word, Excel, PowerPoint, etc:
SSRS Preview a Report
That’s all we have successfully imported the JIRA data in SSRS Reports (SQL Server Reporting Services).

Conclusion

In this blog, we have learned how to retrieve the data from JIRA using ODBC JSON Driver and then generated the SSRS Reports using those data with ODBC DSN in a very simple way. You can achieve many more functionalities with the use of ODBC PowerPack.

References

Finally, you can use the following links for more information about the use of JIRA API with our tools:

JIRA Documentation for API
Landing Page for ODBC JSON / REST API Driver, you can also find Tutorial Video here.
Help File: Documentation of JSON Driver.
Blog/articles link: https://zappysys.com/blog/category/odbc-powerpack/odbc-drivers/json-rest-api-driver/

The post Read JIRA data in SSRS Reports (SQL Server Reporting Services) appeared first on ZappySys Blog.

Calling SSRS Reports in SSIS (Export / Email)

ZappySys Team — Sat, 16 Jun 2018 20:07:59 +0000

Introduction about calling SSRS Reports in SSIS

Calling SSRS Reports in SSIS is straightforward using the ZappySys Reporting Services task. Also, we will show how to export files SSRS files using SSIS, how to send reports in emails and how to send parameters.

In addition, we will be using this ZappySys SSIS PowerPack component to make things work:

	SSIS Report Generator Task (Export SSRS Reports)
	Advanced SSIS File System Task

In order to understand the functionality, the following video tutorial can be useful to understand the functionality of this useful Reporting Services task:
[youtube https://www.youtube.com/watch?v=ajnSgbXls7I&w=560&h=315]

Requirements

First of all, we will need ZappySys SSIS PowerPack. This tool contains the Reporting Services Task.
Secondly, you will require SSDT for Business Intelligence to create SSIS projects.
Also, make sure to have an SSRS report deployed. For more information
about creating reports and deploying, refer to these links:

- Create a Basic Table Report (SSRS Tutorial)
- Publishing Reports to a Report Server

Getting started

We will first show how to export an SSRS Report to Word format (docx). Also, the ZappySys SSIS PowerPack, allows converting your SSRS reports deployed into Word (docx and doc), Excel (xlsx and xls), PDF, TIFF, CSV and XML.

Calling SSRS Reports in SSIS

First of all drag and drop the ZS Reporting Task that is included with our ZappySys SSIS PowerPack:
SSRS task in SSIS
Secondly, in general tab, make sure that the Export server report is enabled.
Additionally, specify the report service URL. If you are not sure what is your report service URL, check the step 3 in requirements.
In addition, in report path, select the report that you want to export to a file.
Also, check the output as a file option:
Export report to file
Additionally, in the export settings tab, go to Save as and specify the path and extension of the file to export. You can export to Excel, Word, PDF, Tiff, CSV and XML:
Export SSRS report using SSIS to Excel, Word, PDF
Finally, run the package and the file will be created:
SSRS report exported to docx

Changing the names of the reports with the date format

In order to explain how to add the prefix or suffix of a file with the current date. For example, I want my SSRS reports with this format:
Filename20180323.xlsx where 20180323 means march 23, 2018. To understand how to do it, In this new example, we will show how to do it.

First of all, we will use the ZappySys Advanced File System Task:
Secondly, we will use the option Rename files and rename using the fun_getdate function like this: Filename<>.xlsx
Rename the file with a date in SSIS
Also, you can watch all the available examples of functions by pressing the Expressions (x) button:
Special SSIS functions
Finally, press insert variable and function examples and you will be able to see all the examples of special functions to simplify your life:
Samples of functions

Moving your report files to a UNC path

Once that you have your files exported from reporting services to a file, you can move, copy them to another path. In this example, we will show how to move files to a Shared folder using a UNC path.

First of all, specify your file name to move. You can use *.xml for example to move all the files.
Secondly, specify the UNC path in destination:
SSIS move files to UNC path
Also, It is possible to sort files by name, size, modified date or other properties:
Sort file in SSIS by name, size, modified date
Finally, press the Examples link, you can see some custom queries that you can create:
Sample SSIS queries to files

Sending SSRS Report as an attachment in an email

The task also allows calling SSRS reports in SSIS and send the reports to an email. To do it, it is necessary to have an SMTP Server. Let’s take a look at the steps:

First of all, in the general tab, check the email report file and uncheck the Output as file option:
Output SSRS report in SSIS as attachment
Also, in Email setting tab, press New in SMTP connections to create a new connection. You will need to provide an SMTP server name, an email and a password. It is also necessary to enter the port. You can find the list of some SMTP servers and ports here.

In addition, you have an option to specify the sender, receiver, subject, and body. It is possible to write the body in HTML format. You can also specify SSIS variables. The following HTML code shows how to write in bold,
italic, with bullets and more:

This is an example using headers

This is an example to write using bold
This is an example to write using italic
This is an example using underline

This is an example with lists
Sedond of the list
Third of the list

This is an example with bullets
Bullet sample
Working with bullets

Dynamic HTML in SSIS

Additionally, in Visual Studio go to the menu and SSIS, Variables and create two variables that will be used in the report named Title and ReportName of type string and specify values for them:
Using SSIS variables in emails
Finally, run the script and check your email received:
Email received SSIS Html format

Calling SSRS Reports in SSIS with parameters

Another key point is the use of parameters. Sometimes your SSRS includes parameters. With our Reporting Service Task, it is possible to call an SSRS report and pass SSIS parameters. You will require a Report with a parameter to test it. If you do not know how to create a parameter in SSRS, click here.

First of all, you will need an SSRS Report with a parameter:
Reporting Service Parameter
Secondly, in SSDT or Visual Studio, in the menu, go to SSIS and variables. Create an SSIS variable:
Variables in SSIS
Finally, in Report Services Task in Visual Studio, go to Report Parameters and map the SSRS parameter with the SSIS variable:
Map SSIS variable with SSRS parameters

Calling SSRS Reports in SSIS using data-driven configuration

Data-driven configuration allows configuring different reports with different configurations. In addition, the option allows handling multiple reports using a table with all the configurations for each report. Also, this task creates a table in SQL Server with the configurations for each report. Let’s take a look to see how this works.

First of all, select the data-driving report export using config table.
Also, you will need to specify the connection to the SQL Server
database.
In addition, go to config table, press new to create a new table:
SSRS Data-driven in SSIS

Additionally, ZappySys allows creating a sample table that can help you to understand how to configure local reports, Calling SSRS Reports in SSIS and save to files, specify paths, ports, email options and more:

CREATE TABLE [{{SchemaName}}].[{{TableName}}](
	Id int identity(1,1) NOT NULL  PRIMARY KEY, 
	GroupName varchar(100) NULL,  /* Used to filter reports */
	ReportType varchar(10) NOT NULL, /*Local or Server*/
	ReportServiceUrl  varchar(500) null, 
	ReportPath varchar(500) NOT NULL, 
	IsEnabled bit NOT NULL default(1),
	ExportAsFile bit NOT NULL default(1),
	ExportAsEmail bit NOT NULL default(0),
	Parameters varchar(max) NULL, /* ParameterName1;IsMultiValue;Value1|....ParameterNameN;IsMultiValue;ValueN */
	ExportPath varchar(500) NULL,
	AddFileSuffix bit NULL,
	ExportFileSuffix varchar(500) NULL, /* e.g. _ddMMyyyy, _ddMMyyyyhhmmss, _ddMMyyyyhhmmss.fff (see this URL http://msdn.microsoft.com/en-us/library/az4se3k1(v=vs.110).aspx) */
	Description varchar(500) NULL,
	EmailFrom varchar(255) NULL,
	EmailTo varchar(1000) NULL,
	EmailCc varchar(1000) NULL,
	EmailBcc varchar(1000) NULL,
	EmailSubject varchar(500) NULL,	
	EmailIsHtml bit NULL default(1),	
	EmailBodyText varchar(max) NULL,
	EmailAttachmentFile varchar(500) NULL, /*Unused: For future use only*/
	LastExportStartDate datetime NULL,
	LastExportEndDate datetime NULL,
	LastStatus varchar(20) NULL,
	LastMessage varchar(max) NULL,
	Datasets varchar(max) NULL, /*if ReportType=local and report file is using dataset(s) then supply data in this column (multiple values must be pipe delimited). e.g. Dataset1|Dataset2)*/
	DatasetConnectionStrings varchar(max) NULL, /*if ReportType=local and report file is using dataset(s) then supply data in this column (connection string must be same order as datasets (multiple values must be pipe delimited) enter just one connectionstring if all datasets using same connection. ConnectionString must be ADO.NET for SQLServer, ODBC or OLEDB connection string and correct driver must be installed on the system)*/
	DatasetQueries varchar(max) NULL /*if ReportType=local and report file is using dataset(s) then supply data in this column (queries must be in the same order as dataset(s) listed in Datasets column. enter multiple queries in this format {query for 1st dataset}{query for 2nd dataset})*/
);

Sample Database in SSIS for SSRS

Finally, you can check the table with the configuration:
Data-driven table created in SSIS

Calling SSRS Reports in SSIS to Export local report option

With local reports, you can work with rdl files. The rdl (Report Definition Language) files are part of the SSRS. They are physical files that contain the report format and other components. Using the export local report you can customize queries and see the results as reports. Here we will explain how to do it.

First of all, in the Reporting Services task in Visual Studio, make sure to select the option Export local report.
Secondly, in report path, you need to specify your rdl file path.
In addition, check the dataset. The dataset is usually detected by default. It is included in the SSRS.
Also, in Dataset Constr, you will need to specify the connection information. You need to specify the SQL Server name, Database name, Authentication type. For more information about connection string, click here.
Finally, in dataset queries, you need to specify your query using the XML and query tags:
SSIS local SSRS report

Conclusion

In summary, calling SSRS Reports in SSIS is a straightforward task using the ZappySys Reporting Service task. In this article, we learned how to export a Reporting services Report to a file. Also, we learned how to send emails using SSIS with the report attached and we also learned how to rename, copy files and finally how to use Data-Driven configuration and create queries to local reports. If you liked the tool, you can download it here.

References

Finally, refer to these links for more information:

The post Calling SSRS Reports in SSIS (Export / Email) appeared first on ZappySys Blog.

How to read REST API in SSRS Reports (JSON / XML / Call SOAP Web Service)

ZappySys Team — Thu, 19 Apr 2018 19:39:51 +0000

Introduction (Read REST / SOAP API in SSRS)

In this tutorial, you will learn how to read REST API in SSRS (SQL Server Reporting Services). Traditionally to read data from XML / JSON Files or RESTful web service in SSRS, some sort of ETL approach was needed (i.e Load data from JSON / XML to SQL server first and then read from SQL Server to SSRS).

This article will focus on very unique and simple approach, we will use ZappySys drivers for JSON / XML / REST API to read REST API or JSON Files in SSRS reports. ZappySys JSON driver allows you to query any API source or JSON / XML files using familiar SQL query language.

Example purpose, we will only show JSON file format but the same approach can be used for reading from XML files or Calling XML SOAP Web Services in SSRS. We will also learn how to connect using OAuth to Facebook. We can also connect to Google, Azure, Facebook, Twitter, DropBox, Github, Instagram and thousands of other sources using same techniques.

Finally, we will also learn how to handle errors, pagination to handle several pages and how to read an XML file in Reporting Services

Requirements:

Make sure you have SSRS designer installed (You can download SSDT BI for Visual Studio 2015).
In addition, we will need ZappySys ODBC PowerPack Installed.

Getting Started

You can access JSON / XML data in SSRS three different ways. We will only focus on one method in this article but please check other articles by clicking below links.

ZappySys Data Gateway – This method uses Microsoft SQL Server Connection Type option to connect to ZappySys Data Gateway. Check this
Microsoft SQL Server (Linked Server) – This connection type which connects to SQL Server Linked Server. Check this
ODBC (Use ZappySys ODBC Driver) – You can use ODBC connection option in Report when you define data source (NOTE: There are some known issues with this method so we will not discuss)

NOTE: If you are using Method#3 (ODBC Connection) in SSRS 2017 or higher then you may have to do small changes listed under Troubleshooting section in this article. You may consider Method#2 or #3 if Direct ODBC Connection is not working for you.

Now lets look at steps to call REST API in SSRS (SQL Server reporting Services).

Configure Data Source in Gateway (ZappySys JSON / REST API Driver Example)

Configure Data Gateway User / Port

Now let's look at steps to configure Data Gateway after installation. We will also create a sample data source for ODATA API (i.e. JSON based REST API Service).

Assuming you have installed ZappySys ODBC PowerPack using default options (Which also enables Data Gateway Service)
Search "Gateway" in your start menu and click ZappySys Data Gateway

Open ZappySys Data Gateway
First make sure Gateway Service is running (Verify Start icon is disabled)
Also verify Port on General Tab

Port Number setting on ZappySys Data Gateway
Now go to Users tab. Click Add icon to add a new user. Check Is admin to give access to all data sources you add in future. If you don't check admin then you have to manually configure user permission for each data source.

Add Data Gateway User

Configure Data Source

After user is added, go to Data Sources tab. Click Add icon to create new data source. Select appropriate driver based on your API / File format. You can choose Generic ODBC option to read data from ODBC DSN or use Native Driver option.
```
NOTE: Whenever possible use native driver option for better performance / security and ease of use.
```
Add Gateway Data Source (Native JSON Driver)
Click on "Edit" under Data source and configure as per your need (e.g. Url, Connection, Request Method, Content Type, Body, Pagination etc.). For this demo we are going to pick simple JSON REST API which doesn't need any authentication. Enter following URL.
```
https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json
```
You can also view response structure and select default hierarchy (i.e. Filter) like below (Select Array Icon) for data extraction.

Configure JSON API Data source

Test SQL Query / Preview Data

Now go to Preview Tab. You can click Preview button to execute default query OR Select Table name from dropdown to generate SQL with column names.

JSON / REST API Driver Query Preview / Query Examples (Read REST API or JSON Files)
You can also click Query Builder to generate SQL using different options in WITH clause. ANy setting you specify in WITH clause will override UI settings we applied in previous steps.

Using SQL Query Builder (For Files or REST / SOAP API - JSON / XML / CSV Format)
There is another useful option for code generation. Select your Language and quickly copy code snippet. See below Example of XML Driver Query to call SOAP API.

Generate Example Code for ZappySys Driver
Click OK to Close Data Source UI
Once data source is tested and configured you can click Save button in the Gateway UI toolbar and click Yes for Restart Service.

Configure SSRS Report Data source (Use ODBC Connection)

Once you are done configuring ODBC DSN for REST API URL. The next step will be to create a new SSRS project.

In SSRS, in a new Reporting Service Project, add a new Data Source:
Also, specify a name for the data source and in type select Microsoft SQL Server. Press Build to select the Data gateway connection information as below.
Connect to JSON / REST API / SOAP in SSRS (Using ZappySys Data Gateway)
Click OK to save our data source. We will use this Data source in next section.

Create a new SSRS Report

Once your DSN is setup we can create report. There are two ways you can create reports.

Create SSRS Reports using Report Builder App
Create SSRS Reports using Visual Studio (SSDT) – Download SSDT from Here

In this section we will see second method (Visual Studio Method). Now let’s create a new SSRS report which uses the API data source we created in the previous section.

Open Existing SSRS Project or Create a new Reporting Services Project by clicking File > New. When Dialog Opens expand Business Intelligence category and select Reporting Services Project
When Solution opens Right-click on the Reports node and click Add New Report (Wizard mode)
Press the query builder button
Additionally, press the Add table icon and go to Views. Select value(DATA) and press add:
Press next in the following option until the completing wizard and specify a name for the report and check the option to Preview a report:
If everything is OK, you will be able to see the report and export the REST API data to Word, Excel, PowerPoint, etc:

Export JSON and REST API to word, Excel

Working with parameters in SSRS (Dynamic SQL Query)

So far we have seen how to pull data from Table exposed by our ODBC DSN for API Service. In the real world, you may have some sort of parameters passed to your API Service (e.g. CustomerID or Date Parameters).

So let’s configure our report to use parameters.

We can work with parameters in SSRS. You can Add a Parameter in Parameters with the add parameter option:
We will create a parameter named CustomerID and it will be used to assign a customerID parameter:
Create a data source and a dataset, drag and drop your columns to the report:
Right-click your DataSet (which was generated by Report Wizard) and select DataSet properties:
Go to query and select Fx to create a dynamic SQL Query for our data source (Use expression / parameters in SQL):
Just keep in mind that, if you use dynamic SQL for the data source (i.e. Using Expression in SQL) then Fields of that data source won’t refresh automatically when you save the UI. Workaround for this issue simple. Just use a static query for the first time to generate desired fields for the dataset. Once data source fields are generated you can add expression in your SQL Query.
Static Query:
SELECT col1, col2 FROM rows WITH (SRC=’http://abc.com/invoice?year=2017′)
Dynamic Query:
=”select col1, col2 from rows WITH (SRC=’http://abc.com/invoice?year='” + Parameters!Year.Value + “‘)”

On the expression dialog box, Enter SQL Query like below

="SELECT CustomerID, CompanyName, ContactName FROM value where CustomerID='"
+ Parameters!CustomerID.Value + "'"

If you don’t want to use URL from DSN then you can supply API URL right inside your SQL Query like below.

="SELECT CustomerID, CompanyName, ContactName FROM value where CustomerID='"
+ Parameters!CustomerID.Value + "'" + 
"WITH (SRC='https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json')"

You can now write a name as a parameter and receive the results:

Working with multi-value parameters in SSRS (Dynamic SQL Query)

If you have a parameter which is multi-valued and you want to use it to filter data then follow the above section and in the expression dialog box use JOIN function to join the values, e.g.:

=SELECT CustomerID, CompanyName, ContactName FROM value where CustomerID IN ('" & JOIN(Parameters!CustomerID.Value, "','") & "')"

Working with SSRS dataset filters (Client-side filtering)

Sometimes its necessary to do filtering on data once it’s retrieved from the server. Dataset Filter is SSRS feature which does data filtering on the client side. To filter the report previously created, right click on the dataset and go to Filters. Press Add.

In this example, we will show how to show a customer with the customerID equal to ALFKI (or click on fx icon to use the expression for dynamic filter:

Add filter SSRS REST API

Working with date parameters in SSRS Reports

Now lets look at how to handle date parameters and format them correctly. Most JSON /XML REST API handle dates in ISO format (i.e. yyyy-MM-ddTHH:mm:ss.fffZ). You can convert or format text parameters to date using the CDate function. The following example converts the parameter mydate from text to a date in SSRS:

CDate( Parameters!mydate.Value)

Next, we will show how to convert the date format to the format yyyy-MM-ddT00:00:00:

FORMAT(CDate( Parameters!mydate.Value),"yyyy-MM-ddT00:00:00")

Also, we will work with a REST API URL with data and retrieve the results:

https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json

Furthermore, in the ODBC Administrator add a connection to the previous URL (Or use URL inside SQL query WITH caluse as per previous section example):

URL with dates in REST API

The following example will convert the parameter to the same format as the URL and compare the OrderDate to the specified format:

="SELECT ShipName, ShipAddress, OrderDate FROM DATA.""value"" where 
OrderDate="+"'"+Cstr(FORMAT(CDate( Parameters!mydate.Value),"yyyy-MM-ddT00:00:00"))+"'"

Pass parameters in a Report URL

In addition, when the report is published, you can specify a parameter in a URL. The following example shows how to pass a date in a parameter named mydate the value 1997-10-13:

http://localhost/ReportServer/Pages/ReportViewer.aspx?%2fReport+Project5
%2fReport5&rs:Command=Render&mydate=1997-10-13

Read JSON files in SSRS Reports

Also, it is possible to connect to a JSON file instead of REST API. The steps are the same that the ones explained previously with the difference that we need to specify the path when we create the ODBC connection. The following example with show how to specify the path of a local JSON file in the connection:

SSRS access to a local JSON file.

Reading XML Files in SSRS Reports

The next example will show how to read an XML file using SSRS.

The XML name is ZS.xml and it contains the following content:

Gambardella, Matthew
XML Developer's Guide
Computer
44.95
2000-10-01
An in-depth look at creating applications with XML.

Ralls, Kim
Midnight Rain
Fantasy
5.95
2000-12-16
A former architect battles corporate zombies, an evil sorceress, and her own childhood to become queen of the world.

Corets, Eva
Maeve Ascendant
Fantasy
5.95
2000-11-17
After the collapse of a nanotechnology society in England, the young survivors lay the foundation for a new society.

Corets, Eva
Oberon's Legacy
Fantasy
5.95
2001-03-10
In post-apocalypse England, the mysterious agent known only as Oberon helps to create a new life for the inhabitants of London. Sequel to Maeve Ascendant.

Corets, Eva
The Sundered Grail
Fantasy
5.95
2001-09-10
The two daughters of Maeve, half-sisters, battle one another for control of England. Sequel to Oberon's Legacy.

Randall, Cynthia
Lover Birds
Romance
4.95
2000-09-02
When Carla meets Paul at an ornithology conference, tempers fly as feathers get ruffled.

Thurman, Paula
Splish Splash
Romance
4.95
2000-11-02
A deep sea diver finds true love twenty thousand leagues beneath the sea.

Knorr, Stefan
Creepy Crawlies
Horror
4.95
2000-12-06
An anthology of horror stories about roaches, centipedes, scorpions and other insects.

Kress, Peter
Paradox Lost
Science Fiction
6.95
2000-11-02
After an inadvertant trip through a Heisenberg Uncertainty Device, James Salway discovers the problems of being quantum.

O'Brien, Tim
Microsoft .NET: The Programming Bible
Computer
36.95
2000-12-09
Microsoft's .NET initiative is explored in detail in this deep programmer's reference.

O'Brien, Tim
MSXML3: A Comprehensive Guide
Computer
36.95
2000-12-01
The Microsoft MSXML3 parser is covered in detail, with attention to XML DOM interfaces, XSLT processing, SAX and more.

Galos, Mike
Visual Studio 7: A Comprehensive Guide
Computer
tag1
49.95
2001-04-16
Microsoft Visual Studio 7 is explored in depth, looking at how Visual Basic, Visual C++, C#, and ASP+ are integrated into a comprehensive development environment.

This example will read an XML file named ZS.xml. First, in ODBC Administrator add the ZappySys ODBC XML Driver:

ODBC SSRS FOR XML

In data source, specify the path of the file:

XML configuration

Once created the connection, create your report in SSDT in the query, add the following query:

SELECT author, genre, title, price, publish_date
FROM DATA.”store.book”

Create a query to XML in SSRS

Finally, you can visualize your report in SSRS:

SSRS reading XML

REST API Security – Working with OAuth (Facebook API example)

If you API requires credentials then no worries, ZappySys Drivers come with many security standards support. Most common credential types are Basic Auth and OAuth. These are open standard to access Web Services. In this new example, we will show how to read Facebook information in SSRS (Call Facebook Graph API).

For demo we will read the number of friends on Facebook:

Friends on Facebook

First, we will open the ODBC Data Source:

ODBC Data Source

In Authentication type, select OAuth. We will use the following link to get the friends information on Facebook:

https://graph.facebook.com/v1.0/me/friends?

This link retrieves information of my friends. For more information about the Facebook graph API, check our references.

Facebook connection properties

Secondly, go to OAuth settings and select Facebook as the OAuth Provider. You will need a Client Id and a Client Secret. To get a client id and a client secret, you will need to create a Facebook application here. For more information about creating a Facebook application, check this link.

Scopes will use user_friends to get Facebook friends information. For a list of scopes, please check here.

OAuth settings

Once that the connection is created, you need to create an SSRS report using the ODBC connection just created. In the query, we will create the following query:

SSRS query to Facebook

If everything is OK, you will be able to see the number of Facebook friends:

Facebook friends in SSRS

POST Parameters to SSRS Report (avoid GET for long string in URL)

You can call reports from browser using following way (Pass parameters in URL). Below Method by default sends GET requests to Report Server and render report in HTML format in your browser.

http://localhost/reports/report/MySampleReports/Report1?MyParameter1=AAA&MyParameter2=BBB

However there is a problem if you have a very long string as parameter value. In that case use FORM POST method described in this article.

You can try yourself. Just create an html file on your machine and paste below code. Run it in a browser (If you have UAC ON then First launch Browser as Admin and then paste full path of your HTML file). Click on a button displayed in that page to mimic POST.

TestPost.html


			
		

		
		
			
			
			 
			  
			
			  
			
			

			

			Fill out below parameters and click above button

You can use expression like below in your Report to confirm Data Length of posted Parameter

="My Parameter Length is " & Parameters!Notes.Value.ToString().Length

Also you can use below expression to make your query dynamic as below

="SELECT data,origin,url FROM _root_ " + 
 "WITH(SRC='http://httpbin.org/post', " + 
 "METHOD='POST', " +
 "HEADER='Content-Type: text/plain', " + 
 "BODY='" + Parameters!Notes.Value + 
 "')"

Deploying SSRS Report (for ODBC Connection)

NOTE: In this section we will make sure few thing for ODBC Connection Type. If you used Data Gateway approach then you may skip this section.

Once you done with design and testing of reports, our next step would be deploy reports to SSRS Server. This section describes things to make sure when you deploy reports.

Find DSN Name and Full ConnectionString of original DSN

First thing to make sure you install ODBC PowerPack on the report server too (Unless you are using SQL Server Connection Type to connect to Gateway and you dont plan to run it on SSRS Server)
Once ODBC PowerPack is installed on the server next step is to setup DSN Used by Reports. SSRS Service is 64 bit so DSN must be 64 bit and must be named Exact same way just like how you used during Design Phase on Client PC where reports are designed.
To Setup DSN exact same way try this step. First go to Client PC where reports are designed. Open ODBC DSN which you used for Report. Copy two things 1) Name of your DSN, and Find Copy Connection String Button to copy full connection string of your DSN.

Create new DSN(s) on SSRS Server using original settings

Now Remote Desktop (rdp) to SSRS Server, search of odbc 64 bit. Open it and go to System Tab.
Create System ODBC DSN (64-bit)
Click Add to create new DSN just like we did very beginning of this article. Select Driver you wish to use.
Once Driver UI opens up change default DSN name to exact same name like we gave it for SSRS Report on client PC.
find Load Connection String Button and paste connection string we obtained in previous step.
ZappySys ODBC Driver – Load Connection String Example
Click Test connection see everything good. Click OK to save DSN
Repeat these steps for each DSN used in SSRS Report.

Things to know about SSRS 2017 or Higher / Report Builder

We had few users who reported issue with SSRS 2017 after deployment (Everything worked fine during design time). You may get below error when try to preview report from server URL. You may sometimes notice that after saving report in Report Builder if you try to preview Report Builder hangs and you have to restart SSRS service. If you notice any such issue you may have to apply following fix..

Error:

Cannot create a connection to data source 'YourDataSourceName'. ---> System.Data.Odbc.OdbcException:

In such case check steps listed in Troubleshooting Section later this article.

Calling SOAP XML Web Service in SSRS (SQL Reporting Services)

So far we have looked at examples to consume data using JSON driver. Now let’s look at an example, to call XML SOAP Web Service in SSRS.

To call SOAP API you need to know Request XML Body Structure. If you are not sure how to create SOAP Request body then no worries. Check this article to learn how to generate SOAP Request body using the Free tool SoapUI. Basically, you have to use SoapUI to generate Request XML and after that, you can replace parameters as needed in the generated body.

What is SOAP Web Service?

If you are new to SOAP Web Service sometimes referred as XML Web Service then please read some concept about SOAP Web service standard from this link There are two important aspects in SOAP Web service.

Getting WSDL file or URL
Knowing exact Web Service URL

What is WSDL

In very simple term WSDL (often pronounced as whiz-dull) is nothing but a document which describes Service metadata (e.g. Functions you can call, Request parameters, response structure etc). Some service simply give you WSDL as xml file you can download on local machine and then analyze or sometimes you may get direct URL (e.g. http://api.mycompany.com/hr-soap-service/?wsdl )

Example SQL Query for SOAP API call using ZappySys XML Driver

Here is an example SQL query you can write to call SOAP API. If you not sure about many details then check next few sections on how to use XML Driver User Interface to build desired SQL query to POST data to XML SOAP Web Service without any coding.

SELECT * FROM $
WITH(
	 Src='http://www.holidaywebservice.com/HolidayService_v2/HolidayService2.asmx'
	,DataConnectionType='HTTP'
	,CredentialType='Basic' --OR SoapWss
	,SoapWssPasswordType='PasswordText'
	,UserName='myuser'
	,Password='pass$$w123'
	,Filter='$.soap:Envelope.soap:Body.GetHolidaysAvailableResponse.GetHolidaysAvailableResult.HolidayCode[*]'
	,ElementsToTreatAsArray='HolidayCode'	
	,RequestMethod='POST'	
	,Header='Content-Type: text/xml;charset=UTF-8 || SOAPAction: "http://www.holidaywebservice.com/HolidayService_v2/GetHolidaysAvailable"'
	,RequestData='

   
   
      
         
         UnitedStates
      
   
'
)

Now let's look at steps to create SQL query to call SOAP API. Later we will see how to generate code for your desired programming language (e.g. C# or SQL Server)

Video Tutorial - Introduction to SOAP Web Service and SoapUI tool

Before we dive into details about calling SOAP API using ZappySys XML Driver, lets first understand what is SOAP API and how to create SOAP requests using SoapUI tool. You will learn more about this process in the later section. The video contains some fragment about using SOAP API in SSIS but just ignore that part because we will be calling Soap API using ZappySys ODBC Driver rather than SSIS Components.

Using SoapUI to test SOAP API call / Create Request Body XML

Assuming you have downloaded and installed SoapUI from here, now we are ready to use WSDL for your SOAP Web Service Calls. If you do not have WSDL file or URL handy then contact your API provider (sometimes you just have to add ?wsdl at the end of your Service URL to get WSDL so try that. Example: http://mycompany/myservice?wsdl ). If you don't know what is WSDL then in short, WSDL is Web service Description Language (i.e. XML file which describes your SOAP Service). WSDL helps to craft SOAP API request Body for ZappySys XML Driver. So Let's get started.

Open SoapUI and click SOAP button to create new SOAP Project
Enter WSDL URL or File Path of WSDLFor example WSDL for our sample service can be accessed via this URL
```
http://www.dneonline.com/calculator.asmx?wsdl
```
Create new SOAP API Project in SoapUI tool for SOAP API Testing
Once WSDL is loaded you will see possible operations you can call for your SOAP Web Service.
If your web service requires credentials then you have to configure it. There are two common credential types for public services (SOAP WSS or BASIC )
1. To use SOAP WSS Credentials select request node and enter UserId, Password, and WSS-PasswordType (PasswordText or PasswordHash)
  
  Configure SOAP WSS Credentials for SoapUI (SOAP API Testing Tool)
2. To use BASIC Auth Credentials select request node and double-click it. At the bottom click on Auth (Basic) and From Authorization dropdown click Add New and Select Basic.
  Configure Basic Authorization for SoapUI (SOAP API Testing Tool)
Now you can test your request first Double-click on the request node to open request editor.
Change necessary parameters, remove optional or unwanted parameters. If you want to regenerate request you can click on Recreate default request toolbar icon.
Create SOAP Request XML (With Optional Parameters)
Once your SOAP Request XML is ready, Click the Play button in the toolbar to execute SOAP API Request and Response will appear in Right side panel. Test SOAP API using SoapUI Tool (Change Default XML Body / Parameters, Execute and See Response)

Create DSN using ZappySys XML Driver to call SOAP API

Once you have tested your SOAP API in SoapUI tool, we are ready to use ZappySys XML driver to call SOAP API in your preferred BI tool or Programming language.

First open ODBC Data Sources (search ODBC in your start menu or go under ZappySys > ODBC PowerPack > ODBC 64 bit)
Goto System DSN Tab (or User DSN which is not used by Service account)
Click Add and Select ZappySys XML Driver ZappySys ODBC Driver for XML / SOAP API
Configure API URL, Request Method and Request Body as below ZappySys XML Driver - Calling SOAP API - Configure URL, Method, Body
(This step is Optional) If your SOAP API requires credentials then Select Connection Type to HTTP and configure as below.
ZappySys XML Driver - Configure SOAP WSS Credentials or Basic Authorization (Userid, Password)
Configure-Request Headers as below (You can get it from Request > Raw tab from SoapUI after you test the request by clicking the Play button) Configure SOAP API Request Headers - ZappySys XML Driver
Once credentials entered you can select Filter to extract data from the desired node. Make sure to select array node (see special icon) or select the node which contains all necessary columns if you don't have array node. Select Filter - Extract data from nested XML / SOAP API Response (Denormalize Hierarchy)
If prompted select yes to treat selected node as Array (This is helpful when you expect one or more record for selected node) Treat selected node as XML Array Option for SOAP API Response XML

Preview SOAP API Response / Generate SQL Code for SOAP API Call

Once you configure settings for XML Driver now you can preview data or generate example code for desired language (e.g. C#, Python, Java, SQL Server). Go to Preview tab and you will see default query generated based on settings you entered in previous sections. Attributes listed in WITH clause are optional. If you omit attribute in WITH clause it will use it from Properties tab.

Preview Data

Preview SOAP API Response in ZappySys XML Driver

Generate Code Option

Generate Example Code for ZappySys Driver

SOAP / REST API pagination in SSRS Reports

Even we set up ODBC Data Source to get the data, it may not be enough. Usually, if you are getting a huge data set from API provider, it won't give it to you in one HTTP response. Instead, it gives back only a subset of data and provides a mechanism for data pagination. The good news is that ZappySys ODBC Driver includes many options to cover virtually any pagination method.

Below you will find a few examples of API pagination. If you need something more sophisticated check the below link (the article was written for SSIS PowerPack but UI options and concepts apply to ODBC Driver too):

https://zappysys.com/blog/ssis-rest-api-looping-until-no-more-pages-found/

Paginate by Response Attribute

This example shows how to paginate API calls where you need to paginate until the last page detected. In this example, next page is indicated by some attribute called nextlink (found in response). If this attribute is missing or null then it stops fetching the next page.

SELECT * FROM $
WITH(
SRC=@'https://zappysys.com/downloads/files/test/pagination_nextlink_inarray_1.json'
,NextUrlAttributeOrExpr = '$.nextlink'  --keep reading until this attribute is missing. If attribute name contains dot then use brackets like this $.['my.attr.name']
)

Paginate by URL Parameter (Loop until certain StatusCode)

This example shows how to paginate API calls where you need to pass page number via URL. The driver keeps incrementing page number and calls next URL until the last page detected (401 error). There are few ways to indicate the last page (e.g. By status code, By row count, By response size). If you don't specify end detection then it will use the default (i.e. No records found).

SELECT * FROM $
WITH (
SRC=@'https://zappysys.com/downloads/files/test/page-xml.aspx?page=1&mode=DetectBasedOnResponseStatusCode'
,PagingMode='ByUrlParameter'
,PagingByUrlAttributeName='page'
,PagingByUrlEndStrategy='DetectBasedOnResponseStatusCode'
,PagingByUrlCheckResponseStatusCode=401
,IncrementBy=1
)

Paginate by URL Path (Loop until no record)

This example shows how to paginate API calls where you need to pass page number via URL Path. The driver keeps incrementing page number and calls next URL until the last page is detected. There are few ways to indicate the last page (e.g. By status code, By row count, By response size). If you don't specify end detection then it will use the default (i.e. No records found).

SELECT * FROM $
WITH (
SRC=@'https://zappysys.com/downloads/files/test/cust-<%page%>.xml'
,PagingMode='ByUrlPath'
,PagingByUrlAttributeName='<%page%>'
,PagingByUrlEndStrategy='DetectBasedOnRecordCount'
,IncrementBy=1
)

Paginate by Header Link (RFC 5988)

API like GitHub / Wordpress use Next link in Headers (RFC 5988)

SELECT * FROM $
LIMIT 25
WITH(
	 Src='https://wordpress.org/news/wp-json/wp/v2/categories?per_page=10'
	,PagingMode='ByResponseHeaderRfc5988'
	,WaitTimeMs='200' --//wait 200 ms after each request
)

SOAP / REST API Error Handling in SSRS Reports

Sometimes errors occur... they just do and there is nothing you can do! Or can you? Actually, in ODBC PowerPack you can handle them in two ways.

METHOD 1 - Using Error Handling Options

When to use?

You may want to use them when your source is a resource located on the Internet; e.g. a file on a website, a file on an FTP server or just a plain API HTTP response. By default, when a remote server returns an error, data retrieval is stopped, an error is raised and no data is given back to you. This might not be always desirable.

Scenario 1

Imagine a scenario, that there is a web server which each day at 12 AM releases a new JSON file with that day's date as filename, e.g. http://www.some-server.com/data/2018-06-20.json. And, of course, you want to download it and use it daily in your Power BI report. But you have a problem: Power BI report data sources are refreshed each hour and you may get HTTP 404 status code (no file was found) when a file is not released yet. Which consequentially means other data sources won't be updated as well and you will see old and cached data on the report. That's where you could use Continue on any error or Continue when Url is invalid or missing (404 Errors) to avoid an error being raised and let other data sources to be updated.

Scenario 2

Another scenario is when you expect a web server to raise some kind of HTTP error when accessing a URL. You don't want ODBC Data Source to raise an error but instead, you want to get response data. That's where you can use Continue on any error or alike together with Get response data on error to continue on an error and get the data:

METHOD 2 - Using Connection [Retry Settings]

Another scenario you may run into is a buggy web server. You ask it to give you some file or data and it, like a snotty kid, just doesn't give it to you! You have to ask twice or thrice before it does its job. If that's the case, you have to retry HTTP requests using Connection:

Security / Connection Types (Options for HTTP, OAuth, SOAP) in SSRS Reports

If you need to authenticate or authorize your user to access a web resource, you will need to use one of the Connections:

HTTP
OAuth

HTTP Connection

Use HTTP Connection for simple Windows, Basic, NTLM or Kerberos authentication. Just fill in a username and a password and you are good to go!

You can also use HTTP Connection for more sophisticated authentication like:

SOAP WSS (when accessing a SOAP WebService)
Static Token / API Key (when need to pass an API key in HTTP header)
Dynamic Token (same as Static Token method except that each time you need to log in and retrieve a fresh API key)
JWT Token (As per RFC 7519)

OAuth

If you are trying to access REST API resource, it is a huge chance, you will need to use OAuth Connection. Read this article to understand how OAuth authentication and authorization works and how to use it (article originally was written for SSIS PowerPack, but the concepts and UI stay the same):
https://zappysys.com/blog/rest-api-authentication-with-oauth-2-0-using-ssis/

Other Consideration for Calling Web API in SSRS Reports

There are few settings you can coder while calling Web API

API Limit / Throttling

While calling public API or other external web services one important aspect you have to check, how many requests are allowed by your API. Especially when you use API pagination options to pull many records you have to slow down based on API limits. For example, your API may allow you only 5 requests per second. Use Throttling Tab on Driver UI to set delay after each request.

2D Array Transformation

If you are using JSON or XML API Driver then possible you may have to transform your data using 2D array transformation feature. Check this link for more information.

Working with pagination to read REST API using SSRS

Another important aspect of any API call is handling pagination. When you have many records to read from API, most likely your API won’t send you data in one response. You have to loop through all pages of data until the last page is detected. ZappySys driver comes with many options to configure virtually any pagination strategy.

Here is the screenshot of Pagination options included in ZappySys JSON / XML API Driver:

Moreover, you can configure the maximum page number and the response length. It is also possible to set the minimum response length.

In addition, you can also configure the page number increment and pagination mode. You can also specify conditions to detect the last page and more.

Reading API data from SQL Server Stored Procedure

If you want to read data from SQL Server Stored procedure rather than using Data gateway or ODBC connection then check this post.

Handling errors to read REST API using SSRS

The ZappySys ODBC PowerPack allows handling errors. For example, if the page is not found (error 404), the driver can continue working. You can also continue on any error. Continue on status code, stop the execution on error or more options:

SSRS – REST API Error Handling Options

Troubleshooting SSRS Issues

If you experience problems accessing data from ODBC data source, you may try to set up a data source in ZappySys Data Gateway and access it instead. Check how to troubleshoot errors when SSRS crashes to find out how to accomplish that.

Report Builder Hangs / ODBC Connection errors in SSRS 2017 or Higher

Sometimes you may notice that after saving Report to Server in Report Builder when you preview it hangs or you may get below error. This issue may occur If you are using SSRS 2017 or higher and report is using ODBC Connection Type. If your preview hangs or get below error then you have to try few steps listed below to avoid such error. This error may occur in other version too but from our experience it mostly happens in newer SSRS version.

ERROR : Cannot create a connection to data source 'YourDataSourceName'. ---> System.Data.Odbc.OdbcException:

Steps to fix this error.

First we have to Gac Newtonsoft.json.dll. For this search for “Powershell ISE” and right click and launch as Admin

Run below command to register Dll

[Reflection.Assembly]::LoadWithPartialName("System.EnterpriseServices") | Out-Null 
[System.EnterpriseServices.Internal.Publish] $publish = new-object System.EnterpriseServices.Internal.Publish

$publish.GacInstall("C:\Program Files (x86)\ZappySys\ZappySys ODBC PowerPack\JsonDriverX86\Newtonsoft.Json.dll")

Now go to SSRS Install folder typically found here

C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer

Find rssrvpolicy.config . Backup the file before making any changes below. Right click on the file and edit it.
n the above config file we need to add extract CodeGroup nodes for each ZappySys Driver dll Path which you like to use in SSRS Reports. For demo purpose we have added XML and JSON driver paths you can do more as needed. Basically in SSRS 2012 this may not be needed but in newer version of SSRS (i.e. 2017 and higher) Custom Drivers or Assemblies need Grant to execute under SSRS service. Here is the code you have to add in config file.
```
                    
               
              
                    
               
              
			  
              
                    
              
```

Here is Full rsssrvpolicy.config code in case you like to review. Your file may slightly different so dont just copy full content as is.

Thats it now Restart SSRS Service after above change and you should be fine. If you still face the issue we suggest you use Data Gateway approach.

Conclusion

To conclude, we can say that it is now easy to get JSON and REST API data in SSRS. We only need to download the ZappySys ODBC PowerPack and we will be able to access the data.

Furthermore, you learned how to work with parameters (Dynamic Queries), with dates and pass parameters to URL.

References

Finally, for more information about how to read REST API using SSRS you can check the following links:
⦁ Category Archives: ODBC PowerPack
⦁ Develop with the REST APIs for Reporting Services
⦁ Facebook Graph API

Keywords: SSRS JSON data source, SSRS REST API data source, SSRS SOAP Web Service data source, Call REST API in SSRS, Load JSON into SSRS, Read REST API in SSRS, Read XML SOAP Web Service in SSRS, Read JSON file in SSRS,
Read XML file in SSRS

The post How to read REST API in SSRS Reports (JSON / XML / Call SOAP Web Service) appeared first on ZappySys Blog.