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
 
Profile picture
Chase Dorsey
Administrator
0 Questions, 2 Answers
Active since 30 April 2021
  Last activity 3 years ago

Reputation

0

Badges 1

  Editor
0 What is the relationship between these IDs in the marketplace subscription event?

All fields with the name uuid are generated by our marketplace vendor and will not correspond to anything in the Q2 platform.

sso_user_id is a guid that we generate in the marketplace to link an online banking user to an SSO user within our vendor's system, as well as the customer key for the FI environment that the event originated from (deliniated with a ':' ). The first piece will likely not be useful to you as a partner developer. The second can be useful to populate HQ credential...

3 years ago
0 How do I subscribe "retail0" user to my marketplace product in dev?

We currently do not have a way to run the purchase/subscription workflow in sandbox environments.

However, that should not prevent you from accessing your extension. It seems like you've encounted a bug in the library code. If you could submit a bug ticket through the developer portal, we would appreciate it.

As a temporary workaround, you can run the following command in your dev environment. This will disable all subscription checks in your sandbox.

`q2 db add_vendor_configs [ext...

3 years ago