Thanks in advance for any help.
I do apologize for the size of this question, but I could sure use some help and it does not seem to be coming from Crystal.
We are starting an effort to implement row-level security on our reports and I really have no clue how to do it. Due to licensing fee issues, our are using Crystal Enterprise without named users and we would like to find a way to enforce row level security on the dbase which we are reporting.
We are using a single signon (as Administrator) from our web app and would like to pass our application's userid to a hidden parameter for which to run the report. This parameter would then be used to enforce security based on the business logic in the dbase. This way the security layer is invisible to our customer's CE Admin.
Has anyone done this? Does anyone know a good place where I can see an example of this? Reading the forums, it looks like using URL reporting might be a good way to go, but that would mean I'd have to do some serious recoding of our version of CE's ePortfolio.
All ideas are welcomed.
Thanks Mucho,
EZT
I do apologize for the size of this question, but I could sure use some help and it does not seem to be coming from Crystal.
We are starting an effort to implement row-level security on our reports and I really have no clue how to do it. Due to licensing fee issues, our are using Crystal Enterprise without named users and we would like to find a way to enforce row level security on the dbase which we are reporting.
We are using a single signon (as Administrator) from our web app and would like to pass our application's userid to a hidden parameter for which to run the report. This parameter would then be used to enforce security based on the business logic in the dbase. This way the security layer is invisible to our customer's CE Admin.
Has anyone done this? Does anyone know a good place where I can see an example of this? Reading the forums, it looks like using URL reporting might be a good way to go, but that would mean I'd have to do some serious recoding of our version of CE's ePortfolio.
All ideas are welcomed.
Thanks Mucho,
EZT