# Jvris plugin

File handler plugin that parses JSON exports from Jvris case management system and maps fields to SharePoint client and matter information.

DLL: Epona.Jvris.dll

# What it does

  • JSON parsing — reads Jvris JSON export files
  • Field mapping — extracts client and matter information
  • Client import — imports client codes and names
  • Matter import — imports matter/case codes and names
  • Custom metadata — maps additional Jvris fields to SharePoint columns
  • Batch operations — processes multiple JSON files for bulk import

# Prerequisites

  • Jvris case management system with JSON export capability
  • JSON export files containing client and matter data
  • Excel batch file or other mechanism to trigger imports

# Configuration

# ClientCode

Type: string | Required: No

JSON property name for client code

# ClientName

Type: string | Required: No

JSON property name for client name

# ClientFieldMapping

Type: string | Required: No

Maps JSON fields to SharePoint columns (format: sharepointcolumn1=jsonproperty1;)

# MatterCode

Type: string | Required: No

JSON property name for matter code

# MatterName

Type: string | Required: No

JSON property name for matter name

# MatterFieldMapping

Type: string | Required: No

Maps JSON fields to SharePoint columns

# Example JSON format

{
  "clients": [
    {
      "ClientID": "ACME",
      "ClientName": "ACME Corp",
      "Email": "contact@acme.com"
    }
  ],
  "matters": [
    {
      "CaseNumber": "00123",
      "CaseTitle": "Smith v. Jones",
      "Status": "Active"
    }
  ]
}

# Example configuration

Property Example value
ClientCode ClientID
ClientName ClientName
ClientFieldMapping ClientEmail=Email;
MatterCode CaseNumber
MatterName CaseTitle

# Troubleshooting

Issue Cause Resolution
Data not imported JSON property names don't match configuration Verify property names match ClientCode, ClientName, etc.
Fields missing Field mapping incorrect Check ClientFieldMapping and MatterFieldMapping
Last Updated: 4/15/2026, 8:56:27 AM