Answers.Body: <p>No there isn't. In the same way as Craft, each field has a unique handle which is used both for templating and for email notifications.</p>
  
  <p>Solspace support might have some other ideas, but I think this is just the way Freeform is built.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-16T07:49:05.677Z
Answers.LastActivityDate: 2019-10-16T07:49:05.677Z
Answers.UserDisplayName: darylknight
Answers.Body: <p>There is the MySQL limitation that Freeform can run into, and it seems likely in your situation. One thing you can do is reuse fields across forms... so for example, every form might have a first name, last name, email field, etc. Instead of having a new one for each form, you can have those as 3 fields used multiple times. And then, if possible, you can still override fields from one form to the next. For example, you could have a USA form with a field named "Zip Code", and use it in the next form as "Postal Code" for a Canadian version of the form, etc. I do get how you can run into issues if you start building very complex and different forms that pretty much require a different set of fields for each.</p>
  
  <p>We have heard that several customers have had success by switching the field's column type from VARCHAR 255 to TEXT and they have reported getting upwards of 300 fields.</p>
  
  <p>Also, if possible, one other option would be using the new <a href="https://docs.solspace.com/craft/freeform/v3/overview/fields-field-types.html#table" rel="nofollow noreferrer">Table fieldtype</a>.</p>
  
  <p>We're also beginning to work on Freeform 4, which will have several areas of the plugin rebuilt, including how fields and forms are architected and stored in database tables. A release date on this would likely be early 2020. :)</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-16T21:55:14.087Z
Answers.LastActivityDate: 2019-10-16T21:55:14.087Z
Answers.UserDisplayName: Solspace
Answers.Body: <p>You might want to bypass the graphical form builder in this case and code it manually. I <em>think</em> this would let you give multiple fields an array-name: <code>name="fieldname[]"</code> (not sure what the correct terminology is for that). </p>
  
  <p>Basically though, that would mean that all the fields with <code>name="fieldname[]"</code> would end up having their data combined and saved to the single <code>fieldname</code> field.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-16T15:42:15.853Z
Answers.Text: thanks for the idea
Answers.UserDisplayName: Erant
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-16T11:41:01.680Z
Answers.LastActivityDate: 2019-10-16T11:41:01.680Z
Answers.UserDisplayName: Sandwich
Body: <p>I have a set of very long forms.  Many of these forms require repetitive field types - example:  one of my forms requires the "date" field 15 times.</p>
  
  <p>Another form requires at least 30 single line text entries + dozens of radio button entries.</p>
  
  <p>It appears I can only use a field once per form, forcing me to create a new field each time I use a previous one.  Is there any way around this?</p>
  
  <p>I see I can re-label fields for each form which helps but wondering if there is a better way.</p>
  
  <p>I'm definitely going to run up against the 130 field limit if I have to create new ones each time.  </p>
  
Tags: <plugin-freeform><solspace>
Title: Freeform - using multiple fields on the same form
ThreadText: # Freeform - using multiple fields on the same form
  
  (Asked by: username_0 on 2019-10-16)
  
  I have a set of very long forms. Many of these forms require repetitive field types - example: one of my forms requires the "date" field 15 times.
  
  Another form requires at least 30 single line text entries + dozens of radio button entries.
  
  It appears I can only use a field once per form, forcing me to create a new field each time I use a previous one. Is there any way around this?
  
  I see I can re-label fields for each form which helps but wondering if there is a better way.
  
  I'm definitely going to run up against the 130 field limit if I have to create new ones each time.
  
  **Tags:** plugin-freeform, solspace
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2019-10-16. Score: 1
  
  No there isn't. In the same way as Craft, each field has a unique handle which is used both for templating and for email notifications.
  
  username_2 support might have some other ideas, but I think this is just the way Freeform is built.
  
  
  ---
  
  ### Answer by username_2 on 2019-10-16. Score: 1
  
  There is the MySQL limitation that Freeform can run into, and it seems likely in your situation. One thing you can do is reuse fields across forms... so for example, every form might have a first name, last name, email field, etc. Instead of having a new one for each form, you can have those as 3 fields used multiple times. And then, if possible, you can still override fields from one form to the next. For example, you could have a USA form with a field named "Zip Code", and use it in the next form as "Postal Code" for a Canadian version of the form, etc. I do get how you can run into issues if you start building very complex and different forms that pretty much require a different set of fields for each.
  
  We have heard that several customers have had success by switching the field's column type from VARCHAR 255 to TEXT and they have reported getting upwards of 300 fields.
  
  Also, if possible, one other option would be using the new [Table fieldtype](https://docs.username_2.com/craft/freeform/v3/overview/fields-field-types.html#table).
  
  We're also beginning to work on Freeform 4, which will have several areas of the plugin rebuilt, including how fields and forms are architected and stored in database tables. A release date on this would likely be early 2020. :)
  
  
  ---
  
  ### Answer by username_3 on 2019-10-16. Score: 1
  
  You might want to bypass the graphical form builder in this case and code it manually. I *think* this would let you give multiple fields an array-name: `name="fieldname[]"` (not sure what the correct terminology is for that).
  
  Basically though, that would mean that all the fields with `name="fieldname[]"` would end up having their data combined and saved to the single `fieldname` field.
  
  > **Comments:**
  > **username_0**: thanks for the idea  
  
  ---
  
  