Did you know that you can create lookups in Maximo (in the lookups.xml)\u00a0with whereclause and attach it to an attribute in application designer. The attribute doesn’t require\u00a0a\u00a0domain to be attached to it to show the data in the lookup .<\/p>\n

<\/a><\/p>\n

The lookup will simply query the object\u00a0mentioned in the mboname<\/em> with the whereclause<\/em> and display the result. The only drawback to this approach is that there is no validation on the attribute – any value entered in the field would be accepted without any validation.<\/p>\n

The where clause also accepts run-time variables such as :user.<\/p>\n

This is useful in places such as report request pages where a parameter needs to be passed to the report with a lookup which shows much filtered data then is\u00a0usually shown in the lookup in\u00a0the application.<\/p>\n

For instance this asset availability report request page has a parameter as Tool which only shows items of type tool and not all the items.<\/p>\n

<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Did you know that you can create lookups in Maximo (in the lookups.xml)\u00a0with whereclause and attach it to an attribute in application designer. The attribute doesn’t require\u00a0a\u00a0domain to be attached to it to show the data in the lookup . The lookup will simply query the object\u00a0mentioned in the mboname with the whereclause and display … Continue reading Lookup With WhereClause<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[11,5],"tags":[],"yoast_head":"\n