Hello yuri + the rest of the Espo team.
I'm looking for some advice.
I have a patch that exports via Excel rather than CSV. It works really well, different field types are supported, correctly formatting the columns, combining id + name pairs into links back to the espo url. Uses the translated labels rather than field names.

I also added the concept of 'default export field lists' for users as a configurable layout in the Admin section. This is a separate commit.

I would be really happy for it to be included in Espo (one less separate commit to refactor every few months). However since I wrote this patch you introduced the Custom Field List modal dialog in both core + the Advanced pack.
In my patch I reduced a lot of the duplicate code between Core + Advanced pack as well as refactored the Core/Services/Record class to perform all the Excel formatting for both Core + Reports.
I've started refactoring this against latest Espo - but I wonder if it's worth the effort? Would you consider adding it? The current exports are not great to look at, and everyone here is really happy with them. I think Espo users might appreciate this.
The question would be how to handle the Custom Field List modal - whether to expand it ? Auto populate the Custom Field list from the 'layout'. Users could choose what is default mode - the rich Excel version or CSV. PHPExcel also supports OpenOffice which could be configurable.
I'm happy to do the work getting it suitable for core - but need guidance on how you'd see it working.
thanks.
Alasdair
I'm looking for some advice.
I have a patch that exports via Excel rather than CSV. It works really well, different field types are supported, correctly formatting the columns, combining id + name pairs into links back to the espo url. Uses the translated labels rather than field names.
I also added the concept of 'default export field lists' for users as a configurable layout in the Admin section. This is a separate commit.
I would be really happy for it to be included in Espo (one less separate commit to refactor every few months). However since I wrote this patch you introduced the Custom Field List modal dialog in both core + the Advanced pack.
In my patch I reduced a lot of the duplicate code between Core + Advanced pack as well as refactored the Core/Services/Record class to perform all the Excel formatting for both Core + Reports.
I've started refactoring this against latest Espo - but I wonder if it's worth the effort? Would you consider adding it? The current exports are not great to look at, and everyone here is really happy with them. I think Espo users might appreciate this.
The question would be how to handle the Custom Field List modal - whether to expand it ? Auto populate the Custom Field list from the 'layout'. Users could choose what is default mode - the rich Excel version or CSV. PHPExcel also supports OpenOffice which could be configurable.
I'm happy to do the work getting it suitable for core - but need guidance on how you'd see it working.
thanks.
Alasdair
Comment