Can you help with an example of "predictAccount" #49
-
|
👋 @ananthakumaran. 🙏 for the 🏆 tool! Can you provide some examples of the I am unable to understand the references to |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Think of predictAccount as doing a search & ranking the results, so it's going to search across all your existing transactions. Now you need to provide the query to match which is called as corpus in the doc (I think it's not a great name, I will update with a better one soon). The match will be performed against the description of the transaction (and amount) predictAccount(salary) would likely match the first transaction and use the account from that. Normally, you pass the same value you used in the description |
Beta Was this translation helpful? Give feedback.
-
|
🙇 thanks for the quick revert. Please confirm if I am understanding this correctly.
For a past Salary transactions that looks like the below... For any subsequent Salary transaction imported from the bank statement, Is that correct?! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, correct
…On Mon, 25 Sep, 2023, 10:55 pm Mohan Sridharan, ***@***.***> wrote:
🙇 thanks for the quick revert.
Please confirm if I am understanding this correctly.
predictAccount is meant to search previous transactions (treats as the
corpus) and automatically assign the balancing account based on those
past occurrences.
For a past Salary transactions that looks like the below...
2023/07/28 - My Salary
Assets:Checking:Axis1234 100 INR
Income:NEFT/CITIN23413141026/GREAT EMPLOYER/SALARY T -100 INR
For any subsequent Salary transaction imported from the bank statement,
predictAccount would automatically populate the value of
"Checking:Axis1234"
2023/08/28 -
Assets:Checking:Axis1234 100 INR
Income:NEFT/CITIN23413141026/GREAT EMPLOYER/SALARY T -100 INR
Is that correct?!
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABEN5R34S4AQ2BMPK34EW3X4G5CHANCNFSM6AAAAAA5GMXHWE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Think of predictAccount as doing a search & ranking the results, so it's going to search across all your existing transactions. Now you need to provide the query to match which is called as corpus in the doc (I think it's not a great name, I will update with a better one soon). The match will be performed against the description of the transaction (and amount)
predictAccount(salary) would likely match the first transaction and use the account from that. Normally, you pass the same value you used in the description