Hi @Sourabh Jain

Have you considered extending the Query Clause for the assignedPMWorkorders saved query definition in MAS Manage, rather than using mobile-qbe-filter?

------------------------------
Bartosz Marchewka
IBM Maximo Consultant
AFRY
------------------------------

Hi Bartosz,

I'm working on filtering records for the mobile device and have run into a limitation with the mobile-qbe-filter.

The Scenario: I have a Work Order with multiple assignments (e.g., two assignments for LABOR-X). Currently, I am using the condition assignment[0].status_maxvalue.

The Issue:

• If a Work Order has two assignments and only one is marked as COMPLETE, the Work Order is excluded from the dropdown list because the filter only evaluates the first element of the array ([0]).
• On mobile, we don't change the Work Order status directly. We complete the assignments instead. We need the Work Order to remain visible until all relevant assignments are handled, or be excluded only when specific criteria across the array are met.

Since the standard QBE filter seems limited to single-index checks, I am considering using onAfterLoadData within appCustomizations to implement the business logic and filter the records programmatically.

------------------------------
Sourabh
------------------------------


Original Message:
Sent: Tue April 14, 2026 05:15 AM
From: Bartosz Marchewka
Subject: mobile-qbe-filter Syntax in Maximo Mobile

Hi @Sourabh Jain

Have you considered extending the Query Clause for the assignedPMWorkorders saved query definition in MAS Manage, rather than using mobile-qbe-filter?

------------------------------
Bartosz Marchewka
IBM Maximo Consultant
AFRY

Since we have less control over which record assignment[0] may have, I think doing programmatically in onAfterLoadData is good option here. We have done something similar where we replaced the UI to use Json data source and then update the Json data source on onAfterLoadData. Below is sample script if that helps at all, similar to what we have created:

async onAfterLoadData(dataSource, items) {if (dataSource && dataSource.name === "assignedPMWorkorders") {      console.log("Entering AppCustomizations.onAfterLoadData for assignedPMWorkorders");      let workorderDisplayData = [];      let obj = {};      let cus_activeassignments = [];            //      // find the datasouce cus_dswolist_json_ds and read the attributes defined.      //      let cus_dswolist_json_ds = this.app.findDatasource("cus_dswolist_json_ds");      let json_attributes = cus_dswolist_json_ds.baseQuery.select.split(',');      //      //  Ensure we have at least one record      // 'items' referenced below is the the rows in assignedPMWorkorders datasouce.      //      if (items && items.length > 0) {        //        //for each row in assignedPMWorkorders datasource, iterate        //        items.forEach((record) => {          //          // Check how many active assignments are there for this record (WO/Task)          // and set it to cus_activeassignmentcount.  We only want to show          // WO/Task with atleast one active assignments in List view. Below logic          // makes sure the app behaves properly even when users are not in           // network and have one or multiple assignments that they complete.          //          if (record.assignment) {            cus_activeassignments = record.assignment.filter(s => s.status_maxvalue != 'COMPLETE')            if (cus_activeassignments.length > 0) {              //              // for each attribute defined in json datasouce cus_dswolist_json_ds, make a copy of value in obj dictionary if found in assignedPMWorkorders              //              json_attributes.forEach((element) => {                //console.log("element " + element + " " + record[element]);                obj[element] = record[element];              })            }          }          //          // save data from obj dictionary into workorderDisplayData array          //          if (Object.keys(obj).length != 0) {            workorderDisplayData.push(obj);          }          //          // Empty Obj dictionary to process next row from  assignedPMWorkorders datasource          //          obj = {};        })      }      //      // load the data created above onto cus_dswolist_json_ds datasource to display in UI      //      await cus_dswolist_json_ds.load({        src: workorderDisplayData,        noCache: true      });      console.log("Exiting AppCustomizations.onAfterLoadData for assignedPMWorkorders");    }  }

Hi Bartosz,

I'm working on filtering records for the mobile device and have run into a limitation with the mobile-qbe-filter.

The Scenario: I have a Work Order with multiple assignments (e.g., two assignments for LABOR-X). Currently, I am using the condition assignment[0].status_maxvalue.

The Issue:

• If a Work Order has two assignments and only one is marked as COMPLETE, the Work Order is excluded from the dropdown list because the filter only evaluates the first element of the array ([0]).
• On mobile, we don't change the Work Order status directly. We complete the assignments instead. We need the Work Order to remain visible until all relevant assignments are handled, or be excluded only when specific criteria across the array are met.

Since the standard QBE filter seems limited to single-index checks, I am considering using onAfterLoadData within appCustomizations to implement the business logic and filter the records programmatically.

------------------------------
Sourabh


Original Message:
Sent: Tue April 14, 2026 05:15 AM
From: Bartosz Marchewka
Subject: mobile-qbe-filter Syntax in Maximo Mobile

Hi @Sourabh Jain

Have you considered extending the Query Clause for the assignedPMWorkorders saved query definition in MAS Manage, rather than using mobile-qbe-filter?

------------------------------
Bartosz Marchewka
IBM Maximo Consultant
AFRY

Thanks PJ. I tried few things using onAfterLoadData and JSON data source but being a schedule page datasource is making it complex. 

Was your requirement also for the Schedule page datasource?

I have used JSON data sources for other pages a number of times successfully.

Since we have less control over which record assignment[0] may have, I think doing programmatically in onAfterLoadData is good option here. We have done something similar where we replaced the UI to use Json data source and then update the Json data source on onAfterLoadData. Below is sample script if that helps at all, similar to what we have created:

async onAfterLoadData(dataSource, items) {if (dataSource && dataSource.name === "assignedPMWorkorders") {      console.log("Entering AppCustomizations.onAfterLoadData for assignedPMWorkorders");      let workorderDisplayData = [];      let obj = {};      let cus_activeassignments = [];            //      // find the datasouce cus_dswolist_json_ds and read the attributes defined.      //      let cus_dswolist_json_ds = this.app.findDatasource("cus_dswolist_json_ds");      let json_attributes = cus_dswolist_json_ds.baseQuery.select.split(',');      //      //  Ensure we have at least one record      // 'items' referenced below is the the rows in assignedPMWorkorders datasouce.      //      if (items && items.length > 0) {        //        //for each row in assignedPMWorkorders datasource, iterate        //        items.forEach((record) => {          //          // Check how many active assignments are there for this record (WO/Task)          // and set it to cus_activeassignmentcount.  We only want to show          // WO/Task with atleast one active assignments in List view. Below logic          // makes sure the app behaves properly even when users are not in           // network and have one or multiple assignments that they complete.          //          if (record.assignment) {            cus_activeassignments = record.assignment.filter(s => s.status_maxvalue != 'COMPLETE')            if (cus_activeassignments.length > 0) {              //              // for each attribute defined in json datasouce cus_dswolist_json_ds, make a copy of value in obj dictionary if found in assignedPMWorkorders              //              json_attributes.forEach((element) => {                //console.log("element " + element + " " + record[element]);                obj[element] = record[element];              })            }          }          //          // save data from obj dictionary into workorderDisplayData array          //          if (Object.keys(obj).length != 0) {            workorderDisplayData.push(obj);          }          //          // Empty Obj dictionary to process next row from  assignedPMWorkorders datasource          //          obj = {};        })      }      //      // load the data created above onto cus_dswolist_json_ds datasource to display in UI      //      await cus_dswolist_json_ds.load({        src: workorderDisplayData,        noCache: true      });      console.log("Exiting AppCustomizations.onAfterLoadData for assignedPMWorkorders");    }  }

Hi Bartosz,

I'm working on filtering records for the mobile device and have run into a limitation with the mobile-qbe-filter.

The Scenario: I have a Work Order with multiple assignments (e.g., two assignments for LABOR-X). Currently, I am using the condition assignment[0].status_maxvalue.

The Issue:

• If a Work Order has two assignments and only one is marked as COMPLETE, the Work Order is excluded from the dropdown list because the filter only evaluates the first element of the array ([0]).
• On mobile, we don't change the Work Order status directly. We complete the assignments instead. We need the Work Order to remain visible until all relevant assignments are handled, or be excluded only when specific criteria across the array are met.

Since the standard QBE filter seems limited to single-index checks, I am considering using onAfterLoadData within appCustomizations to implement the business logic and filter the records programmatically.

------------------------------
Sourabh


Original Message:
Sent: Tue April 14, 2026 05:15 AM
From: Bartosz Marchewka
Subject: mobile-qbe-filter Syntax in Maximo Mobile

Hi @Sourabh Jain

Have you considered extending the Query Clause for the assignedPMWorkorders saved query definition in MAS Manage, rather than using mobile-qbe-filter?

------------------------------
Bartosz Marchewka
IBM Maximo Consultant
AFRY