Automatic ID Lookup

Some sites need to display both numeric identifiers and human-friendly names for employees, organizations, room categories and types, buildings, and other data.  Most existing Web Central views include only the primary or foreign key field, which is where the numeric ID is stored.  For example, views showing rooms display Building Code and Department Code, but do not display Building Name and Department Name.

The report below illustrates the general issue.  Imagine that the Room Category, Room Type, Division Code, Department Code, and Employee Name fields were all just numeric values; the form could not be used off-the-shelf.  You would need to add the name fields to the view manually, for example, dp.namermcat.description, and so on.

You may need to change forms, reports, and other views to meet this requirement, and you may need to re-implement the changes with every release. The Automatic ID Lookup feature obviates the need for this customization because it automatically displays in views and controls a designated human-readable name or title field alongside -- or instead of -- the numeric code field. ARCHIBUS views and reports can be configured to work using numeric primary keys.

Automatic ID Lookup:

Examples of using automatic ID lookup

You may want to use the Automatic ID Lookup feature in these cases:

Terminology

The documentation for Automatic ID Lookup uses these terms: .

See Also

Configuring Automatic ID Lookup

Using Automatic ID Lookup in Data Sources

Using Automatic ID Lookup in Views

Using Automatic ID Lookup in Custom Code

Using Automatic ID Lookup for Translatable Fields

Upgrading Existing Applications to Support Automatic ID Lookup

Manage Automatic Lookups task

Copyright © 1984-2019, ARCHIBUS, Inc. All rights reserved.