Our use case is data coming from BBIS. We need to save the original state of the records from BBIS before batch processing starts manipulating the data in ways we didn't intend. The most severe example is with direct debit account info supplied for recurring gifts (sponsorships). In batch, if we switch the constituent from wife to husband (where the sponsorship exists), the batch processing erases the account information from the batch row. For constituent updates and addresses, we need to check for user supplied data that is substantially different (e.g. they moved) versus basic formatting changes where we want to keep the address finder results.
The value is when a section of the batch import fails. By being to export the collection fields, you can fix whatever the problem is without having to go back to the original import file and manipulating it to have the data that is in the collection fields.
Please provide some more information regarding the requirement for batch gird export enhancement. For example,What is it used for? What additional value is added by exporting one-to-many fields from batch rather than via export?
FWIW, it's not necessary to add 2 addresses to see the problem. Even a single address gets replaced by the word addresses. Same issue for phone number and email address.
You won't be notified about changes to this idea.