Skip to main content
Solved

Repeating group is creating an extra row with all selections

  • September 29, 2024
  • 4 replies
  • 36 views
J
Forum|alt.badge.img+6

In the Change Request form I've created, users can enter information about a change request -- item, change type, notes, screenshots, etc -- and then they can use a multiple select dropdown to choose up to four Regions where the changes should apply.

I'm using a Repeating group to cycle through the Regions input to create a separate record for each Region. 4 Regions chosen, 4 rows, 3 Regions chosen, 3 rows, etc. Beautiful! The trouble is, it also creates a single row with ALL 4 or ALL 3 regions etc on it. How do I stop that?

Best answer by ScottWorld

You can’t prevent that, because a form submission always creates a new record.

You may want to create your form in a different table, and then loop through the multi-select field to create records in the ACTUAL table where you want the records to appear.

— ScottWorld, Expert Airtable Consultant

4 replies

ScottWorld
Forum|alt.badge.img+35
  • ScottWorld
  • Genius
  • 9808 replies
  • Answer
  • September 29, 2024

You can’t prevent that, because a form submission always creates a new record.

You may want to create your form in a different table, and then loop through the multi-select field to create records in the ACTUAL table where you want the records to appear.

— ScottWorld, Expert Airtable Consultant

J
Forum|alt.badge.img+6
  • jillmonterey
  • Author
  • Known Participant
  • 11 replies
  • September 29, 2024

You can’t prevent that, because a form submission always creates a new record.

You may want to create your form in a different table, and then loop through the multi-select field to create records in the ACTUAL table where you want the records to appear.

— ScottWorld, Expert Airtable Consultant


Bleah, I feared this. I also had the idea of the pass-through table where I collect junk rows. I don't get that junk row when my trigger is When-Record-Is-Created or When-Record-Matches-Conditions -- but in either of those cases, I get an infinite loop. 

TheTimeSavingCo
Forum|alt.badge.img+31
  • TheTimeSavingCo
  • Brainy
  • 6457 replies
  • September 30, 2024

Bleah, I feared this. I also had the idea of the pass-through table where I collect junk rows. I don't get that junk row when my trigger is When-Record-Is-Created or When-Record-Matches-Conditions -- but in either of those cases, I get an infinite loop. 


Try putting a "Run a script" action to delete the form submission:



And here's a thread where there's a simple delete record script you can modify for yourself

Adam, Airtable Consultant - thetimesaving.company
J
Forum|alt.badge.img+6
  • jillmonterey
  • Author
  • Known Participant
  • 11 replies
  • October 2, 2024

You can’t prevent that, because a form submission always creates a new record.

You may want to create your form in a different table, and then loop through the multi-select field to create records in the ACTUAL table where you want the records to appear.

— ScottWorld, Expert Airtable Consultant


This is what I wound up doing.


Terms & ConditionsAccessibility statement