View Property Access for Each Tile

Having property access on each tile in Raiser’s Edge NXT for digital forensics when users update data in specific areas is essential for maintaining a robust audit trail. This feature allows organizations to track changes meticulously, ensuring that any modifications can be traced back to the responsible user and the exact time of the update. Such detailed logging is invaluable for identifying and addressing discrepancies, enhancing accountability, and ensuring compliance with data governance policies. Moreover, it provides a clear and transparent record that can be crucial during audits or investigations, helping to safeguard the integrity and reliability of the organization’s data.

  • Mari Nguyen
  • Oct 15 2024
  • Reviewed: Voting Open
  • Attach files
  • Ursula Stacks commented
    17 Sep 17:17

    This is a BIG need! We also need these properties to see Import IDs as well as the created by/last edited fields. All admins should agree with the need for this webview.

  • Dana Troy commented
    07 Jul 19:16

    Agreed, this is important. E.g. when merging duplicate records it's necessary to see the dates mailing addresses were added/modified in order to figure out which is the most recent.

    I'm trying to use the web view more, but this info is still only available in the database view so I'm having to switch back and forth frequently. If features like this are still not available when we lose access to the database view, it's going to be a serious problem.

  • Emily Marshall commented
    26 Feb 16:57

    Yes! Here is a real-life example of why those properties are so important to us: I am currently trying to fix a constituent that someone else merged badly. I am TRYING to do this in Web View, and I am running into the issue of which address is the current address (the To and From fields had not been utilized). I need to see the properties on the addresses in the system to see which is the newest address. Well, in Web View this is impossible!

    Thankfully, though, I am able to still access this information in database view, for the moment. With access this information I could then easily tell that the address marked as primary was not the current address, and that the current address was one of the addresses further down the list.

    Without having access to these properties, I would not have been confident which of the address was the correct address - so basically, we would be left with a high change of garbage in the system.