SAP Crystal Reports Azure Blob CSV File Connector In this article you will learn how to integrate Azure Blob CSV File data to SAP Crystal Reports without coding in just a few clicks (live / bi-directional connection to Azure Blob CSV File). Azure Blob CSV File Connector can be used to read CSV Files stored in Azure Blob Container. Using this you can easily integrate Azure Blob Storage CSV File data. It's supports latest security standards, and optimized for large data files. It also supports reading compressed files (e.g. GZip /Zip).. Using Azure Blob CSV File Connector you will be able to connect, read, and write data from within SAP Crystal Reports. Follow the steps below to see how we would accomplish that. Download  Help File  Buy  Driver mentioned in this article 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. ODBC PowerPack - System Requirements and Installation Getting Started - Using ODBC PowerPack ODBC API Driver Help File

See also Connect Azure Blob CSV File in SSIS Connect Azure Blob CSV File in SQL Server Connect Azure Blob CSV File in Power BI Connect Azure Blob CSV File in SSRS Connect Azure Blob CSV File in Informatica Connect Azure Blob CSV File in MS Access Connect Azure Blob CSV File in MS Excel Connect Azure Blob CSV File in SSAS Connect Azure Blob CSV File in C# Connect Azure Blob CSV File in Python Connect Azure Blob CSV File in JAVA Connect Azure Blob CSV File in Tableau Connect Azure Blob CSV File in Azure Data Factory (ADF) Connect Azure Blob CSV File in ODBC

Create ODBC Data Source (DSN) based on ZappySys Azure Blob CSV Driver

To get data from AzureBlobCsvFile using SAP Crystal Reports we first need to create a DSN (Data Source) which will access data from AzureBlobCsvFile. We will later be able to read data using SAP Crystal Reports. Perform these steps:

1. Install ZappySys ODBC PowerPack.

2. Open ODBC Data Sources (x64):
   

3. Create a User Data Source (User DSN) based on ZappySys Azure Blob CSV Driver

   ZappySys Azure Blob CSV Driver

   
   You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.

4. Create and configure a connection for the Azure Blob storage account.

   

5. You can use select your desired single file by clicking [...] path button.

   mybucket/dbo.tblNames.csv

   dbo.tblNames.csv

   
   
   
   ----------OR----------

   You can also read the multiple files stored in Azure Blob Storage using wildcard pattern supported e.g. dbo.tblNames*.csv.
   

   Note: If you want to operation with multiple files then use wild card pattern as below 
   (when you use wild card pattern in source path then system will treat target path as folder regardless you end with slash)
   
   mybucket/dbo.tblNames.csv (will read only single .CSV file)
   mybucket/dbo.tbl*.csv (all files starting with file name)
   mybucket/*.csv (all files with .csv Extension and located under folder subfolder)
   

   mybucket/dbo.tblNames*.csv

   
   
   
   ----------OR----------

   You can also read the zip and gzip compressed files also without extracting it in using Azure Blob CSV Source File Task.

   mybucket/dbo.tblNames*.gz

   

6. Navigate to the Preview Tab and let's explore the different modes available to access the data.
   

   1. --- Using Direct Query ---

      Click on Preview Tab, Select Table from Tables Dropdown and select [value] and click Preview.
      

   2. --- Using Stored Procedure ---

      Note : For this you have to Save ODBC Driver configuration and then again reopen to configure same driver. For more information click here.
      Click on the Custom Objects Tab, Click on Add button and select Add Procedure and Enter an appropriate name and Click on OK button to create.
      

      1. --- Without Parameters ---

         Now Stored Procedure can be created with or without parameters (see example below). If you use parameters then Set default value otherwise it may fail to compilation)
         
         

      2. --- With Parameters ---

         Note : Here you can use Placeholder with Paramters in Stored Procedure. Example : SELECT * FROM $ WHERE OrderID = '<@OrderID, FUN_TRIM>' or CustId = '<@CustId>' and Total >= '<@Total>'
         

   3. --- Using Virtual Table ---

      Note : For this you have to Save ODBC Driver configuration and then again reopen to configure same driver. For more information click here.

      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.

      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 Buckets with slight variations you can create virtual tables with just URL as Parameter setting).

      vt__Customers
      DataPath=mybucket_1/customers.csv
      
      vt__Orders
      DataPath=mybucket_2/orders.csv
      
      vt__Products
      DataPath=mybucket_3/products.csv
      

      1. Click on the Custom Objects Tab, Click on Add button and select Add Table and Enter an appropriate name and Click on OK button to create.
         
      2. Once you see Query Builder Window on screen Configure it.
         
      3. Click on Preview Tab, Select Virtual Table(prefix with vt__) from Tables Dropdown or write SQL query with Virtual Table name and click Preview.
         

7. Click OK to finish creating the data source

8. That's it; we are done. In a few clicks we configured the to Read the Azure Blob CSV File data using ZappySys Azure Blob CSV File Connector

Read data in SAP Crystal Reports from the ODBC data source

1. First of all, open SAP Crystal Reports and create the new Crystal Report.
   

2. And it will open the new data source selection window. Under ODBC(RDO) double click on the Make New Connection and Select the desired ODBC DSN, in our case we need to select AzureBlobCsvFileDSN which we created in upper section. And Click on Next.
   

   AzureBlobCsvFileDSN

   

3. Expand the Connection and under the data select the desired table(s) or view(s) and click Add > button and click on Next.
   

   AzureBlobCsvFileDSN

   AzureBlobCsvFileDSN

   

4. Add the desired Fields to Display in the Reports. Here we are adding all fields and click on Finish.
   

5. That's it and you will be able to load the data in the Report.
   

Using ZappySys Driver Custom Views and Store Procedure in SAP Crystal Report

You can create parameterized Stored Procedure and Virtual Tables on the same Data Source (ODBC DSN or Data Gateway Data Source). Please refer to this article for the same. You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Using Custom Views in the SAP Crystal Report

After establishing the connection with AzureBlobCsvFileDSN Data Source you can use the custom view in SQL Crystal Report.

Using Custom Store Procedure in the SAP Crystal Report

1. First of all, create the custom store procedure in the ZappySys Driver. Please refer to this article to create the custom store procedure.
   
2. After establishing the connection with AzureBlobCsvFileDSN Data Source you can use the custom Store Procedure in SQL Crystal Report. Same way you can write custom queries also in the query box.
   AzureBlobCsvFileDSN

   

Create Custom Store 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 Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
   

2. Enter the desired Procedure name and click on OK:
   

3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store 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>';
   

   
   

4. That's it now go to Preview Tab and Execute your Store 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';

   
   

5. Let's generate the SQL Server Query Code to make the API call using store 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''')

   
   

6. Now go to SQL served and execute that query and it will make the API call using store 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.

1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
   

2. Enter the desired Table name and click on OK:
   

3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

4. 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'

   
   

5. 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"

   
   

6. Let's generate the SQL Server Query Code to make the API call using store 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''')

   
   

7. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
   

Conclusion

In this article we discussed how to connect to Azure Blob CSV File in SAP Crystal Reports and integrate data without any coding. Click here to Download Azure Blob CSV File Connector for SAP Crystal Reports 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 Azure Blob CSV File Connector for SAP Crystal Reports Documentation 

Other App Integration scenarios for Azure Blob CSV File

Other Connectors for SAP Crystal Reports

Download Azure Blob CSV File Connector for SAP Crystal Reports Documentation 

Common Searches: