You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to put in a feature request for the API:
Allow an active or in-use filter to the resource_classes and properties endpoints
This would allow us to grab those custom metadata attributes that are in use, which will typically be a very small subset of the available attributes. Right now, the only way to narrow that down is to iterate over all the classes or properties to see if there are any results, or just to hard-code them into any search interface
It seems like it would be low-cost on the server side, I think the sql looks like:
select resource_class_id,label from (select distinct resource_class_id from resource) as tmp join resource_class on (tmp.resource_class_id=resource_class.id);
The text was updated successfully, but these errors were encountered:
So we're on the same page, you're looking for a new API filter that just returns properties/classes that are being used by anything at all? I'm not opposed to that, I think.
One point though: you do have an option currently that's not hard-coding to limit properties in the search interface, using the feature that lets you apply a template.
Aaah I'm so terrible, I missed your reply until I saw you close this :p
We did make use of templates to this end, apologies again. But we did have a few cases left over I believe where we would make two calls: one to retrieve the property_id and another to insert the value into that property.
I would like to put in a feature request for the API:
select resource_class_id,label from (select distinct resource_class_id from resource) as tmp join resource_class on (tmp.resource_class_id=resource_class.id);
The text was updated successfully, but these errors were encountered: