As there is no public issue tracker (afaik) or reporting workflow (other than support tickets and ideas), I'd like to collect some things that were found trough hour-long trial end error (some includ...
Issue: #? Type: BUG Area: REST API v2 Collection: settings Platform Version: >= 22.12? Summary: Per Khoros Support, Community 22.12 broke the API V2 field-setting capability. Ping: not sure who's in charge
ISSUE SUMMARY: Kudos to keithkelly for reporting that publicly, it seems that if you do a query like SELECT * FROM settings WHERE id = 'c_custom_field_name' AND user.id = '409' won't work properly, not confirmed for all types of requests, but at least POST requests to update a setting value seem to be affected. If someone has more info, please let me know. For some reason I also can't find the settings collection anymore in the API v2 docs, I was pretty sure it was there at some point, was this removed?
Details about this in case it helps anyone who stumbles across it:
Bug ID: 00407790 Submitted 2/10/23
Setting Custom Board Property (is no longer working)
Description:
I have some PostMan scripts that I used a couple months ago to set the "c_dc_scope" board property successfully. However, this is no longer working, even when I set the user to have Administrator permissions.
This acts successful, but the value isn't updated
Workaround provided by Khoros Support (and worked) was to use: