i am configuring Report Server Community for 3 groups of users. As administrator i have created also 3 dashboards, that i want to be showed as default, just one for each of the groups. I created them on the dadget library under the Dashboard Root, i assigned to each of them the corresponding ACE to their group but when i try to login with the users that belongs to each of the groups, the dashboard tab only shows the “Deafault” empty one ready to be created from scrach
Is there a way of assigning to each group a “default” Dashboard already created as i am trying to do?
the users see only the “default” empty dashboard because they first have to import the existing dashboards. Click on tools → import dashboard, then select the previously created dashboard. The groups must have access to the dashboards, as you pointed, i.e. have the corresponding ACEs.
For deleting the “default”-dashboard, the users have to select the default-dashbourd, then click on tools → remove dashboard
I would also like to set a default dashboard (or multiple dashboards) based on everybody, group or person).
Person is less important for me as they can do that themselves but new user should see the default setup.
Mayby something for the new release? A user-variable (can also be on everybody and group level) to set the default dashboard ID or something?
How many users per day do you add to your ReportServer instances?
If it is 1-10, I would use SU command, log in as the added user and import the default dashboard from the dashboard library for her/him.
If the number is in tens or hundreds, I’d do it by scripting (I have never tried it, but technically it should be possible).
Then you just have to be aware that if a user has no permission to see a report added to a dashboard by scritpting, she/he will see error message or error stack trace (which is not nice ;-))
Thanks for your response.
At the moment we are still using Actuate iHub 3.1 for our production environment. But we are looking for alternative solutions and the advantage of ReportServer is that we can keep most of our BIRT reports without having to redesign them in another tool (only convert from BIRT Pro to BIRT OS).
The number of new users a day is not that much (at the moment about 1800 users total) but it is growing slowly. We use a dashboard like a central landingspage that is shown to all new users. To make sure I do understand correctly, all new users get a blank dashboard and have to manually add available dashboards (based on authorization) to their dashboard page? In my opinion that is not very user-friendly. But mayby I misunderstand how the dashboard is suppose to work.
we are planning to change this behavior for the next reportserver release in an analogous form as the user property “teamspace:primaryTeamSpace”
So we will have: “dashboard:primaryDashboard”
With this user property, the administrator will be able to set the default dashboard for each user, either manually by setting the user property or with a script.
please take a look at https://forum.reportserver.net/viewtopic.php?id=563 (#15) for this functionality of importing a dashboard for a number of users and updating it.
With the actual version and the next release, have in mind that all users are getting copies of the “mother”-dashboard. Because, as stated in the documentation, a dashboard is per-user only.
With future versions we are planning to introduce shared dashboards. Until then, the solution in the thread should achieve this functionality.
We notice that there hasn’t been a new release since last June. When do you think shared dashboards will be out? We need this functionality to consider this product for production use.
with 3.0.3, which we aim to release in June, the new functionality “dashboard:primaryDashboard” I mentioned in #8 will be out.
With this user property, the administrator will be able to set the default dashboard for each user, either manually by setting the user property or with a script.
Shared dashboards will not be in 3.0.3, we are looking at 3.1 for this. The date for the 3.1 release is not yet planned.
Eduardo,
Thanks for the response. Until there are shared dashboards, we can’t deploy this across our organization. Our users are just not tech savvy enough to walk them through adding all of their own dashboards. Additionally, we update our dashboards all the time, so we can’t have them constantly re-importing. Looking forward to 3.1
we have ticket RS-2731 for this. This ticket is currently in the development queue, as we had to postpone its development, it was not possible to include this into 3.1.
Please note that you can achieve this functionality by scripting as mentioned above.
Eduardo,
No disrespect, but this issue is multiple years old. No support for shared dashboards is very likely going to have us move to another platform soon. We can’t keep building functionality on top of this platform if it’s not scalable. Having to update everyone’s dashboard when we make changes is going to force us to look at other solutions.
to avoid misunderstandings, I want to note that this is a feature request. Shared dashboards are not currently supported and the feature request is to actually support them.
We cannot make guarantees on time frames of feature request implementation. We do have a ticket on this which is in the development queue as I mentioned above.
For extension of functionality not directly supported by ReportServer, there is scripting. As mentioned above, a script could refresh the dashboards of your users after dashboard modification. So there is a workaround.