XenDirect consists of over 300 data tables that store and manage different types of records. These tables are interrelated, meaning changes in one table may impact other related tables. Understanding how tables relate to each other helps users efficiently manage their data.
This guide explains the types of tables, their relationships, and how they function within XenDirect.
Navigation: N/A
Applies To: Enterprise | Plus | Basic
Types of Tables in XenDirect
1. Parent, Child, and Select Tables
-
Parent Tables (Primary Tables):
- Store main records that other tables depend on.
- Example: Clients Table, Courses Table.
-
Child Tables (Secondary Tables):
- Sub-level tables that rely on a Parent Table.
- A record must exist in a Parent Table before a Child Table can store related data.
- Example: Case Notes Table, Fees Table.
-
Select Tables:
- Used to categorize or classify Parent and Child Table data.
- Often appear as drop-down lists in XenDirect.
2. Table Relationships
Tables in XenDirect are related in one of two ways:
-
One-to-Many Relationship:
- One record in a Parent Table can have multiple related records in a Child Table.
- Example: Client Table → Assignment Table (A single client may have multiple assignments).
-
One-to-One Relationship:
- One record in a Parent Table is linked to one record in a Child Table.
- Example: Client Table → Client Intake/Exit Table (Each client has only one Intake/Exit record).
Primary Keys and Data Integrity
- Primary Keys uniquely identify each record and link Parent and Child tables.
- These hidden fields (usually numeric values) ensure accurate data connections.
- Primary Keys cannot be duplicated in the same Parent Table.
Automatic Data Updates
- XenDirect prevents duplicate data across tables.
- Example: The Client ID exists in the Client Table and is linked through a Primary Key.
- If the Client ID is updated, all related tables reflect the change automatically.
Restrictions on Deleting Parent Records
- Cascade delete is disabled in XenDirect to prevent accidental deletion of related records.
- If a Parent Table record has linked Child Table records, the system will not allow deletion.
Branches in XenDirect
- A Branch functions like a separate unit within an organization (similar to a bank branch).
- The Branch Table stores system-wide settings and preferences.
- Some organizations use one Branch, while others operate multiple Branches with unique profiles.
Tables Shared Across Branches
In multi-Branch environments, some tables are shared across all Branches instead of being Branch-specific.
Shared Tables by Version
Basic Version:
- Companies
- Company Log
- Company Type
- Country
- Course Activity Type
- Course Format
- Degree Type
- Ethnicity
- IP Allowed/Blocked
- Language
- Name Prefix
- Organization Profile
- Payment Type
- Postal Codes
- Program Group
- Permission Group
- Room Type
- State
- System User
Plus Version (Includes Basic Version + Below):
- Employment Cycle
- Job Category
- Test Type
Enterprise Version (Includes Basic & Plus Versions + Below):
- Business Codes
- Company Donation (No longer used in Release 3)
- County
Identifying Shared Tables
- Tables marked as "Branch Shared" in the title bar are accessible across multiple Branches.
- Not all shared tables are available in all XenDirect versions.
Select Lists in XenDirect
Select Lists are tables used to manage drop-down lists in the system.
Key Features of Select Lists
- User-defined lists where administrators can control the content.
- Some lists allow modifications, while others are system-defined.
- Select Lists can be Branch-unique or Branch-shared.
Impact of Changes in Select Lists
-
Changes affect all past and future records.
- Example: A Marketing Source entry named "Newspaper" has been used 232 times.
- If changed to "Periodical", all 232 records will now reference "Periodical," and "Newspaper" will no longer exist.
Conclusion
XenDirect organizes data using Parent, Child, and Select Tables, with well-defined relationships that prevent redundancy and ensure data integrity. Understanding these relationships helps users manage data efficiently, especially in multi-Branch environments. For further assistance, refer to related articles or contact support.