Hi Everyone, I am looking for SKY API end point for "Request No Email" checkbox in Database View, is it available or is it still on hold?

Hi Kylee, I believe the underlying problem is not that you cannot manually mark off requests no email, but when someone unsubscribes from an NXT Marketing email it adds a consent mapping and does NOT mark the requests no email which is different than all of your other programs that filter into RE when someone unsubscribes like LO, OLX, and NetCom therefore creating a conflict among the way staff are pulling lists and recording information to date in the system. The other issue is the NXT Marketing consent update does not seem to be adding the solicit code that consent needs set up to work correctly from the database side. MANY lists are still pulled on the database side and there is an inconsistency. I hope that makes sense. I rambled a bit. :)

I may not have understood the original idea bank. I need it to be a filterable field when creating lists.

[Ohio Living]

Suzi Jensen
Database Analyst
Ohio Living Foundation
614.888.7800 | www.ohioliving.org/foundation

[cid:51c7d6ec-be6f-4274-ab71-61b9864a8442]

Hi everyone. Just to make sure I understand the initial request, is it that you all want "requests no email" to be visible on the constituent summary in NXT? I ask because I do see an option to manually mark the constituent as "Requests no Email" in NXT and it adds an indicator right below their name on the cons record. Is that what is needed, or is it more than that? I just want to make sure I understand.

This needs to be added ASAP. I can't believe this was never addressed.

I was shocked to learn this . . . This is kinda important.

This is very important for us as it is the same way we have always done it in NetCommunity, to suddely change the method means we will have a whole lot of the database with one style of unsubscribe and then a whole lot with a different style.

This should be a very simple thing to add to the NXT constituent record screen. It is vital information if your email service is linked to your NXT database, like ours is with LO.

We need this because it syncs from Luminate Online and can change. Manually updating this field is time consuming and will lead to incorrect data when a user unsubscribes or resubscribes.

This field connects to Luminate online to mark those that do not receive email, there isa high level of need for us to have this on the webview.

I agree with what Mark commented in the above. Currently Request No Email (RE field) and No Email solicit code (Org defined opt-in/out table) both determine if a constituent is emailable or not. But in NXT, Request No Email field is missing. Blackbaud needs to find a way to make this work in NXT ASAP. I know Consent opt-in/out mapping works only for solicit code. Although we don't like redundant No Email flag, but that's how RE works at moment. So please resolve this in NXT with better solution. Thanks!

Could this field be added as an option in Business Rules / Consent so that it can be set to automatically convert to a Communication preference like Do Not Email, allowing NXT users to include this in List filters and see the preference on constituent records?

We were hoping to move away from this field with the new Consent fields in RE, but it seems that it is required if you use BBNC. It really needs to be at least visible if it can't be replaced, as users will have no idea why a constituent is not receiving any email.

Also, I was encouraged to maintain that "requests no email" in that check box as opposed to in the solicit codes, so now I can't filter lists in NXT using the Requests No Email button. Now I have to go change all records to add the solicit code so that I can pull that list. Which is kind of madness.

With PECR and GDPR, it doesn't make sense that the 'Requests no email' indicator does not show up in NXT. 

Also, the speed of creating Lists in NXT is wasted when you then have to then save them into database view just to exclude people who do not want to be emailed.  

Please add to NXT as a matter of urgency. Thank you

This is a crucial field that is well-used by our org as well. Please make sure this becomes part of NXT!

Agree.  Requests no email  is such an important field to be ble to view.  It definitely needs to be visible in NXT

Yes this is a necessity for us. We use the Requests no Email checkbox in database view to determine who gets our emails through our online CRM. We absolutely need to have this checkbox visible and editable in NXT!

YES - this is very important. The "requests no email" box on Bio 1 IS a solicit code for us. It is automatically updated through opt out's in BBNC and it will be such a pain to have to regularly query to find new opt outs and add a solicit code. It should automatically migrate to the communications preferences section of NXT. Where does this information go currently?!

It is unfathomable that such an important designation as "Request No Email" does not appear in NXT! On what planet did the developers think this glaring omission was at all acceptable? This needs to be fixed immediately!