These are some basic items to look at when an uploaded conduit CSV file is not processing correctly.
Conduit column headings are case sensitive
Conduit column headings are case sensitive:
For the “action” column, the column heading needs to always be “action.” "Action" or "ACTION" will not work.
For all other columns, the column heading needs to exactly match what was provided in the Conduit mapping for that field. (Located under Conduit Settings > Mappings)
The only special character that can be used in a Conduit column heading is the underscore character ( _ ).
Conduit also requires that the start and end of every column heading be an alphanumeric character. Conduit will trim leading and trailing blanks in the entry.
Since the file is a CSV or a comma separated volume, the comma (, ) is a reserved symbol. If used in a column heading, mapping, or entry, the file will break because the CSV format interprets that comma as the end of a value and the start of the next.
Are the file names the same as they are set in the Conduit Settings?
The Conduit file name must match what is set up in Conduit > Settings > File. If the file name does not match what is listed, Conduit will not know what to do with it, and it will stay unprocessed in the SFTP directory.
Conduit can handle variable file names for each type, where course.csv files might work as a fixed file name for some processes, others might need support for names that index or change. You can set up Conduit to use simple patterns to match changing file names. In the file name mapping, an asterisk (*) matches any number of characters (including none), and a question mark (?) matches any single character. The (?) is available to allow you to specify the number of characters required in the variable space.
-
The default file names are as follows:
Users: user.csv
Courses: course.csv
Enrolment: enroll.csv
Groups: groups.csv
Group Members: group_members.csv
Role Assignments: role_assign.csv
Cohort Members: cohort.csv
Are the files in the location that is specified for them to be?
The Conduit file must be placed in the directory specified on Conduit > Settings > File via SFTP. If the file is located somewhere else, it will not be processed because Conduit only looks in the path specified in the settings.
The path in the settings is hard-coded by Open LMS and cannot be accidentally altered by you or other Site Admins.
You can upload the file directly by going to the Upload tab in Conduit and selecting the file type to be uploaded. (Please notice that this method is recommended only if you have a few entries)
If you are using Conduit and do not have SFTP credentials created for your site, please submit a case, and Open LMS support can provide that information.
Should I check Update Moodle, Update Conduit, or both in Conduit Settings > Mapping?
Most fields in most implementations of Conduit do not have either value checked. Having both "Update Moodle" and "Update Conduit" for one field will not work. These settings work against each other; one tells Conduit to be in charge of the value and force what it has always, the other says to allow changes and copy those changes into Conduit when they happen in the system.
Update Conduit - Users are able to change their profile information and similar things in Moodle. The changes made will then be updated to Conduit.
Update Moodle - Users cannot make changes in Moodle. If a user tries to change something, Conduit will update the record back to what is set in Conduit.
When using Update Moodle on user record fields, Open LMS recommends that you lock those fields from user alteration in the corresponding Authentication module (Site Administration > Plugins > Authentication > Manage authentication)
An enroll.csv file will not unenroll a particular student.
Conduit can manage enrollments for users and is designed to both create and delete enrollments when handling enrollment information. If users are not being unenrolled as expected, these are some good troubleshooting tips:
Check your Conduit enrolment .csv file. If you are trying to unenroll a student and the action column does not have “delete,” then the student will not be unenrolled.
Check the Conduit > Settings > General settings page, Enrollments section, and verify that Auto-unenroll users is set to "Yes". Without this set to allow, Conduit will not unenroll users.