Field filtering has never worked on /api/metadata endpoint, it only supports viewClasses… I do want to rewrite that endpoint to support field filtering, but its not something that can be done quickly (unless we hacked it in)
You can however do something like this (I think this is close to what you want)
This will disable those types.
On Wed, Mar 18, 2015 at 1:40 PM, Mahendra Kariya email@example.com wrote:
We want all the fields from /api/metadata except a few.
We tried http://localhost:8080/api/metaData?fields=:all,!attributes,!options expecting that the “attributes” and “options” fields will be filtered out. But that’s not the case. Earlier this used to work.
Has the API changed recently?