We have found the user activity tracker to be very disappointing. It works well, but the performance hit is so great as to make it not worthwhile. And that is despite the fact that this feature had been requested for decades. 

Hi Jim Love this is interesting as we haven't experienced a performance hit with the User Activity Report at the sites we upgrade, although we did notice a performance his with the Enhanced Security Update in version 2023 and 2024 generally.  We found turning User Activity Reporting off made almost no difference.  Fragmented data that's not regularly indexed or SQL latency on the Vault/Store databases can certainly hammer the performance of User Activity Reporting.  Thinking about it, it could be the number of users.  If its not too sensitive, roughly how many Sage 300 users at the site as maybe its a much larger site then the ones we deal with?

 Jeffrey DM We found the User Activity Report does not contain enough forensic data nor enough data about what users actually do to be useful.  Essentially all it tracks is the Sage 300 user ID, their login time and the screens they open.  This is why we use Pacific Technology Audit Logger at our Government and sensitive company client sites because it tracks AD account of the user, the host, the ip address, and exactly what fields are read/written to with extensive controls over how much is recorded. It also audits the ADMIN account properly.  I highly recommend it.

Thank you, Accsys, for that input.  Sounds like we should revisit it.  The primary site on which we came to that conclusion had only ten users, and we had a similar experience at a smaller client site, at which point we put that feature on hold for the time being.  And yes, Audit Logger is certainly more comprehensive, though it, too, can noticeably impact performance if too many of its options are turned on.  We considered the Sage reporting a good compromise were it not for the performance hit we saw, but we are not great about SQL maintenance, so it is certainly possible that the dbs need reindexing. 

Hi Jim Love yes Pacific Tech Audit Logger can cause a performance hit too, though I'm sure you found the same thing, if you can get the client to invest the time to sit down and tune auditing at the field level - i.e. only audit the exact fields they want rather than blanked turning on auditing for entire modules or module subsections, you can reduce the impact.  Again, I'm sure you found this as well - that if too much auditing is turned on the volume of audit data is so huge it becomes impractical to generate reports on it

Thanks to both Accsys Consulting AU and Jim Love for sharing. We have been holding off the upgrades as there are other modules that are on the verge of being deployed, and the fact that I am also not clear as to what the impact of these changes are. Keeping options open for now.

On a separate note - are there any other options that are available?

No other solutions to my knowledge.  Audit Logger has been the go-to solution for many years.