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 3

Original
Ryan Hollister
196 × 4 Administrator
Definition of fields for GetAccountHistory
Definition of fields for GetAccountHistory
Quick rundown of the fields: "AllTransactionType": indicates type of transaction (0 = Posted, 1 = Memo, 2 = Insufficient Funds "TransactionID": Q2 ID for this transaction (unique per FI) "HostAccountID": Q2 ID for this account (unique per FI) "PostDate": date transaction posted on the core. "TxnAmount": unsigned amount of transaction "Description": description of the transaction from the core "HostTranNumber": Core ID for this transaction (not guaranteed to be unique) "DorC": Debit or Credit "ShowImage": has an associated image "HostTranCodeID": Code/Category ID of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "HostTranCode": Code/Category of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "OfxTrnType": OFX Is a ISO specification for data exchange (basically just an XML format) https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf TranType values are defined in section 11.4.4.3 "OfxCheckNumHandling": //0=drop check num //1=change transaction type to CHECK //2=move check number to description append REF# //3=move check number to description prepend REF# "ShowTransactionItemDetail": has associated transaction sub-items., "SignedTxnAmount": signed amount of transaction "StatementDescription": description that will show up on the statement.
Quick rundown of the fields: ``` "AllTransactionType": indicates type of transaction (0 = Posted, 1 = Memo, 2 = Insufficient Funds "TransactionID": Q2 ID for this transaction (unique per FI) "HostAccountID": Q2 ID for this account (unique per FI) "PostDate": date transaction posted on the core. "TxnAmount": unsigned amount of transaction "Description": description of the transaction from the core "HostTranNumber": Core ID for this transaction (not guaranteed to be unique) "DorC": Debit or Credit "ShowImage": has an associated image "HostTranCodeID": Code/Category ID of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "HostTranCode": Code/Category of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "OfxTrnType": OFX Is a ISO specification for data exchange (basically just an XML format) [https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf](https://financialdataexchange.org/common/Uploaded%2520files/OFX%2520files/OFX%2520Banking%2520Specification%2520v2.3.pdf) TranType values are defined in section 11.4.4.3 "OfxCheckNumHandling": //0=drop check num //1=change transaction type to CHECK //2=move check number to description append REF# //3=move check number to description prepend REF# "ShowTransactionItemDetail": has associated transaction sub-items., "SignedTxnAmount": signed amount of transaction "StatementDescription": description that will show up on the statement. ```
4 years ago
Ryan Hollister
196 × 4 Administrator
Quick rundown of the fields: ``` "AllTransactionType": indicates type of transaction (0 = Posted, 1 = Memo, 2 = Insufficient Funds "TransactionID": Q2 ID for this transaction (unique per FI) "HostAccountID": Q2 ID for this account (unique per FI) "PostDate": date transaction posted on the core. "TxnAmount": unsigned amount of transaction "Description": description of the transaction from the core "HostTranNumber": Core ID for this transaction (not guaranteed to be unique) "DorC": Debit or Credit "ShowImage": has an associated image "HostTranCodeID": Code/Category ID of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "HostTranCode": Code/Category of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "OfxTrnType": OFX Is a ISO specification for data exchange (basically just an XML format) [https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf](https://financialdataexchange.org/common/Uploaded%2520files/OFX%2520files/OFX%2520Banking%2520Specification%2520v2.3.pdf) TranType values are defined in section 11.4.4.3 "OfxCheckNumHandling": //0=drop check num //1=change transaction type to CHECK //2=move check number to description append REF# //3=move check number to description prepend REF# "ShowTransactionItemDetail": has associated transaction sub-items., "SignedTxnAmount": signed amount of transaction "StatementDescription": description that will show up on the statement. ```
Quick rundown of the fields: ``` "AllTransactionType": indicates type of transaction (0 = Posted, 1 = Memo, 2 = Insufficient Funds "TransactionID": Q2 ID for this transaction (unique per FI) "HostAccountID": Q2 ID for this account (unique per FI) "PostDate": date transaction posted on the core. "TxnAmount": unsigned amount of transaction "Description": description of the transaction from the core "HostTranNumber": Core ID for this transaction (not guaranteed to be unique) "DorC": Debit or Credit "ShowImage": has an associated image "HostTranCodeID": Code/Category ID of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "HostTranCode": Code/Category of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "OfxTrnType": OFX Is a ISO specification for data exchange (basically just a defined XML format) https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf TranType values are defined in section 11.4.4.3 "OfxCheckNumHandling": //0=drop check num //1=change transaction type to CHECK //2=move check number to description append REF# //3=move check number to description prepend REF# "ShowTransactionItemDetail": has associated transaction sub-items., "SignedTxnAmount": signed amount of transaction "StatementDescription": description that will show up on the statement. ```
4 years ago
Ryan Hollister
196 × 4 Administrator
Definition of fields for GetAccountHistory

Quick rundown of the fields: ``` "AllTransactionType": indicates type of transaction (0 = Posted, 1 = Memo, 2 = Insufficient Funds "TransactionID": Q2 ID for this transaction (unique per FI) "HostAccountID": Q2 ID for this account (unique per FI) "PostDate": date transaction posted on the core. "TxnAmount": unsigned amount of transaction "Description": description of the transaction from the core "HostTranNumber": Core ID for this transaction (not guaranteed to be unique) "DorC": Debit or Credit "ShowImage": has an associated image "HostTranCodeID": Code/Category ID of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "HostTranCode": Code/Category of the transaction from the core. Not owned by Q2, list of Codes available in Q2_HostTranCode table "OfxTrnType": OFX Is a ISO specification for data exchange (basically just a defined XML format) https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf TranType values are defined in section 11.4.4.3 "OfxCheckNumHandling": //0=drop check num //1=change transaction type to CHECK //2=move check number to description append REF# //3=move check number to description prepend REF# "ShowTransactionItemDetail": has associated transaction sub-items., "SignedTxnAmount": signed amount of transaction "StatementDescription": description that will show up on the statement. ```