report.saveas project report command format

[pcaspa]

Re: report.saveas project report command format

Hi,

For anyone reading this who, like me, struggled to implement a5w_report_saveAs check out:-

http://msgboard.alphasoftware.com/al..._report_saveAs

Also my twist on the theme for a multi tenanted invoice system (comments welcome):-


Dim filename as c = "Invoice_"+e.datasubmitted.invoiceNumber +"("+e.datasubmitted.BizID+").pdf"
Dim filepath as c = a5_removetrailingbackslash(request.applicationRoot) +"\sbcsfiles\invoices"+chr(92)+filename

dim args as sql::Arguments
dim Options as p
dim printOptions as p
args.set("blank", "")
options.propogateErrors = .t.
printOptions.blank = ""
Dim reportname as c = a5_removetrailingbackslash(request.applicationRoot) +"\Invoice.a5rpt"
Dim saveAs as c = "PDF"
Dim filter as c = "INVID = "+val(e.datasubmitted.InvID)
Dim order as c = ""

fn = a5w_report_saveAs(reportName,saveAs,filter,order,filepath,global_variables(),printOptions,args,options)


if file.exists(fn)=.f. then

[Selwyn Rabins]

Re: report.saveas project report command format

report.saveas() is not safe to run in a background thread because you could run into threading issues if two requests try to load use the amyuni printer driver at the same time.

if you look at the system page __a5RunReport.a5w (which is automatically published to the webroot) you will see how Alpha Anywhere handles a request to print a report. you will see that it uses this command (line 470)

a5w_report_saveAs(reportName,saveAs,filter,order,filename,global_variables(),printOptions,args,options)


global variables in a web application are any variables dimmed as global in the current executing .a5w page.

for example

<%a5

dim g as global_variables()
g.myname = "peter"

'if you were to put code here to print a report the report could refer to 'myname'

%>

%>

[pcaspa]

Re: report.saveas project report command format

Hi,

Could someone please explain why using .report.saveas() is not safe to run in a background thread. I tried a5w_report_saveas() in place of report_saveas() and it could not find the report? Also what are the Global Variables referred to in the docs.

Any info or a direction on where to look for the answers would be greatly appreciated.

Cheers
Peter

[dionmccormick]

Re: report.saveas project report command format

Excellent point. Thanks for the info!

[DaveF]

Re: report.saveas project report command format

If this is a web application, you should be using a5w_report_saveas(). report.saveas() is not safe to run in a background thread on the WAS.

[dionmccormick]

Re: report.saveas project report command format

Thanks Selwyn!!! That worked perfectly for my need. Also, I love the request.GetRequestTempFileName(".pdf") function. Makes my code simpler and easier to manage!

Quick follow up question. The request.GetRequestTempFileName(".pdf") function sets up the temp file so it is deleted as soon as the request is completed. For my use case, this works great for the temporary files I create to combine into a single PDF. But, I would like to use that function and NOT have it delete it. The reason is that after I have generated the multiple temporary files, I combine them into a single PDF file. That PDF file must live beyond the current request because I do a "response.redirect" to open the combined PDF file in the web browser for user display.

Is there another similar function to request.GetRequestTempFileName(".pdf") that generates a temp file name, but allows it to live beyond the current request.....

[Selwyn Rabins]

Re: report.saveas project report command format

you need to give a fully qualified filename for the project report.

e.g. (assuming your project reports have been published to the webroot)

dim fn as c 
fn = request.GetRequestTempFileName(".pdf")
fn = report.SaveAs(request.applicationRoot + "customerReport.a5rpt","pdf","","",fn)

[omagarc]

Re: report.saveas project report command format

I'm getting a similar error in v11 3381 - 4096. Its complaining of extra characters in an expression???

[dionmccormick]

What is the proper command formatting to reference a project report with the new V12 system.

In my V11 system, I use the following command to generate a PDF version of a report in code.

filename = report.saveas("bs_period1_filtered", "pdf","guid = '" + session.cashflow.guid + "'","",filename1)

I have moved the report over to a project report with the same name. But, I get the following error:

Error:<br>Amyuni Low Level Print:<br>Layout name: bs_period1_filtered@ProjectReport<br>Layout type: report<br>Error loading Y:\Documents\Dropbox\Private\GKR\cashmax\CashMax Version 2\cashmax alpha project 2\ProjectReport: The system cannot find the file specified.
Y:\Documents\Dropbox\Private\GKR\cashmax\CashMax Version 2\cashmax alpha project 2\ProjectReport.DBF