Troubleshooting DBLookup filtering

If you end up with no results in your secondary 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 primaryInputFields values do not contain the _# (the underscore followed by a number) extension.
3. Ensure that if you have more than one primary DBLookup, the order of the primaryInputFields values matches the order of the primaryDataFields values.
4. Ensure that if you have more than one primary DBLookup, the order of the primaryInputFields 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 primaryInputFields must be reversed:

   Docket	Department	Project
   FIELDS5X	FIELDS4X	FIELDS3X

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

   primaryInputFields=[A,B]
   primaryDataFields=[C,D]

   Or:

   primaryInputFields=[B,A]
   primaryDataFields=[D,C]

   But never:

   primaryInputFields=[A,B]
   primaryDataFields=[D,C]

   And never:

   primaryInputFields=[B,A]
   primaryDataFields=[C,D]

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

   For example, if your secondary DBLookup is Job, and your primary 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.