Third Light Developer Exchange

ohilton

Member

Registered: 2013-10-04

Posts: 12

Missing metadata fields in Search.GetSearchConfiguration

We seem to be missing some of our custom metadata fields from the list when calling the Search.GetSearchConfiguration API endpoint.  The missing attributes are generally quite new ones but others that have been around a while are also missing.  We have a number of custom metadata fields available to us but these largely seem to be ones we created a number of years ago. I can't see anything in the configuration of the metadata fields themselves to make them available to the Advanced Search API which is our ultimate goal, wondered if it was a permissions thing.

Support.Engineer

Member

Registered: 2015-06-08

Posts: 3

Re: Missing metadata fields in Search.GetSearchConfiguration

Hi, enabling the missing custom metadata fields in the 'Configuration > Search Preferences > Search Scope' page should resolve the issue.

ohilton

Member

Registered: 2013-10-04

Posts: 12

Re: Missing metadata fields in Search.GetSearchConfiguration

Hey, no the fields I want to search on are already enabled in that view, it also seems some of the field not enabled are coming through in the Search.GetSearchConfiguration response too so it doesn't look like there's any correlation between the two.

steve

Third Light Staff

Registered: 2013-06-06

Posts: 105

Re: Missing metadata fields in Search.GetSearchConfiguration

Hi,

Are you using an API key but are not subsequently impersonating a particular user's account? If so the account that would be used for your session would be the first administrator account listed on the following page:

Users > Users & Groups

You should then confirm that the metatadata field you are interested in does not have any restrictions placed upon it for that user account.

Configuration > Metadata > Customise Metadata > Edit YourField > Restrictions > User Restrictions

ohilton

Member

Registered: 2013-10-04

Posts: 12

Re: Missing metadata fields in Search.GetSearchConfiguration

That could well be the issue then, is that a new concept?  Can you point me at the documentation around impersonating a specific account in the API?

steve

Third Light Staff

Registered: 2013-06-06

Posts: 105

Re: Missing metadata fields in Search.GetSearchConfiguration

User impersonation and per-user metadata restrictions have been available for a few years now. Here is a post  from 2015 for example: https://devexchange.thirdlight.com/viewtopic.php?id=139

Please see Core_ImpersonateUser under Help > API Reference

ohilton

Member

Registered: 2013-10-04

Posts: 12

Re: Missing metadata fields in Search.GetSearchConfiguration

Thanks Steve