Interesting fact about SalesLogix.By simply adding in a seccodeid field
(standardId) to a table in SalesLogix, the Provider will automatically enforce
security on that table.What does that
mean?We can grant Lee Hogan access to
Abbott Ltd. and restrict his access to some of Abbott Ltd.’sContacts, Opportunities, Tickets, Activities,
History, Document attachments…
How Does It Work?
All 8 Contacts in Abbott Ltd. are assigned to Owner = Midwest (seccodeid = FDEMOA000003).Lee Hogan has rights to the Midwest Team and can
see all 8 contacts.
If you allow users to edit the Owner field on the Contact
Detail screen, by default this field is read only, and you select Southeast
(seccodeid =FDEMOA000007) for Lou Balbo, Lee Hogan will only be able to see 7
contacts. Why?Lee Hogan does not have rights to the
Adding in a Seccodeid
Field to OOB and Custom Entities
Add in “Seccodeid” field (Type standardId) to an entity
(e.g. SalesTeam).On a data entry form
add in a field (Type Owner, bound to seccodeid, caption whatever you want).
·If there is no data in this table (e.g.
SalesTeam) nothing else is required for transactional level security to
work.All new entries will automatically
have a seccodeid assigned to them.
·If you have already entered data into this table
run a SQL script to populate Seccodeid’s since the Administrator is the only
person who can see records where Seccodeid is Null.