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
Storing Custom Form Data in DB

I am working on a form for members to use to request that their data be deleted. In that form, I want to capture the reason they are making the request from a pre-defined list of reasons in a dropdown. I'd like to store those reasons in the Q2 DB rather than hard coding in the extension. What would be the appropriate table to store those items? My thought is that it would be easier to maintain if we ever wanted to remove/ add reasons.

Posted 2 years ago
Votes Newest

Answers


Hello,

In terms of the list of questions, I would recommend that be stored in the wedge address configs. The form then could be built off that list of questions in the wedge address configs any you could change those when you desire. It would also be easy to test and show off in the sandbox, Staging, and Production through the self service wedge address config changes.

-Trey

Posted 2 years ago
Trey Teter
489 × 4 Administrator
114 Views
1 Answer
2 years ago
2 years ago