Maximo Open Forum

 View Only

Related Content

  • 1.  How do I hide step buttons and force a lookup for WO Priority in Technician app?

    Posted 12-04-2025 06:11

    I'm customizing the Work Order Priority field in the Maximo Mobile Technician app and ran into something I'm not fully understanding.

    For most smart-input fields that use a lookup, Maximo automatically shows the lookup icon (magnifier). But for the Priority field, the default step buttons (numeric increment/decrement) appear instead, and the lookup icon does not show up.

    Here's the scenario:

    • I want to disable the default numeric step buttons for Priority.

    • I want to enable a lookup so the technician selects a priority from a configured lookup definition.

    Even with hide-step-buttons="true" and enable-lookup-buttongroup="true", the priority field still doesn't display the lookup button, unlike similar fields using the same properties.


    #EverythingMaximo
    #MaximoApplicationSuite

    ------------------------------
    Abhishek M R
    IBM
    ------------------------------


  • 2.  RE: How do I hide step buttons and force a lookup for WO Priority in Technician app?

    Posted 12-04-2025 09:28

    The MAF framework doesn't currently support lookups on smart-input when the data type is numeric. I opened an idea for this a while back (Support lookups on | IBM Sustainability Software - Ideas Portal) but I don't believe it has been implemented yet. 

    To do a lookup, you need to do something like TECHMOBILE does for worktype out of the box where you use a field control to display the selected value and then add a button that opens the lookup and copies the value and another to clear the value. 



    ------------------------------
    Steven Shull
    Naviam
    ------------------------------



  • 3.  RE: How do I hide step buttons and force a lookup for WO Priority in Technician app?

    Posted 12-08-2025 03:12

    Thanks for the clarification and pointing me in the right direction, it made things much clearer.

    I followed that approach and used a field-control layout with a clear button and lookup trigger. Here's the XML I ended up using :

    <border-layout fill-parent="true" padding="true" width="100%" id="a1_dmrxv">
    <start direction="row" horizontal-overflow="hidden" shrink="0" vertical-align="center" width="60" id="a1_qjy2z">
    <field empty-field-placeholder="Select Priority" required="true" label="Work Priority" swap-position="false" value="{dsWoedit.item.wopriority}" id="a1_drbrr"/>
    </start>
    <middle horizontal-align="end" horizontal-overflow="hidden" id="a1_bgaj9">
    <button hidden="{!dsWoedit.item.wopriority}" icon="Carbon:close--outline" kind="ghost" on-click="clearPriority" on-click-arg="{{'wopriority':''}}" padding="false" id="a1_b67xy"/>
    </middle>
    <end direction="column" horizontal-align="end" vertical-align="center" id="a1_j6v24">
    <button icon="Carbon:chevron--right" kind="ghost" on-click="openPriorityLookup" on-click-arg="{{'page':page,'app':app, 'item':dsWoedit.item}}" padding="false" id="a1_xbv4w"/>
    </end>
    </border-layout>



    ------------------------------
    Abhishek M R
    IBM
    ------------------------------

    Original Message