Default view not working?

#1


I have a (Dundas) group called “MS Leads” with a couple of (active directory authentication) users in it. I have the default view for the group set to a “My Dashboard” that I created for the users of this group.


I’ve tried sending the user (via a link) both the root url of our site (e.g. https://ourdundassite.ourdomain.local ) and explicitly to the root with the ‘DefaultViewOrHome part of the url included (e.g. https://ourdundassite.ourdomain.local/Home/DefaultViewOrHome )


My understanding of how the Default View works is that when a user would login to our Dashboard/Dundas site this would be the first thing they see, unless they changed their default view otherwise. This is not what is happening though, instead the user always get directed to the generic “Hello USER NAME” home screen.



Any suggestions on how to trouble shoot this?

#2

Also, is there is a hierarchy of which default view takes precedencewhen a default view is set (by the administrator) for a user as well as a groupthe user is in?

#3

Your expectation is correct, the user should see the view indicated as default when they log in to the root or the the DefaultViewOrHome link. The hierarchy in this case is that unless it's set to Home, the default view of the account overrides the default view of the group, which in turn overrides the default view of the instance (you can set it using the Default Home Page configuration setting).


Unfortunately, I was not able to replicate the behavior you are describing. I suspect that it has something to do with the way permissions are set up for these users or the group. Can you make sure that they can access the dashboard you are interested in?

#4

I’m fairly confident that confirmed and re-confirmed the dashboard, metric set and datacube has permissions allows for the users.


It seems to be system-wide problem though, so I have a ticket into support for this problem I’m experiencing.

#5

I'm going to revive this old thread since I'm having a similar problem.


I want the users of a user group to only see the dashboards that I allow them to navigate to (using buttons on the dashboard template). I don't want them to see the home screen, the menu bar on the left side, nor the project explore on the right side. When a user logs in, they go to the default view. Full screen is disabled. The user is able to log off using using a button on the dashboard template.


So far everything works when the user logs in for a new session.


The problem occurs when either the user opens a new tab or window, or they close their browser without logging off and open a new browser window. Their session is still active. When they go to the url (portal.ourdomain.com) they don't get the log in screen, they get the home page where all of the dashboards and scorecards are listed, along with the menu bar on the left. I don't want them to see this at all. Only the dashboards.


I haven't figured out how to solve this problem. I'm using Google Chrome which is what we are going to recommend to our users.


Thanks,

Matt

#6

Looks like you just got a reply in the new topic you posted:

#7

Just noticed this reply to my post. I'm not sure if this helps, but this was my experience:


Reviewing my support ticket and based on our experience in the last few months, it seems the problem was due to the hierarchy of how default dashboard is given precedence; basically whatever is closest wins. So user-defined dashboard seems to take precedence over group-set defaults and if a user is in two groups and doesn’t have a user-defined dashboard then things get tricky. Setting each user to have a default dashboard seems tedious. Setting up an environment where I have a one-to-one relation between users and groups is not feasible with the application, at least to my understanding as of my support call back in October.


Right now I don’t really have a solution except to manually set up each user with a default home on both test and prod, which put a lot more of the responsibility on the administrator instead of utilizing the application to help me manage permissions.

#8

Updating in case someone runs into the same situation: the reason behind this issue was that one user was assigned to two groups, and each of those groups had conflicting values stored in the default view. The solution here is to setup multiple groups for different purposes, one for default views, one for permissions, etc. That way you are still able to have users in multiple groups, but the underlying issue of conflicting default view values is resolved. Note we have improved the Dundas BI system message in case you have this situation.