Maximo Open Forum

Are you talking about on a record in Maximo where you are trying to pick something like a work type & sub work type where the sub work type is dependent on work type? Or are you looking for something in the list tab/advanced search dialog?

The first scenario when you're on a record is more straight forward with a concept called a table domain. The second, while possible, I'd be hesitant to do unless you are dealing with custom attributes. I cover the second a bit here: Failure Reporting Search on Work Order Tracking Advanced Search | Maximo with some additional information here: Possible to Filter Lookup based on another field's value in the Advanced Search Dialog Box using Automation Script? | Maximo

The first scenario with table domains there are a lot of blog posts and IBM technotes and such. Bruno does a good breakdown here: MaximoDev - How to correctly define a Table Domain, though there is one thing in his example that I would change. The list where clause is used for filtering and the validation where clause is used for validating the value entered as he mentions. There are some exceptions but almost always, everything in your list where clause should be in the validation where clause. In his example, they only want to show active users which is critical for cron tasks because the user must be active to run a cron task. However, the validation is ensuring the userid exists but doesn't care about the status so if someone types in a value (or loads the data using the MIF), as long as it's a valid user, even if it's INACTIVE it will be allowed. This can lead to scenarios where you have users enter invalid data. 

Hi Justin - without knowing your full context, I'll add my bit:

We created an ALN domain for budget categories (values) and the departments responsible for those categories (description).
Then I created a table domain that references the ALN domain and searches for those departments by description.

If ASSET.EQ5 has the department number, then the table domain would look like this:

domainid='CATEGORY' and description like '%' || (select :eq5 from asset where assetnum = :assetnum) || '%'

The table domain looks up the ALN domain called category, and searches for one or more departments written in the description field. :eq5 allows you to search on non-persistent data (data that hasn't been saved to the database yet), and :assetnum looks at the current asset numbers. You apply the table domain to the lookup of the field for which you want a filtered list.

You could probably do something similar with that one ALN with a Conditional UI, but I couldn't tell you which scales better.