Chat now with support
Chat with Support

Identity Manager 9.0 LTS - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using Windows PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Order by clauses

The Order by clause in the One Identity Manager query language, specifies the order in which entries are returned.

ORDER BY <list of columns>

The column order can be specified by

  • ASC or ASCENDING (Standard)


When display values are selected, a default order by clause is created for the display columns.

Examples of Where clauses

ORDER BY Lastname, Firstname


You can specify fallback columns, which will be used for sorting if the previous values are NULL. These fallback values are specified by the null coalescing operator ??.

Examples for a fallback column's data

ORDER BY DisplayName ?? CN

ORDER BY DisplayName ?? CN DESC, XDateInserted

Paging clauses

Paging operators of the One Identity Manager query language make it possible to return only a subset of the selected entries.

Take clause

The Take clause specifies the maximum number of entries to be returned. If more than one Take clause is specified, only the last take clause is effective.

TAKE <integer>


-- Return only the first ten persons from the result set


Skip clause

The Skip clause specifies how many entries should be skipped from the beginning of the results before the entries are returned.

SKIP <integer>


-- Skip 50 persons and return the following 15


Display value clauses

Display value clauses allow the definition of a user-defined display pattern. The table's display pattern and the display pattern (long) can be overwritten by a display value clause in the returned entries.

DISPLAY 'Display pattern'

LONGDISPLAY 'Display pattern'

The parameter in both cases is a string containing the display pattern with placeholders in the form %ColumnName%.


FROM Person


DISPLAY '%Lastname%, %Firstname%'

LONGDISPLAY '%Lastname%, %Firstname% - %CentralAccount%'

Related topics

Query parameter clauses

In the One Identity Manager query language, query parameter clauses allow values to be passed in parameters that can be used in where clauses. You can pass a single parameter or a list of parameters.

Syntax for a single parameter

PARAM <Parameter name> [ OF <Type> ] = <Value>

Syntax for multiple parameters


<Param1> [ OF <Type> ] = <Value>,

<Param1> [ OF <Type> ] = <Value>,

Permitted parameter names are:

  • Syntax for parameter references with a qualifying @ character

  • Identifier

Valid types are the .Net data types of the object layer defined in ValType enumeration. If the type can be derived from the value, you do not have to give a type.

Examples of query parameters

PARAM Parameter1 = 'User'

PARAM @Parameter2 = 'User'

PARAM Parameter3 OF String = 'User'

PARAM @Parameter4 OF String = 'User'

PARAM Parameter5 = 42

PARAM Parameter6 OF Int = 42


Parameter7 OF Double = 3.14,

Parameter8 OF Date = 2020-04-30

Example: Complete query with parameter reference and definition

FROM Person

WHERE LastName = @Param1


PARAM Param1 = 'User'

Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating