Pre-defined search via Filter or separate CRUD

[Schyzophrenic]

Running EA 3.1.3

I originally had separate CRUD related to the same entity. Nonetheless, it seems the Autocomplete of the Association field take into account a random (I am sure there is a logic but I didn't check) CRUD for the searchField to apply. I then assume the searchField should always be the same? It seems odd to have separate controllers, to be able to call them separately in the Dashboard but they then get mixed up later on.

Considering things were getting mixed up, I looked at implementing Filters instead. Is there a way to use predefined searches (via Query Builder for instance)?
I don't need forms, just a predefined search. It seems the Filters should be applied to specific fields so it may not fit my need.

As an example, let's imagine we have EntityCrudController with:
$id,
$name
$myLinkedEntity

I would like to display only when $name is null and $myLinkedEntity is null.
If we have a separate CRUD, we can just use a specific QueryBuilder, but then I run into the other issues I mentioned. I feel like I am missing something.

Thanks

[seb-jean]

This feature could be interesting.

[Schyzophrenic]

@seb-jean Happy to look into it but I'll need some pointers as I got no idea where to start or if we should try to properly allow multiple controllers per entity (which seems to be a bug as we have the set Controller method) or go on with the predefined filters, which could also be useful no matter what..

[lukasluecke]

Maybe #3551 could be a solution?

[Schyzophrenic]

It may work indeed @lukasluecke, I'll give it a try.
But isn't it a bit odd to have controllers not independent from one another?
Here it means I need to have my exceptional use case as the default and then modify the autocomplete wherever I need something standard.

[lukasluecke]

There is also an option on the AssocationField to configure the target CrudController FQCN I believe, maybe look into that as well if that's more closely aligned to your use case 🙂

[Schyzophrenic]

I missed this one! I guess I gotta spend more time looking at these options. Let me investigate and revert! Thanks Le sam. 25 juil. 2020 à 16:17, Lukas Lücke <notifications@github.com> a écrit :

…

There is also an option on the AssocationField to configure the target CrudController FQCN I believe, maybe look into that as well if that's more closely aligned to your use case 🙂 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI6XT4MZT3QQZSUUVQX5O3R5LZQRANCNFSM4PHDIZBA> .

[Schyzophrenic]

I am closing this issue as I can't reproduce the issue in an isolated way. Let me know if you guys want me to create a Feature Request for the pre-defined searches though (I still think it'd be useful instead of creating X CRUD Controllers), but it may be lower priority as we do have an easy workaround

[Schyzophrenic]

There is also an option on the AssocationField to configure the target CrudController FQCN I believe, maybe look into that as well if that's more closely aligned to your use case 🙂

This was actually the way to do it.
@lukasluecke I checked the doc but I can't find all these use cases explained. Is it something in the pipe or how could we enhance this?
This used to be covered by a symfonycast course for EA 2 but we don't have anything yet for EA3.