-
Re: Profile field bug in response from osapi.jive.corev3.people.get()
Could you share information about your instance, so we can check the Profile configuration? Also, any chance you can post a screen shot of the configuration screen and a sample of the results?
-
Re: Profile field bug in response from osapi.jive.corev3.people.get()
You know what, I think I just figured out what's going on. It looks like the Department field had its English language translation entry changed from "Department" to "Company" rather than adding a new profile property for Company. It does bring up a question, though – how do you get the i18n translations for the labels? Is that something you can specify in the request? Does it look at headers?
Here are the screenshots...
JSON:
PROFILE PAGE:
PROFILE SETTINGS:
DEPARTMENT FIELD SETTINGS:
-
Re: Profile field bug in response from osapi.jive.corev3.people.get()
Didn't realize there was a follow-up question here. Let me loop in Engineering, as I'm not quite sure how to get a list of translations myself. Stay tuned.
-
Re: Profile field bug in response from osapi.jive.corev3.people.get()
Casey Gum - Learn something new every day. Check this out =)
More info on what locales are supported by Jive here: Jive REST Rest API v3.6 → LocaleMetadata service
Localized labels of profile fields can be obtained by calling /api/core/v3/metadata/objects/profile. see: Jive REST Rest API v3.6 → ObjectMetadata service
-
Re: Profile field bug in response from osapi.jive.corev3.people.get()
1 person found this helpfulOkay, so it looks like if you want to actually get translated field names, you first need to:
1) Make a call to /api/core/v3/metadata/locales/supported
2) Take the "id" value for the language you are interested in. (like "es" for Spanish)
3) Set the Accept-Language header to that value (e.g. Accept-Language="es")
4) Make a call to /api/core/v3/metadata/objects/profile
-
-
-
-
-
