Adding SSRS Reports inputs/ parameters to browser history

Question

Adding SSRS Reports inputs/ parameters to browser history

Pandabay 6

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)

3 answers

Your answer

Answer 1

Olaf Helper 47,601

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

Answer 2

Anonymous

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

Pandabay 6 Reputation points

2022-11-03T14:40:52.81+00:00

The main issue I had with it that the content script did not see any input fields in the DOM while there are def some in the html. Don't know how to fix it.
Anonymous

2022-11-04T08:02:03.873+00:00

Hi @Pandabay

How do you try to get the elements? In my test, I made a simple SSRS report and the input field has an id. I can access the input by id.

If you can't access the elements, I think there will be some error when you run the extension. Do you know how to debug the extension? You can refer to this doc to debug the extension and check if there's any error message. If possible, it is better to provide a minimal code snippet which can reproduce the issue. We can't identify the issue with only the text description.
Pandabay 6 Reputation points

2022-11-16T19:58:05.953+00:00

content.js

document.querySelectorAll('form').forEach(f => f.addEventListener('submit', function () {
var attrs = ''
var inputs = document.querySelectorAll('input').forEach(x => {attrs += "&" + x.id + "=" + x.value; });
history.pushState({}, '', attrs.substring(1))
}));
Anonymous

2022-11-17T07:45:46.753+00:00

Hi @Pandabay

The content.js code looks OK. I test with it and it still can get all inputs' ids and values on my SSRS report via extension.

Is there any error on this page when you load your extension in Edge? Could you please also provide the code of manifest.json? Besides, please open F12 devtools in Edge when you run the extension, and add breakpoints on your content.js code and run the code line by line to check the values and if there's any error in console.

Pandabay 6

Thanks for the reply.

While it looks ok, it is not working? It will not push anything to the browser history for srss reports.

The manifest was just a basic from the docs.

{
    "name": "test",
    "version": "0.0.0.1",
    "manifest_version": 2,
    "description": "test",
    "content_scripts": [
        {
            "matches": [
              "<all_urls>"
            ],
            "js": ["scripts/content.js"]
        }
    ],
   
}

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  
;

Pandabay 6 Reputation points

2023-02-10T19:14:19.4+00:00

Thanks for the reply, thats nice to know. Browser history would be more user friendly though.

Share via

Adding SSRS Reports inputs/ parameters to browser history

3 answers

Your answer