One or our more restrictive profiles that gives read only access on a limited number of fields is getting this error box across Contacts and a custom object. 2 other custom objects seem to be fine. Records do appear in Classic just fine. 1st level of support is stumped (idea was to clone a Standard Profile and make the custom profile again, but that hasn't solved this). Any ideas out there in the Lightning Community?
1 commentaire
OK, just solved this. Here is what I found out. If a Custom Lightning Component references an object, the profile has to have read access on that object to display the lightning page. Is this WAD? Secondly, when I gave read permission to that object, the user is then able to use the Custom Component to modify a record via the Custom Lightning Component despite only have Read access. Is this WAD?
