I had this feature with another database. It would be a super helpful tool to maintain data integrity, user accountability, and record history. I have had instances in the past where I needed to view previous values of a field, and this is just not available in RE.

At a minimum, I need to be able to see the properties that are available in database view. Some of my fundraisers are not good at adding the dates for opportunities, etc, so I use the properties to add a "date asked" if it hasn't been populated.

What would excite me would be being able to see a granular view of specific fields, edited by whom, when, etc. Maybe a little i in a circle (the info symbol) next to fields to see the properties? As previous commenters have mentioned, having specific information about what was changed by whom would allow me to be able to support other team members with additional training where needed and find other similar errors and correct them.

Full change log audit trails would be ideal.

Yes, this is needed. In database view there is the ability to see who last modified a record.

I had this with a prior CRM, and it allowed us to pinpoint (and fix!) names after someone outside of the data team uploaded a huge import of records to an API connected system that we didn't control with a CSV that had an error on every record. We would have had no hope of fixing an issue like that in the way Raiser's Edge is currently

Without having to buy a 3rd party app.

Knowing when a field is edited and by who helps us tremendously. It can also be used as a training aid - If I see something done wrong, I can go to that individual and let them know what they did wrong and train them on the correct way to do it.

This would be extremely useful to track down issues!

I also want to echo Velma Matt's comment - it helps identify which team member needs some support and training, which gets down to the root 'issue,' so it prevents recurring issues and supports overall data health and accuracy.

Where "paper trails" are necessary in many other aspects of nonprofit/charity life SOPs... this is another area where a paper trail/digital trail needs to exist!

Definitely

Yes - and, to piggyback on this - to be able to track versioning! What it was prior to changing, and what it was changed to, and when(!) This was a lifesaver for me in other CRMs that had APIs, it helped me track issues or resolve them before they became a problem for leadership.

It also helped me understand which team members needed support and additional training - and sometimes, it even revealed integration issues that didn't stem from the team member.

I'm beyond shocked NXT doesn't already have built-in audit trails; they are a safety rail for your data security and data integrity.