Many a times Salesforce developers are confused about the point of deploying Salesforce profile using Changeset Deployment. To be Concise, Earlier it was not possible to deploy Profiles using Changeset in Salesforce but due to evolving Salesforce platform, the developers are blessed with this feature in SF Release v30.0.
Following points would help in clearing some doubts regarding profile deployment through Changeset:
Following points would help in clearing some doubts regarding profile deployment through Changeset:
| - Adding profiles or permission sets to outbound change sets is designed to allow administrators to migrate permissions for users so they can access new functionality. Including profiles in change sets is NOT designed to be a tool or method to update profile settings and permissions for functionality already existing in the target environment as per the Change Sets Best Practices documentation. - Starting in API version 30.0, when deploying a new custom field, the default values for the editable and readable fields in profile field permissions are false. To override the default values, include field permissions for the new field in your profiles. - A deployment containing a profile and record type, but not the assigned page layout for that record type, removes the existing layout assignment from the profile for that record type. Always include all page layouts for all required record types in the change set. See the Special Behavior in Deployments documentation for more details. - Profiles or permission sets and field-level security — The contents of a retrieved profile or permission set depend on the other contents of the retrieve request. For example, field-level security for fields included in custom objects are returned at the same time as profiles or permission sets. |
No comments:
Post a Comment