Summary
This article explains how to request changes to how certain data fields (such as Year Level) are displayed in Orah when they are synced from an external system.
🧩 Overview
Orah syncs student data from external systems (such as Student Information Systems) using predefined field mappings. In some cases, the default mapping may not match how your organisation expects to see the data displayed.
If a synced field (for example, Year Level) is showing unexpected values, you can request a change through Orah Support.
Applies to:
Roles: School Admins and IT Staff managing data integrations.
Supported Systems: Custom mapping is currently available for Blackbaud, Veracross, TASS, Synergetic, FACTS, iSAMS, and Wonde.
🧩 When Would You Need This?
You may want to request a field change if:
A synced field shows a technical or system-specific value
The displayed value doesn’t align with how your organisation labels data internally
All users are seeing the same incorrect or unexpected value
The data appears correct in your source system but different in Orah
Common examples include:
Year Level display
Group or cohort naming
Code vs name formatting
🧩 How to Request a Field Mapping Change
Open a support request to support@orah.com
Clearly explain:
Which field needs to be changed (e.g. Year Level)
What it is currently showing
What you expect it to show instead
Confirm whether:
The issue affects all records
The data looks correct in your source system
Submit the request and wait for confirmation from the Orah Support team.
Once reviewed, Support will let you know whether the change:
Can be applied directly for your organisation, or
Requires additional review or setup
💡 Best Practices / Tips
Be specific about current vs expected values
Mention whether the issue affects everyone or just certain records
Include screenshots if helpful (optional but recommended)
Avoid making changes in your source system unless advised by Support
❓ FAQs
Can I change synced field mappings myself?
No. Synced field mappings are managed by Orah to ensure data consistency.Is this a global change?
No. Field mapping changes are applied on a per-organisation basis where supported.
Will this affect historical data?
In most cases, changes apply to how data is displayed moving forward. Support will confirm if historical data is impacted.How long does it take?
Timing depends on the request type. Orah Support will advise once the request is reviewed.
🛠️ Troubleshooting
The data looks wrong, but I’m not sure why
Confirm what the field shows in your source system
Contact Orah Support with a brief description
Multiple fields look incorrect
Submit a single request listing all affected fields to avoid delays
I’m unsure what value Orah is using
Ask Support to confirm the current mapping for your organisation