Check for Anomalies scans the data stored on the Record for values that are likely to cause trouble in searches, workflow rules, exports or on screen. It is on the Record screen under the Admin Actions menu in the footer, on systems licensed for Enterprise features, and is available to Administrators. It changes nothing; it only reports.


The dialog, titled Record Anomalies, checks the header fields and, when the Record has any, the line item data, and shows each check as a panel. A green check mark means nothing was found. A red heading means the fields listed beneath it need a look, and line item fields are listed with the line they are on.


  • Data Element Count. A Record is expected to hold no more than a thousand data values, counting header fields, line items and table cells together. Beyond that it becomes slow to open and save, and the panel reports Too Many Data Elements. Look for an automation that adds line items or values on every pass instead of replacing them.
  • Fields with suspect characters. Values containing characters outside the basic printable English set, other than line breaks. Invisible control characters from a bad import or paste are the real problem, since they break matching and exports while looking like ordinary text. Accented letters, curly quotes and other non-English characters are reported by the same check, so a listed field is not necessarily wrong; open it and look.
  • Fields with line feed characters. Values that contain a line break. That is harmless in a memo-style field but can upset single-line displays and exact-match rules, so every field that has one is listed for you to decide.
  • Fields with large values. Values longer than a thousand characters. A long memo is fine, but a value that long in a field meant for a code, a name or a date points at a bad import or an automation writing to the wrong field.


The check only reports. To fix a value, open the Record for editing, or use Revert Record Data to put a field back to what it held before the problem appeared.