1. What is the importance of field level security in CRM?
2. What are the permission we can restrict on specific field with field level security?
3.What are the high level steps to enable field level security?
4. What will happen if a field is enabled for field level security?
5. What a field level security profile contains in CRM?
6. Can we add user/team to more than one field level security profile?
7. Can we delete System Administrator field level security profile?
8. Can we set field level security for OOB fields?
9. Do Audit history maintained for enabling and disabling field level security by setting “IsSecured” on a field?
10. What will happen if the user don’t have “Read” security on a field?
11. How can we know what are all attributes can be secured in CRM with field level security?
12. Do all attribute data types support to restrict all permissions with field level security?
13. Which security roles allow you to see secured fields?
14. What will happen if multiple profiles assigned to user/team?
15. How do secured fields behave for create or update?
16. How do secured fields behave for Retrieve and RetrieveMultiple?
17. How do secured fields behave when records are shared?
18. How do secured fields behave for filtered views?
20. How do secured fields behave for offline synchronization?
21. Can we control the field level security based on security role?
Subscribe to:
Post Comments (Atom)
Featured Post
-
Merging PDF Files Based on Name Segments in C# In this blog post, we will explore how to merge multiple PDF files using C#. The me...
-
Dynamics CRM Questions and Answers Q251) How do you create and manage multiple forms for a single entity? + T...
-
Automating Email with VBA In this blog post, I will walk you through a VBA script that automates the process ...
No comments:
Post a Comment