Each content type is included in a web service, together with a list of the most useful properties and field properties. For each content type, you can exclude fields that are included by default or include fields that are not included by default. You can also change the properties that are included for each field, such as sorting or filtering.
Perform the following:
The Author field is no longer available through the web service and the news Summary is available only as a read-only field.
Each type can have properties assigned to it, such as Name, Author, Related media, Parent, etc. There the following types of properties – Persistent, Calculated, Navigational, and Complex.
Perform the following:
NOTE: Filtering and sorting should be done on fields that have indexes on them. Most of the fields do not have indexes and as a result the filtering and sorting on those fields might take longer to execute. Use caution when enabling these two settings. Or as an alternative, you could manually add indexes on the fields that you want to filter or sort.
NOTE: If your service has an auto-generated collection of types, when you add a related data or related media to a type, Sitefinity CMS automatically creates a property mapping for this field. If the collection is not auto-generated, you have to create it manually.
IMPORTANT: If you want a related data or media field to be available in the service, the type of the related data or media must also be part of the service. For example, if you want a service to expose the related images of news items, the images type must also be exposed in the service.
EXAMPLE: You can query the related images of a news item, using the following query string:
In this case, RelatedImages is the exact name of the custom field that is set in the backend.
Expand will return all the properties of the related items of the news type.
For more information about to querying navigational properties, see oData documentation » System Query Option $expand.
NOTE: Navigational properties do not support filtering or sorting and are not optimized for performance.
Back To Top
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.