How does a Maximo crossover domain copy fields, and what do its two check boxes do?

A CROSSOVER domain validates a value like a TABLE domain and then copies fields from the matching record. In our lab, with the default settings, an empty source value was not copied and clearing the field cleared nothing.

Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same fields, the two check boxes, the messages and the delivered crossover domains are present (17 November 2026). The behaviour described here was tested in our lab on Maximo 7.6.1.0 (3 November 2026); we have not re-run the behaviour test on Maximo Application Suite 9.1.

IBM’s page: IBM’s current Maximo Manage documentation says: “Crossover domains are similar to table domains because they validate a field value against another table in the product. However, crossover domains allow data from the other table to be copied into fields in the current application.” That page does not cover empty values or overwriting.

Last checked: 17 November 2026

How it works

Each crossover row names a Source Field (on the domain’s object), a Destination Field (on the record being edited) and two check boxes. When the field gets a valid value, Maximo finds the matching source record and copies each source field to its destination.

Our test: a crossover domain on ASSET that copied the asset number and the asset’s priority into two fields of a work order.

Check boxesTestResult
Both clear (default)Choose an assetBoth destinations filled.
Both clearUser typed values first, then chose another assetOverwritten.
Both clearAsset whose priority is emptyDestination kept its old value. An empty source is not copied.
No Overwrite on the asset numberChoose one asset, then anotherDestination kept the first asset.
Accept NULL value on priorityThen an asset with no priorityDestination cleared.
AnyClear the fieldDestinations keep their values.
AnyA value that does not existBMXAA4191E. Nothing copied.

What we observed in our lab: IBM’s class documentation for 7.6 says empty source values are copied and that clearing the field clears the copies. With the default settings, in our lab we observed neither. Tick Accept NULL value if you need empty values copied, and clear the copied fields yourself if the trigger field is cleared.

Steps

  1. Domains > Add New Domain, type CROSSOVER.
  2. Add a row: Object = the source object, and a Validation Where Clause that uses every key, for example assetnum=:assetnum and siteid=:siteid.
  3. Add the crossover fields: Source Field, Destination Field, and the two check boxes as needed.
  4. Save. Then attach the domain to the trigger attribute in Database Configuration.
  5. Test four cases: a first value, a changed value, a source with empty fields, and a destination the user already filled.

Where it breaks

How we checked it

On a Maximo 7.6.1.0 lab system we created test table and crossover domains. A test script made a work order in memory, attached our domain to an empty spare field with the same domain classes Maximo uses, set values and rolled back. This runs the same code Maximo attaches from the Domain field, but it is not the screen path. On Maximo Application Suite 9.1 we only read the domain tables, the field names and the messages. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.

This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.