Anyone have any experience reading and writing to user custom fields
through the REST API. I can create and read everything but custom fields.
I’m posting to /REST/1.0/user/new/edit with the following:
id: new
email: jsmith@georgefox.edu
name: jsmith
CF-Emplid: 1190885
The user is successfully created, but the Emplid Custom Field is blank.
I’m connecting as root and can see/edit the field through the web.
Ryan Backman
Programmer / Analyst
George Fox University
503.554.2576
Anyone have any experience reading and writing to user custom fields
through the REST API. I can create and read everything but custom fields.I’m posting to /REST/1.0/user/new/edit with the following:
id: new
email: jsmith@georgefox.edu
name: jsmith
CF-Emplid: 1190885The user is successfully created, but the Emplid Custom Field is blank.
I’m connecting as root and can see/edit the field through the web.
Hi Ryan,
I do not think that the REST piece for working with user custom
fields has been written.
Cheers,
Ken
Looking at the database, it would be a simply SQL statement to insert the
desired value into the user custom field… Do I need to be aware of
anything before I start directly inserting into the RT tables?
Ryan Backman
Programmer / Analyst
George Fox University
503.554.2576
Looking at the database, it would be a simply SQL statement to insert the desired value into
the user custom field… Do I need to be aware of anything before I start directly inserting
into the RT tables?
That’s recommended against.
If you have DB access, then you probably have access to the Perl API
which is much more powerful than the REST API anyway.
-kevin
I’m using RT 4.4.1 and wanted to confirm that it’s still the case (as established, seemingly, in this thread) that the REST API doesn’t support user-level custom fields. I’m using the search method and keep getting “Invalid field specification,” but is it possible that I’m just formatting the field name incorrectly?
Thanks!
Bump.
I’m running into the same issue in RT 4.4.2