Since I changed from Report Title to Region ID, you need to go through the Readme.pdf
a) delete one page item T_REPORT_NAME
b) create another one (T_REGION_ID)
c) and correct your link and your application process by replacing the old item name
with the new one.
Sorry, but as I said, the package is in development and no guarantees therefor.
The above mentioned error messages I received where due to the fact that I installed the package in another schema, created a public synonym and granted execute rights to PUBLIC.
When installing the package in the APEX parsing schema it works.
Is it possible to only install the package once and have it available to all APEX parsing schemas?
Another question. Are there any SQL restrictions in using your package. I'm having a rather complex SQL report, and this report generates the following error:
Report Header Error: ORA-01403: no data found / 100
I didn't test sharing the package with other schemas. I will do that. Normaly, if you grant
execute to any schema, it should be available there as well. However, I will test.
To your second question. The header error happens, when no SQL behind the report
can be found. This means that the package got the wrong input. I changed the
application names recently (posted in this thread), the application process and the
link for generating the excel file. Check the Readme.pdf once again and make sure
that you have the required items, process and the link as the new version of the package
Consider also the following:
If you are saying a complex report then I assume the same could also happen as for normal .csv export.
You probably have some items as binds for your report. I experienced
the same behaviour by not having a computation on some items and loading the
page report would show the header but no data. After computing
the items on load or submitting the report (submit button), the export was working.
The package is getting the SQL behind the report, replacing the :p_item variables with
v('p_item') and fetching the values. If the values are not assigned, the header will be
generated but no values will be fetched.
Hi, Denes, i've followed your instruction about exporting report to excel file under XE envronment, the problem is that now when i open the generated file i see an error in the first row before the columns headings. The error is
Report Values Error: ORA-06550: riga 12, colonna 12: PL/SQL: ORA-00942: tabella o vista inesistente
(table or view does not exists..) and also
PLS-00364: uso della variabile di indice ciclo 'C' non valido ORA-06550: riga 17, colonna 100: PL/SQL this error is repeated for many times and last
PLS-00364: uso della variabi / -6550 / select.......
The XE user is flows_020100 , the user that owns and runs the application is vsg so i granted him the execute on dbms_sql and the select on wwv_flow_page_plugs. Have i forgotten something else?
Hi Denes sorry but i've had problems with my adsl line.This is the query i use to obtain my report, it shows correct result in "video printing" and only after i've added the Download_excel feature i have the errors after clicking on download to excel button and opening "my_report.xls" file instead of saving it on my hd
"MOVIMENTI_CONTABILI"."IMPORTO"*decode ("MOVIMENTI_CONTABILI"."TC",0,1) entrate,
"MOVIMENTI_CONTABILI"."IMPORTO"*decode ("MOVIMENTI_CONTABILI"."TC",1,1) uscite,
BETWEEN :P17_DA_Data AND :P17_A_Data
AND "SOCI"."N.TESSERA_SOCIALE" = "MOVIMENTI_CONTABILI"."OPERATORE"
AND "MOVIMENTI_CONTABILI"."CAUSALE" = "CAUSALI"."CODICE_CAUSALE"
ORDER BY "MOVIMENTI_CONTABILI"."DATA_MOVIMENTO"
You should download the latest version of the package. I found some mistakes in it
and corrected it accordingly. However, apex.oracle.com seems to be down at the moment.
After you reinstall the package, your export will work.
Denes what kind of package are you talking about? If you intend export_to_excel_xe_pkg.sql I've downloaded it next week from
is there a new version?
Exactly. I may update and change the package frequently. The version date you see
in my app on the page where you download it. Yesterday evening I changed it as I said,
becouse of some errors in it.