Auto-complete Association Field & Controlling the Query

Hey @fvquicke

Thank you for sharing your problem and solution!

Hey @Naim!

This is... always trickier than it should be! Yes, the first part of the answer is using form events. But the second answer is "how do I make an Ajax call to "submit" the category data and re-render the "sub-category" field. As far as I know, EasyAdmin doesn't supply anything for that second part - https://github.com/EasyCorp/EasyAdminBundle/issues/4716

Personally (though I have not done this yet), I would solve this by:

A) First setting up the form events as needed to change the sub-category options/query based on the category field. Form events are tricky, but this is well-documented. You can test that this is working by selecting the category field and submitting your form. When the page re-renders (with validation errors), if you've done your job correctly, the sub-category field will have the correct options.

B) For the 2nd part (the Ajax call), I would LOVE to use LiveComponents for this... it would be super easy... except I think it will be difficult, currently, to build the identical "form" inside of your component class that you have in your crud controller. It'd be great to make that easier in the future. Without that option, I think you'll need to write a little bit of custom JavaScript that, on change of your category field, submits the form via Ajax. When you get back the HTML response, you would find the sub-category field in that new HTML and replace the sub-category on the page with it. It's some pretty boring work to make it happen, but it shouldn't be too bad.

Let me know how it goes - it'd be great to make this easier for everyone using EasyAdmin in the future - the solution I'm giving you doesn't excite me :).

Cheers!

Hey Dmitry,

Well, that's not configurable, unfortunately, but you can override that autocomplete method in the CRUD controller to which it sends AJAX requests and do there whatever you want.

I hope this helps!

Cheers!

Hey @Klaus-M!

Hmm. Ok, so if I understand correctly, when editing a single runSheets entity, you would like to show a "collection" of sub-forms for each related runSheetStations where each sub-form shows the done and memo field. Is that correct?

If so, the solution should be to use the CollectionField - https://symfony.com/doc/4.x/EasyAdminBundle/fields/CollectionField.html - for the runSheetStations property on runSheets (I'm assuming that your runSheets entity has a runSheetsStations property which is a OneToMany to the runSheetStations entity). That... should be all you need to do (though, this stuff is complex enough that I would NOT be surprised if I'm forgetting a detail). The CollectionField stuff can get really complex... but that's mostly if you need to be able to dynamically add new relations... but it doesn't sound like you even have that case: you just want the user to be able to modify some fields on the existing, related runSheetStations.

Let me know if that helps :). Cheers!

Hey suabahasa,

Good question! Though it's not that much important fairly speaking, but I'll try to explain you some details. Just functions are bind to the instance context, i.e. you can use $this inside those functions, i.e. they are bind to the *objects* of classes where you use them. When static functions are bind to the class, i.e. they do not have access to the $this variable inside of them. And so, they are mostly like static and regular methods on its behaviour, and also has similar performance. If you're not going to use $this inside those functions - it's recommend to make them static that will have a better performance, but that is minor and difficult to be noticed anyway, but depends on your project code complexity. So, it's mostly like a "hipster" question, use static when you could to be more hipster :p ;)

I hope it's clearer for you now.

Cheers!

Hi Victor,

thank you for detailed answer.
Before, I curious if there is some special use case/best-practice of using the "static" for this chapter, but now I got the answer.

Cheers!

Hey Suabahasa,

Awesome, glad to help! :)

Cheers!

Hey Peter,

Ah, I see your problem. Yeah, that's a tricky case. You're on the correct way, you would need to use a custom query builder to filter that out. How to get the current Employee ID? Take it from the URL. If you look closer at the URL - you will notice that the current employee ID is written there as "entityId". So, inject RequestStack into your controller, get the current Request object from it and get the "entityId" from the query. Then, just use it in the query builder to filter it out.

Or, probably even better, you can leverage EasyAdmin getContext() to get the current Request object, i.e. call "$this->getContext()->getRequest()". Btw, you can even try to get the current entity object as "$this->getContext()->getEntity()->getInstance()", but it might be overkill in case you just need its ID - you just can fetch it from the URL query parameter.

I hope this helps!

Cheers!

nice..Thanks

Hey Tomáš S.!

Excellent question! It is not, unfortunately. The technical reason is that, in addition to querying for all the items to list them, iirc, the QueryBuilder is also used when an item is submitted to figure out if the submitted item is a "valid" item. For example, it would take your QueryBuilder (which may already have some WHERE on it) and (again, I'm going off memory here, but I believe this is how it works) add a AND id = 12 where 12 is the id of the submitted item. If the system allowed you to only pass it the findBy(), then even for just checking the validity of the submitted item, it would need to use your method to query for ALL of the items... just to check if the submitted one is in there.

Anyways, the "best answer" I can give you is this: if you already have an existing, custom findByABC() method in your repository, and you'd like to re-use that logic, then isolate your custom QueryBuilder logic into some createFindByABCQueryBuilder(QueryBuilder $qb = null): QueryBuilder method. Then, call this from your custom findByABC() method and when working with this field.

I hope that helps :).

Cheers!

Thank you.

I am absolutely beginner of Symfony and EasyAdminBundle. It would be nice to reuse the code, but it is not important at the moment for me.

Best regards

Hey Debasish N.

Could you elaborate a bit more? I don't quite understand what you mean by "dependent select"

Cheers!

Thanks, @Diego Aguiar
I have Category and Subcategory entities. Now on the product creation
page, I need to select category and subcategory. When I select a
category then I want to show the subcategories which belong to the
selected category. How can I do that in easy admin?

Hey Debasish,

Unfortunately, that's not available our of the box. I suppose you can create a custom EasyAdmin filter in this case, and with some AJAX requests it's doable. I'm not sure if you can reuse the exist EasyAdmin filter for the root categories, it still might be tricky, so you may need to implement your custom filter for both root categories and subcategories. Unfortunately, we do. not cover such a complex case in this tutorial, but I think it's possible to do in theory with some custom JS code.

I hope this helps!

Cheers!