I wanted to match up a field in wufoo that contains a single checkbox with a ‘Multi-Options (select many)’ field in CM (the wufoo field will have additional checkboxes added at a later date).

The problem is that wufoo won’t even display these fields in the ‘Match Fields’ dialogue UNLESS there’s MORE THAN ONE option defined for the corresponding Campaign Monitor field.

I’ve worked around this by simply adding a ‘Test (do not delete)’ option to the field in CM, but obviously this is less than ideal.

We have ended up (after advice from Andrew at wufoo) deciding to create a text field which has a predefined value. We will hide this field using CSS. We then map the hidden field through to the corresponding field in Campaign Monitor. This approach allows us to very easily and quickly (no techy involvement) create new forms.

We investigated using an field visible by admin only (and even using rules to hide the field based on the field itself not being empty). Both hide the field effectively – but they also result in the field value not being submitted.

The ideal solution would be for wufoo to create a new hidden field type in the editor (which they say is not planned at this stage). But for now we have big grins on our faces anyway because we can archive some code.

If you could either:
1) Submit “admin only” fields even when a non admin is submitting the form
This would allow us to set a single line text field with a predefined value indicating the “source” of this email subscriber as being this wufoo form.
OR
2) Give an additional option in the select controls on the “Match Fields” screen with allows the form name to be passed through.

We would prefer option 2 (and this might have less impact on other areas too).

Thoughts?