This is a great suggestion and I hope that YM will give it some serious consideration! Would make data management much easier on the associations.

Wow, this idea just keeps growing in popularity. Let's start to compile a list of the pages and exports that you feel are required for a Release 1.0? We know we can't have it all so only list the pages and exports that have the greatest and immediate impact for your members.

I strongly support the idea of being able to change the field label for profile fields as well as the ability to add sub-headings and organize fields in a way that will make the end-users' experience easier to understand / navigate. I also think it would be great if YM could include several undefined "hard-coded" profile fields that admins could customize. These fields would be extremely helpful in registration and custom forms as they would be pre-populated for signed-in members and would greatly improve data consistency for admins. Having the ability to add these new fields, or select from current custom fields, to the Quick Search function would be amazing!

Renaming fields would be great! ditto "Location" causes plenty of confusion in our case we wound change that to State/Providence in a heart beet. It would be expected that the names would carry over to the export.

I WHOLE HEARTEDLY endorse this IDEA! Being able to not only customize the labels of hard-coded fields AND reorganize all fields into some semblance of order for both members and admin would be a dream come true.

Still strongly in support of this changeover. I think that not only changing the field labels for YM's hard coded fields as I have mentioned before but being to determine the order of fields (regardless of their status as custom vs. hard coded) would be ideal. I don't want my custom fields to default to being below Ym's hard coded fields. Thanks!

This is a great idea. There are situations where we create a custom filed just because you are unable rename a profile field. Determining the order would also be a great idea. Certain fields have no relevance to us and so placing them diferently would be great.

Being able to change the name, sub header and order of each field would be great. The Post Code/Zip Code field should also change name depending on the country selected in the drop down. I found the Birthday field could cause a significant problem if your association has members from different countries. This is quite a complex issue to explain so bare with me. Our locale settings in the admin back end are set to UK where the date format is DD/MM/YYYY. However, the info in parentheses next to the Birthday field still shows the format MM/DD/YYYY. (In the image below) As well as this, the little calendar icon defaults to MM/DD/YYYY when you click on a date. This alone could be confusing for our UK members, which will be the majority. With our Locale settings set to UK I found that when you write your Birthday in the US format MM/DD/YYYY and save the settings, the date changes to the UK format DD/MM/YYYY. This only happens if the date written does not make sense as a UK date format, for example, writing 29th December 1999 in the US format - 12/29/1999 will automatically change to the UK format - 29/12/1999 because it knows there are not 29 months in a year. However, if you were to write 6th May 1999 in the US format - 05/06/1999, this will not change to the UK format because it still makes sense as a date even though it is the wrong date. A simple solution for this is to let us change the info in parentheses and make the calendar icon submit dates in the UK format. This would mean non UK users would have to write in a format they are not used to. A better but more complicated solution is giving users the ability to select a global setting so all dates on the site are displayed in their local format. All of their account data would have to be converted to the Locale settings in the back end. This could be incorporated into when they select their time zone or you could make another drop-down for language. Hopefully this makes sense.

Why no response and why haven't some of these suggestions been implemented, especially allowing admins to change hard code field names?

Adding custom fields that you can do more with would also be nice. We have a custom field for "Certifications" that we usually want to append to everybody's name, but we can't do that in most places.