Hi John, let's take up the conversation on the open idea https://blackbaudk12.ideas.aha.io/ideas/K12OR-I-1804 specifically for this topic.  See my question posted there.  Thanks!

BTW, BB support has responded to this non-unique issue by saying, "just make it unique and then import it".

In my view, this does not address the issue.

Janet [et al],  Thanks for your interest and the information.  I used this yesterday and, unfortunately, the implementation has some serious problems, namely: 

- it does not work with non-unique fields.   e.g. if you have a non-unique field and you want to add another instance of it to a record, it OVERWRITES the original  [or, sometimes, it doesn't work at all]

- there needs to be a way to specifically address individual values , at least to delete them.  Consider my "miscTag" example:  if I reuse this over the years for various things, they will PILE UP on the record.  There really needs to be a way to update them or, at very least, to delete them.

Great news! This has ben implemented and can be found under Core > System Tools > Data Import.  Create a job and choose the category type 'User Update'.  

Ok, I just found the emails about it all and it looks like it was a refresh.  My memory is clearly failing.  Sorry about that.  I am going to follow up with Blackbaud because the Publishable Field one they created for me currently resides in the Import section, not the refresh section which caused my confusion.  The emails show it was created as a Refresh back in 2017 when I had it made.  If I find out anything useful for you John, I will let you know. 

This is actually possible or at least it used to be.  A while ago, I had BB create an import for publishable fields  because it was not available at the time.  I inquired about the possibility of creating another one for the admin-only fields and they said they could do it too.  Ultimately I didn't ask them to create it, because I didn't end up needing it but I have emails stating they can do it.