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
SymXchange conversion - read message from the core

In some of our SDK forms, we were reading the message from the core to determine if Symitar was in memo mode using the "status_message" of the query result of the Symitar/Symconnect build_base_query

When switching over to the SymXchange core, we can't easily find how to replicate this. When testing with Symitar in memo mode, execution of the query just throws an error "Unknown Symitar message type received". Is there a property/method to read the actual message back from the core in the same fashion as "status_message" from the Symitar core?

Posted 2 years ago
0

Hey Todd,

Good question. The SymXchange Python core is written to parse out both the status_message and status_code into known properties. The status_code is going to be the same codes you see in eDocs under Symconnect/SymXchange error codes.

It sounds like the adapter though is not returning the actual shape back to us. Let me do some research on this scenario. Would you happen to have a time frame or maybe the SDK log I could pull the session id from?

— Jason Herbert   2 years ago
0

@<1327001115966836736|Todd Barrow> If you want to open a case with those details I'll grab it.

— Jason Herbert   2 years ago
Votes Newest

Answers

138 Views
0 Answers
2 years ago
2 years ago