Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
We have the option to add a Participant Attribute to forms, which gives us the ability to collect certain information not covered by standard fields. This appears to have been intended for including extra details pertinent to each separate registrant (for example, we've used it to collect T-shirt size information for a 5k race). As such, the field will appear once on the form for each registrant, so if someone buys 5 tickets to something, it will appear 5 times. This is really the only custom field we have available in Online Express at the moment.
Once in a while, we would like to collect a single piece of data regardless of the number of registrations (for example, we'd like to ask registrants how they heard about an event, and we only need that one answer no matter how many tickets the person is purchasing), but if we add that as a Participant Attribute and someone buys 5 tickets, they'll be confused and/or annoyed that the field appears 5 times. Worse, if we make it required (as we likely would), people are likely to abandon the form instead of filling it out.
We should have the ability to collect data with custom fields that appear once per form regardless of the number of registrants. Attributes in RE: are flexible enough to allow us to collect all sorts of interesting data, but the current restriction to a one-to-one implementation is a highly limiting factor. It would be theoretically possible to add a field that operates in a one-to-many orientation, recording an Attribute as applicable to the registration itself, rather than individual registrants. In practice, it could be as simple as using the exact same Attribute table, but having the field apply that Attribute only to the primary Participant and not to any of the Guests. That way, we could have more flexibility in the data we collect on forms.
We have people in-house with the skills to develop custom forms that go through PayPal instead of Online Express if we really, really need to collect data that we can't get through OLX, but not all organizations do. Beyond that, it adds extra steps, as anything that comes through a custom form has to be manually entered into Raiser's Edge after-the-fact. Adding a custom field would open doors for a lot of organizations that turn to OLX for the simplicity it offers.