Currently all data fields on Event Registration forms are text fields.  Since we have several events with multiple payments (and sometimes different costs based on trip options), we create fields on the Registration form for the Event Manager to record/track payments.  When the data is exported to Excel for reports, Excel doesn't recognize the numbers, so you can't do formulas until you convert the fields with numbers to Numerical fields in Excel.  If we had the ability to designate specific fields as numeric or text, it would facilitate Event Managers in using Excel to track payments and easily determine the amount due for each attendee (copy/paste dollar amounts into a spreadsheet template that we create for them with formulas built in to do the calculation).  Not all our Event Managers are proficient or comfortable in Excel, so we want to make this as easy as possible for them.  I can build the spreadsheets for them, but they are the ones exporting the data for their event.

This makes total sense to me. I am surprised nobody else has commented on this.

Everyone - if you need this, please vote and/or comment here. 

---

Dmitry Buterin, Chief Apricot

I agree, this is needed.

Our association also would like more advanced reporting for events registration purchases.

We need expanded online admin reports of registration transactions with a breakdown showing the totals for optional add-ons that were selected by registrants. (e.g., 100 current registrants at $X in payments transacted, among whom 42 people bought ballgame tickets at $Y transacted.)

It also would be good to have some choices for how to review the registration data in addition to viewing registrations only by category of registration. (We have several different registration categories, and a consolidated table with totals for all registration categories in one view would be nice to have.)

Also, at the time of the user transaction, giving the registrant an itemized summary of the expenses incurred at the time they pay would be appreciated.  If someone picks several different options, they currently don't see an itemized display and they need to break out the calculator to be sure the total makes sense.

 Thanks!

 

I'd like to raise the bar on this and see if we could not just get numeric fields but also date fields. 

We like to capture the date of birth of club members and of event participants and it becomes difficult to manage that data if it is not in a constant format. 

Gordon

There is a separate thread re date fields, see

http://community.wildapricot.com/thread/4243.aspx

---

Dmitry Buterin, Chief Apricot

We've identified this as being in our Top 50 - The 50 issues we plan to develop solutions for in the next 12 months.

This thread will be moved to the  roadmap. Please keep the suggestions coming, and we'll let you know when we have a solution designed and a release date set.

 

It seems that there are several closely-related themes here:

• This is about creating new numeric-only fields.  I'd probably want to specify either whole numbers or fractions and to limit the number of decimal places if allowed at all.  Plus maximum and minimum values would be handy.
• There's a thread about limiting field length http://community.wildapricot.com/thread/15887.aspx
• There's a thread about setting a mask on a field http://community.wildapricot.com/thread/16505.aspx which in some respects is a more flexible version of forcing a field to be numeric only or fixing field length as the mask would allow mixed alpha numeric formats like post codes, social security numbers etc which have a particular length and distribution of alpha and/or numeric characters.
• There's a thread about editing the field-type on existing fields http://community.wildapricot.com/thread/16504.aspx

Perhaps all these (and any other similar threads/ideas) which to some degree overlap could be worked into a wider update on data entry forms.

I certainly have what are now text fields that I would always have preferred to be numeric only (if it was available) and others which are text now that I'd have wished to force format and capitalisation.

Seems to me that we're getting ever more complex functonality about events etc, but some basic functionality that any database created on a PC probably has to ensure consistent data entry doesn't exist here. 

I recently posted a request on the wish list for limits on text fields in the membership directory area: http://community.wildapricot.com/thread/16564.aspx before I saw this thread

As mentioned in the previous post, it seems that all these requests are related and that we should have basic data entry validation/limitation as a priority.

 

Regards,

Ian

They are related and we are looking at them together but each one requires a bit of work on its own - its not only about data entry and validation but also about Advanced search on these fields, proper export and many other considerations.

---

Dmitry Buterin, Chief Apricot