This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Identifying objects uniquely

BMC Remedy AR System uniquely identifies entries in a form through the Request ID field.

Objects in a directory service have an attribute called the distinguished name (dn), which uniquely identifies each object. An object's distinguished name often consists of one attribute or multiple concatenated attributes. For example:


BMC Remedy AR System Request IDs are 15 bytes maximum in length and are assigned by AR System when the entry is created. Distinguished names, on the other hand, are often longer than 15 bytes. However, you can map distinguished names longer than 15 bytes to AR System Request IDs.

When designing an BMC Remedy AR System form to access data stored in a directory service, you must determine what attribute to use to distinguish one object from another.


If you specify an attribute for the Request ID that resolves to an empty value for an object in the directory service, you receive an ARERR (100) Entry ID list is empty message, and no records are displayed in the client. If more than one record has the same value, you retrieve data only for the first matching entry.

For example, in a typical system the dn attribute uniquely identifies objects defined by the inetorgperson object class. You would create a field for User ID and associate both the Request ID field and the User ID field with the dn attribute.


This is the only case where you should associate one attribute with more than one BMC Remedy AR System field. Associating an attribute with more than one field might lead to run-time errors or incorrect behavior.

Was this page helpful? Yes No Submitting... Thank you