When should integrity checks be run, and when should they be avoided? When Integrity Check finds discrepancies in the data, does it try to fix them, or does it merely issue a report about them? A report would be handy, but I would like to see the proposed course of action before it actually makes changes.
*This post is locked for comments
Exactly the info I was looking for, thanks!
Most, but not all, of the integrity check screens have options to report and/or fix various issues. However, that menu item under Cash Manager automatically fixes (Cash Manager being the odd-duck of all the modules).
The biggest issue with integrity check runs is when you manually change something with a SQL query in such a manner that you do not hit all the spots affected and the integrity check finds the inconsistency and possibly undoes your manual change. For example, in AR, if you clear out an invoice's balance with a SQL command but there is not corresponding aradjust record for that invoice, integrity check, if you select the correct document balance option, we reset the invoice back to a balance based on what it finds in aradjust. The bottom line is: any direct database changes done in SQL should only be done if you really know all the places to hit.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156