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
 
Answered
Is User ID not sufficient for the unique customer identifier when using the aggregator?

In the aggregator docs it says I'll need:

A unique customer identifier (token) that will be inserted into the Q2 DB enrolls/signs up/engages with your integration inside their digital banking session

I'm curious if self.online_user.user_id is sufficient to use as key value in here or whats the reasoning behind generating a uuid? Can the same user id exist in multiple different FI's?

await rlu.add_update(customer_id=None, user_id=self.online_user.user_id, key_name=‘abc_inc_account_integration’, key_value=uuid)

With that being said, is there any reason to store that value on our end if we can always do the reverse lookup?

Posted 3 years ago
Votes Newest

Answers


Hi Draden,

The purpose of generating a uuid is to have a unique identifier for each user across all FIs in your system that can also be used to identify users in Q2. User IDs are typically replicated across multiple financial institutions. If you currently have a way of uniquely identifying your users, that can be used as the token.

-Solène

Posted 3 years ago
119 Views
1 Answer
3 years ago
3 years ago