Schools using Bromcom only
We have been doing some detailed data checking, and it appears that some schools (not all) have not ticked all the relevant permissions when setting up the third-party access to allow the data to feed from Bromcom to OCC.
Can I ask that you check all the permissions below have been ticked so that all the data is sent to OCC. The main issue appears to SEN data (SENStudents SENStudentNeeds from the list below).
(Only items that are listed on the Data Sharing Agreement will be collected so ticking all these permissions will not allow the data to be shared as the template OCC uses does not include all these data items).
Here is the link to the instructions
- Xporter: Enable Access in Bromcom
- https://support.venturedsolutions.co.uk/s/article/Xporter-Enable-Access-in-Bromcom
Please refer to item 11 of the notes where it lists the list of permissions.
| Addresses |
| AdministrationDoctorTelephones |
| AssessmentAssociationAssessmentTypes |
| AssessmentAssociationSubjects |
| AssessmentAssociationTerms |
| AssessmentAssociationYearGroups |
| AssessmentGradeSetGrades |
| AssessmentGradeSets |
| AssessmentGradeSetVersions |
| AssociationAssessmentMarksets |
| AssociationAssessmentMarksetVersions |
| AssociationAssessmentMarksheets |
| AssociationAssessmentResults |
| AssociationAssessmentTemplateColumns |
| AssociationAssessmentTemplates |
| Attendances |
| BehaviourEventAdjustments |
| BehaviourEventCategories |
| BehaviourEventLinks |
| BehaviourEventRecords |
| BehaviourEvents |
| BehaviourStudentActions |
| CalendarModels |
| Calendars |
| Candidates |
| Classes |
| CollectionAssociates |
| CollectionExecutives |
| CollectionExecutivesRoleTypes |
| CollectionHierarchy |
| Collections |
| Disabilities |
| Emails |
| EmployeeContacts |
| EmployeeRoles |
| Ethnicities |
| GypsyTravellerStudents |
| HouseClasses |
| Languages |
| LocationClosures |
| Locations |
| MealType |
| MedicalConditions |
| People |
| PersonAddresses |
| PersonCommunications |
| PersonMedicalConditions |
| PersonMedicalEvents |
| PersonParamedicalSupportTypes |
| PersonPhotos |
| PersonTelephones |
| PreAdmissionGroups |
| PupilPremiums |
| RoomCovers |
| Schools* |
| Series |
| Seasons |
| SENStudentNeeds |
| SENStudents |
| Staff |
| StaffContracts |
| StaffCovers |
| StaffFlatView |
| StaffQualifications |
| StudentAdditionalInformation |
| StudentContacts |
| StudentDetentions |
| StudentEnrolments |
| StudentExclusions |
| StudentImportedCTFAssessments |
| StudentInformation |
| StudentLearning |
| StudentMealPatterns |
| StudentMeals |
| StudentMiscellaneousInformation |
| StudentParentalConsent |
| StudentProtectionRegister |
| Students* |
| StudentSchoolTransportInformation |
| StudentSiblings |
| StudentsInCare |
| StudentSurgeries |
| StudentSurgeryDoctors |
| SubjectClasses |
| TimeTable |
| YearGroupClasses |
- These API permissions are designed for maximum capability with any potential application you can connect to via XoD. Without all these permissions, we cannot guarantee that XoD will be able to access the data areas it requires, and in some cases the service may not work at all.
- Although XoD requires the capacity to access a wide range of data, it will only collect the data that you have authorised for any 3rd party applications. Read our guide for further information: Best Practices: Xporter and MIS Permissions.
* We use the Schools and Students permissions to check that the provided login details are correct.