Hi @Andrea Boriero,

I encountered this situation also but my use case is a bit different. I have only one FilterDef in my project, but for an audited entity. When the audited entity is generated a filter def with the same name is generated and therefore I encounter the same issue with: Multiple '@FilterDef' annotations define a filter named.

Is it known and intended behaviour?

Thank you in advance 🙂