REST API - Update Custom Choice-Property Type Request

/api/v1/projects/{projectid}/metadata/choicepropertytypes description updates the custom (project level) choice type property, including custom property name, valid values, and default value url structure \[blueprint uri]/api/v1/projects/{projectid}/metadata/choicepropertytypes projectid the id of the project that contains the custom property you want to update or create supported methods patch docid\ rcjvhrlby6de zgkehxui you can override the patch docid\ rcjvhrlby6de zgkehxui method and use the post docid\ hsi lzxs8g rx ydudzkg method instead request body the list of artifacts that you want to publish must be included in the body of the request read more about how to specify a list of artifacts in the request body docid 5qd6 fuzdothy7 mrc1t1 blueprint result codes your response may contain resultcode and message parameters if your request involves changes to blueprint data these parameters provide detailed information about the result of your request 200 (ok) the artifact updated successfully 400 (bad request) 403 forbidden the applicable permissions are needed for example, this error can occur when an author or collaborate license is needed for access comment permissions are needed on the artifact edit permissions are needed on the change summary job 404 (not found) artifact not found in the project artifact type not found http status codes 200 ok 201 successfully created 206 partial content 400 bad request this error can occur for a variety of reasons at least one uri or request body parameter is invalid, such as one of the filter docid\ sv9gjverxczcgqdn28j7u , traces, offset or limit parameters a required value has not been provided if you are submitting a post docid\ hsi lzxs8g rx ydudzkg or patch docid\ rcjvhrlby6de zgkehxui request and have not added the x http method override parameter to your request header 401 unauthorized the blueprint token is missing, invalid or expired 403 forbidden the applicable permissions are needed for example, this error can occur when an author or collaborate license is needed for access comment permissions are needed on the artifact edit permissions are needed on the change summary job 404 notfound item is not found in the project for example, this error can occur when artifact not found artifact type not found project not found alm target not found change summary job not found user does not have edit permissions for this artifact, project or alm target 409 conflict reason for failure can be found in the response body additional information may also be found in the log 411 length required if the content length header is missing in the request 413 request entity too large if the provided file size is larger than allowed 415 unsupported media type if the provided media type is not of mime multipart content "form data " 416 request range not satisfiable if offset points to a part of a collection that is not available 500 internal server error 501 not implemented examples xml example request uri https //production blueprintcloud com/api/v1/projects/45921/metadata/choicepropertytypes request body \<?xml version="1 0" ?>\<choicepropertytype xmlns="http //www blueprintsys com/blueprint/api/v1" xmlns\ i="http //www w3 org/2001/xmlschema instance"> \<id>928\</id> \<name>activity type\</name> \<defaultvalueindex>1\</defaultvalueindex> \<validvalues> \<validvalue>instant\</validvalue> \<validvalue>responsive\</validvalue> \<validvalue>waiting\</validvalue> \</validvalues>\</choicepropertytype> json example request uri https //production blueprintcloud com/api/v1/projects/45921/metadata/choicepropertytypes request body \[ { "id" 928, "name" "activity type", "defaultvalueindex" "1", "validvalues" \[ "instant", "responsive", "waiting" ] }]