Designation upload validation messages and skipped rows – GiveCampus University

For GiveCampus giving forms and school-level designation settings.

The designation upload checks the whole file and reports two kinds of result before you rely on it: errors, which identify rows that will be skipped or a file that cannot be used at all, and notices, which describe something that will still happen. A row number in a message refers to the row in your file, and row 0 means the problem is in the header row rather than any single row. A file can import while individual rows are skipped, so read the validation result rather than treating a completed upload as proof that every row was created.

Problems that stop the whole file

The CSV headers contain empty columns. Every column needs a header name. A trailing blank column counts.
The provided CSV headers are incorrect. Use the headers from the downloadable sample file.

The required headers are name, backend_identifier, write_in, group, program_priority, group_name1, group_name2, group_name3 and description. Required headers do not mean every cell must be populated.

Rows that are skipped

In your file	What the validation reports
`name` is blank	"name" must be populated.
The same designation appears on more than one row	The designation is in the upload multiple times; the later row is skipped and the message names the earlier row.
The same group appears on more than one row	The group is in the upload multiple times; the later row is skipped. A group is identified by its name together with its parent names and description, so two rows differing only in description are two different groups.
`description` longer than 255 characters	The description must be 255 characters or fewer, and the row is skipped.
The designation already exists at your school	Skipped, unless the row places it in a new group. In that case it is reported as a notice and the existing designation is added to the new group.
The group already exists at your school	Skipped. Re-uploading an existing group does not update it.

Hierarchy problems

Parent group names go in group_name1 through group_name3, outermost first, and intermediate levels cannot be left out:

group_name1 must be populated if group_name2 is populated.
group_name1 and group_name2 must both be populated if group_name3 is populated.
A parent group that exists neither at your school nor on another row of the same file is reported by name as not existing. Create parent groups before their children, and match existing parent names exactly.

Program priority

If program_priority names something that is not a designation on a separate row of the file and does not already exist, the group is still created but no program priority is attached to it. This is reported as an error even though the group is created, so read the message rather than assuming the group failed.

After the upload

Check the created structure against your file, especially where rows were skipped as already existing. Correct the file and upload again for anything that was skipped; re-uploading an unchanged file produces the same skips.