Import of Admin view-only custom fields - handle non-unique values

This is not so much an idea as a bug report:  this import cannot import NON-unique custom fields.

e.g. if a student has a value for the Probation field of "17_18", we cannot add the value "18_19" via import even though we can do this manually.

  • john ronan
  • Jan 31 2019
K-12 Core
  • Attach files
  • Janet Wittenberg commented
    January 31, 2019 19:10

    Hi John,

    Part of the decision to limit the import capability was we had to trade off the ability to edit or delete a value versus add an additional custom field value for the same custom field.

    If the file you build for import has student x with one row called 'Probation' with '18_19' - should we assume we are adding that value as a second custom field, or should we assume you are trying to fix the original value? How would you expect to communicate the difference?

    The other option would be that you would always have to provide existing plus new values, so to keep 17_18 and add the value 18_19, you would need to supply two rows for that student to add the new value.

    Does this make sense?

    I'd appreciate your feedback on what would make this usable through the import pattern.

    ×

    Attachments Open full size

Related ideas