New answers tagged

1

As you are working with divs, that could be achieved with css grid layout. Please find below the best guide I found about it. CSS Grid Guide CSS Grid also gives a very good responsive result, and it is always a good option in terms of layouts. Every div you have will be dropped into a cell of your css grid, but you first must specify the columns and rows ...


0

We were getting the same error and it turned out to be a Licence issue. Lightning Page was accessing Object belonging to a package, which User didn't have licence. You don't get any Client-side or Server-side logs to understand that it's an object access issue. Working well for us now.


0

Bhawna is correct, you cannot call a Lightning Component from a List button directly. In the past, I have implemented something which may be useful in this scenario. Step 1: Create the component you want and make it implement the lightning:isUrlAddressable interface <aura:component implements="flexipage:availableForAllPageTypes,force:appHostable,...


0

Make sure the user have create access to the custom object either through profile or permission set.


0

This is a very interesting use case. A draft for a solution I can think of —not proven though— would be to: Define a Custom Browser Protocol to open AS400 —needs to be done on every terminal you want to use this functionality on Create a custom lighting component —or VF page—that you will link/embed in your Account Detail page. This component/VF will ...


0

You can call a lightning app on click of a Detail Page Button and embed your lightning component in the lightning app. Try using something like below in the Button or Link URL value /c/OpptyProductDuplicateApp.app?recid={!Opportunity.Id} Here recid is the attribute of the lightning app - OpptyProductDuplicateApp , which will hold the record Id. ...


0

You cannot call lightning component from Button or Link. Instead you can create an Action and can be added to "Salesforce Mobile and Lightning Experience Actions" section in the page layout. Also make sure to include force:lightningQuickAction interface to the lightning component


0

Lookup field is a reference field. You can set default value by using AccountId instead of Account.Name. Just change your formula from Opportunity.Account.Name to Opportunity.AccountId


1

This feature will become available in Lightning in Spring '20. From the linked release notes: How: To construct a custom button or link that launches a new record with prepopulated field values, use this sample formula: /lightning/o/Account/new?defaultFieldValues= Name={!URLENCODE(Account.Name)}, OwnerId={!Account.OwnerId}, AccountNumber={!...


Top 50 recent answers are included