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
 
← Back to post

Revisions 2

4 years ago
It would be nice if the SubscriptionEvent model contained more information about the order. One item we'd like to be able to access is the order `price/amount`, which should go into the object below contained in the subscription event payload. If these items are already included e.g. in `items`, could you possibly share the full subscription event payload with missing items filled in? ``` 'order': { 'editionCode': 'RECURRING', 'addonOfferingCode': '', 'pricingDuration': 'MONTHLY', 'freeTrial': { 'active': False }, 'items': [], 'customAttributes': [] }, ``` There are also other questions like: * Is SubscriptionEvent triggered on a renewal? * If so, does it maintain the same `subscription_id` and how would we track payments on renewals? Is there a separate child object to track renewal activity on a unique subscription? Thanks!
It would be nice if the SubscriptionEvent model contained more information about the order. One item we'd like to be able to access is the order `price/amount`, which should go into the object below contained in the subscription event payload. If these items are already included e.g. in `items`, could you possibly share the full subscription event payload with missing items filled in? ``` 'order': { 'editionCode': 'RECURRING', 'addonOfferingCode': '', 'pricingDuration': 'MONTHLY', 'freeTrial': { 'active': False }, 'items': [], 'customAttributes': [] }, ``` Thanks!
Subscription Event Needs More Order Information

It would be nice if the SubscriptionEvent model contained more information about the order. One item we'd like to be able to access is the order `price/amount`, which should go into the object below contained in the subscription event payload. If these items are already included e.g. in `items`, could you possibly share the full subscription event payload with missing items filled in? ``` 'order': { 'editionCode': 'RECURRING', 'addonOfferingCode': '', 'pricingDuration': 'MONTHLY', 'freeTrial': { 'active': False }, 'items': [], 'customAttributes': [] }, ``` Thanks!
#marketplace