Update Column Value in RE NXT not working when column is applied to batch

Leslie Archibald

I was really excited to see that the update column value was coming to the unified view, since we have a lot of gifts that we currently have to update the campaigns on for our web batches. However, the campaign column isn't available for the mass update, even after I've added it as a column on the grid. Is there something I'm doing wrong? I tried following the instructions in the help article but it doesn't seem to be fixing the problem for me. Has anyone else run into this, and if you have what have you done to fix it?

ETA these are the steps I was following:

1. Open an unapproved batch from the BB payment processor in web view
2. click "edit batch gifts" (edit in grid view does not seem to be an option anymore like the help article says)
3. click "configure columns"
4. check the box to have the campaign column added to the grid and click the apply button
5. click update column value
6. check the "overwrite existing data" box

Despite doing this, when I go to the select field, the campaign column is not an option to update. I have also tried it where I set a default value for the campaign column before applying it, and that does not make it show up

Melissa Chin

Leslie, you're not doing anything wrong. The newly released RE NXT Gift Batch Update Column Value functionality is limited to these fields:

Receipt status
Gift subtype
Comment
Amount
Receipt amount
Gift date
Gift type
Anonymous
Post status
Post date

Leslie, I am encountering the same issue. This Update Column Value functionality is more limited compared to what we are used to having/using in RE (database view).

Lucy, thank you, but what you proposed is not a solution to the problem. My organization intentionally does not set FY campaigns and appeals as defaults for a gift fund record. I hope that the RE NXT Gift Batch Update Column Value functionality can be updated further to offer the exact same Update Column Value functionality ability available in RE (database view). Expanding the choices of fields that can be updated is the solution.