Filtering Locations by Domain alternative?
-
For years, our apps queried location data (Example: Office 1 in GA, Office 2 in FLA, Office 3 in UTAL) by reading the DOMAIN from an API call. We also used NT Groups as logins on SQL Server, and then in each database, used ROLES to which we added the logins to. When the user opened any of the apps, their domain would determine which location of records they could view/edit/update, and would filter the records that way so they only saw their location data.
This will no longer be feasible as we are going to only have one domain for everyone. Does anyone have a better idea, than us making a USER TABLE with the location information in it? It would be a maintenance nightmare to maintain a user table with so many employees coming and going.
-
You can try creating a group depending on the domain. 😉
-
That's what we WERE doing, but now all groups will be on ONE domain, so that won't work. Perhaps you mean creating an NT Group for each Location?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply