Form Unable to use CJ Filters

Usually, enabling CJ filters in a form is as simple as deleting the STL/Local filters, saving the field, and re-opening it. But sometimes, you might find a form that, no matter what you do, simply will not allow the use of Configurable Joins in conditional logic or prompt logic.

Cause

If you query the [form] table, you'll probably find that the form is very old. Further, you may notice that [form].[xml] is not null. That column has been deprecated for years.

To the best of our knowledge, any forms with [xml] data populated cannot be enabled for CJ's.

Solution

Your only course of action is to copy the form and migrate to the copy. If the offending form is an event template, we recommend copying the template and switching child events to the new template.

If you switch child events from the broken template to another, preexisting template, form field data will probably no longer display for existing registrations. Copying the template should preserve field-level data by copying the form fields exactly.

Note that switching templates is not destructive. You can switch templates, observe whether the fields work, and switch it back or to another template. The only consequence will be momentary disruption to anyone trying to use the events.