Metadata Searches exclude access profiles, even when the rest of the search includes access profile results

I just finished the video by Tim Nimmo and I’m trying to understand what would happen in a campaign generated by the bulk campaign importer when metadata searches are included.

I’m not sure if this is a scenario where there’s a problem or if the metadata search capabilities just won’t work for mixed mode campaign generation.

This search returns requestable entitlements, access profiles and roles.
requestable:true
(In our environments, we have some of each, all properly returned)

This search returns any item which has ANY metadata.
@accessModelMetadata(value:*)
In our environment, we have only setup metadata on a few test entitlments.

I would expect the following search to return all requestable roles, access profiles and entitlements PLUS all items having any metadata.
requestable:true OR @accessModelMetadata(value:*)
…however, access profiles are missing from the results. Both requestable and metadata-assigned entitlements are included in the combined results.

So how could I launch a campaign which includes these two conditions?

You can try using it this way, removing the @:
accessModelMetadata.value:* OR requestable:true

@rmccoy-unum you can try to tag the requestable profiles and then use the queries( tags:“requestable” and try it once

We have too many items to use tags effectively. If tags could be applied broadly enough, we wouldn’t be looking at Metadata. I’m guessing you were able to repeat the search and demonstrate the undesirable result.

I’m just hoping that someone who reads this has the ability to act to correct this awkward behavior.

Hey wow! That worked. Nice find.

2 Likes

you can mark as solution if it worked thanks