ServiceDesk Plus Domo Connector

ServiceDesk Plus connector in Domo lets you fetch request datasets from ServiceDesk Plus Cloud and project them to DOMO, where you can visualize datasets as per your requirements. 

Due to security compliance requirements, MSP instance datasets are not supported currently. However, you can import data from other ServiceDesk Plus Cloud instances to Domo by creating individual datasets.

While fetching datasets related to request and change modules, only default request/change fields are supported in DOMO. Additional fields are currently unsupported.

In this guide, we will discuss the prerequisites for using the connector, best practices, and steps to connect to a ServiceDesk Plus account.

Prerequisites

You will need the ServiceDesk Plus login username and password to authenticate via OAuth 2.0.

Best Practice

Schedule reports at frequent intervals to maintain accurate and latest data of request details.

How to connect to ServiceDesk Plus

 

 

 

 

Report type selection


 

Dataset Schedule

Select a schedule for the data fetch. You have two options: Basic and Advanced.

Under Basic scheduling, you can set the Update interval to:

You can also set a particular time for the schedule. In the update method, you can choose either Replace or Append. The Replace option replaces all the data in the application with the new data that is being added. The Append option compares and adds only the differential data on top of the existing data.   

 

Under the Advanced option, you get to schedule the data update in the following ways:

 Select the schedule you require and set the time.

 

Error Handling

Select how the data update failure should be handled. You can choose between "Do not retry when update fails" and "Always retry when an update fails"

Once you have configured the scheduling, click Next.

Name and Description for Dataset

Enter a Dataset Name and Description. The name you select here will be displayed for your dataset under Data in Domo.

 

Click Save and Run. The dataset will be rendered.

Data entities that will be fetched include Request ID, Subject, Description, Template, Status, Technician, Created Time, Mode, Site, Group, Level, Approval Status, and etc.