Export Database Flexibility & Saved Configurations

The idea is:

Ability to have more flexibility with exporting. Some nice options would be:

  • Export as CSV (not xlsx)

  • Export the current view (ensuring hidden fields are not included) as well as filters (excluding certain rows) is honoured.

  • Save export configurations e.g. if we save an export configuration for standardisation like ‘export config - Service A’ → 'save as CSV, includes columns A, C, D and X + filter rules e.g. to exclude/include certain rows. Perhaps (nice to have - not critical) could even map column renaming to certain configurations e.g. if you want to use regular column names that are useful for internal reference inside Bika - but for exporting to use with other services, they need certain columns to have special compatible names. Basically like saving a view as an export configuration, with some additional options.

My use case:

The case is I need to export a csv in a certain configuration to upload for Wise/Transferwise batch payments for payroll. It needs to have specific columns and names. Currently, export will include hidden columns (I think probably filtered rows also - but not 100% certain) - making it not compatible unless I manually edit it after export. I want to use Bika to manage this sheet, handle updating all the values as needed conveniently and easily export it matching the required specifications of the third party service.

The minimum to cover this fairly conveniently would be if export would export the current view only and not include hidden columns (as well as excluding filtered records). The other suggestions would be nice to have QoL improvements though and add flexibility.

Hi @log , thanks for sharing your feature request! I’ve passed it along to our product and engineering team for review. Please keep an eye on your inbox — we’ll follow up with any updates via email. Appreciate your input! :raised_hands:

1 Like