For SIS Uploads, provide more granular control for overriding sticky fields

Idea created by leward@iu.edu on Apr 19, 2018
    Open for Voting
    Score6
    • Greg Thomas
    • leward@iu.edu
    • Rob Ditto
    • Andrea G Schmidt
    • Jim Wolf
    • Christopher Maurer

    Currently, the option to override data in sticky fields during SIS Uploads is an all or nothing proposition.  It would be helpful if institutions could choose the files and specific fields we wish to override during the SIS import process.  Due to a recent change in the  stickiness of the course_id in the sections.csv file, we had a need to run the batch in override mode, but the override had a negative affect on other fields that should have respected changes made through the user interface.  If it were possible to specify the sticky fields that should be overwritten, that would have allowed us to address the problem without a major overhaul of our provisioning job.