Update to Field in Raiser's Edge NXT may not be immediately reflected in SmartTHING Application

Update to Field in Raiser's Edge NXT may not be immediately reflected in SmartTHING Application

When a Raiser's Edge NXT application reads data it is really reading a locally cached copy. This is a required to ensure RE NXT is not compromised in terms of speed and to allow both RE and RE NXT to access the same database (ask Blackbaud for more information on this if you wish!). The outcome is that looking at the same record in RE NXT and in the RE client may for a short while show different data if a recent change has been made in one of the environments.

The same is true when accessing data through the RE NXT API which may not immediately visible in your RE NXT application (even after a refresh).

One example of this is when using SmartGMAIL NXT PRO to display constituent as a sidebar (screenshot below). The constituent information that is displayed is a cached version retrieved from the NXT API and will show actions that are in the cache. You may have to wait a few minutes if you have made changes to RE actions for this to show in the sidebar.

 



 Illustrates display of constituent information when viewing an email with SmartGMAIL NXT PRO