the grid edit is so useful for updating records and the bulk edit further improves productivity. What if we could mark records, much like bulk edit/delete, and have new records inserted into a second table passing key fields from the 1st table along with default values to populate the 2nd table records. The 2nd table could subsequently use the very efficient grid edit for changes/updates.
For example: a teacher has a list of students, rather than use line item action (i.e. "add grade") to insert one grade at a time, select all the students still active(enrolled) and "add grade" for all - passing the student id, course and a dummy value for letter grade to be edited in a grid report
cooper Odell commented
I agree with Matt. This would be a very helpful feature. We use a similar set up where our users will want to create 1 or 2 records in a new table for every unique ID in another table. The only way to currently accomplish this is by hand, adding either one record at a time (gets tedious when the number is in the 100's or 1000's) or with an import. Imports also lack a lot of ease of functionality when it comes to relational database structure. Our average back end users get confused if they must fill in and complete an import based on multiple columns using just ID's.
With Matt's idea, a user could use a similar structure in place with the bulk edit feature and highlight all results to create a new record in a new table passing along either just a UID or even possibly selecting other fields that would be applied to all new records.