Policies fail to save with no category

Question

Policies fail to save with no category

sheagcraig opened this issue 10 years ago · 3 comments

Pulling an existing policy with no category, or creating a new one, and then trying to .save() results in a HTTP 409 error: "Conflict/Error: Problem with category name".

It seems that Jamf has changed it so, lacking a category, a policy now has a category id of -1 and a name of "No category assigned". However, it won't accept those values when you try to PUT/update.

I imagine that this also affects other things that have categories, like Packages.

Answer 1 · 2014-12-03T19:17:37.000Z

Indeed, I can look for empty categories prior to the PUT, strip out the "-1/No category assigned", and THEN PUT, and it will merrily accept it, and add it back in upon GETting it again.

Answer 2 · 2014-12-03T19:25:49.000Z

Confirmed: It fails on packages as well.
Confirmed: It fails even on 9.61.

Answer 3 · 2014-12-03T19:34:32.000Z

Also, it appears that changing the category name to "Unknown", then doing the PUT works. So I think JAMF probably forgot to change it in the code at that point. I have opened a support case with them on this issue.