How can enable the filter on managed metadata fields on REST API direct? - rest

How can enable the filter on managed metadata fields label on REST API direct and fetch all the fields using the filtering of the MMS field using direct REST API?

I got the same situation on this i have enable the filtering using the Managed Metadata fields on a list using the below API:
_api/Web/Lists/GetByTitle('List-name')/Items/?$select=*,TaxCatchAll/Term&$filter=TaxCatchAll/Term eq '${Managed-Metadata-field-value}'&$expand=TaxCatchAll
'Managed-Metadata-field-value' means: Country is the MMS field and US is the value put US on here
But the API have limitation i think this filter enable only on a single MMS field.
Refer:workaround-to-filter-on-taxonomy

its not possible out of the box, but there are some workarounds for this.
See: http://www.cleverworkarounds.com/2013/09/23/how-to-filter-on-a-managed-metadata-column-via-rest-in-sharepoint-2013/

Related

Clio API Filter data based on nested resource

Filtering data based on a top level resource is straightforward, but what is the proper syntax for the url when attempting to filter based on a nested resource? For example, if I want to return all tasks but only for open matters, how should I enter that into the URL endpoint since the Matter Status is a nested resource under Tasks?
I do not see the method for filtering based on nested resources covered in the Clio API documentation.
As far as I understand, you can only filter by the options Clio's API provides. For example when querying a Matter, you can filter by an originating_attorney_id but not a user_id as the API doesn't provide a way to do that. You'll just have to pull in all the data and filter it in your code logic.
You can reach out to the Clio API team and ask them to add a specific filter option and see if they'll do that for you. I've found that they are at least willing to have a dialog.

Is there a way in Camunda REST API to retrieve task’s form field property?

Camunda Modeler can let us set form field properties for tasks. I would like to use this feature to store some information for frontend input field rendering, e.g. inputtype=file for file upload selector.
Unfortunately, I found that the REST API /task/{taskid}/form-variables is not returing me such information and I have no other way to retrieve these information.
Any advice on how to get back these properties of task? Or any suggestion on how to store information for task that can let me retrieve them back through REST API?
Thanks in advance

DOCUSIGN REST API: Search by title/name of Envelope

I am trying to search for a list of envelopes in Docusign with the similar title/name. Is there a way to do this in REST API? The closest i can find is the SearchFolder API but it seems like it only allow to specify dates, folders (Draft,Sent etc) without a way to search by title.
yes, you can do that using the v2.1 API.
See here https://developers.docusign.com/esign-rest-api/guides/concepts/envelopes/search
using the search_taxt query parameter you can search for a specific text.
GET
/v2.1/accounts/4644/envelopes?search_text=Tabs&from_date=2019-03-04T00:00:00.000Z&to_date=2019-03-07T00:00:00.000Z

WSO2 API Manager - API Group inside another group

Im aware that in order to group APIs, we need to tag tha APIs with desired "suffix"-group in WSO2 Publisher.
Is it possible to create a subgroup within existing API Group?
No, tags are not hierarchical.

Find users with a particular license in Azure Graph REST

Has anyone queried the Azure Graph REST API by licenses? I can't find any examples using REST online. We use REST for our operations and a need has come up to generate license reports and I'd like to be able to execute queries based on license codes.
Any help would be appreciate. Thanks for your time.
According to your description, it seems that you’d like to filter users by assignedLicenses that is a multi-valued complex type. From this documentation, we could find that currently the API seems not support querying of (filtering) a multi-valued complex type (assignedLicenses).
As a workaround, you could try to get users from API and leave the filtering on the client side.