Filter Conditions fails cause of database prefix

I’m using this query in config_filter as a condition:

conditions: id in (select id from records where player_id in (select id from players where playername = :value ))

The tablenames are not the real ones in case you wonder.

Now I face the following problem: On different deployments, the tablenames vary due do different random table prefixes. Obviously, those prefixes are not included if there’re hardcoded tablenames.

Now I wonder if there’s a quick way to still find the proper table or if I have to change all those conditions to scopes.

In this case where the table name changes according to the environment, I think it will be easier to create scope.

1 Like