2

I am aware that it is possible to create dependent picklist values using the Metadata API but I want to use the REST API.

I know how to create triggers, classes, and pages but I can't wrap my head around picklist values, nevermind their dependency.

Is this possible at all? If so what would the body of the request look like? I am guessing the service URL would be:

/services/data/v41.0/sobjects/standardvalueset

I have seen a few unresolved older threads on this topic but I am hoping things have changed by now.

0

The REST API (/services/data/vXX.X/sobjects/) is strictly a user-level API. It does not allow you to modify any metadata components, including fields, objects, layouts, and so on. If you want RESTful access to metadata configuration, use the Tooling API instead (/services/data/vXX.X/tooling/). The StandardValueSet is supported.

  • Ok. Tooling API works! But I am still having difficulty putting together the request body; How do I link the new value to the picklist field? How do I create the field dependency? It seems EntityParticle is what I should use but it only allows GET requests. By the way do you know if all of this can be done in production orgs? – Mossi Nov 2 '17 at 23:26
  • To further elaborate, I cannot access PicklistMaster or ValueSet via the REST API (tried Tooling and Metadata API's). I believe this is what I need to create and link it to a StandardValueSet (or CustomField in case of a non-standard picklist). But I don't know how to do it. Of course creating the dependency remains as another problem! – Mossi Nov 3 '17 at 23:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.