Replies: 1 comment 2 replies
-
I see you have multiple spaces in your transaction descriptions, but you use only single spaces in your search queries.
Multiple spaces between PTMO. and 123456 And in your query:
A single space. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Support guidelines
I've found a bug and checked that ...
Description
I am trying to create a rule for a recurrent transactions that contains a number on the description.
The description is always the same, it is
/TXT/D|LIQUID. CUOTA PTMO. 123456
When I try to search by the full description (
description_is:"/TXT/D|LIQUID. CUOTA PTMO. 123456"
) the transaction is not found.I have tried with "description contains" (
description_contains:"/TXT/D|LIQUID. CUOTA PTMO. 123456"
), and it doesn't work neither.Finally I have found a way to it, splitting the query into two "Description contains" ->
description_contains:"/TXT/D|LIQUID. CUOTA PTMO."
description_contains:"123456"` It works, but I don't think it is the best way.Any idea way the other triggers don't work?
I assume it should be something related with some regex used to match the description
Debug information
Expected behaviour
I would expect that
description_is:"/TXT/D|LIQUID. CUOTA PTMO. 123456"
anddescription_contains:"/TXT/D|LIQUID. CUOTA PTMO. 123456"
find my transactionSteps to reproduce
1-. Be sure a transaction with description
/TXT/D|LIQUID. CUOTA PTMO. 123456
exists in your DB2-. Create a rule with a trigger:
description_is:"/TXT/D|LIQUID. CUOTA PTMO. 123456"
3-. Test the trigger
====================
1-. Be sure a transaction with description
/TXT/D|LIQUID. CUOTA PTMO. 123456
exists in your DB2-. Create a rule with a trigger:
description_contains:"/TXT/D|LIQUID. CUOTA PTMO. 123456"
3-. Test the trigger
Additional info
No response
Beta Was this translation helpful? Give feedback.
All reactions