Build a Case Escalation and Review Log with a Custom Dataverse Table: Series 9

Build a Case Escalation and Review Log with a Custom Dataverse Table: Series 9

Some organizations need a structured record of why a Case was escalated, who reviewed it, and what action was decided. If the standard Case fields and audit history do not meet the reporting requirement, create a related custom table.

1. Create the custom table

Create a table such as Case Escalation Review with a many-to-one relationship to Case. Example columns include Escalation Reason, Review Notes, Decision, Requested By, Reviewed By, and Review Date. Use an autonumber primary name if a readable reference is useful.

2. Choose data types deliberately

  • Reason and Decision: Choice columns.
  • Case: Lookup to the standard Case table.
  • Requested By and Reviewed By: User or Team lookup as appropriate.
  • Review Date: Date and time with a defined time-zone behavior.
  • Review Notes: Multiline text, with length and sensitivity considered.

3. Create a review record

Patch(
    'Case Escalation Reviews',
    Defaults('Case Escalation Reviews'),
    {
        Case: varSelectedCase,
        'Review Notes': txtReviewNotes.Text,
        'Review Date': Now()
    }
)

Use your actual table and column display names. Restrict who can create or approve review records through Dataverse security roles and ownership.

4. Reporting and audit

Build views and charts by decision, reason, reviewer, and review date. Enable auditing on fields that require a change history. A custom review log is not a substitute for platform auditing or a regulated approval process unless its controls have been designed and tested accordingly.