When a sync completes and a blue exclamation mark displays on the Data Sync History page, you can investigate the issues that caused this flag to be triggered using the Data Quality page.

Issues are highlighted on one of three tabs, depending on the data rules that triggered the flag:

When records have issues, the number of records affected displays to the right of a tab name; clicking the tab displays details about the affected records based on the enrollment data type containing the issue.

When you add an Import app to the Amplify OneRoster CSV Upload Portal, you are prompted to set Data Requirements that flag and/or skip a record if that record is missing values for one or more attributes. Additionally, you are asked to use Domains of Uniqueness to define attributes that must be unique within your district. As you import your data, records are checked against these rules, and any records that do not meet them are displayed on the My Rules tab. Click My Rules to view information about the affected records.

Each data type with an issue displays on the tab. Click a data type to expand it and view additional information about each affected attribute and its associated issue.

To locate more specific information about issues, click the icon for your Import app in the Applications column.

After your Import app opens, click the Data Quality tab on its dashboard.

Click a blue number to view details for the associated records.

The affected records display in a table; if an error message is truncated, you can pause your mouse on it to view the full message. In this example, the student is missing an email address; the student’s record in users.csv will need to be updated with an email address, and the CSV files will need to be re-uploaded to the portal.

When your enrollment data is exported from the Amplify OneRoster CSV Upload Portal to the Amplify and/or mCLASS enrollment systems, records are checked against data rules set by Amplify for each of these systems, and any records that do not meet them are displayed on the App Rules tab. Click App Rules to view information about the affected records.

Each data type with an issue displays on the tab. Click a data type to expand it and view additional information about each affected attribute and its associated issue.

To locate more specific information about issues, click the icon for your Export app in the Applications column.

After your Export app opens, click the Data Quality tab on its dashboard.

Click the Show Data Requirements button to view the required attributes for each data type; click Close when you’ve finished.

Click a blue number in a data type to view details for the associated records.

The affected records display in a table; if an error message is truncated, you can pause your mouse on it to view the full message. In this example, two students are missing the value for the required Gender demographic; the students’ records in demographics.csv will need to be updated with their gender, and the CSV files will need to be re-uploaded to the portal.

When you import your data, records are checked against your set Domains of Uniqueness, and when more than one record contains a value that is supposed to be unique within your district, the first record processed from each set displays on the Duplicates tab. Please note that duplicate records also are flagged on the My Rules tab, but issue resolution involves fewer steps when done through the Duplicates tab. Click the Duplicates tab to view the affected records.

Click a record in the Duplicates table to view the Duplicates Resolution screen.

The affected records display in a table; attributes with unique values are highlighted yellow. In this example, you can see that two students share an Identifier, which must be unique. It will need to be determined which student should be associated with this identifier and the what the correct identifier should be for the second student. The second student’s record will need to be updated with the correct identifier in users.csv, and the CSV files will need to be re-uploaded to the portal.