Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Unanswered
← Is the Q2 Central API LookupUser operation response being limited?

Hey Eric,

Can you add a little more detail about what you are using? LookupUser, and the "Data" field you mentioned makes it seem like you are referring to Caliper API, and not Q2 Central. LookupUser in CaliperAPI does have a 10 user limit, and that is mostly because it is meant to be a very targeted call, and not used as a search function. But, if you are in an extension using Q2 Central, you should not have to call the CaliperAPI. Can you add a little more information about your code flow to confirm or clarify what you are seeing?

Thanks,
Paden Rose

Posted 3 years ago
Paden Rose
160 × 1 Administrator
0

Apologies - you are correct. I wrote the wrong 'C' word in my question. I meant the Caliper API. This limit is not called out in the documentation- I recommend it be added for clarity.
Is there a way to work around that limit? You mention it is there because it is meant to be a targeted call- I am targeting by a customer ID as I am wanting to receive a list of all the users of a customer. If that customer has more than 10 users, how will I retrieve them? There is no pagination for stringing multiple calls. The SearchUser = 1 response, so is there another option?

— Eric Lacey   3 years ago
17 Views
0 Answers
3 years ago
3 years ago