Thanks Steve. We do not have a table domain for INVBALANCES.BINNUM.
I did get a while back, the getList limit and changed the system property mxe.db.fetchResultStopLimit.INVBALANCES global value to -1.
I am checking on the automation scripts at the moment. I included below the full error from the cron task for context.
Template user: MAXIMO-ADMIN;
Template user insert site: XYZ;
Person groups associated: XYZPRELOAD;
--------------------------------------
Error list:
--------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Object structure: MXAPIINVBAL;
Table name: INVBALANCES;
Select attributes: invbalancesid,siteid,itemnum,location,binnum,curbal,lotnum,conditioncode;
Saved query: ACTIVEITEMSITE;
**************************************
Error to query filter INVBALANCES_BINNUM page 1: BMXAA4107E - Because of an implementation or customization problem, the system cannot determine how the attributes of object INVBALANCES correspond to the attributes INVBALANCESID of object INVBALANCES. You might need to populate the MAXLOOKUPMAP table and restart the server.
**************************************
Error to query filter INVBALANCES_LOTNUM page 1: BMXAA4107E - Because of an implementation or customization problem, the system cannot determine how the attributes of object INVBALANCES correspond to the attributes INVBALANCESID of object INVBALANCES. You might need to populate the MAXLOOKUPMAP table and restart the server.
**************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~