Question about errors in load log

[seanpurcell]

One of the institutions in our consortia is testing the Alma CSV User loader cloud App, and recently tried a file with about 50 users in it. The app reported back that 46 were processed and 3 had errors. Here is a snippet of the resulting log (anonymized). We're not exactly sure exactly what the error means? The Primary IDs of the folks with errors do match their primary IDs in Alma, so we're puzzled as to why they aren't getting updated.

Processed: 9271xxxxxx Processed: 9275xxxxxx Processed: 9273xxxxxx Processed: 9278xxxxxx Processed: 9271xxxxxx Processed: 9270xxxxxx Processed: 2010xxxxxx Failed: The external id in DB does not fit the given value in xml - external id cannot be updated. (2099xxxx, Baggins, Jane) Processed: 9271xxxxxx Processed: 9121xxxxxx Processed: 9123xxxxxx Processed: 9120xxxxxx Processed: 9270xxxxxx Processed: 9278xxxxxx Failed: The external id in DB does not fit the given value in xml - external id cannot be updated. (9154xxxx, Strider, Bob)

Thanks! Sean

[jweisman]

Hi Sean. The field referred to here is the external_id, which in the UI is called "owner":

If this field is being updated to something different than already exists in the record, you will get this error.

So a few questions:

1. Is this field mapped in your profile?
2. Is this field defined in the input CSV?
3. Is it different than what this record shows (we can see it set as 'BULK_UPDATE'

Thanks, Josh

[seanpurcell]

Hi @jweisman,

Re-posting your questions with my answers below:

• Is this field mapped in your profile?

  • No here's the current test profile: (GIL-Test.zip)

• Is this field defined in the input CSV?

  • Here are the fields in the CSV: LAST_NAME | FIRST_NAME | ADDRESS1 | ADDRESS2 | CITY | STATE | POSTAL | PHONE | EMAIL_ADDR | BANNER_ID | LOCATION | USER_GROUP

• Is it different than what this record shows (we can see it set as 'BULK_UPDATE'

  • I think you're on to something here. All of the records that couldn't get updated, their "owner" was "BULK_UPDATE". The ones that updated fine were set as "SIS"...

[jweisman]

Hi @seanpurcell. Thanks for sending the profile export- very helpful!.

I see that the external_id field is indeed in the profile with a default of SIS:

      {
        "header": "",
        "fieldName": "external_id",
        "default": "SIS"
      },

This means that if the field is not specified in the CSV the value SIS will be set. If the saved record has a different "owner," the update will fail.

Is the field defined in the profile intentionally?

[seanpurcell]

Hi Josh,

Good catch, yes that is set in the profile… We can pull that out, I don’t recall why we set that to be honest. We’ll try that. Can this be left blank or is it required?

Thanks, Sean

From: Josh Weisman @.> Sent: Sunday, August 29, 2021 5:25 AM To: ExLibrisGroup/alma-csv-user-load @.> Cc: Sean C Purcell @.>; Mention @.> Subject: Re: [ExLibrisGroup/alma-csv-user-load] Question about errors in load log (#42)

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]

Hi @seanpurcellhttps://github.com/seanpurcell. Thanks for sending the profile export- very helpful!.

I see that the external_id field is indeed in the profile with a default of SIS:

  {

    "header": "",

    "fieldName": "external_id",

    "default": "SIS"

  },

This means that if the field is not specified in the CSV the value SIS will be set. If the saved record has a different "owner," the update will fail.

Is the field defined in the profile intentionally?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ExLibrisGroup/alma-csv-user-load/issues/42#issuecomment-907759205, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABLOGDKXKGR5OZVFZNPMRRLT7H4GXANCNFSM5CZY6OOA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[jweisman]

Hi @seanpurcell - I believe that field is mandatory if creating an external user. It's not required if updating external users. So I recommend having a separate profile for updating that doesn't include that field. That way the existing value will be used.

Let us know how that works out for you.