Tchater maintenant avec le support
Tchattez avec un ingénieur du support

KACE Systems Management Appliance 12.1 Common Documents - API Reference Guide

Existence

Existence

The existence of associated data in sub-entities can be tested using the following operators.

* 
NOTE: Values are not required for these operators:
•
ex: Exists
•
nex: Does not exist

Examples:

All machines with a recorded location:

/machines?filtering=machine_location.id ex

All machines without a recorded location:

/machines?filtering=machine_location.id nex

Filtering on related data

Filtering on related data

Note that adding a filter on a sub-entity does not cause the data for that sub-entity to appear in the result set.

The filter is applied, but shaping (or sorting) is required in order to specify extra return data.

Using wildcards in filters

Using wildcards in filters

There is a special case in which a filter can be applied to match any field of the entity. To use that capability, an asterisk '*' can be used as the field name.

The wildcard filter in some cases also matches values in sub-entities, to make them more useful to the client. The Service Desk API GET /api/service_desk/tickets has special handling to include owner names and submitter names in the wildcard. To find out if this handling is available and for more information about the Service Desk API, see Service Desk API Reference.

Examples:

Return the machines in which any field contains the string ABC:

/machine?filtering=* co ABC

Filters can be combined. The following example retrieves the machines that have the software title DEF installed and also have fields containing the ABC string:

/machine?filtering=* co ABC,software.name eq
DEF

Sorting

Sorting

Sorting is accomplished with the sorting query parameter. Commas can be used to separate multiple sorting requests. Each sorting request must give the sort entity and field. Optionally, a sort order can be specified. If the sort order is not specified, the default sort order is ASC (ascending). Sort requests are processed from left to right.

Sorting can be performed on the base entity as well as on any sub-entities. If sorting is indicated for a sub-entity that does not appear in the shaping clause, that sub-entity is automatically included at the standard shaping level. Any given shaping level overrides that value.

Examples:

Sort the machines by their ID in a descending list, and retrieve the software for each machine. Shaping is not necessarily required here. It is assumed that since ordering was requested for the software, it is expected in the result set:

/machines?sorting=machine.id,software.name
desc

Since shaping is not specified in the above example, the standard level is applied. However, note also that shaping can still be specified, if needed:

/machines?sorting= software.name
desc&shaping=software all

In this example any result data is sorted by the machine name and then the ID:

/machines?sorting=machine.name,machine.id
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation