That looks like a nice solution, a bummer that we'd have to deploy custom code to get it to work. We're trying to stick to the core form components when possible, given this step is supposed to achieve the same thing. I guess i'll dive into the error logs a bit more to try and figure out what's goin...