tag:blogger.com,1999:blog-2565836540734979604.post5367857028021828263..comments2023-03-22T04:55:19.173-07:00Comments on Salesforce Hacker: Why 'Standard' Profile Permissions Can't Be Changedatormanhttp://www.blogger.com/profile/12188546691736154200noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-2565836540734979604.post-31675981203685121992017-04-24T16:42:57.240-07:002017-04-24T16:42:57.240-07:00The issue where you have dependent permissions can...The issue where you have dependent permissions can't be solved with enhanced profile list views. They allow you to change many of the same permissions across profiles. What the issue described above involves is actually change many different OBJECT permissions at the same time on the same profile. In the Enhanced Profile List Views, each object permission is its own separate column requiring its own separate save. Oftentimes it is multiple sets of non-interrelated dependencies as well (e.g. 10 objects affected but really the issue is 4 specific object permissions that need to be removed simultaneously). Enhanced Profile List Views are also basically unusable in larger orgs as all you see is the "Search to refine criteria" error. Much faster and easier to go back to the old editor.Patrickhttps://www.blogger.com/profile/11795545920812792289noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-49282478629190540622017-04-22T13:18:11.736-07:002017-04-22T13:18:11.736-07:00Not entirely impossible: http://www.salesforcehack...Not entirely impossible: http://www.salesforcehacker.com/2013/01/mass-edit-profiles-using-enhanced.html?m=1atormanhttps://www.blogger.com/profile/12188546691736154200noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-85668608323877470432017-04-21T15:18:59.732-07:002017-04-21T15:18:59.732-07:00This is an unfortunately common issue especially a...This is an unfortunately common issue especially after turning on a new feature in SF or installing a package. In terms of how to fix it, you have to go into the OLD profile setup page (toggle this setting from User Interface in setup). That allows you to change multiple object permissions at once and then save. If you are using the new interface, it's impossible to fix as you can only set one object's permissions at a time. Patrickhttps://www.blogger.com/profile/11795545920812792289noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-88322747752643711302017-01-23T13:13:22.278-08:002017-01-23T13:13:22.278-08:00Hope you solved this by now but the short answer i...Hope you solved this by now but the short answer is that objects have dependencies between them and you must fulfill those dependencies before saving the profile. IN this case, you can't change the permissions because Read Orders is required.atormanhttps://www.blogger.com/profile/12188546691736154200noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-48087927811411315622017-01-03T11:06:34.589-08:002017-01-03T11:06:34.589-08:00Getting below error while updating any profile in ...Getting below error while updating any profile in salesforce. Please help.<br /><br /><br />Error: Invalid Data. <br />Review all error messages below to correct your data.<br />• Permission Create Invoices depends on permission(s): Read Orders<br />• Permission Delete Invoices depends on permission(s): Read Orders<br />• Permission Edit Invoices depends on permission(s): Read Orders<br />• Permission Read Invoices depends on permission(s): Read OrdersAnonymoushttps://www.blogger.com/profile/17659291062663245871noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-31509814159940529122016-12-15T09:00:40.904-08:002016-12-15T09:00:40.904-08:00Hi Candy,
Sorry for the delayed response. Unfortu...Hi Candy,<br /><br />Sorry for the delayed response. Unfortunately, we don't allow editing of standard profiles (currently). That may change in the future. Creating a custom profile is really a best practice. The only standard profile I ever recommend assigning is the System Administrator. Otherwise, the first thing I do with all profiles in a new org is create a custom clone of it so that I have full control of the permissions.atormanhttps://www.blogger.com/profile/12188546691736154200noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-50809512868885471442016-11-28T11:39:59.892-08:002016-11-28T11:39:59.892-08:00Hi - in our org, we would like to restrict group c...Hi - in our org, we would like to restrict group creation from any other users except System Administrator. But when users with the "Chatter User" profile are created by invitation - they are by default given the access to create new groups. Is there a way to go around this without having to create a custom profile?Candyhttps://www.blogger.com/profile/13258825583399137534noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-1385289301304559592014-04-16T09:40:46.306-07:002014-04-16T09:40:46.306-07:00Really good points! I've shared internally. Th...Really good points! I've shared internally. Thanks for the feedback!atormanhttps://www.blogger.com/profile/12188546691736154200noreply@blogger.comtag:blogger.com,1999:blog-2565836540734979604.post-24423222940761919932014-04-01T11:32:31.008-07:002014-04-01T11:32:31.008-07:00Good information as usual (slowly making it throug...Good information as usual (slowly making it through all your posts). I would like to point out one implication that we ran into when we turned on Chatter Plus. The "standard" profile that was created by support actually contained a random grouping of custom objects. I would really recommend having NO object cred on the Chatter Plus or Force.com one app licenses where the license is supposed to be limited to only certain object and/or a certain number of objects. This was problematic for our org because:<br />-The custom objects added to the standard profile added up to 14 objects, leaving us out of compliance on that profile (license type is limited to 10) and no way to fix it.<br />-Two of the objects had a dependency to Case (which isn't included at all in Chatter Plus), and therefore when we Cloned it, we couldn't make any changes to that profile until we fixed that dependency. Since you can't edit two object CREDs at once in the Enhanced Profile editor, had to revert back to the old version, remove the objects and then switch back. This took quite awhile to figure out.<br /><br />In general, we're moving to a model where the profile itself only has CRED on standard objects and all custom object cred is handled via permission sets, which really is a better way to do it and setting up those standard profiles with no custom object cred really makes the most sense as it forces you to go to the custom, which I believe is the goal anyway.Patrickhttps://www.blogger.com/profile/11795545920812792289noreply@blogger.com