Closed JonathanLill closed 2 years ago
@JonathanLill, forgive but I must verify...have you selected "Add/Update" for your profile type? If so, please add a comment with the details of the profile you are using. Thanks.
No worries, I understand the need for precise verification. I've attached two screenshots, one of the profile settings and one of the csv test upload.
@JonathanLill, thanks...I'll take a look.
Okay, I created a new profile, pictured below, along with an image of the test upload, and although I can't see any difference between the two profiles that would make a difference, this new profile worked. And I've subsequently successfully run the update on 1000+ user records. So the question, which may not be worth your time at the moment, is whether this was a a real bug, a phantom, or caused by something outside the program. Thank you nonetheless for your quick response. This app has been of tremendous help to me.
Jonathan
@JonathanLill, glad it is working for you, as I have not been able to replicate the problem. Sorry, I can't offer any reasonable explanation; the only difference I see in your cases is the job category in the second csv file does not contain commas...but I tested with your original csv with the commas, and it worked for me. Closing the issue...please create a new one if you encounter further issues. Thank you.
I ran this app a few times successfully, but when I've tried to run it recently it doesn't seem to be functioning correctly. It wouldn't surprise me if I'm doing something incorrectly though. I want to update the Job Category field in existing user records. My profile maps two fields in my import csv "Primary identifier" and "Job Category" to "Primary ID" and "Job category" with no default value. When I run it it adds a new user record instead of updating an existing one. The new record is entirely blank except with the correct value in the job category field, and the Alma user unique ID in the primary identifier field. I don't understand why it doesn't seem to be able to match on the primary identifier. It's handling job category correctly in that it will produce an error message if my import value doesn't match a previously defined option.
Am I missing something, or forgetting a step? Or can you offer any guesses why it is not currently working like I expect?
Thanks much,
Jonathan