September 20, 2006 at 10:05 pm
All,
I have some questions about a possible solution to my scenario. Here it is.
A person can belong to multiple applications
A person within an application can have multiple roles
A role within an application can have access to different navigation(pages)
How can I prevent redundant navigational elements from showing? I use a distinct filter to prevent duplicates but for some reason i get an uneasy feeling about this method. Since a person can have multiple roles..a single page will be used where different access will be applied. Example, widget.aspx will check your roles and display certain items via the code behind.
Here are a couple of queries to pull the information.
http:
http:
Is there a way to make the navigation truely dynamic or is there a better solution I am completely missing?
September 22, 2006 at 6:06 am
From your schema I can't see where people are related to a role.
From what I can see you need a table that relates users to an application role.
Then you could join across:
UserXApplicationRole -> ApplicationRoleXPage -> Page
When querying I'm assuming you'll be filtering by a particular user and application.
Not sure which would be better without testing it, either using distinct, or using the select above to get a list of page ids and then selecting the pages that are in that list. I.e. SELECT ... FROM Page WHERE PageID IN (SELECT ...)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply