Publishing a project with different folders within

Question

Publishing a project with different folders within

Debbie Edwards

SSCrazy Eights

Points: 9217
More actions
April 15, 2008 at 5:00 am

#184433

Hello again,
Still getting my head round Reporting Services. Managed to publish it to our reporting server via visual studio but I have no idea how you publish the reports within a project to different folders.
In the project properties it asks for...
StartItem main.rdl
Overwrite Data Sources True
Target Data Source Folder OurDept/Data Management/Data Quality Report/Data Sources
Target Report Folder OurDept/Data Management/Data Quality Report/
So everything goes here when I deploy. However I have lots of reports and for example I want
OurDept/Data Management/Data Quality Report/main.rdl
OurDept/Data Management/Data Quality Report/ManagementReps/TotalNumbers.rdl
OurDept/Data Management/Data Quality Report/ServiceReps/Service_reps.rdl
Ect. Is it possible to to this? I can move them about and add folders in Report Manager but when I deploy from Visual studio they just all get deployed to the top level again.
Debbie

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

JohnG-529958 Old Hand Points: 366 More actions · Answer 1

Hi Debbie,

From what I've read I don't think this is possible. You can set the target folder from the report properties as you've already discovered. And it's possible to have multiple configurations set up (eg I have my Debug profile publish to all the reports to an In Progress folder that only I have access to and my Production profile publishes all the reports to the public folder). But from what I can gather it's not possible to publish reports to multiple folders from within a single project.

I've dealt with this by having separate projects for different groups - a Rent Accounting project, a General Management project, a Maintenance project etc. But this doesn't allow for any fine control over report destination and I still have to manually move some of the reports after deploying.

Hope this helps,

John

Debbie Edwards SSCrazy Eights Points: 9217 More actions · Answer 2

Ahhhh, I had a feeling this was going to be the case.

Im going to get round it now by havng a main report which contains links to the other reports which Im going to hide. I think thats the best bet to keep things simple.

Thanks for that!

Debbie

Adnan-509283 Valued Member Points: 52 More actions · Answer 3

Debbie,

I would not recommend hiding the reports since sometimes users want to go directly to a report rather than having to navigate via a summary report.

I would recommend scripting your reporting hierarchy using the Reporting Services Scripter tool that can be downloaded from here:

http://www.sqldbatips.com/showarticle.asp?ID=62

This tool basically automates many of the tasks required to maintiain SSRS site and uses the object model by creating an executable to perform repetitive tasks.

You can refactor the generated code to create routines to create reporting hierarchy and one for uploading reports to that report hierarchy. Unfortunately, this can not be done via Visual Studio; however, once set up this is easy to maintain.

Hope that helps.

Debbie Edwards SSCrazy Eights Points: 9217 More actions · Answer 4

Thanks for that but thats way beyond my capabilities at the moment. :blush:

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 5

Create a subproject...put the other reports in there. The project seems to hold the publishing folder.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

Debbie Edwards SSCrazy Eights Points: 9217 More actions · Answer 6

I think I may have to go down that route after the problems I have had today. I was creating a top level report to navigate down to each sub report but it causes issues with lower level parameters.

Ill have a think as to the navigation and set up seperate projects.

Im guessing this means I can have a project of DATA QUALITY REPORT

and a sub project of SERVICE REPORTS?

I havent tried making sub projects yet, is it fairly straighforward?

Debbie

Robin Brown Grasshopper Points: 15 More actions · Answer 7

Creating a top level project solution is easy if you have your source control well structured.

Create a new Report Project - this will create an empty or dummy project (which you will later remove)

Add Each of your other projects (assuming you have groups your reports by folder)

Remove the dummy project and save your solution.

This way you will be able to manage the whole reporting solution as a true heirarchy with each project having its own respective publishing parameters.

It also allows other team member to work with individual report projects concurrently.

Hope this helps