You may not turn off permission Can use dashboards without same license type as running user for this License Type - Answers - Salesforce Trailblazer Community
Ask Search:
Munna JaiswalMunna Jaiswal 

You may not turn off permission Can use dashboards without same license type as running user for this License Type

I getting below error on updating profile. After Spring 2019 Release in Sandbox.
User-added image
 
Best Answer chosen by Munna Jaiswal
Russell McGibbonRussell McGibbon
Hi Peter, I needed to update a profile with some object settings which it wouldn't let me do on the profile. So I created a new permission set with the required permissions on and then assgined it to all the users that have the profile. Fortunatly there wasn't too many users with that profile but its pretty easy to assign them from within the permission set. I've also been able to amend existing permission sets on the object and system permissions. I'm in a Full Production sandbox using the Winter release and LEX is not setup. Hope this helps

All Answers

Susie TurpinSusie Turpin
We are having this same issue and cannot save ANY edits to new profiles.  We are logging a ticket with SF.
Ryan MoodyRyan Moody
I'm having the same issue as well. I was able to make changes to the user a week or two ago, nothing has been changed related to dashboards.
Libby GrayLibby Gray
I'm also having this problem today.  
André Luiz Taufic CosenzaAndré Luiz Taufic Cosenza
We are facing this issue as well.
Andy HeidrichAndy Heidrich
Us too.
Peter LarsenPeter Larsen
Us too.
Jeff HunsakerJeff Hunsaker
Me as well.
Jeff HunsakerJeff Hunsaker
Specifically for me, it is updating a profile connected to a Salesforce Platform License.
Russell McGibbonRussell McGibbon
Same issue which looks to be related to our dashboards running as a SalesForce Licence user when trying to change a Platform licence profile.

I managed to get round this by using a permission sets until SF fix this issue as I don't fancy updating all the dashboards.running user
Peter LarsenPeter Larsen
Russell McGibbon, can you provide more details on your workaround?
Russell McGibbonRussell McGibbon
Hi Peter, I needed to update a profile with some object settings which it wouldn't let me do on the profile. So I created a new permission set with the required permissions on and then assgined it to all the users that have the profile. Fortunatly there wasn't too many users with that profile but its pretty easy to assign them from within the permission set. I've also been able to amend existing permission sets on the object and system permissions. I'm in a Full Production sandbox using the Winter release and LEX is not setup. Hope this helps
This was selected as the best answer
Russell McGibbonRussell McGibbon
For those having this problem, I've found if you clone the Standard User and Standard Platform user profiles and create your new profile, then it appears you can make edits to it afterwards without this error. If you clone one that has the issue then the new profile will also show the error when you try to make changes to it. Obvoiusly this only works if you need to create a new profile.
Faye DownesFaye Downes
We are facing the same issue. In Sandbox, we have amended all Dashboard "running users" with Salesforce Platform licenses to "running users" with Salesforce licenses and we are still receiving the above error message. 
Bryan LeamanBryan Leaman
This is a big problem in our sandbox environment too. I cannot remove permissions on our platform profiles. I can add needed permissions via permission set, but cannot remove authority this way!
Catherine FAURE MALANCatherine FAURE MALAN
Same issue when we update a profile connected to a Salesforce Platform License
Jeff HunsakerJeff Hunsaker
Has anyone actually created a Case against the new release for this?  Good information here, but need to get to salesforce.
Alex TuckerAlex Tucker
Yes. I submitted this issue to Salesforce support today and am waiting for a response.
Alex TuckerAlex Tucker
Here's what Salesforce support wrote:

This is Michelle from Salesforce.
I've taken ownership of case 21255940 which is about an error message you're receiving when enabling permission to Profiles.

Upon further review, this issue has already been tagged and raised to our Research & Development team for further investigation. For now, what we can do is to escalate the case to our higher tier of support so that we can track the updates from R&D and note that your organization is also affected by this concern.
 
Bryan LeamanBryan Leaman
I have created a case as well.
Ryan MoodyRyan Moody
I have an open case and have received a response from Salesforce. See below:

"The error message pertains to permission given in platform users in relation to the Dashboards. For this case, it is advisable to make sure that the dashboards being shared to users under this profile have the same license type with the running user of the dashboards. "
Tiare SolTiare Sol
I am having this problem, too. I switched back to Classic to change all of the dashboard running users I could find, but my changesets with Platform user profiles added are still failing to validate.
Russell McGibbonRussell McGibbon
Just wanted to update my previous comment as I've changed all the running user on Dashbaords to a Platform user on another dashbaord but did get the error message. So I have one sandbox that I can make changes and another one which I can't but I cannot see any differences. As a quick fix I created a new profile cloning the standard platform user profile and then setup the access on the new profile as per the old one and reassgin the profile to the required users (so replaced the profile). If you export the existing profile permissions using data loader and then amend the ID in the export file to the new profile you can then do an update which sets up the permissions. I have done this and I can confirm no error message appear now when editing the new profile. If I just clone the old Profile to create the new one I still get an error when performing edits. I have no issues in Production. Hope this helps.
Tiare SolTiare Sol
I opened a case about this yesterday and received this response from Salesforce Support:

"This is an ongoing issue that is affecting multiple customers. Our Product team is aware of the issue and are working as quick as possible to resolve the issue. They plan on implementing a fix by the end of this week (Safe Harbor)."

 
Mauricio MurilloMauricio Murillo
Known issue: https://success.salesforce.com/issues_view?id=a1p3A000000BMQIQA4