Troubleshooting DBLookup filtering

If you end up with no results in your slave DBLookup after you set up filtering, follow these steps:

1. Ensure the table exists in the database and that the table contains the expected data.
2. Ensure the masterInputFields values do not contain the _# (the underscore followed by a number) extension.
3. Ensure that if you have more than one master DBLookup, the order of the masterInputFields values matches the order of the masterDataFields values.
4. Ensure that if you have more than one master DBLookup, the order of the masterInputFields in the SQL expression is in the opposite order of how the DBLookups are displayed on the page.

   For example, if the DBLookups on the page are in this order:

   Project	Department	Docket

   This condition means that in the SQL expression, the order of the masterInputFields must be reversed:

   Docket	Department	Project
   FIELDS5X	FIELDS4X	FIELDS3X

5. If you still have difficulty, you can try changing the order of the masterInputFields and masterDataFields (as long as they still correspond):

   masterInputFields=[A,B]
   masterDataFields=[C,D]

   Or:

   masterInputFields=[B,A]
   masterDataFields=[D,C]

   But never:

   masterInputFields=[A,B]
   masterDataFields=[D,C]

   And never:

   masterInputFields=[B,A]
   masterDataFields=[C,D]

6. If you cannot find a value in the slave DBLookup, even when no master DBLookup values have been entered, check that every required value in the slave DBLookup table is associated with at least one value in the master DBLookup table.

   For example, if your slave DBLookup is Job, and your master DBLookup is Project, and you are looking for the Training job value, ensure that Training is associated with at least one project in your table.