LogoLogo
HomeNewsletterSupportKnowledge Base
Rapla Knowledge Base
Rapla Knowledge Base
  • Rapla
  • 📘Terminology
  • 🌟Get Started
    • Install the App
    • Navigate the Interface
      • Section 1: Side Menus
        • Select a Side Menu
        • Conflicts Menu
      • Section 2: Top Menu Bar
        • Switch Account View
        • Apply Filters
        • Edit Preferences
      • Section 3: Main Calendar View
        • Calendar Types
        • Customise the Calendar Space
    • Add New Users
    • Add New Resources
      • Facility
      • Staff
      • Equipment
    • Create Time Periods
  • 🗓️Create Events
    • Choose an Event Type
      • Paradigm Session
      • Generic Meeting
      • Generic Event
      • Student Booking
    • Repeat Events
    • Use Multiple Appointments
      • Delete Appointments
      • Convert to Single Events
    • Add Exception Dates
    • Allocate Resources
  • 🕚Example Events
    • Session Group and Class
    • Scenarios
      • ▫️Scenario 1
      • ▫️Scenario 2
      • ▫️Scenario 3
      • ▫️Scenario 4
      • ▫️Scenario 5
  • 🛑Resolve Conflicts
    • Identify Conflicts
    • Disable Conflict Checking
  • 🔀Synchronise with Paradigm
    • Prepare Scheduled Unit Records
    • Prepare Rapla Events
    • Trigger Import
    • Troubleshoot Import Errors
    • Validate Imported Data
    • Change Event
      • Impact: NONE Change (1)
      • Impact: NONE Change (2)
      • Impact: NONE Change (3)
      • Impact: NONE Change (4)
      • Impact: NONE Change (5)
      • Impact: LOW Change (1)
      • Impact: LOW Change (2)
      • Impact: LOW Change (3)
      • Impact: LOW Change (4)
      • Impact: LOW Change (5)
      • Impact: LOW Change (6)
      • Impact: LOW Change (7)
      • Impact: HIGH Change (1)
  • ⚙️Advanced Configuration
    • Publish HTML Calendar Views
    • Manage User Accounts
      • Change a User Permission Level
      • Archive Inactive User Accounts
    • Add New Resource or Event Type
    • Colour Code Resources
    • Change Events Name Format
    • Change Data Schema
      • Make Fields Visible
      • Hide Fields
      • Add New Fields
      • Change Field Options
  • ❓Support
    • Online Helpdesk
    • Silverband Slack workspace
    • Phone Numbers
Powered by GitBook
On this page
  • Overview
  • Understand the Sync Results
  • 1. Processing Rapla Session Details
  • 2. Checking the Unit Code Details in Rapla
  • 3. Matching the Unit Code Details in Paradigm
  1. Synchronise with Paradigm

Troubleshoot Import Errors

This page will discuss the structure of the results of the import to better understand errors if they arise after the sync.

PreviousTrigger ImportNextValidate Imported Data

Last updated 2 years ago

Overview

Right after you synced your Paradigm Session events from Rapla to Paradigm, you will be shown a page with the results of the synced. For an import with no error, you will just normally see a Success message for each Unit Code that you have imported. For cases when you receive error messages after the import, refer to the sections below to understand the sync results in Paradigm.

Understand the Sync Results

In the example screenshot below, the two scheduled unit sessions are imported successfully without errors.

However, for sessions or events with detected errors, Paradigm will provide you with an error message accordingly. To understand the error, it's good to understand first the structure of how Paradigm displays the error for each Unit Code imported.

1. Processing Rapla Session Details

This will serve as the starting point of the checking - Paradigm will do for each Unit Code imported from Rapla. Each Unit Code detected or specified to be imported will always have this starting point message to check for errors

2. Checking the Unit Code Details in Rapla

This section will read the details coded in Rapla for that specific Unit Code. This will include the Session Type, name, group and class numbers, session day, start date, start and end time, room, teacher, provider information, campus code and name, school code and name, session provider code and Id, and the Delivery Mode.

3. Matching the Unit Code Details in Paradigm

The sample screenshot below is showing an error with a Session created in Rapla with no matching Provider Code Scheduled Unit created in Paradigm:

This section will compare the details coded in Rapla to its equivalent Scheduled Units in Paradigm, see for the required fields. If it won't detect a match, it will give you an error about a Scheduled Unit not found - meaning, there is no Scheduled Unit in Paradigm recorded equivalent to the details of the Unit Code or Session event in Rapla.

To resolve a Scheduled Unit not found error, refer to the previous pages: and .

🔀
Prepare Rapla events
Prepare scheduled unit records
Prepare Rapla events