Custom Import & Export Table used by Prebuilt Actions
In our application, we have already have an import and export table.
This causes issues when we want to use the Filament Prebuilt Import/Export Actions.
Does anyone know of a way to customise what table Filament uses for this ? I looked through the code and it appears pretty hardcoded and I was thinking of submitting a PR for v4 to make them them configurable but I don't know it would be accepted or wanted.
Does anyone know of a way to customise what table Filament uses for this ? I looked through the code and it appears pretty hardcoded and I was thinking of submitting a PR for v4 to make them them configurable but I don't know it would be accepted or wanted.
3 Replies
To see the PR would be wanted post on the git hub page and tag Dan from the filament team…
https://filamentphp.com/docs/3.x/support/contributing#development-of-new-features
personally I think you can just build you own action to use the custom tables so doesn’t seem like a big deal ?
Possiblilty, but it seems like at alot of effort and code when the only thing that is stopping use using the prebuilt actions that have a number of features like column matching, is a silly little old table name.
I've thrown it on GH and will see what happens https://github.com/filamentphp/filament/discussions/16288
GitHub
Making the import and export table names configurable · filamentph...
I love Filament and we are integrating it with our existing application currently. One problem we are finding is that we can't use the prebuilt import and export actions. We currently have data...