Hi,

I am working on a project which will be used by many Customers and these may have many branch offices, I am working on having one SQL2005 database for everybody, but of course the end users will only be able to see data from their Customer ID and Branch Office ID.

When login to the application I need to capture the Customer ID and Branch Office ID in the Login form, but how to filter the RBS data per Customer ID and Branch Office ID, so when the managers of one office creates an user and assign roles will only be able to do so for their records?

What would be the best approach to handle this with SF RBS?

Thanks!

Edhy Rijo

Oh no, we don't give the users a full blown version of the DDT. Just thinking about doing that gives me chills . When I said we use the DDT to handle structure updates, I meant we use a DDT package, and deploy that package within our normal installation and update. It's all fairly transparent to the user (they hit "Next" and it does its thing.)



Obviously, if the data were being housed on our servers, the customer wouldn't be updating anything since we would be loading any updates ourselves.



And yep, if you change the RBS source, then you effectively put yourself on an island. Meaning that if you want to load a future update, you'll have to go back and re-do your changes afterwards.