How to handle custom form fields for different forms ?

[Anonymous]

We have set of standard demographic fields and in addition to that we need to create custom fields to capture additional information in forms. Especially in case of events this list could be very long e.g. food preferences, itinerary, tracks.

These additional fields are not used in all the forms, and are not of big use once the particular campaign using these fields in finished.

So, how should we manage this large list of custom fields.

Any  thoughts ?

[Anonymous]

We have tons of custom fields. It would be wise to use a prefix (e.g. "custom_" or "temp_"). This will enable you to see which fields are relevant and which are not. You could also create an archive field. Every time you decide to remove a custom field you can append it's value to the archive field (text field). Example: Archivefield = {{lead.Archivefield}} | FieldLabelOfToRemoveField: {{lead.FieldNameOfToRemoveField}}.