Adding SSRS Reports inputs/ parameters to browser history

Question

How can I add the parameters with which I queried the report to the browser history/url via MS-Edge extension?

Want to go back and forward a few days if needed.

(So the report parameters should be added to the browser history in the for of <reporturl>?val1=x after each submit from the input fields)

(Don't comment if your answer is "it is not possible" thx)

Answer 1

SSRS server don't know a "client history" and I am not aware Edge browser supports this; so it's not possible.

Answer 2

Hi @Pandabay

Sorry that I delete my comment unintentionally. I can only give some advice from Edge extension side.

If you only want to get the input field's value, you can get it in Content scripts.

Content scripts are files that run in the context of web pages. By using the standard Document Object Model (DOM), they are able to read details of the web pages the browser visits, make changes to them, and pass information to their parent extension.

Then you can use chrome.storage to pass data between background.js and Content script. You can also use chrome.history to add browser history according to the input field's value. But I have no idea if sth like <reporturl>?val1=x will work in SSRS report.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Regards,
Yu Zhou

Answer 3

There's an execution log that houses the parameters of reports that were run. You'd need to

• isolate just the ones run by the current user
• parse the parameters out (this is probably the tricky part)
• Take those parsed parameters and put them into a https:// string that passes the same parms back to the original report. This will vary wildly depending on the report and number and type of params.

This script shows where the data comes from. The Parameters field is the key. I don't know a generic parse of params from the execution log code offhand, seems feasible.

DECLARE @DateStart date='11/1/2022',@DateEnd date='11/8/2022 10:00AM',@ChosenReport varchar(255)='/Sales/Daily/DailySales';  
  
  
select   
ItemPath,  
UserName,  
RequestType,  
[Source],  
[Format], -- 5  
[Parameters],  
AdditionalInfo as AddInfo,  
TimeStart,  
TimeEnd,  
datediff(ms,timestart,timeend)/1000.0000 TimeinSeconds, --10  
[RowCount],  
ByteCount/1024 as ByteCount,  
Status,  
ExecutionID, --14  
(select min(timestart) from executionlog3 e) as OldestReport,  
(select MAX(timestart) from executionlog3 e) as NewReport, --16  
space(300) as ReportID   
into #TempResults  
from ExecutionLog3   
where DATEADD(dd, DATEDIFF(dd,0, timestart), 0)  >=DATEADD(dd, DATEDIFF(dd,0, @DateStart), 0)   
and  
DATEADD(dd, DATEDIFF(dd,0, timestart), 0)  <=DATEADD(dd, DATEDIFF(dd,0, @DateEnd), 0)   
and ItemPath = @ChosenReport  
;