使用 Talend Job 在 excel 中添加数据透视表的最佳方法是什么？

Question

I am developing a Talend Automation Job ,
where I need to fetch my data in a " data " sheet in Excel.
And then add a summary using Pivot table in excel in a separate sheet " Segment_Summary "
in same excel workbook. (using Excel 2016)
Then send it in tsendMail to clients as attachment.

Can you tell me a better way than what I did as explained below?

So, here is what I tried doing:

I created a sample Workbook with " data " sheet .
Selected cells of " data " sheet and created a named range for them.
Then added a pivot table on that named range in new sheet " Segment_Summary ".
Also set my Pivot Settings to Automatically Refresh whenever File gets opened.
Inside Talend , I fetch my data into a new excel file using tFileOutputExcel .
Copy Segment_Summary sheet from my Sample Workbook into this new excel file using tFileCopy .
Using tsendMail sent the excel as attachment

What happened to the output :

Executed my job,
checked the new Excel created.
Its good, pivot is automatically refreshed to new data .

So what goes wrong here:

When I download the file from mail and then open it, pivot is not refreshed. This is because by default MS Excel opens every file in Protected Mode and disables Editing. So, when clients will open this file, they will see outdated data instead of refreshed one.

(I cannot simply write in mail that open it in editing mode, as this has to be sent to many people..and my email template is word-to-word decided by sales.)

Answer 1

doesn't tFileCopy copy files? How are you using this to copy a single sheet from an Excel file?

Given that Talend doesn't "understand" Excel - only data and files - the only approach I can think of that might work is to have your target Excel file already containing the pivot table and then use Talend to update the sheet in that target file that contains the raw data.

I'd probably create a template Excel file with example data and a pivot table and then in each run create a copy of this file and update the copy.

Given that the size of the raw data is likely to change from run to run, you're probably also going to have issues with the named range that the pivot table is using - assuming the named range is fixed. Having a dynamic named range may be needed, this link explains how to implement this, if you need to know: Dynamic Named Range