Version 6.11 and Scheduled Reports

I note that the release notes for 6.11 say:

All reports are now migrated to client-side generated Excel. The benefits are performance and localization.

How does this impact Scheduled Reports that are automatically Emailed?

It should not. Emailed reports were already emailed as the app links.

But it is still working to email reports as report.xlsx files using API and crone script on server side

for example

response=$(curl -X GET "$traccarUrl/reports/trips?${deviceIdsQuery}from=$startDate&to=$endDate&format=xlsx&mail=true" \
    -H "Authorization: Bearer $token" \
    -H "Accept: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet")

For now yes, the API is still there. But it will be removed eventually.

Hi Anton
Just wanted to confirm that the current API workaround still applies. Unfortunately, I'm not very excited about the change that forces scheduled reports to be in link only delivery mode since this is actually a legit use case for our company.
I work with fleet/logistics software used by a haul transport company, and all their processes are based on getting an actual xlsx file attached to the email and not on getting a link to the report. They download and redistribute those reports to other systems and archive them offline; sometimes the corporate network environment doesn't allow using links to external applications at all. Link-based approach is not what they need.

Do you know if it's possible to somehow configure Scheduled Reports to attach the generated xlsx file to the email? Or, at least, will server-side report generation and possibility to send file attachments from email be deprecated at all?

Thank you

Would exporting CSV format for your use case?

CSV at least gives a real file not just a link though it won't fully cover our case (client needs proper Excel formatting, not raw CSV).

Is xlsx as attachment possible at all? And if not how would we enable CSV attachments for Scheduled Reports?

Thanks

That's not something that's available currently. I'm just brainstorming ideas. Generating Excel on the server has a lot of issues. That's why we're trying to get away from it.