would be the same as you would include the content of the procedure to the original report. It is treated like a normal query, not as a report.
select 'dbr.report', 'sp_DBR_EditRec', 'new_window', 'inRecID=RecID';
when clicked the linked report, would open the sp_DBR_EditRec-report to new window and if the report has other parameters, asks them and the output of the editing report would be the final content of the new report.
So the use case you are looking for is:
- You have a main report with link to editing report sp_DBR_EditRec which has parameters user needs to fill
- User clicks the link and is presented the parameters and a "Run report"-button (you can change the name of the button)
- The editing report is executed and after that you want run another reporting automatically so user moves from original main report to the new one
What is the reason for asking the parameters in a popup if you still will move away from the main report after editing?
However, to do this, you would need to make the editing report to do two thing: 1) edit the data according to parameters and 2) move to new report.
So a simplified main report would look like this:
select 'dbr.button', 'Click here to edit';
select 'dbr.report', 'sp_DBR_EditRec', 'linked_output.whatever.noshow', 'inRecID=RecID';
select 1 as 'dummy';
select 'dbr.embed_object', 'linked_output';
This would indicate that the output of the sp_DBR_EditRec report would be put into a DIV 'linked_output' and the content would be hidden (using CSS class 'noshow' which has definition of 'display:none'.
/* Make the update */
set col = in_col
where id = in_id;
/* Go to final report, create link */
select 'dbr.report', 'sp_DBR_final_report', '[data]';
select 'dbr.colclass', 'data', 'clickme';
select 1 as 'data';
/* Go to final report, click the link */