ManagedEngine ServiceDesk Plus (Zoho) Connector
Documentation
Version: 2
Documentation
Endpoint

Delete Request


Name

delete_request

Description

No description available

Related Tables

Requests

Parameters

Parameter Label Required Options Description
RequestId RequestId YES

Output Columns

Label Data Type (SSIS) Data Type (SQL) Length Raw Description
status_code DT_I4 int False
status DT_WSTR nvarchar(180) 180 False
If the column you are looking for is missing, consider customizing ManagedEngine ServiceDesk Plus (Zoho) Connector.

Input Columns

Label Data Type (SSIS) Data Type (SQL) Length Raw Description
id DT_WSTR nvarchar(4000) 4000 False
Required columns that you need to supply are bolded.

Examples

SSIS

Use ManagedEngine ServiceDesk Plus (Zoho) Connector in API Source component to read data or in API Destination component to read/write data:

Delete rows from Requests table using API Destination

This Endpoint belongs to Requests table, therefore you cannot work with it directly. Use this table and table-operation pair instead:

ManagedEngine ServiceDesk Plus (Zoho)
Requests
Delete
SSIS API Destination - Access table operation

ODBC application

Use these SQL queries in your ODBC application data source:

Delete request

SELECT * FROM delete_request
WHERE id = 'abcd-1234-requestid'

Delete request

This example shows how to delete a request by ID.

DELETE FROM Requests Where id=111112345

delete_request endpoint belongs to Requests table(s), and can therefore be used via those table(s).

SQL Server

Use these SQL queries in SQL Server after you create a data source in Data Gateway:

Delete request

DECLARE @MyQuery NVARCHAR(MAX) = 'SELECT * FROM delete_request
WHERE id = ''abcd-1234-requestid''';

EXEC (@MyQuery) AT [LS_TO_MANAGEDENGINE_SERVICEDESK_PLUS_ZOHO_IN_GATEWAY];

Delete request

This example shows how to delete a request by ID.

DECLARE @MyQuery NVARCHAR(MAX) = 'DELETE FROM Requests Where id=111112345';

EXEC (@MyQuery) AT [LS_TO_MANAGEDENGINE_SERVICEDESK_PLUS_ZOHO_IN_GATEWAY];

delete_request endpoint belongs to Requests table(s), and can therefore be used via those table(s).