Apex Code Development You need to sign in to do that
Don't have an account?
ForceCom force:outputfield problem with winter 17 release
Hi All,
I am having a problem from past 2 days with the force:outputfield on lightning component.
<force:outputField aura:id="accountLookupOutput" value="{!v.spoc.CBRE_SPOC_Employee__c}" class="slds-hide"></force:outputField>
When loading the component I see the below error .
"Access Check Failed! ComponentService.getDef():'markup://force:outputLookup' is not visible to 'markup://c:AccountMatrixComponent ".
The locker service have been enabled since the winter 17 release which was few weeks ago. If I remove the force:outputfield , it seems to work fine but the first instance why force:outpufield was added was because of another salesforce bug as explained in below article.
http://salesforce.stackexchange.com/questions/119455/lightning-component-initialization-after-redirect
If I remove force:outputfield , it loads the component with no issues, but cannot remove it because of the issue explained in above article. Any help is appreciated.
Thank You,
Dharani
I am having a problem from past 2 days with the force:outputfield on lightning component.
<force:outputField aura:id="accountLookupOutput" value="{!v.spoc.CBRE_SPOC_Employee__c}" class="slds-hide"></force:outputField>
When loading the component I see the below error .
"Access Check Failed! ComponentService.getDef():'markup://force:outputLookup' is not visible to 'markup://c:AccountMatrixComponent ".
The locker service have been enabled since the winter 17 release which was few weeks ago. If I remove the force:outputfield , it seems to work fine but the first instance why force:outpufield was added was because of another salesforce bug as explained in below article.
http://salesforce.stackexchange.com/questions/119455/lightning-component-initialization-after-redirect
If I remove force:outputfield , it loads the component with no issues, but cannot remove it because of the issue explained in above article. Any help is appreciated.
Thank You,
Dharani
I found it as a known issue, please refer link below.
https://success.salesforce.com/issues_view?id=a1p300000008d7fAAA
Please mark it as solved so that it will make available for others as a proper solution.
Thanks and Regards
Sandhya
Thanks