copying my note from similar idea regarding deleting individual gifts vs. batches. Idea: I-5193
The RE NXT features grid shows Delete batches as already existing in NXT, and yet buried within the Help info (see attachment) it says:
Delete batches: To the left of the batch's name, select the ellipsis, then Delete.
Only batches that contain no gifts can be deleted. You can move all the gifts from the batch you want to delete to another batch to make it eligible to be deleted.
The ellipsisdoes not showthe delete option otherwise.
What does this even mean and what does it entail? There is no explanation of how to move gifts to another batch - does this mean admins will need to create a query, group load all to a new batch and then fill in everything else manually? What is the use of only being able to delete empty batches? An Administrator should absolutely have the ability to delete batches, and if the only current way to do so is in database view, what does that mean for database view going away, that we can't delete batches at all unless we "move all the gifts"? If I'm creating test gifts in a test batch I want to be able to delete the entire batch after I see how fields move over. I don't want to have to zero out all the gifts or go one by one into records to delete. Let alone if a batch is created erroneously or some other issue when committing.
It is also far too easy to commit a batch in web view; there is no pop-up like in database view regarding applying gifts to recurring gifts and pledges or not; we have multiple donors with an active recurring gifts that also give additional types per year and we need the options at minimum to have:
the data to be validated for error checking
To have gifts apply to pledges and recurring setups only when prompted
the option to have the commit batch reports are finally added - when! - unless commit reports will be automated for every single batch. I as many others need this to reconcile.
delete batch after committing - I would love to this not be an option in WebView or one admins could toggle off as I never want a batch automatically deleted after it is committed
Our data entry person was having this problem of not being able to delete a row in an open batch, and actually wasn't even able to change the amount to $0. We learned via support that the user had to have DELETE BATCH rights just to remove a row in a batch she was working on. This should be fixed as a security issue, it shouldn't take that level of access when you are charged with data entry you should be able to delete a row before the batch is committed.
I have a constituent that made a gift through RENXT forms as a one time gift but intended to make a recurring monthly gift. We need to have the option to delete gifts in RENXT web view for these instances.
copying my note from similar idea regarding deleting individual gifts vs. batches. Idea: I-5193
The RE NXT features grid shows Delete batches as already existing in NXT, and yet buried within the Help info (see attachment) it says:
Delete batches: To the left of the batch's name, select the ellipsis, then Delete.
Only batches that contain no gifts can be deleted. You can move all the gifts from the batch you want to delete to another batch to make it eligible to be deleted.
The ellipsis does not show the delete option otherwise.
What does this even mean and what does it entail? There is no explanation of how to move gifts to another batch - does this mean admins will need to create a query, group load all to a new batch and then fill in everything else manually? What is the use of only being able to delete empty batches? An Administrator should absolutely have the ability to delete batches, and if the only current way to do so is in database view, what does that mean for database view going away, that we can't delete batches at all unless we "move all the gifts"? If I'm creating test gifts in a test batch I want to be able to delete the entire batch after I see how fields move over. I don't want to have to zero out all the gifts or go one by one into records to delete. Let alone if a batch is created erroneously or some other issue when committing.
It is also far too easy to commit a batch in web view; there is no pop-up like in database view regarding applying gifts to recurring gifts and pledges or not; we have multiple donors with an active recurring gifts that also give additional types per year and we need the options at minimum to have:
the data to be validated for error checking
To have gifts apply to pledges and recurring setups only when prompted
the option to have the commit batch reports are finally added - when! - unless commit reports will be automated for every single batch. I as many others need this to reconcile.
delete batch after committing - I would love to this not be an option in WebView or one admins could toggle off as I never want a batch automatically deleted after it is committed
Our data entry person was having this problem of not being able to delete a row in an open batch, and actually wasn't even able to change the amount to $0. We learned via support that the user had to have DELETE BATCH rights just to remove a row in a batch she was working on. This should be fixed as a security issue, it shouldn't take that level of access when you are charged with data entry you should be able to delete a row before the batch is committed.
I have a constituent that made a gift through RENXT forms as a one time gift but intended to make a recurring monthly gift. We need to have the option to delete gifts in RENXT web view for these instances.