Multiple conditions for a fixture

Becario · May 26, 2026, 5:27pm

I’m using ERPNext v16.

I would like to include all the Print Formats which contain “AST” or end in “ (test)” as part of my fixtures in hooks.py. I can’t work out the correct format to do this however.

At first I tried including the two conditions as separate lines:

fixtures = [
    {"dt": "Print Format", "filters": {"name": ["like", "%AST%"]}},
    {"dt": "Print Format", "filters": {"name": ["like", "% (test)"]}},
]

But this only included the formats which ended in “ (test)”.

I saw somewhere suggest that in can take multiple parameters:

fixtures = [
    {"dt": "Print Format", "filters": {"name": ["in", ("%AST%", "% (test)")]}},
]

But that included nothing so mustn’t be correct.

AI suggested using regex:

fixtures = [
    {"dt": "Print Format", "filters": {"name": ["regex", r".*\bAST\b.*|.+ \(test\)$"]}},
]

But various combinations of escaping backlashes or character sets:

fixtures = [
    {"dt": "Print Format", "filters": {"name": ["regex", ".*[[:<:]]AST[[:>:]].*|.+ [(]test[)]$"]}},
]

All resulted in a MySQLdb.ProgrammingError:

(1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'REGEX '.*\\\\bAST\\\\b.*|.+ \\\\(test\\\\)%' ORDER BY `idx` ASC,`creation` ASC' at line 1")

(1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'REGEX '.*[[:<:]]AST[[:>:]].*|.+ [(]test[)]$' ORDER BY `idx` ASC,`creation` ASC' at line 1")

I think it may be a hallucination about Frappe supporting regex as an operator at all. I certainly couldn’t find the code that would construct the query.

AI nonsense aside, how do you have multiple conditions for a fixture joined by an OR rather than an AND?

Becario · May 27, 2026, 3:20pm

No further forward with a solution, but I have learnt some things on the way.

in obviously takes multiple parameters, but all as fixed strings. There is no wildcard matching using %.

Looks like the AI was correct in that Frappe does support regex as a filter operator, just not in a way that it must ever have worked:

There is no special handling needed in DatabaseQuery#prepare_filter_condition so there is no mention of regex there.
Engine#_apply_filter is where the filters are added to an SQL query. It is here invalid/unknown operators are rejected.
That searches the operator map
From the map func_regex is returned for regex
func_regex calls PyPika’s Field#regex which is where REGEX comes from in the final SQL

For filtering with a regex, MySQL and MariaDB both use RLIKE or REGEXP, and PostgreSQL uses ~. I don’t know which database uses REGEX. This much looks like a Frappe bug.