[SalesForce] Lightning out App error in callback function

I had created a lightning component to upload multiple files with the help of this URL how to create upload multiple file url

which is working fine in action button but when I try to call that component in my VF page having the issue of Lightning out App error in callback function

To use the lightning component in VF page I follow this URL:-
how to call component in VF page

and here is my vf page code:-

<apex:includeLightning />
<div id="fileMultiContainer" />
<script>
    $Lightning.use("c:UploadFileApplication", function() {
      $Lightning.createComponent("c:UploadFile",
          {},
          "fileMultiContainer",
           function(cmp) {
               component.set("v.recordId",'{!order.Id}');
            });
     });
 </script>

Can someone please help me where I did wrong.

Best Answer

Documentation: Usage Considerations

This component is not supported in Lightning Out or standalone apps, and displays as a disabled input. Additionally, if the Don't allow HTML uploads as attachments or document records security setting is enabled for your organization, the file uploader cannot be used to upload files with the following file extensions: .htm, .html, .htt, .htx, .mhtm, .mhtml, .shtm, .shtml, .acgi, .svg. For more information, see Upload and Share Files in Salesforce Help.

In short, below are not allowed:

Don't allow HTML uploads as attachments or document records security setting
Lightning Out or standalone apps - is not supported

You are using lightning out and so will not work

Related Solutions

[SalesForce] uncaught ReferenceError: <> is not defined when using external js in lightning

Interesting - there are a few things going on here I think but let's first focus on the use of onclick= bound to a non aura client side controller - that should plain not work, ever. In aura markup what looks like a simple div is actually syntactic shorthand for something more like:

<aura:html tag="div" HTMLAttributes="{!bagOfAttributes}">

and in LC/Aura all event handlers must be bound to {!c.someHandler} expressions and not plain old JavaScript. If direct binding to a global plain old JavaScript function works I believe it's 100% unintentional and likely to be "fixed"/removed.

Second, this looks like LockerService's expected behavior inherited because all component JavaScript and any external JavaScript you require/import now runs with JavaScript strict mode enabled which cleans up many long standing global scope issues. In helper01.js are you publishing toggleSection() as a global variable? In other words simply declaring a function no longer makes it global - same is true for any variable/object in strict mode. You need to explicitly indicate that you want it added to global scope like so:

window.toggleSection = toggleSection;

You can of course directly assign window.toggleSection = function() { ... };

This is a strict mode standard and is not specific to LS.

Lastly, ltng:require is itself a Lightning component and is designed to be used inside of the component lifecycle - it's dynamically including your CSS and scripts much like RequireJS and other dynamic loaders do with a twist: it's integrated into the init/render flow. It removes most of the issues around dynamic loading (inherently asynchronous) and LC's component lifecycle but to get the benefits you'll need to work inside of the life cycle's constraints.

[SalesForce] Call Lightning component using URL button

First Add lightning:isUrlAddressable interface to the component to which you want to expose it as url and then use below for navigation in calling component

Add lightning:navigation aura:id="navService" in cmp file

({

handleClick: function(cmp, event, helper) {
        var navService = cmp.find("navService");

        var pageReference = {    
             "type": "standard__component",
             "attributes": {
                  "componentName": "c__MyLightningComponent"    
              },    
             "state": {
                "recordId": recordId
             }
       }
        event.preventDefault();
        navService.navigate(pageReference);
    }
})

Best Answer

Related Solutions

[SalesForce] uncaught ReferenceError: <> is not defined when using external js in lightning

[SalesForce] Call Lightning component using URL button

Related Topic