Closed schlossmj closed 2 years ago
We are experiencing the same issue and would appreciate a quick turn around on this as the end of the year and staff holidays are fast approaching.
We are experiencing the same problem. FYI, this occurs with Opportunity's "Is Gift Aid Excluded" field. If you add that to the default template and then try to make a new batch, it's the same problem. (There's an additional bug where it won't even save if that field is unchecked. You have to check and then uncheck it. But it displays in the table as checked. Will file a separate bug report on the saving error.)
It seems things were fine on December 15 and then not working on December 17.
@geoffhom @SaraStuart This issue has not been picked up yet to be worked on. Please feel free to open a support case and reference this Issue so it can be attached. Unfortunately, we are not releasing a new version of NPSP until early 2021 and we don't provide direct support in Github. Thanks!
@judisohn: thank you for the info! @SaraStuart: my org has good support (I think it's the top), so I'll look into opening a support case.
@judisohn Thank you! @geoffhom Thank you for opening the ticket. I'm new to Salesforce administration, do you think I should also open a ticket or should I wait and hear an update from you?
Hi @SaraStuart! Sorry for not updating! I'm new to Salesforce, too. My org (Mercy Ships) pays for the top support (Premier+), so my understanding is we can submit as many cases as needed; we don't pay per case. (I am used to Apple Development, where you do pay per instance.) I'm not sure how the other Salesforce plans work.
Anyway, Salesforce Support got back to me within a day. They noted that the issue with the checkboxes in the table is supposed to be fixed in the next release. That's scheduled to deploy to all sandboxes on January 6, and then to production the week after.
My org has a second issue, noted above, that any checkbox (even ones native to NPSP, which I did verify later) reports an error and prevents saving in batch entry. Salesforce Support suggested waiting until the release on January 6 to see if that fixes it. I asked if there was a way to check the beta earlier, but they said no.
If you have any more questions, let me know. This was my first case, and they did get back to me promptly, so that was good. I encourage you to try it out next time you have an issue.
Hi @geoffhom Thanks for the update! It is much appreciated! I am just getting set up with Premier support but at the basic level and your reporting of your experience with Salesforce Support is encouraging.
For context, I believe that the issue @geoffhom is referring to as the second issue is this https://github.com/SalesforceFoundation/NPSP/issues/5890
@mbeaty-sf: Thank you for the link. The "second issue" (and most important to us) is the one I linked above #6138. But you're kinda right in that #5890 is the issue that should definitely be fixed in this week's NPSP version released to sandboxes.
This issue has been migrated to the Known Issues site: https://trailblazer.salesforce.com/issues_view?id=a1p4V0000029kRdQAI&title=gift-entry-checkbox-picklist-values-marked-as-checked-in-the-ge-table-when-value-is-false
Please follow the status of the issue there and select "This Issue Affects me" if you are affected by the issue.
If a picklist with true/false values has been mapped to a checkbox on the target object (per https://powerofus.force.com/s/article/NPSP-BGE-Add-Cust-Fields#topic-2649), and a gift is saved in a batch with a 'False' value on the picklist, the BGE table still shows the value as "true" with a checkbox.
Steps to Reproduce:
GUS WI: https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07B0000008l6KWIAY/view