1
In the code, you have shared. Looks you are using 'querySelector'. querySelector will always return the only first element.
Instead, Add data attribute to each reference of the lookup component.
and query specific elements bypassing the data attribute to the querySelector.
Here is a simple example to refer to.
App.html
<template>
<lightning-...
1
I made a mistake in the code by adding the ContentDocumentLink's Id in the list instead of adding ContentDocumentLink.contentDocumentId.
Fixed code :
public static List<Id> getContentDocumentLinks(Id loanId) {
try {
String baseUrl = URL.getSalesforceBaseUrl().toExternalForm();
List<ContentDocumentLink> ...
1
You're on the right track with event.getParams();. The property that hold the error message you're seeking depends on the location of the error defined in your validation rule.
If the error is to appear on a field, the error messages can be found in event.getParam('output').fieldErrors - an object of field errors.
Example:
const fieldErrors = event.getParam('...
1
onerror is a built-in event of lightning:recordEditForm. So to read the events you must use the event like var err = event.getParam("error");. This returns an object which has
message: General description of error.
detail: Description of error details, if any.
output: Record exception errors with errors and fieldErrors properties. For example, to ...
1
Permission set is exactly for this purpose. You can use combination of custom settings/validation rules, but I think permission set is the simplest and best solution. + this was it easy to change the allowed users easily
1
I have recently encountered the same situation. If anyone is looking out for the solution, here is what you need to do !
let me first reframe the situation here,
"Lightning Component is invoked from Visualforce Page using ltng:outApp. You would want to change data or have control on already created Lightning Component from a button click on Visualforce ...
Only top voted, non community-wiki answers of a minimum length are eligible
