Warnings and errors need to be handled individually when it comes to data integrity checks.
Closed fiscal periods and inactive key fields can occupy a significant number of pages in a data integrity report making it almost useless when looking for a needle in a haystack. How about the ability to suppress "warnings" during a data integrity check?

Comments

  • Would be very useful to have more selection criteria for the data integrity checks. Specific example would be for PO Receipts - any receipt which has not been invoiced, where the receipt is dated for a locked fiscal period, generates an error message. Many of our clients have these errors dating back to 2004.... Could we have something for dates like - 'do not check data dated before _____'

  • Also check box to choose whether to "Check history" would be useful in all modules.

  • If not "suppress warnings", give the ability to segregate types of messages so that critical errors are together on the report.

  • I agree. I inactivate GL accounts when they are no longer needed but that triggers a lot of data integrity errors for history items or terminated employees or inactive vendors that used these accounts. It is unneccessary for these to print on the report. The accounts were active when the items happened. They are data integrity issues.

  • All modules need options like those in BK integrity check, so you can check only specific areas. As it stands, it's often not feasible to run DIC for OE or IC because it can take days, but being able to ignore sales history, or ignore completed transactions, or ignore posting journals would save a lot of time. Also "Report closed periods?" could be a checkbox.

    In the report, identify some errors as warnings not errors (eg references to inactive customers, items, shipto addresses, salespeople etc). Instead of the report saying "0 errors" for each section, use another phrase such as "Nothing to report". By combining these two changes in the report, we could then search the report for the word "error" to find all errors.