User Extension Attribute not updating

Question

User Extension Attribute not updating

seanism opened this issue 7 years ago · comments

I created a CSV with all my users and the data for the user extension attribute. I set attribute ID which I get from the URL when I view the attribute. I run the update and it says it worked but nothing shows up in JAMF. Any thoughts? Thanks in advance.

CSV: /Users/seanyoung/Downloads/JAMF_OFFICE.csv
Found 292 rows in the CSV.

Example row from your CSV:
Username: adam.levinson, User Extension Attribute: HQ

Device Type: Users
ID Type: Username
Attribute Type: User Extension Attribute

Beginning Update Run!

Device with name adam - OK! - 201
Device with name adam.levinson - OK! - 201
Device with name adam.lohr - OK! - 201

Mike Levenick · Answer 1 · Thu Oct 05 2017 21:51:43 GMT+0800 (China Standard Time)

Hey Sean, thanks for reaching out.

I looked over my code and everything looks good, so I tried an extension attribute update via the API in terminal, and I got similar results--everything looks good, but no actual update takes place.

I'll keep digging in on my end, but I also suggest reaching out to Jamf and get a case created to see if they have any more information about User Extension Attributes not updating properly from the API.

garavs · Answer 2 · Fri Nov 17 2017 05:29:15 GMT+0800 (China Standard Time)

Mike,
I talked to you about this feature back at JNUC and we had it work then but I haven't been able to since. It had something to do with using the user id.

Josh Bourdon · Answer 3 · Fri Nov 17 2017 08:11:27 GMT+0800 (China Standard Time)

JAMF support referenced PI-003359 for being unable to update user objects with the API issue in a ticket recently. I haven’t been able to find mention of it in release notes however.

Mike Levenick · Answer 4 · Fri Nov 17 2017 22:22:14 GMT+0800 (China Standard Time)

@bumbletech good to see you! Love your work, and glad you're keeping in touch.

I have to be a bit delicate with my overlap as a Jamf employee in addition to my work outside Jamf on MUT, but from what I'm seeing, PI-003359 is unrelated to this issue.

That said, from the release notes of 10.1 beta, I see under bug fixes and enhancements:

[PI-004025] Fixed an issue that resulted in the API failing to modify the user extension attribute values when a user was created.

I am doing some independent testing currently to verify that it is functioning properly in 10.1 beta. Will report back as I find out more.

Mike Levenick · Answer 5 · Fri Nov 17 2017 22:50:36 GMT+0800 (China Standard Time)

I have tested and confirmed that in Jamf Pro v10.1 beta, MUT is able to update user extension attributes.

Please let me know if anyone is finding something different.

garavs · Answer 6 · Mon Nov 20 2017 23:26:20 GMT+0800 (China Standard Time)

How did you run it? Anna

…

On Nov 17, 2017 7:50 AM, "Mike Levenick" ***@***.***> wrote: I have tested and confirmed that in Jamf Pro v10.1 beta, MUT is able to update user extension attributes. Please let me know if anyone is finding something different. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgLAtZ7krhCFWvvw2DihbnM_Nd39rDZtks5s3Z09gaJpZM4PulJX> .

Mike Levenick · Answer 7 · Mon Nov 20 2017 23:31:27 GMT+0800 (China Standard Time)

The beta installer for 10.1 can be found in JamfNation under Assets if you are part of the beta program. If you are not yet, you can request to join the beta program.

From there, I filled out the dropdowns as follows:
I want to update: Users
Unique Identifier: Username
Attribute to update: User Extension Attribute
Extension Attribute ID: 5 (this may be different for you).

CSV file was username in column A, and value for the EA in column B.

garavs · Answer 8 · Mon Nov 20 2017 23:54:39 GMT+0800 (China Standard Time)

the ext attribute id is the number from the url for the user, correct?

…

On Mon, Nov 20, 2017 at 8:31 AM, Mike Levenick ***@***.***> wrote: The beta installer for 10.1 can be found in JamfNation under Assets if you are part of the beta program. If you are not yet, you can request to join the beta program. From there, I filled out the dropdowns as follows: I want to update: Users Unique Identifier: Username Attribute to update: User Extension Attribute Extension Attribute ID: 5 (this may be different for you). CSV file was username in column A, and value for the EA in column B. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgLAtbKs4owZtuXJFim-QuELAJ4k4_HLks5s4ZtQgaJpZM4PulJX> .

Mike Levenick · Answer 9 · Tue Nov 21 2017 00:45:18 GMT+0800 (China Standard Time)

Yup! Right here:

garavs · Answer 10 · Tue Nov 21 2017 01:07:12 GMT+0800 (China Standard Time)

I swear I'm doing the same thing but it will not update my EA on 10.0.0

…

On Nov 20, 2017 9:45 AM, "Mike Levenick" ***@***.***> wrote: Yup! Right here: [image: screen shot 2017-11-20 at 10 44 23 am] <https://user-images.githubusercontent.com/12515543/33030046-dbce3228-cddf-11e7-9e03-e39d0fa37abf.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgLAtby8jojjLJ0B_EvypQpZNTye46pTks5s4ayegaJpZM4PulJX> .

Mike Levenick · Answer 11 · Tue Nov 21 2017 02:19:25 GMT+0800 (China Standard Time)

Correct.

From the release notes of Jamf Pro v10.1 beta, I see under bug fixes and enhancements:

[PI-004025] Fixed an issue that resulted in the API failing to modify the user extension attribute values

garavs · Answer 12 · Thu Dec 21 2017 01:51:57 GMT+0800 (China Standard Time)

Hurray! It works for me now that I've updated to 10.1.1!
THANK YOU THANK YOU THANK YOU

Mike Levenick · Answer 13 · Fri Apr 06 2018 23:34:54 GMT+0800 (China Standard Time)

Excellent, I'm glad to hear it!