The current Bulk Processing settings to accept or reject constituent profile information in the NetCommunity RE plugin apply to all transactions in the batch. This requires that users who process transactions go into each individual transaction and decide whether profile information will be accepted or rejected, so they can be processed in separate batches. This adds considerably to the time it takes to process transactions at our organization, where we have over a hundred transactions to process each day. Bulk processing in the NetCommunity plugin should be able to handle a batch where some transactions contain profile information to be accepted and others contain information to be rejected.
If we could save profile update selections when bulk processing, this would dramatically streamline the process. Currently when we bulk process, the individual boxes we've ticked or unticked for each transaction/registration (as to what should/shouldn’t be applied as a change) are lost.