Timeline for Create security field
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 3, 2011 at 17:40 | comment | added | Alexander | the best solution on this time that I found is a link in the Omlin answer. This solution uses two lists to restrict users, but it provides a simple way to create/edit new items for the user. | |
| Nov 2, 2011 at 20:01 | comment | added | Eric Alexander | The idea is that you create the public information first, then create the secured information. The lookup in the secure list is to the person. This allows you to secure all data about the user absolutely. The other methods are more security by obscurity. You can use tools like jQuery and SPServices to help ease the entry. | |
| Nov 2, 2011 at 19:54 | comment | added | Alexander | I discribed this solution in my question. I don't like it. Because, in this case, for new salary, people that can access to the isolated information have to create a new item in the isolated list, then create a new item in the public list and select predefiend value for the lookup field. There a lot of steps in this solution, thus it is not a convenient approach if the user should create a lot of records. | |
| Nov 2, 2011 at 18:54 | comment | added | Andrey Markeev | +1, I reckon in most situations this solution will solve the problem. | |
| Nov 2, 2011 at 17:40 | history | answered | Eric Alexander | CC BY-SA 3.0 |