How can we use route parameters with Filament panels?

[myregistration]

Package

Panel builder

Package Version

v3

How can we help you?

I need to set a route slug parameter to use a particular model instance with the panel panel. For example, /organization/{organization:slug}/. How can we modify Filament routes to include parameters? Thanks

[leandrocfe]

I think you should override the route in you web.php file

[myregistration]

I tried that but getting some weird side effects, like it's showing the wrong panel (I have multiple), it's redirecting to the default panel.

[myregistration]

Do you know how to override the Filament routes? I don't think it's straightforward. Thanks!

[danieledelgiudice]

Not sure if you've already tried it, but I had a similar requirement and after trying different things (clusters, nested resources, etc.), I actually solved it using Multi-tenancy.

When you specify that a Panel has a tenant model (in your case, I would choose the Organization model), you effectively give it a parameter. You can then access models scoped by relationships with the current tenant via global scopes and/or by accessing the current tenant with Filament::getTenant().

The documentation on that page is very thorough and covers several use cases, and you can customize your setup a bit (e.g., I chose not to have registration/profile pages).

Let us know how it goes!

[myregistration]

I'll give it a try. I was worried about using something built-in that wasn't intended for it in case there are side effects with future updates. I wish there was a better solution that followed Laravel basics. I'll let you know if it works. Thanks

[myregistration]

Multi-tenancy didn't work for my needs. Any other way to add a slug to the Panel's path? Maybe using Middleware? Thanks!

[bilogic]

I don't know if this works, but this is what I would try:

$panel has a ->path(...), what happens when you put ->path('/organization/{path}')?

However, I suspect it will also require a view composer to resolve {path} in which multi-tenancy is used to determine which tenant (organization) should be applied.

[myregistration]

Thanks, I had tried that initially. Would have made my life a lot easier if we could just model bind like that. I can't use multi-tenancy because I am using a one-to-many, not many-to-many relationship. My users can be a member of multiple organizations, but they have a member record per each organization, so don't need belongsToMany relationship. I hope that makes sense. Starting to regret using Filament, but I've invested too much time at this point. Hopefully there is a solution. I'm considering using domains, but I don't really like that option either. My current workaround is to append the organization's uuid to the URL, but that sucks, too. Let me know if you can think of anything else. Thanks!

[bilogic]

Your OP seeks a solution, but I can't quite grasp the problem (on why multi-tenancy doesn't fit), it might be more fruitful to give context of the business problem you are trying to solve without using terms like belongsToMany etc, because they already imply a solution. Speaking rhetorically, if it is pointing to a solution, why doesn't it fit?

Another idea: if what you want is same panel A for different organizations, then it would be copying filament's web.php and wrapping a group around it, i.e. in the form of /{tenant}/panel-A-id

[myregistration]

I was able to get multi-tenancy working by creating a pivot table for organization_user. I was avoiding it because I didn't really need it since I have a one-to-many table that stores a user's member record per organization, but that's the only way I could get tenancy to work. It seems like Filament requires a many-to-many relationship for the multi-tenancy. I'm using the member model's saved lifecycle event to update the pivot table, so it is low maintenance. Thanks for your help!