THANK YOU!!!!

Thanks for that BB!

Thanks!

Thanks to BB for responding to this idea and shipping it. Much appreciated.

Soooooooo relieved and happy to hear Trit!!!!! 💜💜💜💜

OMG - this is so important to our organization as well.

Based on your feedback, we have decided to leave attribute management available in database view.

We rely on constituent attributes to segment our constituents annually for the Annual Fund. It helps to create queries and exports throughout the year. I globally delete and import on an annual basis. I hope NXT will function in the same way.

Thanks for raising this Cindy. We use Constituent Attributes on a daily basis to manage all our consents and preferences as well as for other things, such as Source of Data. Losing Attributes from database view will be a massive problem for us, especially given the very short notice period.

1. Gift Record Attributes
   Since we currently can’t edit gift records in NXT, will gift attributes remain available in database view until full gift editing is supported in NXT? The goal would be to eventually be able to view/edit gifts and gift attributes directly in web view?

2. Address Attributes
   We use attributes in the primary address record to capture returned mail context. Will this still be supported in NXT? If not, is there an alternate recommendation?

3. Attribute Functionality
   Will full functionality of current attributes, including fields like date, comments, and custom dropdowns be retained in web view?

4. Global changes, imports and exports etc.

We regularly import gift data (including attributes), export constituent, and gift attribute data, run various queries, and process global changes specific to attributes to maintain our data. We just want to confirm that these functions will still be available for attributes starting in January.

Also importing!!! Do not retire before we are able to import or make global changes in NXT!!!