November 21, 2013 at 1:37 pm
Afternoon.
I'm currently working on a data retirement initiative within my organization. We are retiring the data from 200ish application to a data repository. One of the things we're working on is a way for the users of these apps to be able to still view this historical data. 1 person could possibly need to view multiple sets of data.
I had started creating a SSRS that lists all applications a person can see and then had the idea of setting a dynamic subreport( as you know and I didn't know, this can't be done!!).
So, my question is, is SSRS an option for the front end? Or, do I need to build an ASP.NET front end with a report viewer control? Seems like this might be the best route.
Thoughts, suggestions!?
Thanks in advance
John
November 21, 2013 at 2:39 pm
My first thought would be how often and how many people need to view the historical data? If one person might view it twice a year, I'd go the simplest route to present the data (SSRS would work fine). Any factor might be how important/critical is this data? For example, will you receive a fine if you can't prove/show the historical data to auditors or government regulators?
Just a couple thoughts,
Rob
November 21, 2013 at 2:47 pm
Thanks for the reply.
I think it will be viewed quite often by many users. Is Ssrs even an option for a front end? I'm thinking not as a user will want to see all reports they are legible for. That's why I'm thinking an asp.net front end with a report viewer control that display ps whichever report(application) they are wanting to see.
November 22, 2013 at 8:26 am
Take a look at the Report Manager interface. You can create folders for organization; setup security so users can only run their reports. I think it will do what you want without having to create a custom front end.
Rob
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply