Skip to main content
Salesforce

Return to Question

better organization
Source Link
krigi
krigi
  • 2.2k
  • 19
  • 29

For simple component work, I prefer to use Lightning Data Service as opposed to @AuraEnabled Apex.

And while I have not seen this documented, it appears that the Lightning Data Service always respects running user's object/field access.

In most cases this is great. In other cases I wish I could toggle this behavior ala "with sharing" keyword in Apex.

Has anyone seen formal documentation that confirms the Lightning Data Service always respects user's object/field access levels and cannot be toggled ala "with sharing" keyword? Is there a way around this?

For simple component work, I prefer to use Lightning Data Service as opposed to @AuraEnabled Apex.

And while I have not seen this documented, it appears that the Lightning Data Service always respects running user's object/field access.

In most cases this is great. In other cases I wish I could toggle this behavior ala "with sharing" keyword in Apex.

Has anyone seen formal documentation that confirms the Lightning Data Service always respects user's object/field access levels and cannot be toggled ala "with sharing" keyword? Is there a way around this?

For simple component work, I prefer to use Lightning Data Service as opposed to @AuraEnabled Apex.

And while I have not seen this documented, it appears that the Lightning Data Service always respects running user's object/field access.

In most cases this is great. In other cases I wish I could toggle this behavior ala "with sharing" keyword in Apex.

Has anyone seen formal documentation that confirms the Lightning Data Service always respects user's object/field access levels and cannot be toggled? Is there a way around this?

Source Link
krigi
krigi
  • 2.2k
  • 19
  • 29

Must Lightning Data Service always respect running user's object/field access?

For simple component work, I prefer to use Lightning Data Service as opposed to @AuraEnabled Apex.

And while I have not seen this documented, it appears that the Lightning Data Service always respects running user's object/field access.

In most cases this is great. In other cases I wish I could toggle this behavior ala "with sharing" keyword in Apex.

Has anyone seen formal documentation that confirms the Lightning Data Service always respects user's object/field access levels and cannot be toggled ala "with sharing" keyword? Is there a way around this?