We had this issue once and used a workaround that required us to put the attribute as an entry in the LogicalAtrribute.xml file in the codebase directory in the section. We did something like this in the file:
<class name="wt.iba.value.IBAHolder">
<property>
<logicalform>AAAGate4Meeting</logicalform>
<externalform>IBA|AAAGate4Meeting</externalform>
</property>
</class>
This allowed us to use AAAGateMeeting or any custom attributes in the search criteria. This was the workaround we used in 9.1 M020, I believe this issue might already be resolved in M060. Which release version are you on?
Hope this helps.
Alexius C. Chukwuka
IT Analyst, Global SAP Basis - TCM
Deere & Company World Headquarters
400 19th St, Moline, IL 61265