Review every blocked save and warning, build analytics reports, and export data for audits.
Overview
Every time a validation rule blocks a save or issues a warning, the event is recorded in Validation Logs. This creates a complete audit trail showing who did what, when, and why.
Validation Reports turn this data into charts and pivot tables for deeper analysis.
How It Works
Logs are created automatically – you do not need to configure anything. When a rule fires:
- A log entry records the rule, profile, affected record, user, severity, message, and timestamp.
- For line-level validations, the parent record (e.g., the sales order) is also recorded.
- Demo log entries are tagged so you can filter them out of real reports.
Step-by-Step Guide
Viewing Validation Logs
- Go to Advance Validations → Validation Logs.
- Browse the list – newest entries appear first.
- Use filters to narrow down:
- By severity (Blocked or Warning)
- By rule or profile
- By user
- By date range
- Demo vs. real data
- Click any log entry to see full details including the affected record.
Using Validation Reports
- Go to Advance Validations → Validation Reports.
- Switch between views:
- List – same as logs but with report-specific filters
- Pivot – cross-tabulate failures by rule, user, model, or week
- Graph – bar chart of failures by rule
- Drag fields in the pivot table to explore patterns (e.g., which user triggers the most blocks).
Exporting Logs to CSV
- From Validation Reports, click Export Validation Logs.
- Set date range and severity filters.
- Click Export to download a CSV file.
- Use the CSV for external audits, compliance packages, or management reports.
Log Fields
| Field Name | Description | Example |
|---|---|---|
Reference |
Auto-generated log identifier |
Contact #42 – Email Required |
Rule |
Which validation rule was triggered |
Email Required on Contacts |
Profile |
Profile the rule belongs to |
Contact Data Quality |
Model |
Type of record that was validated |
Contact |
Record |
The specific record affected |
John Smith |
Parent Record |
Parent record for line validations |
Sales Order SO001 |
Trigger |
What action caused the validation |
On Write |
Severity |
Blocked or Warning |
Blocked |
Message |
Error message shown to the user |
Please enter an email address. |
User |
Who triggered the validation |
Jane Doe |
Company |
Which company the event belongs to |
My Company Ltd. |
Date |
When the event occurred |
15 Jul 2026, 10:30 AM |
Demo Data |
Whether this is a sample log entry |
No |
Field Explanations
Severity – Blocked vs. Warning
Blocked means the save was rejected. Warning means the save succeeded but the issue was recorded. Filter by severity to focus on hard stops vs. soft reminders.
Parent Record
When a line-level rule fails (e.g., on a sales order line), the log shows both the line and the parent order. This helps you find the full context quickly.
Demo Data
Sample log entries created by the demo importer. Filter these out when reviewing real business activity.
Pivot – Week
Reports can group events by week, making it easy to spot trends over time during management reviews.
Tips
- Review logs weekly to identify rules that fail too often – they may need clearer messages or process changes.
- Use the pivot view to present validation trends in management meetings.
- Export CSV monthly for compliance archives.
- Filter out demo data before sharing reports with stakeholders.
Common Mistakes
- Including demo data in reports – always filter demo entries when presenting real metrics.
- Ignoring warning logs – many warnings on the same rule signal a process problem users are working around.
- Not exporting regularly – logs accumulate over time; export important periods before they become hard to filter.