ManagedEngine ServiceDesk Plus (Zoho) Connector for Informatica

In this article you will learn how to integrate ManagedEngine ServiceDesk Plus (Zoho) data in Informatica without coding in just a few clicks (live / bi-directional connection to ManagedEngine ServiceDesk Plus (Zoho)). ManagedEngine (Zoho) ServiceDesk Plus Connector can be used to integrate ServiceDesk Plus data in your App / BI Tools. You can read/write Requests, Tasks, Comments, Worklogs and many other items..

Using ManagedEngine ServiceDesk Plus (Zoho) Connector you will be able to connect, read, and write data from within Informatica. Follow the steps below to see how we would accomplish that.

Download Documentation

NOTE: If you need to consume API which is not listed on connector library page then please refer to the below article links. It talks about how to read / write pretty much any API and not just ManagedEngine ServiceDesk Plus (Zoho) API. It explains various API tips / tricks using our other Universal Drivers not mentioned in this article (i.e. ZappySys JSON / XML and CSV Drivers).
How to read API data in Informatica (Call JSON / XML SOAP Service)
How to write data to API (POST) in Informatica (Call JSON / XML SOAP Service)

Introduction

Informatica PowerCenter LogoJSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to access ManagedEngine ServiceDesk Plus (Zoho) data or may be other API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate ManagedEngine ServiceDesk Plus (Zoho) / XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.

After going through this article you will learn how to Read ManagedEngine ServiceDesk Plus (Zoho) / JSON / REST API data in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate  ManagedEngine ServiceDesk Plus (Zoho) or REST API integration in Informatica PowerCenter.

XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica,  Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)

Requirements

This article assumes that you have full filled following basic requirements.

  1. Download Install ZappySys ODBC PowerPack (API Driver for ManagedEngine ServiceDesk Plus (Zoho) included)
  2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
  3. Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

High level Steps for Import ManagedEngine ServiceDesk Plus (Zoho) data using Informatica (Read ManagedEngine ServiceDesk Plus (Zoho) API data)

Before we dive deep to learn how to load ManagedEngine ServiceDesk Plus (Zoho) data in Informatica (i.e. ManagedEngine ServiceDesk Plus (Zoho) to SQL Table), Here the summary of high-level steps you need to perform to import ManagedEngine ServiceDesk Plus (Zoho) in Informatica (same steps for Import JSON / XML / REST API).

  1. Download and Install ZappySys API Driver (for connecting to ManagedEngine ServiceDesk Plus (Zoho))
  2. Create ODBC DSN using ZappySys API driver and choose ManagedEngine ServiceDesk Plus (Zoho) Connector during Wizard
  3. Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
  4. Import ManagedEngine ServiceDesk Plus (Zoho) Source Definition in the Informatica Mapping Designer > Sources Tab
  5. Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
  6. Create source to target mapping in Mappings tab
  7. Save mapping (name m_API_to_SQL_Load )
  8. Create Session using the mapping we created in the previous step
  9. Save Workflow and execute to load ManagedEngine ServiceDesk Plus (Zoho) data into SQL Table. Verify your data and log.
    Loading JSON data to SQL Table in Informatica (Import ManagedEngine ServiceDesk Plus (Zoho) / REST API / JSON Files)

    Loading ManagedEngine ServiceDesk Plus (Zoho) data to SQL Table in Informatica (Import REST API or JSON Files)

Video Tutorial – Read any API / JSON data in Informatica (Load ManagedEngine ServiceDesk Plus (Zoho) to SQL Table)

Below video is not about ManagedEngine ServiceDesk Plus (Zoho) API but its showing API access in general (for any API). By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.

Getting Started – Import ManagedEngine ServiceDesk Plus (Zoho) to SQL Server in Informatica

Now let’s get started. For example purpose, we will read data from ManagedEngine ServiceDesk Plus (Zoho) and load data into SQL Server Table using Informatica Workflow.

Create ODBC Data Source (DSN) based on ZappySys API Driver

Step-by-step instructions

To get data from ManagedEngine ServiceDesk Plus (Zoho) using Informatica we first need to create a DSN (Data Source) which will access data from ManagedEngine ServiceDesk Plus (Zoho). We will later be able to read data using Informatica. Perform these steps:

  1. Install ZappySys ODBC PowerPack.

  2. Open ODBC Data Sources (x64):
    Open ODBC Data Source

  3. Create a User Data Source (User DSN) based on ZappySys API Driver

    ZappySys API Driver
    Create new User DSN for ZappySys API 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. When the Configuration window appears give your data source a name if you haven't done that already, then select "ManagedEngine ServiceDesk Plus (Zoho)" from the list of Popular Connectors. If "ManagedEngine ServiceDesk Plus (Zoho)" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

    ManagedEngineServiceDeskPlus(Zoho)DSN
    ManagedEngine ServiceDesk Plus (Zoho)
    ODBC DSN Template Selection

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

    OAuth Connection for ManageEngine ServiceDesk Plus API [API Help..]

    Steps to get ManagedEngine ServiceDesk Plus (Zoho) Credentials : OAuth [OAuth]
    To register custom App, perform the following steps (Detailed steps found in the help link at the end)
    1. Go to Zoho API Console
    2. Click Add Client link
    3. Select Server-based Applications option
    4. Enter desired client name (Display purpose only)
    5. Enter some URL for Company homepage
    6. For Authorized Redirect URI enter https://zappysys.com/oauth (Or enter your own but we recommend using ZappySys one if possible). This URL must match on Zoho Connector UI.
    7. Click CREATE.
    8. Copy Client ID and Secret and paste on Zoho Connector UI.

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

    ManagedEngineServiceDeskPlus(Zoho)DSN
    ManagedEngine ServiceDesk Plus (Zoho)
    OAuth [OAuth]
    https://sdpondemand.manageengine.com/api/v3
    Required Parameters
    Optional Parameters
    ClientId Fill in the parameter...
    ClientSecret Fill in the parameter...
    Permissions Fill in the parameter...
    AccountUrl Fill in the parameter...
    RedirectUrl Fill in the parameter...
    RetryMode Fill in the parameter...
    RetryStatusCodeList Fill in the parameter...
    RetryCountMax Fill in the parameter...
    RetryMultiplyWaitTime Fill in the parameter...
    ODBC DSN Oauth Connection Configuration

  6. Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
    ODBC ZappySys Data Source Preview

  7. Click OK to finish creating the data source.

Video instructions

Create Connection in Informatica Workflow Designer

Once you create DSN using API Driver our next step is to define a connection for ManagedEngine ServiceDesk Plus (Zoho) source in Informatica PowerCenter Workflow designer.

  1. Open Workflow designer [W] icon
  2. Goto Connections > Relational
    Create new connection for JSON in Informatica

    Create a new connection for ManagedEngine ServiceDesk Plus (Zoho) in Informatica

  3. Click New and select ODBC
    Select ODBC connection type in Informatica (Using ZappySys JSON ODBC DSN)

    Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)

  4. Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
  5. In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)
    Configure ManagedEngine ServiceDesk Plus (Zoho) connection in Informatica for REST API – Using ZappySys API ODBC Driver

    Configure ManagedEngine ServiceDesk Plus (Zoho) connection in Informatica for REST API – Using ZappySys API Driver

  6. Click OK to close the connection properties.

That’s it. Now we ready to move to next step (define source and target in Mapping Designer).

Import ManagedEngine ServiceDesk Plus (Zoho) Source Definition in Informatica Mapping Designer

Now let’s look at steps to import ManagedEngine ServiceDesk Plus (Zoho) table definition.

  1. Open Informatica Mapping Designer (Click [D] icon)
  2. Click on Source Icon to switch to Sources designer
  3. From the top menu > Click on Sources > Import from Database
    Import JSON Source definition in Informatica Mapping Designer (JSON file or REST API)

    Import ManagedEngine ServiceDesk Plus (Zoho) Source definition in Informatica Mapping Designer (JSON file or REST API)

  4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
  5. Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.
    DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
    —————————————————-
    Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
    Select JSON Source Table in Informatica Mapping Designer (JSON file or REST API)

    Select ManagedEngine ServiceDesk Plus (Zoho) Source Table in Informatica Mapping Designer (JSON file or REST API)

  6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
  7. Optionally once table structure is imported you can rename it
    Rename imported table definition in Informatica Source Designer

    Rename imported table definition in Informatica Source Designer

  8. That’s it, we are now ready to perform similar steps to import Target table structure in the next section.

Import SQL Server Target Definition in Informatica Mapping Designer

Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server).

Now lets look at steps to import target table definition in Informatica mapping designer.

  1. In the Mapping Designer, Click on Target Icon to switch to Target designer
  2. From the top menu > Click on Targets > Import from Database
  3. Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).
    Import target Table Definition in informatica

    Import target Table Definition in informatica

  4. Enter your userid , password and Schema name and click Connect to see tables
  5. Select Table name to and click OK import definition.
    Import Target SQL Table Definition in Informatica - Select table from the list

    Import Target SQL Table Definition in Informatica – Select table from the list

Create Source to Target Mapping in Informatica (Import JSON to SQL Server)

Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.

  1. First open Mapping Designer (Click [D] icon)
  2. Drag JSON Source from sources folder
  3. Drag SQL Table from Targets folder
  4. Map desired columns from Source to target
    Define Source to Target mapping for JSON to SQL Table load in Informatica

    Define Source to Target mapping for ManagedEngine ServiceDesk Plus (Zoho) to SQL Table load in Informatica

  5. For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
    TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM')
    
     --For ISO use below way
                    TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')
    Informatica JSON to SQL Table Mapping - Datatype conversion (nstring to datetime)

    Informatica ManagedEngine ServiceDesk Plus (Zoho) to SQL Table Mapping – Datatype conversion (nstring to datetime)

  6. Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
  7. Now lets move to next section to create workflow.

Create Workflow and Session in Informatica

Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.

  1. Open workflow designer by click [W] icon.
  2. Launch new workflow creation wizard by click Workflow top menuWizard
    name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)

    Creating Informatica Workflow - Wizard UI (Import JSON data to SQL Table)

    Creating Informatica Workflow – Wizard UI (Import ManagedEngine ServiceDesk Plus (Zoho) data to SQL Table)

  3. Finish the wizard and double-click the Session to edit some default properties.
  4. First change Error settings so we fail session on error (By default its always green)
    Fail Informatica Session on error (JSON to SQL Load)

    Fail Informatica Session on error (ManagedEngine ServiceDesk Plus (Zoho) data to SQL Load)

  5. Select JSON connection for Source
    Select JSON Source Connection in Informatica - JSON File / REST API Load to SQL Table

    Select ManagedEngine ServiceDesk Plus (Zoho) Source Connection in Informatica – Load ManagedEngine ServiceDesk Plus (Zoho) data to SQL Table

  6. Change default Source query if needed. You can pass parameters to this query to make it dynamic.
    Modify JSON Source SQL query - Pass parameters, change URL, set filter etc

    Modify ManagedEngine ServiceDesk Plus (Zoho) Source SQL query – Pass parameters, change URL, set filter etc

  7. Select Target connection of SQL Target Table
    Select SQL Target Connection in Informatica - JSON File / REST API Load to SQL Table

    Select SQL Target Connection in Informatica – Load ManagedEngine ServiceDesk Plus (Zoho) data to SQL Table

  8. Save workflow
  9. That’s it. We ready to run our first workflow to load JSON data to SQL.

Execute Workflow and Validate Log in Informatica

Now once you are done with your workflow, execute it to see the log.

Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

Loading ManagedEngine ServiceDesk Plus (Zoho) data to SQL Table in Informatica (Import REST API or JSON Files)

 

POST data to ManagedEngine ServiceDesk Plus (Zoho) in Informatica

There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article.

Video Tutorial – How to POST data to REST API in Informatica

Here is detailed step by step video on REST API POST in informatica PowerCenter

 

Keywords

how to import ManagedEngine ServiceDesk Plus (Zoho) in informatica | how to read ManagedEngine ServiceDesk Plus (Zoho) data in informatica powercenter | how to test json from informatica | how to use ManagedEngine ServiceDesk Plus (Zoho) data as source in informatica power center | how to connect ManagedEngine ServiceDesk Plus (Zoho) in informatica 10 | informatica how to import data from ManagedEngine ServiceDesk Plus (Zoho) | informatica jtx to import ManagedEngine ServiceDesk Plus (Zoho) (use of java transformation) | informatica plugin for restful api using json | informatica power center and ManagedEngine ServiceDesk Plus (Zoho) support | informatica read ManagedEngine ServiceDesk Plus (Zoho) | informatica rest api | informatica ManagedEngine ServiceDesk Plus (Zoho) connector | json parser import informatica

Advanced topics

Create Custom Stored Procedure in ZappySys Driver

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

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

  1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
    ZappySys Driver - Add Stored Procedure

  2. Enter the desired Procedure name and click on OK:
    ZappySys Driver - Add Stored Procedure Name

  3. Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
    Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

    CREATE PROCEDURE [usp_get_orders]
        @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
     AS
        SELECT * FROM Orders where OrderDate >= '<@fromdate>';
    

    ZappySys Driver - Create Custom Stored Procedure

  4. That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:

    Exec usp_get_orders '1996-01-01';

    ZappySys Driver - Execute Custom Stored Procedure

  5. Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')

    ZappySys Driver - Generate SQL Server Query

  6. Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

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:
    ZappySys Driver - Add Table

  2. Enter the desired Table name and click on OK:
    ZappySys Driver - Add Table Name

  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'

    ZappySys Driver - Create Custom Table

  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"

    ZappySys Driver - Execute Custom Virtual Table Query

  6. Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  7. Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Actions supported by ManagedEngine ServiceDesk Plus (Zoho) Connector

ManagedEngine ServiceDesk Plus (Zoho) Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.
 Get Requests
   [Read more...]
Parameter Description
 Get Request Details
   [Read more...]
Parameter Description
RequestId
 Get Request Tasks
   [Read more...]
Parameter Description
RequestId
 Get Request Task Details
   [Read more...]
Parameter Description
RequestId
TaskId
 Get Request Task Comments
   [Read more...]
Parameter Description
RequestId
TaskId
 Get Request Task Comment Details
   [Read more...]
Parameter Description
RequestId
TaskId
CommentId
 Get Request Notes
   [Read more...]
Parameter Description
RequestId
 Get Request Note Details
   [Read more...]
Parameter Description
RequestId
NoteId
 Get Request Worklogs
   [Read more...]
Parameter Description
RequestId
 Get Request Worklog Details
   [Read more...]
Parameter Description
RequestId
WorklogId
 Get Request Task Worklogs
   [Read more...]
Parameter Description
RequestId
TaskId
 Get Request Task Worklog Details
   [Read more...]
Parameter Description
RequestId
TaskId
WorklogId
 Delete Request
   [Read more...]
Parameter Description
RequestId
 Test Connection
   [Read more...]
 Get Changes
   [Read more...]
Parameter Description
 Get Change Details
   [Read more...]
Parameter Description
ChangeId
 Get Change Tasks
   [Read more...]
Parameter Description
ChangeId
 Get Change Task Details
   [Read more...]
Parameter Description
ChangeId
TaskId
 Get Change Task Comments
   [Read more...]
Parameter Description
ChangeId
TaskId
 Get Change Task Comment Details
   [Read more...]
Parameter Description
ChangeId
TaskId
CommentId
 Get Change Notes
   [Read more...]
Parameter Description
ChangeId
 Get Change Note Details
   [Read more...]
Parameter Description
ChangeId
NoteId
 Get Change Worklogs
   [Read more...]
Parameter Description
ChangeId
 Get Change Worklog Details
   [Read more...]
Parameter Description
ChangeId
WorklogId
 Get Change Task Worklogs
   [Read more...]
Parameter Description
ChangeId
TaskId
 Get Change Task Worklog Details
   [Read more...]
Parameter Description
ChangeId
TaskId
WorklogId
 Get Problems
   [Read more...]
Parameter Description
 Get Problem Details
   [Read more...]
Parameter Description
ProblemId
 Get Problem Tasks
   [Read more...]
Parameter Description
ProblemId
 Get Problem Task Details
   [Read more...]
Parameter Description
ProblemId
TaskId
 Get Problem Task Comments
   [Read more...]
Parameter Description
ProblemId
TaskId
 Get Problem Task Comment Details
   [Read more...]
Parameter Description
ProblemId
TaskId
CommentId
 Get Problem Notes
   [Read more...]
Parameter Description
ProblemId
 Get Problem Note Details
   [Read more...]
Parameter Description
ProblemId
NoteId
 Get Problem Worklogs
   [Read more...]
Parameter Description
ProblemId
 Get Problem Worklog Details
   [Read more...]
Parameter Description
ProblemId
WorklogId
 Get Problem Task Worklogs
   [Read more...]
Parameter Description
ProblemId
TaskId
 Get Problem Task Worklog Details
   [Read more...]
Parameter Description
ProblemId
TaskId
WorklogId
 Get Projects
   [Read more...]
Parameter Description
 Get Project Details
   [Read more...]
Parameter Description
ProjectId
 Get Project Tasks
   [Read more...]
Parameter Description
ProjectId
 Get Project Members
   [Read more...]
Parameter Description
ProjectId
 Get Project Milestones
   [Read more...]
Parameter Description
ProjectId
 Get Project Milestone Tasks
   [Read more...]
Parameter Description
ProjectId
MilestoneId
 Get Project Task Details
   [Read more...]
Parameter Description
ProjectId
TaskId
 Get Project Task Comments
   [Read more...]
Parameter Description
ProjectId
TaskId
 Get Project Task Comment Details
   [Read more...]
Parameter Description
ProjectId
TaskId
CommentId
 Get Project Notes
   [Read more...]
Parameter Description
ProjectId
 Get Project Note Details
   [Read more...]
Parameter Description
ProjectId
NoteId
 Get Project Worklogs
   [Read more...]
Parameter Description
ProjectId
 Get Project Worklog Details
   [Read more...]
Parameter Description
ProjectId
WorklogId
 Get Project Task Worklogs
   [Read more...]
Parameter Description
ProjectId
TaskId
 Get Project Task Worklog Details
   [Read more...]
Parameter Description
ProjectId
TaskId
WorklogId
 Get Releases
   [Read more...]
Parameter Description
 Get Release Details
   [Read more...]
Parameter Description
ReleaseId
 Get Release Tasks
   [Read more...]
Parameter Description
ReleaseId
 Get Release Task Details
   [Read more...]
Parameter Description
ReleaseId
TaskId
 Get Release Task Comments
   [Read more...]
Parameter Description
ReleaseId
TaskId
 Get Release Task Comment Details
   [Read more...]
Parameter Description
ReleaseId
TaskId
CommentId
 Get Release Notes
   [Read more...]
Parameter Description
ReleaseId
 Get Release Note Details
   [Read more...]
Parameter Description
ReleaseId
NoteId
 Get Release Worklogs
   [Read more...]
Parameter Description
ReleaseId
 Get Release Worklog Details
   [Read more...]
Parameter Description
ReleaseId
WorklogId
 Get Release Task Worklogs
   [Read more...]
Parameter Description
ReleaseId
TaskId
 Get Release Task Worklog Details
   [Read more...]
Parameter Description
ReleaseId
TaskId
WorklogId
 Get Assets
   [Read more...]
Parameter Description
 Get Asset Details
   [Read more...]
Parameter Description
AssetId
 Get Tasks
   [Read more...]
Parameter Description
 Get Task Details
   [Read more...]
Parameter Description
TaskId
 Get Contracts
   [Read more...]
Parameter Description
 Get Contract Details
   [Read more...]
Parameter Description
ContractId
 Get Purchase Orders
   [Read more...]
Parameter Description
 Get Purchase Order Details
   [Read more...]
Parameter Description
PurchaseOrderId
 Generic Request
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.    [Read more...]
Parameter Description
Url API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body Request Body content goes here
IsMultiPart Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
Headers Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

ManagedEngine ServiceDesk Plus (Zoho) Connector Examples for Informatica Connection

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

List requests    [Read more...]

This example shows how to list requests.

SELECT * FROM Requests

Read request details by ID    [Read more...]

This example shows how to read extended information about a single request

SELECT * FROM Requests Where id=111112345

Delete request    [Read more...]

This example shows how to delete a request by ID.

DELETE FROM Requests Where id=111112345

List request tasks    [Read more...]

This example shows how to read all tasks for a single Request ID

SELECT * FROM get_Request_Tasks WITH (RequestId=111112345)

Read request task details    [Read more...]

This example shows how to read request task details by single Request ID and Task ID

SELECT * FROM get_Request_Task_Details  (RequestId=111112345, TaskId=222212345)

List request task comments    [Read more...]

This example shows how to read all comment for specific task

SELECT * FROM get_Request_Task_Comments  (RequestId=111112345, TaskId=222212345)

Read request task comment details    [Read more...]

This example shows how to read a single comment details for a specific task

SELECT * FROM get_Request_Task_Comment_Details (RequestId=111112345, TaskId=222212345, CommentId=333312345)

List request notes    [Read more...]

This example shows how to read all notes for a single Request ID

SELECT * FROM get_Request_Notes WITH (RequestId=111112345)

Read request note details    [Read more...]

This example shows how to read request note details by single Request ID and Note ID

SELECT * FROM get_Request_Note_Details (RequestId=111112345, NoteId=222212345)

List request worklog    [Read more...]

This example shows how to read all worklogs for a single Request ID

SELECT * FROM get_Request_Worklogs WITH (RequestId=111112345)

Read request worklog details    [Read more...]

This example shows how to read request worklog details by single Request ID and Worklog ID

SELECT * FROM get_Request_Worklog_Details (RequestId=111112345, WorklogId=222212345)

List request task worklog    [Read more...]

This example shows how to read all worklogs for a single Request Task ID

SELECT * FROM get_Request_Task_Worklogs WITH (RequestId=111112345, TaskId=22222345)

Read request task worklog details    [Read more...]

This example shows how to read request task worklog details by single Request Task ID and Worklog ID

SELECT * FROM get_Request_Task_Worklog_Details (RequestId=111112345, TaskId=22222345, WorklogId=333312345)

List projects    [Read more...]

This example shows how to list projects.

SELECT * FROM Projects

Read project details by ID    [Read more...]

This example shows how to read extended information about a single project

SELECT * FROM Projects Where id=111112345

List assets    [Read more...]

This example shows how to list assets.

SELECT * FROM Assets

Read asset by ID    [Read more...]

This example shows how to read extended information about an asset

SELECT * FROM Assets Where id=111112345

List purchase orders    [Read more...]

This example shows how to list purchase orders.

SELECT * FROM PurchaseOrders

Read purchase order details by ID    [Read more...]

This example shows how to read extended information about a single purchase order

SELECT * FROM PurchaseOrders Where id=111112345

List changes    [Read more...]

This example shows how to list changes.

SELECT * FROM Changes

Read change details by ID    [Read more...]

This example shows how to read extended information about a change

SELECT * FROM Changes Where id=111112345

List contracts    [Read more...]

This example shows how to list contracts.

SELECT * FROM Contracts

Read contract details by ID    [Read more...]

This example shows how to read extended information about a contract

SELECT * FROM Contracts Where id=111112345

List tasks    [Read more...]

This example shows how to list tasks.

SELECT * FROM Tasks

Read task details by ID    [Read more...]

This example shows how to read extended information about a task

SELECT * FROM Tasks Where id=111112345

Conclusion

In this article we discussed how to connect to ManagedEngine ServiceDesk Plus (Zoho) in Informatica and integrate data without any coding. Click here to Download ManagedEngine ServiceDesk Plus (Zoho) Connector for Informatica 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 ManagedEngine ServiceDesk Plus (Zoho) Connector for Informatica Documentation 

More integrations

Other application integration scenarios for ManagedEngine ServiceDesk Plus (Zoho)

Other connectors for Informatica


Download ManagedEngine ServiceDesk Plus (Zoho) Connector for Informatica Documentation

  • How to connect ManagedEngine ServiceDesk Plus (Zoho) in Informatica?

  • How to get ManagedEngine ServiceDesk Plus (Zoho) data in Informatica?

  • How to read ManagedEngine ServiceDesk Plus (Zoho) data in Informatica?

  • How to load ManagedEngine ServiceDesk Plus (Zoho) data in Informatica?

  • How to import ManagedEngine ServiceDesk Plus (Zoho) data in Informatica?

  • How to pull ManagedEngine ServiceDesk Plus (Zoho) data in Informatica?

  • How to push data to ManagedEngine ServiceDesk Plus (Zoho) in Informatica?

  • How to write data to ManagedEngine ServiceDesk Plus (Zoho) in Informatica?

  • How to POST data to ManagedEngine ServiceDesk Plus (Zoho) in Informatica?

  • Call ManagedEngine ServiceDesk Plus (Zoho) API in Informatica

  • Consume ManagedEngine ServiceDesk Plus (Zoho) API in Informatica

  • ManagedEngine ServiceDesk Plus (Zoho) Informatica Automate

  • ManagedEngine ServiceDesk Plus (Zoho) Informatica Integration

  • Integration ManagedEngine ServiceDesk Plus (Zoho) in Informatica

  • Consume real-time ManagedEngine ServiceDesk Plus (Zoho) data in Informatica

  • Consume real-time ManagedEngine ServiceDesk Plus (Zoho) API data in Informatica

  • ManagedEngine ServiceDesk Plus (Zoho) ODBC Driver | ODBC Driver for ManagedEngine ServiceDesk Plus (Zoho) | ODBC ManagedEngine ServiceDesk Plus (Zoho) Driver | SSIS ManagedEngine ServiceDesk Plus (Zoho) Source | SSIS ManagedEngine ServiceDesk Plus (Zoho) Destination

  • Connect ManagedEngine ServiceDesk Plus (Zoho) in Informatica

  • Load ManagedEngine ServiceDesk Plus (Zoho) in Informatica

  • Load ManagedEngine ServiceDesk Plus (Zoho) data in Informatica

  • Read ManagedEngine ServiceDesk Plus (Zoho) data in Informatica

  • ManagedEngine ServiceDesk Plus (Zoho) API Call in Informatica