Answers.Body: <p>An entry type can only use a field once, regardless the tab. But you can reuse the field in other entry types of that same section or reuse it in other sections.</p>
  
  <p>Keep in mind, that you (currently [*]) always have the same field settings shared with each instance you use it. Meaning that you'll always end up with the same field name and instructions, which sometimes (I'd say often) is a deal breaker for reusability.</p>
  
  <p><sup>[*]: if I remember this right, I already made P&amp;T aware of this and made a feature request</sup></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-31T06:49:12.273Z
Answers.LastActivityDate: 2014-07-31T06:49:12.273Z
Answers.UserDisplayName: carlcs
Body: <p>Is there a way to duplicate fields when creating "structures" in the visual editor. If I wanted to add four simple textfields, it appears I can't just drag-and-drop four textfields in and give them IDs as that field disappears.</p>
  
  <p>i.e. If I have four tabs with headlines... would I need to create four separate fields called "headline"?</p>
  
Tags: <field>
Title: Can you add duplicates fields in a structured section's GUI?
ThreadText: # Can you add duplicates fields in a structured section's GUI?
  
  (Asked by: username_0 on 2014-07-30)
  
  Is there a way to duplicate fields when creating "structures" in the visual editor. If I wanted to add four simple textfields, it appears I can't just drag-and-drop four textfields in and give them IDs as that field disappears.
  
  i.e. If I have four tabs with headlines... would I need to create four separate fields called "headline"?
  
  **Tags:** field
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-07-31. Score: 2
  
  An entry type can only use a field once, regardless the tab. But you can reuse the field in other entry types of that same section or reuse it in other sections.
  
  Keep in mind, that you (currently [\*]) always have the same field settings shared with each instance you use it. Meaning that you'll always end up with the same field name and instructions, which sometimes (I'd say often) is a deal breaker for reusability.
  
  [\*]: if I remember this right, I already made P&T aware of this and made a feature request
  
  
  ---
  
  