Current Implementation
The PROLIN Power Server REST API exposes a subset of the Smart Suite domain model and provides access to entities and their fields.
Supported Entities
The following entities are exposed by the REST API, each through its own entity set:
| Entity | Entity set |
|---|---|
| Service Request (Service call) | ServiceRequests |
| Problem | Problems |
| Incident | Incidents |
| Change | Changes |
| Work Order | Workorders |
| Configuration Item | ConfigurationItems |
| E-mail Service Request | EmailServiceRequests |
| Service | Services |
| Person | Persons |
| Organization | Organizations |
| Maintenance Contract | MaintenanceContracts |
| Project | Projects |
| Workgroup | Workgroups |
| Service Level Agreement | ServiceLevelAgreements |
| Service Level | ServiceLevels |
| Location | Locations |
| Template | Templates |
Entity set names in URLs are case-sensitive.
Attachments and history lines have no entity set of their own. They are reached through the entity they belong to, for example ServiceRequests(<key>)/Attachments; see Working With Attachments and Navigation.
Two functions complete the API: the Codes endpoint (/Codes) and the Me endpoint (/Me).
Supported Fields
- Most field types are supported, including custom fields.
- Supported field types:
- Text
- Numeric
- Date/Time
- Boolean
- Duration
- Code fields
For a complete list of supported fields, refer to the metadata document, which can be obtained from the OData service endpoint hosted by PROLIN Power Server. Always retrieve it from the server you integrate with: the fields it lists depend on the version and on what is enabled on that server, such as activated custom fields.
Not Supported
The following are currently out of scope in this release:
- Certain relationships between entities (including some aggregated entities like approvals) may not work
- Custom OData actions and functions (the built-in
/Codesand/Mefunctions are supported) - Calculated fields