Having segregation at the DB level is the most effective one for SDE. In case you want to do that on the application side, you can have separate incident types created and associate a custom form to the same. You can use this custom incident type/form to log tickets having sensitive data. These incidents will not be available on the ‘normal’ popup and only on the custom incident form popup.
Hope this will help you.
Many thanks for that. I will most likely go down th DB route as it seems to be pretty well documented in the Database Admin Guide.
Please be aware that data segregation (Group Segregation) is only valid on the SDE (View) level. Any other reporting solutions other than Crystal Reports from within SDE is not affected by this data type of segregation. So if you query the database directly on the tables of the SMDBA (based) views sensitive data is not protected.
With kind regards,
Stationspark 1000, 3364 DA Sliedrecht, The Netherlands
T +31 (0)184 44 44 44 **873 | F +31 (0)184 44 44 45| M +1 (0)6 3882178
This message and any attachment(s) are intended only for the use of the named recipient and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient, please notify the sender by return e-mail and delete this message from your system. Do not disclose the contents of this document to any other persons. Violation of this notice may be unlawful. Please note that internet communications are not secure and e-mails are susceptible to change.
Thank you for your cooperation.
Cheers for that Jos!