mfr - Field Service Management icon

mfr - Field Service Management

Field service management app for scheduling technicians.

Actions20

Service Request → Get Many Service Requests

AI-generated

Overview

This node operation retrieves multiple service requests from the Field Service Management system. It supports fetching all service requests or limiting the number of results returned. Users can apply filters and expand related hidden fields to customize the data retrieval. This operation is useful for scenarios where bulk data about service requests is needed, such as reporting, analytics, or integration with other systems.

Use Case Examples

  1. Fetch all service requests without limit to get a complete dataset for analysis.
  2. Retrieve a limited number of service requests with specific filters to monitor recent or relevant requests.
  3. Expand related fields like Qualifications to get detailed information in a single request.

Properties

Name Meaning
Fetch All Results Whether to fetch all service requests. If true, the limit is ignored and all service requests are retrieved.
Additional Fields Additional parameters to customize the request, including expanding hidden fields, filtering results, and limiting the number of results returned.

Output

JSON

  • id - Unique identifier of the service request.
  • name - Name of the service request.
  • externalId - External identifier of the service request.
  • state - Current state or status of the service request.
  • description - Description or details of the service request.
  • customerId - Identifier of the customer associated with the service request.
  • targetTimeInMinutes - Target time to complete the service request in minutes.
  • dueDateRangeEnd - End date of the due date range for the service request.
  • costCenterId - Identifier of the cost center related to the service request.
  • qualifications - Qualifications required or associated with the service request.

Dependencies

  • An API key credential for authentication with the Field Service Management API

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions to access service requests.
  • If fetching all results, be aware of potential performance impacts or timeouts due to large data volumes.
  • Use valid OData filter syntax in the filter field to avoid errors.
  • Check network connectivity and API endpoint availability if requests fail.

Links

Discussion