RIO Reporting (AU) - EDA vs RIO Reporting Objects and Fields to note
If a Salesforce instance is installed with RIO Reporting (AU) package, this is highly likely because the school is located in the Australia region, and that the school would need to be compliant with the Government's data reporting requirements, such as TCSI.
In this case, it is worth noting that RIO Reporting (AU) package would have its own set of fields and objects defined to be compliant with the Australia Government's data reporting requirements too. With the EDA package, there are fields/objects that may coincide with the RIO Reporting (AU) fields/objects, but they may be defined in a more generic manner than being compliant with the Australia Government's data reporting requirements.
Implementation Recommendation
If the school is required to be compliant with the Australia Government's data reporting requirements, it is recommended to consider using the following fields/objects as opposed to the EDA fields/objects instead:
RIO Reporting (AU) API Field Name | Object | EDA API Field Name (recommended to be replaced by the RIO Reporting field) | Notes |
rio_edaurep__Citizen_Resident_Status__c |
Contact | hed__Citizenship_Status__c |
An additional background engine will create/update an EDA Attribute record to track the student's citizenship. This attribute record can in return be used for TCSI's student citizenship packet. Such sync can be achieved via RIO Connect TCSI integration module for example. |
rio_edaurep__Country_Birth_L1__c, rio_edaurep__Country_Birth_L2__c, rio_edaurep__Country_Birth_L3__c, rio_edaurep__Country_Birth_L4__c |
Contact |
hed__Country_of_Origin__c |
|
rio_edaurep__Language_Spoken_Home__c, rio_edaurep__Language_Spoken_Home_L1__c, rio_edaurep__Language_Spoken_Home_L2__c, rio_edaurep__Language_Spoken_Home_L3__c |
Contact |
EDA may not have any field that coincide with the listed RIO Reporting (AU) fields but it is still worth to be aware of this in case there are other custom fields used for the same purpose. | |
rio_edaurep__Disability_Q1__c, rio_edaurep__Disability_Q2__c |
Contact |
An additional background engine will create/update an EDA Attribute record to track the student's disability. This attribute record can in return be used for TCSI's student disability packet. Such sync can be achieved via RIO Connect TCSI integration module for example. |
|
rio_edaurep__Mailing_Country__c |
hed__Address__c |
hed__MailingCountry__c |
|
rio_edaurep__Is_Residential__c |
hed__Address__c |
If RIO Connect TCSI integration module is being used, it is important to check this checkbox against an address record that represents the student's residential address. This allows the integration to pick up the correct address record for student sync purpose. | |
hed__Default_Address__c |
hed__Address__c |
If RIO Connect TCSI integration module is being used, it is important to check this checkbox against an address record that represents the student's term address. This allows the integration to pick up the correct address record for student sync purpose. |