When you use Excel Data Only Output Format in Epicor it will create a temporary .rdl file so SSRS knows what to use, you may end up with 100s if you keep using that option.
What is everyone else doing to clean those up? Epicor doesn’t seem to clean them up in 10.1.500 atleast.
For me the first one is ReportName_ExcelDataOnly, if i click the Excel Data multiple times the rest become ExcelDataOnly_########.
For example if I Preview “ARForm” in Excel Data Output 5x I get
ARForm_ExcelDataOnly
ExcelDataOnly_#######
ExcelDataOnly_#######
ExcelDataOnly_#######
ExcelDataOnly_#######
Which is fine, I just don’t know if Epicor Task Agent was, is supposed to clean those up after it has presented the Report to the User Judging by some responses, I am not the only one.
Now I assume a Scheduled Windows Task to run rs.exe and prune those is the solution.
I wonder if that only happens on preview. Also not sure if built-in reports (like OrderAck) are different from BAQ Reports.
I have a BAQ report that is scheduled to run daily, with type = “Excel Data Only”, but with an output of email (clicked email tool and setup the email params). And I’m not seeing these.
I wrote this functionality something like a decade ago. Let’s see if I can demystify some of it. This is from memory so don’t shoot me if I get something wrong…
Crystal Reports had something like this built in. SSRS did not so my boss told to make something similar. This involves parsing the SSRS RDLs files and pretty much rewriting them. Basically, figuring out the exact coordinates of each control and determining the columns the data will end up in in Excel.
Since this is somewhat expensive to do, we generate the “ExcelDataOnly” versions of the RDL when they are first used. It doesn’t whether you are printing or previewing. As long as you render the report, the ExcelDataOnly RDLs will be generated.
If you never change the RDLs they are based on, then the extra ExcelDataOnly RDLs will just be reused. There should be one for the main report with “_ExcelDataOnly” added to the end of the file name. There should be an “ExcelDataOnly_###” for each sub-report that is used in the main report or any of the sub-reports.
There is nothing to “clean” these up. The “extra” RDL files would only be created for reports that you use ExcelDataOnly formatting on. The assumption is that if you used it once, you will probably use it again. If you stop using it, then the extra couple RDLs aren’t that big a deal.
You can delete the ExcelDataOnly RDLs if you wish. This shouldn’t cause any trouble. They will just be regenerated if you ever use ExcelDataOnly again.
So here’s the question. Are you seeing more ExcelDataOnly RDL files than you would expect given the above explanation? You should have one for the main report and one for each sub-report. I think the confusion might be about the sub-report having their own RDLs.
In that case it is not a problem. You are right. I saw like 21 of them recently in the Job Traveler folder and immediately thought “that sucks that it regens a fake .rdl everytime”. I just re-tested it and its as you described it. The only time it generates more fake .rdl’s is when you switch to a new Report Style, but it only does that 1x and re-uses them.
HI Guys,
Sorry for digging up this old thread. For some reason, one of the reports prints fine if PDF is selected ut gives erranous alignment and omits label header when Excel Data only is selected.
I made some changes to the original pdf rdl (custom report) of the test environment but since have reverted the original old rdl from live system but for some reason excel output does not still correct itself.
It prints fine in the live system and that’s the reason I brought the rdl file from live back to test so that it would null and void any changes I made to the test environment rdl. But Excel Output still does not go back as in Live.
Any help please?